Release gate
qualified; public launch allowed.
Outcome first, planning when you need it
Use the result first. Then replay the workflow that fits the work.
Play the maintained result, then replay a qualified Basic task from its complete request through review, accepted disposition, closeout, and continuation. Switch to Structured to inspect a specification-backed feature plan, numbered direct tasks, project review evidence, and separate project closeout.
Qualified repository evidence
Both public replays are bound to qualified repository evidence.
Basic remains the first and default evaluation. Structured is available as the normal specification-backed path for planned feature work, with its review and closeout writes shown separately.
Workflow shape
Basic starts with one task pair. Structured adds one canonical specification, one numbered overview, and numbered direct tasks.
Planning boundary
Basic needs no planning parent. Structured references the specification under .day-shift/specs/ instead of relocating or copying it.
The implemented outcome comes first
Play the finished Tic-Tac-Toe game.
This maintained public result is immediately usable. The qualified Basic replay below then shows the smaller lifecycle an evaluator can use for one scoped task.
Round status
Your turn — you are X.
- X You
- 0
- Draws
- 0
- O CPU
- 0
Choose the evidence replay
Start small with Basic, inspect planned feature work with Structured, or stage delivery with Governed.
Basic covers one scoped task, Structured coordinates specification-backed direct tasks, and Governed adds staged hierarchy and reconciliation. Each numbered replay stage represents one operator prompt and expands the work it coordinates.
Qualified Basic lifecycle replay
One scoped task, from request to explicit closeout.
5 prompt stages coordinate 15 captured lifecycle actions for one parentless task pair with no planning hierarchy.
Planning tree explorer1 / 5
Operator prompt
Workflow: .day-shift/workflows/basic-workflow-guide.md Orient to the repository contract, initialize Day Shift when needed, and stop before creating task evidence.
.day-shift/new
planning/new
basic/new
tasks/new
specs/new
workflows/new
config.tomlnew
Current stage
Orient and initialize the workspace
Anchor: Initialize the local workspace
Work included in this prompt
- - Load the repository workflow contract
- - Initialize the local Day Shift workspace
- Accomplished
- The repository is ready to hold one independent Basic task pair.
- Executor
- Day Shift orientation and command surfaces
- Posture
- Read-only orientation followed by an explicit workspace write
Workspace setup establishes the evidence location; it does not create or authorize implementation work.
Inspect Basic fixture context
Replay scope
5 prompt stages coordinate 15 captured lifecycle actions for one task.
Numbered root
.day-shift/planning/basic/tasks/01-basic-evaluation
Only task pair
Task definition + implementation summary, both order 01. No Basic-specific index.
Planning parent
None. No specification, work overview, slice, phase, milestone, or reconciliation is required.
Validation and executor boundary
Declared does not mean automatically executed.
Day Shift can execute and record one explicitly selected declared command, or verify imported evidence produced elsewhere. It does not run every declared command automatically and does not execute arbitrary undeclared commands.
declared command list
Executor: none until explicitly selected
Task declarations preserve required validation commands but do not execute all declared commands automatically.
Automatic execution: no
selected command owned execution
Executor: Day Shift child process
The operator invokes task validation-record with exact argv after --; Day Shift executes that one selected command and records the observed result.
Automatic execution: no
imported external evidence
Executor: CI or another external system
The operator supplies --source imported, --source-reference, and a schemaVersion 1 verified-result --output-reference; Day Shift verifies and records rather than executes the imported command.
Automatic execution: no
In this captured scenario, fixture capture adapter implemented the fixture and Day Shift command-owned child process executed one explicitly selected declared validation check, which exited 0.
Second-session continuation
Resume from repository evidence, not the old chat.
The captured run restored a fresh current selection, resumed the Basic continuation as terminal, and derived none with reason terminal_state.
Prompt: "Show the current selected work in this repository."
Prompt: "Create a resume session for .day-shift/planning/basic/tasks/01-basic-evaluation/task-definition.md."
Prompt: "Resume that session and restore continuation context."
Prompt: "From .day-shift/planning/basic/tasks/01-basic-evaluation/task-definition.md, derive the next action from current repository evidence."Recovery stays explicit
An incomplete validation attempt remains discoverable. Review, disposition, closeout, and retry are separate boundaries instead of inferred mutations.
A second Basic task is not assumed
The fixture blocked an unrelated second task until the operator confirmed independence, and supplied promotion guidance when coordination would make Structured the safer choice.
Choose the fitting workflow
Basic is fastest for one scoped task. Structured is normal for planned feature work.
Choose Structured when work is specification-backed, coordinated across multiple tasks, or needs a shared plan. Use Governed when staged hierarchy and formal reconciliation are part of the delivery contract.
The replays are frozen from apps/website/content/basic-evaluation-evidence.json and apps/website/content/structured-evaluation-evidence.json, captured from the current repository-built CLI. The playable Tic-Tac-Toe result remains a separate maintained public fixture.