OBSERVA // MOMENTO // ADSERVOOpening the VITA development record
Why VITA's public tracker separates plans, implementation, runtime proof, and release confidence instead of collapsing them into one progress number.
Why make the work visible?
VITA is a systems-heavy game. A feature can exist in code without being connected to the right scene, proven in the running game, or safe enough to count toward a release. A single percentage hides those differences precisely when they matter most.
The public tracker keeps those states separate. It shows what is planned, what has been implemented, what has runtime evidence, what is blocked, and what has earned release confidence.
A readable layer above the telemetry
The tracker begins with three ordinary questions: what is being built now, what recently worked, and what is holding progress up. Deeper system targets and QA evidence remain available for anyone who wants the production detail.
Public blocker language is intentionally useful without exposing private paths or internal notes. A target can need a runtime test, art, integration, or a design revision—and the distinction changes what happens next.
What changes from here
Each manual Unity publish updates the tracker snapshot and its chronological worklog. Those publishes can now seed private article drafts, but a draft only becomes a Field Note after it receives deliberate, player-facing context.
That separation lets the telemetry remain automatic while the development story remains human.