lurpicUI

LDP — Lurpic Drive Protocol (major 2)

Thu, 29 Oct 2026 19:54:34 +0000

# LDP — Lurpic Drive Protocol (major 2)

LDP is the local automation seam: typed observations and GUI-backed actions between the lurpicUI runtime and external drivers over an authenticated Unix-domain socket. Protocol major 2 is a deliberate hard break: there are no v1 adapters, aliases, or compatibility dispatch. The advertised method set is the registry’s advertised surface — a major-2 build never puts an unported method on the wire. TestDocsMatchRegistry fails when this document and the registry drift.

Principles of the Facet Runtime Model — Core Principles

Sat, 24 Oct 2026 20:54:41 +0000

This is worth doing carefully. Principles aren’t a summary of what we built — they’re the why behind every decision. If you hand someone these principles and the package list, they should be able to reconstruct the architecture independently. If a principle doesn’t constrain decisions, it’s not a principle — it’s a slogan.

LurpicUX Design System

Tue, 23 Jun 2026 17:47:09 +0000

# LurpicUX Design System

Current design-language and authoring notes. This file describes mark intent and visual language; it does not override the runtime principles in LurpicUI-FacetRuntime-Principles.md.

# Overview

LurpicUX is the design language and mark authoring model for LurpicUI.

LurpicUX Marks describes UX intent. LurpicUI executes that intent through the facet projection runtime.

A LurpicUX mark is not merely a visual component. It is an authored projection contract: a reusable declaration of visual anatomy, layout behavior, interaction behavior, state ownership, theme slots, projection output, and environment adaptation.

LurpicUX V2 Foundation

Tue, 23 Jun 2026 17:47:09 +0000

# LurpicUX V2 Foundation

Draft / superseded foundation notes. Keep this as a historical reference for the layer model and authoring context, but do not treat it as the current engine architecture contract.

# Status: Draft — Pre-mark-spec authoring reference

This document establishes the architectural contracts that every V2 mark spec must satisfy. It sits between the Facet Runtime Model principles (the runtime’s why) and the individual mark schemas (the marks’ what). If a mark spec contradicts anything here, the mark spec is wrong.

Search

Mon, 01 Jan 0001 00:00:00 +0000

Type to search the full documentation index. Results are ranked by title and content matches. Without JavaScript, the complete page list is rendered below the search box — use your browser’s find-in-page.