KB Propose Edit
kb_propose_editDestructive
Propose edits to markdown files in a governance-grade knowledge base. High-confidence proposals auto-commit; low-confidence ones enter a pending queue for operator review.
Instructions
Propose an edit to an existing (or new) markdown file under an indexed tier. High confidence auto-commits + queues for push; low confidence enters the pending queue for operator review.
evidence: optional supporting-context strings (max 10 items, 500 chars each), persisted in pending meta / audit events and surfaced by kb_pending (not rendered into the postimage: unlike kb_propose_memory, the postimage here is caller-supplied verbatim).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | Short reason for the proposed change. | |
| evidence | No | Optional supporting evidence strings, max 10 items of 500 chars each. | |
| postimage | Yes | Complete markdown file content after the proposed edit. | |
| confidence | Yes | Caller confidence in the proposal, from 0.0 to 1.0. | |
| base_commit | Yes | Git commit the proposal was based on. | |
| target_path | Yes | KB-relative markdown path to create or edit. | |
| base_blob_sha | Yes | Optional git blob sha for compare-and-swap protection. | |
| agent_identity | Yes | Human-readable agent identity for audit events. | |
| source_session | Yes | Stable id of the agent session making the call. | |
| target_file_hash | Yes | Optional content hash for compare-and-swap protection. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||