The live xframes.dev website is maintained in a separate repository. This directory also contains legacy Jekyll and generated demo assets; the documents indexed below are repository-level engineering and strategy records.
- XFrames and GPUIX: Technical and Strategic Assessment — dated comparison, architectural corrections, dependency and adoption risks, strategic focus, and continuation gates.
- React Native Fabric Embedding — implemented React Native 0.87 snapshot generation, host contract, workspace rules, upgrade procedure, Node/Wasm verification, and known gaps.
- Fabric-Compatible Runtime Hardening — atomic Fabric commits, explicit destruction, lifecycle tests, recording/replay, invalidation-driven rendering, performance instrumentation, and automation.
- ubx-monitor UI Update Pacing and Streaming Measurements — completed bounded slice: persisted display rates, source-owned histories, production/lifetime gates and final reproduction.
- ubx-monitor Paired Pacing Costs — all three quiet-window pairs, exact retention, publication/CPU reductions and the measured freshness tradeoff; broader framework targets remain open.
- ubx-monitor Ordinary Application Qualification — completed bounded Windows slice: current-package full-App integration, sustained synthetic telemetry across Plot/Table/Map/Canvas, connection lifecycle, cleanup and reproducible setup.
- Stage 4: Invalidation Scheduling — delivered scheduler MVP, producer and lifetime boundaries, local validation, measurements, completed hosted CI stabilization and deferred qualification.
- Stage 3: Atomic Fabric Publication — schema-v2 publication, committed ownership, visibility guarantees and historical acceptance evidence.
- Diagnostics and Reproduction Guide — current fixture commands, platform prerequisites and measurement contracts.
- Canvas Widget Design — canvas purpose, data flow, draw commands, performance model, and integration patterns.
- Project Roadmap — current delivery phases and runtime-hardening milestones.
- Strategy assessments are dated snapshots. Update them with a new dated document when the competitive or dependency landscape materially changes.
- Architecture documents describe proposed or accepted runtime behavior. Keep status and update dates at the top.
- The roadmap tracks delivery status and links to detailed documents instead of duplicating their design content.
- Public product documentation belongs in the separate xframes.dev source repository.