Idea-to-delivery coordination
Day Shift coordinates planning and evidence around work performed by people and their chosen tools. Start in the selected project, refine the idea, create the appropriate planning structure, hand authorized work to an external implementation agent, review its return and record externally performed delivery. Later feedback connects the result to the next explicit planning decision.
Refine the idea in one project conversation
Section titled “Refine the idea in one project conversation”Use Project Brief for the project-wide idea and Specs for a focused specification. Ask requests an answer; Update prepares a document edit for review. The draft is separate from the saved artifact until you apply it. Review target identity, scope, disclosure and the proposed change. Keep unknown requirements visible rather than claiming readiness from fluent prose.
The project conversation persists as you navigate supported planning and evidence workspaces. Prepared feedback and delivery context appends to your current message after current identity checks. Preparing context does not send a message. Project switching changes the session and authority; another project’s identity or credential cannot authorize this project.
See project chat and planning updates for scope, current revisions, draft preservation and document recovery.
Choose and review the planning structure
Section titled “Choose and review the planning structure”Review the specification before creating its next layer. Review plan previews exact destinations and declarations. Creation is a separate confirmation. A created artifact is a draft requiring refinement; its existence is not implementation readiness.
| Structure | Canonical shape | Use |
|---|---|---|
| Basic | One task and implementation summary | A bounded independent task. |
| Structured | One work overview and ordered direct tasks | Shared feature scope with explicit task dependencies. |
| Governed | Slice, phases, milestones and tasks | Work that needs the additional staged review boundaries. |
Keep Structured tasks directly under their overview. Create only declared tasks, validate local links, then assess readiness. Readiness authorization, attempt opening and a baseline precede implementation writes when the task requires runtime attribution. A read-only review or a suggested next action is evidence, not permission for a later mutation.
Hand implementation to your chosen agent
Section titled “Hand implementation to your chosen agent”In the task view, enable Show external agent workflow and choose Prepare implementation handoff. Review or export the revision-bound brief for any agent you operate. Opening the task in an editor does not grant source-write or command authority to Day Shift.
The external agent changes source outside the product. Return to Refresh returned work to compare observed changes with the task’s declared scope and baseline. Out-of-scope changes, unknown attribution and stale evidence remain visible. Use the correction brief when implementation is incomplete or a check fails; do not convert reported external progress into completed status.
Validate and close only from current evidence
Section titled “Validate and close only from current evidence”A declared validation command can run through the bounded validation workflow after its explicit preview and confirmation. This authority covers that exact command, not general source implementation or delivery. Imported reports stay imported and do not become command-executed evidence. A failed check remains in history; a supported explicit retry or refresh supplies a replacement tied to current inputs.
Complete the implementation summary with actual changed paths and acceptance results. Summary review, accepted disposition and task closure are separate current-evidence gates. Reuse closed accepted predecessors with focused impact checks; historical validation drift alone does not authorize reopening them. When formal repair is necessary, use the supported bounded recovery flow and preserve earlier attempts.
Work-level review and closure are additional explicit steps. Finishing every direct task does not itself write a project review or close the work overview. See external-agent handoff and return for the detailed return workflow.
Coordinate delivery with external operators
Section titled “Coordinate delivery with external operators”Open Delivery, select a planning directory and compile its implementation summaries and reconciliations into an Executive Handoff and Technical Handoff. Edit and preview the Markdown, save it under .day-shift/state/delivery/, then copy it into your pull request, merge request or documentation. Document captured external flows in the handoff; use External delivery records for detailed revision and environment evidence. A locally accepted task does not prove CI success, deployment readiness or production health. Instructions remain instructions until an external operator acts and returns evidence.
The operator performs Git delivery, publication, deployment, promotion, migrations, production verification and rollback in external tools. Day Shift does not execute those steps. Record unknown, failed, partial or successful observations honestly. Keep reported, evidence-supplied and authenticated external evidence distinct; an authenticated failure remains a failure.
See delivery guidance and evidence for trust configuration, exact revision checks and evidence retention.
Close the feedback loop
Section titled “Close the feedback loop”Open Feedback to capture a Markdown document and decide whether the follow-up is Basic, Structured or Governed work. Select the document to edit and preview it alongside chat. Save it, then associate existing specs or tasks or review the creation of a new specification.
Once the document has associated work, archive it to keep active feedback focused. The archive preserves its content and links and supports restoration. Archiving does not claim that a fix is implemented, delivered or verified. See feedback and follow-up planning for storage, import and recovery details.
Recover without guessing what committed
Section titled “Recover without guessing what committed”A disconnected browser may have missed a successful response. Preserve the pending operation identity and use its supported receipt recovery. Refetch current state after event gaps; do not replay writes merely because the display was stale. Review version conflicts before reconciling a draft. Preserve immutable receipts, original attempts and transaction recovery evidence.
Local storage is bounded and separate from canonical records. A storage warning means a draft may exist only in the current tab. Copy or save important text before closing it. Keep credentials out of drafts and support material. For a project change, re-establish the correct project session and inspect that project’s current evidence.
What certification establishes
Section titled “What certification establishes”The certification fixtures use real built and extracted installed runtime adapters, Chromium workflows, authenticated local HTTP, controlled external source changes and external signing keys. They exercise intake and traceability, explicit planning, failed and corrected returned source, delivery guidance, verification, recurrence, receipt recovery, page/event gaps and project isolation. Fixture source edits and signed observations are test inputs supplied outside product routes.
These checks establish the tested coordination and authority boundaries. They do not establish the safety of a real deployment, the truth of an arbitrary imported report or the correctness of an application beyond its tested criteria. Evaluate those claims with the relevant external tools and responsible reviewers.