Skip to main content

0006: Add A Personal Solo Unity Profile

Status: Accepted after STAGE 0.3

Release-version and evidence-maturity language in this decision is superseded by ADR 0016. The Solo Unity profile decision remains accepted. Its later profile-specific assessment, attestation, and milestone machinery is retired by ADR 0028.

Context​

STAGE 0.3 deliberately leaves later general maturity gates blocked on independent adoption and longitudinal evidence. The method's actual owner is a solo Unity game developer who primarily wants a durable personal workflow for human-directed agent development. Waiting for unrelated maintainers would not improve that personal workflow.

The Circussy One also provides evidence for a useful but non-universal Unity tool stack: Unity MCP, Odin, UniTask, PrimeTween, VContainer, Feel, Nice Vibrations, Animancer, Shapes, Wwise, AllIn13DShader, and personal editor tools. Copying every dependency into every project would reproduce the overreach that STAGE's proportionality rule is meant to prevent.

Decision​

  • Keep STAGE's normative core engine-neutral and its public maturity claims unchanged.
  • Add a non-normative Solo Unity profile optimized for the owner's recurring workflow.
  • Model the known tool stack as opt-in capability bundles with exact sources, authority, readiness, verification, upgrade, and removal information.
  • Keep paid asset files outside the STAGE repository; record their contracts and private installation sources without redistributing them.
  • Let the personal profile use separate maturity milestones based on repeated personal projects, while clearly distinguishing those milestones from general STAGE evidence.
  • Use fresh Unity projects to dogfood the profile. Feed back only failures and patterns demonstrated by real work.

Consequences​

  • STAGE can become immediately useful to its owner without manufacturing external-adoption evidence.
  • New Unity projects can remain small and avoid Circussy's systems-heavy stack until their coordination risk justifies it.
  • The repository must maintain profile-specific data and validation without allowing it to become a second normative specification.
  • Personal 1.0 and general STAGE 1.0 become separate claims.

Evidence Update​

Lanternworks is the first fresh systems-heavy project built through this profile. At its recorded authored-scene checkpoint, deterministic EditMode, composed PlayMode, and structural visual evidence pass. The trial also exposed seven assumption families that package bootstrap alone could not reveal: UI activation timing, scene-operation asset-handle lifetime, active render-pipeline shader selection, local/world coordinate ambiguity, runtime visual resource ownership, queued virtual-input publication, and scene-load clock contamination. Its deterministic Gamepad rehearsal proves mechanical completion of First Light through the composed input path without promoting that result into human interaction acceptance.

This strengthens the personal workflow without changing general STAGE maturity. The same director and primary agent performed the work, and no human has yet accepted the complete Lanternworks economy loop. See the structured trial.

Last updated on