Drishti
Frontend is orchestration. Creators express experiences; the framework owns the coordination that makes them coherent.
Version 0.0.1 published the documentation-only design package. Version 0.1.0 published the first realized presentation layer. Version 0.2.0 folds in the Canvas mechanisms below. The presentation layer is the Logical Works ink lab (src/ink_lab.rs), its brand tokens (src/design.rs), the GPU residency model (src/runtime.rs), and a native GPU host (src/native.rs, feature ui) that presents ink frames in a GPUI window. GPUI arrives through the estate storefront (lgwks_deps/gpui). A browser host, the goo filter (GPUI 0.2 has no blur or threshold pass), and a qualified Keel integration are still absent.
The crate also holds the Logic OS Canvas mechanisms. They come from kernel#850 row 15, on the Director's order of 2026-11-03 to deprecate the kernel by absorption (D17 in docs/decisions.md). The crate holds the canvas protocol vocabulary and workspace validation, the deterministic motion core, and the bounded native scene and reducer. It also holds the headless trace host with its checker. The native-host contract covers the signal broker, session and governance stores, telemetry, command bar and attestation evidence. Each part has its falsifying tests. These are tested Rust, not qualified product claims: no GPU backend, browser host, or product journey is asserted passed by them. The native-host broker scopes every inspector read to the caller's session and tenant, gates the command bar and cross-tenant reads on an injected grant store, bounds its registries, and reports every decision to a required audit sink (D18).
cargo run --release --features ui --example ink_lab # open the ink lab
cargo run --release --features ui --example ink_lab -- --frames 600 --json # measured session
Drishti is a Rust-first frontend framework design grounded in immersive, context-preserving interaction: documents recall where work stopped, workflows become inspectable routes, and people compose automation from meaningful operations rather than callback plumbing. Ordinary forms and conventional applications remain first-class; immersion is not compulsory animation or a mandatory 3D world.
The default presentation language is the Director's Logical Works brand — flat build, liquid motion: semantic tokens that name roles, nine flat colourways, and eleven ink effects that always settle on the crisp static mark. The brand is not a skin over the framework; its "everything resolves" rule is the same requirement as reduced-motion equivalence and accessible navigation, so the ink lab is part of the correctness surface.
The vision is primary. Universality, ergonomics, security, efficiency, accessibility, portability, and evidence are constraints and comparison axes—not competing product identities. Merely replacing JavaScript syntax, using a GPU, or adding another graph is not the value proposition.
Read in order
VISION.md: product identity, authoring promise, universality, and reference experience.docs/architecture.md: ownership, orchestration, effects, presentation, and limits.docs/codebase.md: the realized seats, the planned module structure and responsibility boundaries.docs/decisions.md: finalized product contract, all 40 answers and conflict-resolution provenance, source conflicts, and blocking proof obligations.docs/research.md: scripting, prior art, and what evidence changed the design.docs/assurance.md: strict acceptance and eventual Keel integration.docs/inklab.md: the Logical Works brand as the presentation layer — tokens, the eleven ink effects, and the adaptive engine.docs/gpu-runtime.md: the GPU residency model — demand scheduling, budgets, reuse, transfer accounting, and device epochs.contract/requirements.tsvandexperience/journeys.tsv: normative requirements and falsification cases.docs/status.md: what exists, what was checked, and what remains unproved.
The same narrative documents are embedded in the crate's Rustdoc modules so they remain readable without access to the GitHub repository. The TSV contracts are also embedded in Rustdoc and included in the Cargo package.
Foundation decisions
- GPUI is the selected presentation foundation, not code to rebuild because of a GPL misconception. Its framework license is Apache-2.0.
- logicalworks-crates first:
std, thenlgwks_std,lgwks_bot, and optional third-party features owned bylgwks_deps;lgwks_astremains the estate parser surface. - One authoritative application-state owner: supplied by the application host; in the Logicalworks constellation, LOK owns durable state and effect authority. Drishti owns derived presentation and bounded execution bookkeeping, not a competing OS.
- No mandatory AI, browser, scripting VM, or per-pane sandbox in the trusted-native baseline. Isolation remains mandatory for any profile claiming to run hostile code.
- Rust-first authoring; JS/Wasm glue and hybrid HTML/GPU presentation are permitted. Useful HTML/forms before Wasm, coherent visible islands and broad desktop/mobile compatibility are requirements, not implemented capabilities. This supersedes the initial strict-no-JS restriction. Native proof cannot stand in for browser proof.
- Experience-as-Code contributes contract and evidence discipline, not an adopted runtime or a claim that its current browser provider is suitable.
- The Logical Works brand is the default presentation language. Its tokens and ink effects are first-party reference code; a GPU backend is admitted through
lgwks_deps, never imported directly. The brand's "everything resolves to the crisp state" rule is enforced as reduced-motion equivalence, not decoration.
This package
Apache-2.0, a member of the logicalworks-crates workspace since ADR 0006 R6, which merged this repository with its history. The library depends on the estate crates lgwks_std (JSON, ids, randomness, trace events), lgwks_ast and lgwks_macros (the typed-error derive). Every third-party crate arrives through the lgwks_deps storefront: SQLite (sqlite), P-256 signatures (p256) and float maths (libm) are always on, GPUI is the optional ui feature and the desktop preview window (winit, softbuffer, cosmic-text) is the optional desktop feature. The default cli feature builds the drishti command, which orchestrates through lgwks_bot's script!. Five more binaries are diagnostics: canvas_preview, trace_check, and the three api_drive_* conformance drivers; the desktop window is the only executable with a display path. There is no build script, telemetry or network client. This is an active project's design publication plus its presentation seats and Canvas mechanisms, not a usable UI framework yet.
drishti tokens the brand: primitives, both themes' roles with WCAG grades, colourways, CSS
drishti ink --seed 7 --frames 90 every effect on its own seeded engine: replay digest, shape bounds, label
drishti present --frames 120 a residency session through drain, loss and recovery, timed per frame
drishti limits every bound the engine and the runtime declare
drishti docs [PAGE] the design publication, one page at a time
drishti lab the native window (feature `ui`)
Each prints one JSON document; a refusal is one JSON line on stderr with a failing status. tests/cli.rs drives the built binary.
Verification, from the workspace root:
cargo clippy -p drishti --all-targets --locked -- -D warnings
cargo clippy -p drishti --all-targets --features ui --locked -- -D warnings
cargo clippy -p drishti --all-targets --features desktop --locked -- -D warnings
cargo nextest run -p drishti --locked
cargo nextest run -p drishti --features desktop --locked
These commands do not discharge runtime, security, experience, performance, or Keel obligations; G01–G15 in docs/decisions.md stay blocked. There is deliberately no empty runtime scaffold or green placeholder lane.
Finalized requirements amendment
The 2026-09-12 contract amendment in docs/contract.md captures the Director's answers and subsequent corrections, including phone workflow parity, structural recovery instead of prompt friction, first-party trust at the chosen layer, and reuse of LOK/Braid authority contracts. Engineering derivations and open proof obligations are labeled separately. The working-tree amendment is not a republication of the immutable 0.0.1 release and does not authorize runtime implementation; D15 and D16 later authorized the presentation seats, and D17 to D19 the Canvas mechanisms.
Publisher
Logical Works Incorporated publishes drishti as one of six independently versioned crates in logicalworks-crates: lgwks_std, lgwks_bot, lgwks_ast, lgwks_macros, lgwks_deps and drishti.
Should I use logicalworks-crates? says when to reach for each one and when to skip it.