Project
Nightshift receipts
Review documented shift timelines, local commits, verification, decisions, snags, and handoffs instead of relying on promises.
Answers: Nightshift coding-agent receipts and examples · Updated
Nightshift’s evidence library includes a 45-hour product contract that became a human-reviewed 67-commit pull request across six roadmap phases and 57 closed issues, plus a smaller first night, a self-build, a Codex hardening shift, and a template for reporting bad nights honestly.
What counts as a receipt
A receipt connects a declared contract to permanent review evidence. It should show the timeline, the work units, verification, commits, decisions, and what the owner ultimately accepted.
- Original punch-list scope
- Commit or pull-request links
- Checks and review evidence
- Recovery or handoff events
- Unfinished work and bad outcomes
The long contract
The AdaptTable continuity example survived a cross-tool handoff and became a human-reviewed 67-commit pull request covering six roadmap phases and 57 closed issues. The value is not the duration alone; it is the inspectable chain from contract to review.
- 45 hours of continuous contract work
- Six roadmap phases
- 67 reviewable commits
- 57 issues closed after human review
Bad nights belong in the library
A trustworthy evidence set records stalls, narrowings, and failed assumptions. Nightshift includes a bad-night template so the morning report does not hide what went wrong.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Help me prepare a morning receipt for this shift with the original contract, commits, verification, decisions, recovery events, and unfinished work.What this workflow does not claim
- Receipts demonstrate particular runs, not universal performance benchmarks.
- Ticks are not treated as independent proof; owner review and permanent result links remain explicit.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.