Ideas · Builder Notes
Propose then apply, bound to the exact diff
Kognita alpha adds public propose_document and apply_proposal_tool, so an agent's change is proposed, approved by a different human and applied once.
What was the gap?
An agent editing a document directly leaves no room for review.
What changed in the code?
A proposal is persisted and bound to a hash of the exact diff. Applying needs a human approver distinct from the proposer, claims the binding once, re-verifies the hash and the target's before-state, and evidences the change in the same transaction.
The propose-then-apply pattern from the decision records is now public.
What turned out to matter most?
If the target changed since the proposal, the apply fails. No silent merge.
What isn't solved yet?
Only document edits are covered so far.
What's worth copying?
Let agents draft, let humans apply. Bind the approval to the diff, not to the intent.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #80, Kognita PR #98 in the Kognita repository.