Method / p. 07
The work stays visible.
Each stage names the creator’s action, the system’s role, the evidence produced, and what becomes possible next.
Bring the mess
Intake identifies what you already know without forcing invention. Explicit matches can become working artifacts; implied or extrapolated material waits for review.
Consequence: Source material becomes structured evidence without pretending uncertainty is settled.
Reveal the map
A Creator Tech Tree makes dependencies, gaps, unlocks, and legitimate next work visible.
Consequence: You can see Now, Next, Later, and why anything remains blocked.
Bound the assistance
Agents are not authors. You choose whether an assistant analyzes, proposes, drafts under direction, executes a constrained task, or stays out.
Consequence: Tool use becomes a recorded role, not invisible authorship.
Review the artifacts
Working material stays inspectable. Approval is never requested without direct access to the version and consequence at issue.
Consequence: Accepted decisions can update the project map; exploratory work cannot sneak across the boundary.
Earn authority
Project authority and human authorship remain independent, documented states.
Consequence: A useful artifact may remain working, mixed, excluded, or unresolved without being laundered into authorship.
Prove the method
Representative-unit tests expose production cost, continuity risk, and practical constraints before scale.
Consequence: Production expands only after the method survives contact with real work.
Continue the work
Persistent state, receipts, and evidence lineage carry the project across sessions.
Consequence: The next session resumes from governed state instead of reconstructing a chat-shaped memory.
Operating principle / p. 08
The desk describes state, consequence, and next action.
It does not advertise while you work, personify automation, or ask you to trust a mood.