Completion Log
Published Updated
What is Completion Log?
The completion log is a project’s permanent record of every prompt that shipped: the prompt number, a description, the commit, the model and notes. It is append-only and outlives the agent session that produced the work.
A permanent audit trail of every prompt that has shipped, stored as `COMPLETION_LOG.md` at each project's root. Append-only — never overwritten.
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`.
How it relates to Orbit
Orbit’s per-project completion log records prompt numbers, commits, models, and notes from finished runs. See Pipeline & History for details.
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
Frequently asked questions
Where does the completion log live?
As COMPLETION_LOG.md at the project root, alongside Orbit’s own history views. See Pipeline & History.
Who decides that a prompt shipped?
Orbit checks the commit and its diff rather than taking the agent’s own summary on trust. See Ghost Ships & Validation.
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.