Development record

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

THE PATH

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.

  1. FOUNDATION — establish the canonical engine boundary.
  2. BOARD — build the 14×14 four-player world.
  3. MOVEMENT — implement canonical piece behavior.
  4. TURN — enforce deterministic game sequencing.
  5. REBIRTH — implement asymmetric systems.
  6. VEIL — implement Radius of Ruin and Veiling.
  7. SANCTUARY — implement Death's protective boundary.
  8. MEMORY — deterministic snapshots and replay.
  9. TRIALS — build canonical scenario tests.
  10. GATE — reach the first developer-ready vertical slice.

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 PATH

PIXIE OS // THREE TIERS

TIER 1 // ANDROID

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.

TIER 2 // PROPOSED

PIXIE ROM

LineageOS 23.2 / Android 16 baseline. PIXIE SystemUI policy, holdings map, ledger, OS log and Device Steward service become one coherent device layer.

TIER 3 // FUTURE

DEDICATED HARDWARE

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.

PRODUCTION STEWARD // NEXT MILESTONE

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.

IMPLEMENTED

PUBLIC DISCOVERY

Bounded ATProto discovery demonstrates read-only observation and explainable surfacing without automatic contact or publication.

IMPLEMENTED / UNVERIFIED

PRIVATE OBSERVATION

The iCloud Mail adapter establishes authenticated private access. It remains read-only until deployment and mailbox tests pass.

NEXT BUILD

ARTIST FILE PROTOCOL

Capture → meaningful name → safe working copy → transcript → optional translation → private re-entry note → provenance receipt → release.

CONSENT LOOP

Observe → explain → propose → consent → act → receipt → release. Observed facts and PIXIE inference stay separate. Consequential actions require explicit approval and an undo path.

01 // INTENT
What are you trying to do?
02 // PROPOSAL
PIXIE describes the action it thinks would satisfy the request.
03 // CONSEQUENCE PREVIEW
Files, permissions, external effects and rollback are made visible.
04 // EXPLICIT CONSENT
No consequential action executes until the user approves it.
05 // EXECUTION + RECEIPT
The action runs and a local rollback receipt records what happened.

APPLE PLATFORM // NEXT STREET

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.

PHASE A

FILE MODEL

Convert the shared PIXIE project/continuity structure into Apple-friendly package boundaries while preserving DID identity, provenance separation, consent policy and market relationships.

PHASE B

iOS / iPadOS

Build a Swift/SwiftUI companion surface for holdings, PXCOIN ledger, market map and stewardship previews. Respect the iOS sandbox and permission model.

PHASE C

macOS

Extend stewardship to a desktop app/menu-bar workflow where file previews, provenance, reversible actions and local OS logs become first-class interactions.

CONVERSION RULE: shared semantics first → platform adapter second → platform-native UI third. Do not flatten Android, Apple and future hardware into one artificial file tree.