Project context changes as a team learns: instructions improve, files are replaced, and new Knowledge becomes relevant. Kestrel One records those changes as revisions instead of rewriting the past underneath existing work.
What a revision contains
A context revision identifies the Project instructions, private files, and selected organization Knowledge available for a new turn. Each accepted change creates a new immutable revision.
Why each turn records one
When a new turn begins, Kestrel One attaches the current revision to it. Later, a reviewer can distinguish what the agent actually received from what the Project contains today. Earlier Threads do not pretend they used files or instructions added afterward.
A simple example
If a teammate replaces requirements-v1.pdf with requirements-v2.pdf, the next turn uses the new revision. A previous result still points to the revision containing requirements-v1.pdf, so its reasoning can be reviewed honestly.