Day Shift concepts

Day Shift is a local workflow layer around coding agents. It does not replace an IDE, coding model, project tracker, or hosted collaboration system. It makes the agreement between human intent and agent execution durable inside the repository.

Human-Agent-Contract

A Human-Agent-Contract states what is being built, where changes belong, what evidence proves success, what changed, and what remains unresolved. Keeping that contract in repository artifacts makes work inspectable across sessions, models, contributors, and reviewers.

Artifact lifecycle

Work moves from a specification through slices, phases, milestones, and implementation-sized tasks. Readiness review checks the contract before code changes begin. Each completed task records changed paths, validation results, acceptance results, deviations, and follow-up work. Milestone reconciliation then rolls task evidence into a review checkpoint.

Deterministic checks and model judgment

The CLI handles repeatable structure, traceability, metadata, and validation checks. Agents and reviewers retain judgment for ambiguous intent, architecture, risk, conflicting evidence, and acceptance decisions. Read-only review and validation remain separate from explicit write commands.

Local-first operation

Planning and implementation evidence stays in repository-visible files. Normal installed CLI operation and signed-license verification are local-first and offline-capable; the website remains responsible for downloads, purchases, delivery, recovery, and public entry points.

Start with Getting Started or explore the workflow guides.

For the complete hierarchy, planning lanes, artifact responsibilities, evidence gates, and role boundaries, read Operating model and artifact lifecycle.