propose_update
Propose a fix, addition, or new knowledge document as a git branch and pull request for human review. Served content stays unchanged until a reviewer merges the change.
Instructions
Propose a change to a knowledge document — fix an outdated rule, add a missing decision, create a document — for humans to review. Commits the complete new file to a git branch briefd/proposal- (and opens a pull request when a forge is configured); returns branch, commit and PR URL. Never changes what briefd serves until a human merges. Use it for knowledge that is wrong, stale ('code changed since' in bundles) or missing, not for scratch notes. To edit an existing document, call get_document, change its source and send the whole result with base_content_hash set to its content_hash; the call is refused if the file changed in the meantime or if the new content drops the front matter. Fails without a writable git source.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"doc_path": "<doc_path>",
"change_description": "<change_description>",
"new_content": "<new_content>"
},
"name": "propose_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| doc_path | Yes | Repository-relative path of the document to change or create, inside a scope folder, e.g. domain/rules/refunds.md or projects/ledger-service/notes.md. Must end in .md. | |
| new_content | Yes | The complete new content of the file as Markdown, including front matter if the document has any — not a diff or a fragment. When editing, start from the source field of get_document (content lacks the front matter and the title). | |
| base_content_hash | No | The content_hash get_document returned for the version you edited. The proposal is refused if the file has changed since. Send an empty string when creating a new file (refused if it already exists). Omit only if you did not read the document first. | |
| change_description | Yes | Why this change is needed and what evidence you have, written for the human reviewer (becomes the commit message and pull request description). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| branch | Yes | ||
| commit | Yes | ||
| pr_url | No | ||
| pushed | Yes | ||
| proposal_id | Yes |