STAGE Architecture Decisions
Current Method-Shape Decision
ADR 0050 separates a small universal safety kernel from optional interoperability contracts and practitioner guidance. It supersedes any earlier implication that STAGE's recommended architecture, full delivery prose, or optional artifacts are universal conformance requirements. Earlier ADRs remain evidence and guidance unless an adopted optional contract depends on them.
Current Authority Decision
ADR 0051 evaluates authority at the proposed operation. Unresolved provenance constrains nearby work without erasing separate narrow authority, and narrow authority never widens into adjacent mutation, replacement, or regeneration.
Current Player-Experience Decision
ADR 0053 requires human-led intent formation before substantial implementation and bounds automated, owner, and representative-player claims. It complements ADR 0052, which requires a thin complete loop and direct human play before a new or materially changed player-facing premise expands. Mechanical success cannot grant product acceptance. ADR 0054 adds a concrete systems-heavy reasoning loop while rejecting a universal fun formula or score.
Current Mapping Decision
ADR 0039 keeps project maps as durable orientation surfaces. Exact run coordinates live in one canonical verification history or an explicitly revision-bound audit or release record rather than being copied across maps.
Current Visual Decision
ADR 0048 is the current routing decision: visual implementation, diagnosis, audits, and polish use the ordinary delivery workflow. ADR 0041 still supplies its scoping rule for outcome-free standing-coverage requests. ADR 0040 remains the current ownership decision for visual capture and export artifacts: retain them only for a concrete decision or operation. ADR 0038 keeps persistent visual UI in the ordinary project backlog when its own player, author, or developer job justifies it. ADR 0025 retires the detached evidence-package path. Earlier visual ADRs remain below as decision history, not alternative recipes.
Current Workflow-Control Decision
ADR 0049 bounds valid positive inspection by decision-bearing uncertainty without imposing a fixed action budget. ADR 0044 requires route rejection to be classified before detailed orientation and makes accepted fragments preservation constraints rather than replacement scope. ADR 0043 makes explicit human rejection of a route's utility terminal for that route. ADR 0042 makes mechanical and authority stop conditions actual control flow: the blocked branch terminates instead of continuing after a warning under a narrower label. ADR 0047 and ADR 0046 keep always-visible routing metadata separate from the policy loaded with a selected skill.
Current Solo Attention Decision
ADR 0055 adds the optional Stage Director's Flow around ordinary delivery. It keeps raw Cues, human gameplay Dialogue, Ready work, active delivery, Rehearsal, the Director's Call, and source-control Checkpoints distinct without requiring a tracker, sprint cadence, story points, or machine-readable work-item schema.
Current Quality-Gate Decision
ADR 0056 separates Source, Model, Engine, Consumer, Distribution, and Director gates. Checks are selected by claim and production boundary; automated green status cannot grant product acceptance, and agents cannot weaken quality policy to obtain a pass.
Current Change-Integration And Release-Identity Decision
ADR 0057 recommends short-lived work-item branches, isolated worktrees, bounded agent concurrency, explicit Unity asset ownership, and serial integration. Product release version, exact build identity, and data contract versions remain separate, while release approval and publication stay human-owned. ADR 0063 specializes that guidance for this repository by requiring Conventional Commits. ADR 0064 consumes that metadata only to prepare a human-completed draft release PR; tags, GitHub Releases, package refresh, and publication remain explicit maintainer actions.
Current Task-Continuity Decision
ADR 0058 treats conversation history as disposable working context. Durable project knowledge lives in a short Project Context Spine, unfinished work crosses task boundaries through revision-bound handoffs, and a fresh-task Orientation Check must reconcile current source before mutation.
Current Agent-Workflow Decision
ADR 0059 keeps ordinary change delivery implicit while adding explicit read-only orientation and check-only verification routes. Project mapping remains a separate explicit workflow, and all three companion routes stop before unauthorized mutation.
Current Documentation-Surface Decision
ADR 0060 keeps one canonical repository source chain while providing compact agent procedures and a derived Docusaurus reading interface for humans. External trackers and knowledge bases remain optional noncanonical attention views.
Current Documentation-Publication Decision
ADR 0062 keeps the quality-gated public mirror established by ADR 0061 and serves it through Cloudflare Pages. The hosting integration sees only the screened generated repository; canonical private source remains disconnected and authoritative.
- 0001: Project-native architecture is authoritative
- 0002: Project maps are proportional profiles
- 0003: Evidence has coordinates
- 0004: Ownership and rehearsal fail closed
- 0005: Schemas are versioned and backward-compatible
- 0006: Add a personal Solo Unity profile
- 0007: Resolve competing gate evidence explicitly
- 0008: Keep visual acceptance human-authoritative (human-authority principle retained; detached machinery superseded by 0025)
- 0009: Make the engine-native Visual Almanac primary (historical; superseded by 0027)
- 0010: Declare native visual review capability without mirroring content
- 0011: Separate native control, state provenance, and visual observation
- 0012: Separate visual subjects, review scenarios, and staging (historical terminology)
- 0013: Distinguish state sequences from continuous motion
- 0014: Prefer runtime-native Almanac hosts (historical; superseded by 0027)
- 0015: Require fresh-launch parity
- 0016: Separate release version, owner readiness, and transferability evidence
- 0017: Separate native visual review surfaces (historical taxonomy)
- 0018: Escalate visual review by recurring need (ladder superseded by 0027)
- 0019: Require earned infrastructure
- 0020: Make change delivery the primary agent workflow
- 0021: Require consumer-complete review
- 0022: Require consumer-complete verification
- 0023: Separate the Practitioner Kernel and Maintainer Laboratory
- 0024: Prefer product-native Visual Almanacs (superseded by 0027)
- 0025: Retire the detached visual evidence pipeline
- 0026: Retire the redundant visual capability manifest
- 0027: Demote the Visual Almanac to an optional product recipe (superseded by 0038)
- 0028: Retire the Solo Unity attestation pipeline
- 0029: Retire the Solo Unity slice charter
- 0030: Retire normalized Unity test receipts
- 0031: Close owner-source transfer at the staged checkpoint
- 0032: Make the artifact-free Practitioner Kernel normative
- 0033: Separate reachability, affordance, and acceptance
- 0034: Replace adoption levels with need-triggered capabilities
- 0035: Retire unconsumed method-level visual taxonomy
- 0036: Make optional companion skills explicit-only (visual-skill portion superseded by 0048)
- 0037: Package the Practitioner Kernel separately
- 0038: Treat visual galleries as ordinary project features (dedicated-skill portion superseded by 0048)
- 0039: Keep project maps out of the verification ledger
- 0040: Require decision-bearing artifact consumers
- 0041: Bound visual questions before inventory (routing folded into 0048)
- 0042: Make stop conditions terminal
- 0043: Make route utility rejection terminal
- 0044: Reject before orientation and preserve without inferring
- 0045: Inspect agent traces without making them release gates
- 0046: Keep skill launcher prompts concise
- 0047: Keep skill routing metadata concise
- 0048: Fold visual diagnosis into change delivery
- 0049: Stop inspection at decision sufficiency
- 0050: Separate the safety kernel, optional contracts, and guidance
- 0051: Evaluate authority at the proposed operation
- 0052: Gate player-facing expansion on human play
- 0053: Keep gameplay design human-led and experience claims bounded
- 0054: Use player-system hypotheses, not fun scores
- 0055: Use an optional Director's Flow for solo attention
- 0056: Layer quality gates without automating product acceptance
- 0057: Use small-batch agent branches and separate release identities
- 0058: Use context spines and revision-bound task handoffs
- 0059: Add explicit orientation and verification workflows
- 0060: Derive human documentation from canonical sources
- 0061: Publish derived human documentation after quality (serving provider superseded by 0062)
- 0062: Serve the public documentation mirror through Cloudflare Pages
- 0063: Enforce Conventional Commits in the STAGE repository
- 0064: Automate draft release proposals without releasing