Day Shift Documentation
Day Shift is a local CLI that keeps coding-agent plans, scope, validation evidence, and handoff records in your repository.
These records give humans and coding agents a shared continuation point across sessions, tools, and contributors. Instead of reconstructing a plan from chat, tickets, terminal output, and memory, the next contributor can continue from the work agreement and evidence beside the code.
Start with a task
Section titled “Start with a task”Choose the outcome you need; each path stays in this canonical documentation tree:
- Try Day Shift with one Basic task
- Plan a feature with Structured work
- Add Day Shift to an existing repository
- Choose a workflow level
- Review completed agent work
- Resume selected work
- Recover from scope or specification drift
- Look up a command
- Understand the architecture
Choose the smallest useful workflow
Section titled “Choose the smallest useful workflow”Basic is the first workflow to learn: The fastest path for one scoped task. Showing Basic first does not make it the default planning workflow.
Structured is the normal next step: The normal path for planned feature work. Structured is the default for specification-backed planning when no explicit workflow level or parent context overrides it.
Use Getting Started to install and verify the CLI, then use Workflows for an end-to-end path that matches your work.
Preserve evidence without hiding decisions
Section titled “Preserve evidence without hiding decisions”Day Shift records the work agreement and implementation evidence. Review is read-only; acceptance and closure are explicit actions.
Day Shift exposes collaboration policy to compatible agents but does not grant unlimited authority or force unsupported agents to comply.
The current Day Shift CLI can execute a task revision’s complete declared validation set in order with task validation-set, execute one explicitly selected command with task validation-record, or import evidence produced elsewhere. Declared-set execution rejects arbitrary extra argv, records every command independently, and stops on the first required failure.
Together, the work agreement and implementation evidence form a Human-Agent-Contract.
When the work needs staged hierarchy, formal checkpoints, and milestone evidence, use Governed: The staged path for formal review and reconciliation. The detailed artifact and lifecycle model remains available in Concepts and Reference when your task requires it.
Go directly to the detail you need
Section titled “Go directly to the detail you need”- Concepts explains the work agreement, implementation evidence, and operating model.
- Guides provides goal-oriented procedures, including licensing and troubleshooting.
- Workflows provides verified end-to-end working patterns.
- Command reference and the automation schema reference record precise command and machine-consumer contracts.
- Troubleshooting provides diagnostic and recovery procedures.
- Architecture explains the system model, and Decisions preserves durable choices.
- Recovery covers resume, trace, archive, and reviewed release handoff.
- Contributing documentation explains how canonical documentation changes are proposed and checked.
Day Shift organizes and preserves agent-assisted engineering work. It does not replace the coding agent, Git, CI, issue tracking, or code review.
This documentation site owns reusable product guidance. tnsds.tech remains the source for release downloads, purchases, signed-license delivery and recovery, legal terms, and support entitlements.