LAUNCHER
Native Kotlin launcher using the HOME role. Stock Android + LineageOS compatible. Read-only bridge to the holdings surface. No root. Pixel 8a is the first test device.
Preserved roadmap copy from 18 October 2026. This is historical planning context, not a statement that the listed platform integrations are released. Check the owning repository before acting.
Implementation homes and handoff · Current game-engine source
From canonical rules to a living, testable game. The public summary shows the ten-stage implementation path; the engineering repository carries the full working document.
PUBLIC SUMMARY: This page is the product-facing layer. The full implementation path remains in the Veiled Dominion Engine repository and is updated there as the build advances.
READ THE FULL IMPLEMENTATION PATHNative Kotlin launcher using the HOME role. Stock Android + LineageOS compatible. Read-only bridge to the holdings surface. No root. Pixel 8a is the first test device.
LineageOS 23.2 / Android 16 baseline. PIXIE SystemUI policy, holdings map, ledger, OS log and Device Steward service become one coherent device layer.
Signed production image, verified boot, rollback protection, signed OTA metadata and documented recovery. A physical-QWERTY PIXIE device can carry the Sidekick design philosophy forward.
PIXIE's target use case is creator stewardship: preserve the original, propose meaningful names and locations, create derived files only with permission, support transcripts and translations, leave a private re-entry note, and record provenance. Mail is a private adapter proving the same consent machinery—not PIXIE's identity.
Bounded ATProto discovery demonstrates read-only observation and explainable surfacing without automatic contact or publication.
The iCloud Mail adapter establishes authenticated private access. It remains read-only until deployment and mailbox tests pass.
Capture → meaningful name → safe working copy → transcript → optional translation → private re-entry note → provenance receipt → release.
Observe → explain → propose → consent → act → receipt → release. Observed facts and PIXIE inference stay separate. Consequential actions require explicit approval and an undo path.
Apple development is planned as a parallel platform, not as a claim that iOS can become a system-wide replacement launcher. The current file-structure conversion is UNDER DEVELOPMENT and should remain marked proposed/unverified until platform tests pass.
Convert the shared PIXIE project/continuity structure into Apple-friendly package boundaries while preserving DID identity, provenance separation, consent policy and market relationships.
Build a Swift/SwiftUI companion surface for holdings, PXCOIN ledger, market map and stewardship previews. Respect the iOS sandbox and permission model.
Extend stewardship to a desktop app/menu-bar workflow where file previews, provenance, reversible actions and local OS logs become first-class interactions.