Completion Log
A permanent audit trail of every prompt that has shipped, stored as `COMPLETION_LOG.md` at each project's root. Append-only — never overwritten.
What it is
Every entry in the Completions Log includes the prompt number, a description of what was built, the commit hash, the model used, and detailed notes. The log is append-only — entries are never overwritten or deleted. It is the authoritative record of what has been done to a codebase over time. Even prompts that completed without a detected commit get logged with `no commit detected`.
When you would use it
You read the Completions Log when reviewing project history, building release notes, or trying to understand when and why something landed.
Common operations
- Tracking what was shipped to a project over time
- Auditing AI-generated changes
- Generating release notes from log entries
- Powering the Handoff document's recent activity section
Related terms
Dashed terms are named in the source but do not have a page here yet.
Where this is taught
No learning path uses this term yet. Browse the Learning Atlas for guided sequences through related ideas.