Feedback and follow-up planning

Open Feedback to select a document or create a new one. Feedback lives in project-local Markdown files:

.day-shift/state/feedback/ contains active documents.
.day-shift/state/feedback/archive/ contains archived documents.

There is no feedback database or separate document index. You can add a Markdown file directly to the directory, edit its body in another editor, or remove it. Refresh documents reads the files currently on disk. Files saved by Day Shift include front matter that keeps their identity, associated work, and any retained decision history with the document. Preserve that front matter when editing outside the GUI.

Choose and refine a document

New feedback document starts a Markdown draft with the question Is this basic, structured or governed work? Use the document to explain the change, evidence, desired outcome, and the appropriate work mode:

Basic for one bounded task.
Structured for related tasks that need coordination.
Governed for work that needs formal phases, milestones, or review.

Selecting a document replaces the document list with the full Markdown editor and preview. Use Source, Preview, or Split as on Project Brief. Back to feedback returns to the list. Chat stays alongside the workspace; on a narrow screen, use the Feedback documents and Chat tabs.

Use Save feedback to write the file. Unsaved drafts are retained separately in this browser for each project and document. Switching documents or returning to the list preserves them. If the file changes on disk, saving is blocked until you review the conflict. Copy changes you want to keep before choosing Use current file.

Discuss feedback and create work

Save the document, select Discuss feedback, then Add feedback context to message in chat. Review and send your message. Feedback context is checked again against the saved file before use. The chat context explorer defaults to the whole project and can be narrowed to selected files or recursive folders.

Use Associate specs or tasks to select existing work, then save the feedback document. Alternatively, Create specification previews the exact destinations before Create reviewed specification creates and associates the specification. Refine that specification and choose its planning mode in Specs. Writing a mode in feedback does not create planning artifacts automatically.

Saving feedback, discussing it, and associating existing work do not run an implementation agent, change a task’s lifecycle, or operate production.

Archive and restore

Archive feedback becomes available after a saved document has an associated specification or task. Day Shift checks that at least one associated document still exists before moving the feedback to archive/.

Archiving preserves the Markdown content and its associations. It removes the document from the active list. Select Archive to browse archived documents, and Restore feedback to move one back for editing. Archiving means the intake has linked work; it does not claim that implementation or verification is complete.

Use Delete beside an item in either the active list or Archive, or Delete feedback while its document is open. Review the document name and choose Delete permanently. Deletion removes the Markdown file, its retained feedback history, and its unsaved draft in this browser. Associated specifications and tasks remain. Cancelling preserves the document and draft; if the file changed on disk, refresh and review it before deleting. Unsaved new documents can also be deleted without creating a file.

You can also remove files directly when you no longer need them.

Import earlier feedback

If this project has the earlier SQLite feedback store, the page offers Import existing feedback. Import preserves report identities, content, and retained triage and verification history in Markdown files. Previously retired content stays unavailable in the archive.

The import uses a checked filesystem transaction. It replaces the old feedback database only after the document writes commit, records the migration, and rejects conflicting destinations. New projects never create a feedback database. If import fails, preserve the existing files and inspect the reported conflict before retrying.

Runtime integration

The authenticated endpoint remains POST /api/v1/feedback. Document operations include save-document, read, list, archive, restore, and delete-document; saves, moves, and deletions check the current file revision. storage-status reports whether legacy import is available, and import-legacy explicitly performs it. Existing triage, verification, and follow-up adapters retain their separate evidence and authority checks, with their history now stored in the Markdown document.