reject_entity
Mark a knowledge-layer entity as rejected by writing status: rejected and an optional reason to its canonical file, then sync validation. Use only for active entities, not content edits.
Instructions
Reject a knowledge-layer entity — writes status: rejected (and an optional rejected_reason) into its canonical file, then syncs so the status lattice validates the transition. Only active entities can be rejected; verify a stale one first if it must be ruled wrong. This is a verdict, not an edit — do not use it for content changes. Rejected entities stay on record: retrieval filters them out, and dedup can warn when a matching claim resurfaces.
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": {
"repo": "<repo>",
"id": "<id>"
},
"name": "reject_entity"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | UUID of the entity to reject. | |
| repo | Yes | Absolute path to the project root containing `.cogz/`. | |
| reason | No | Why the entity is rejected — stored as `rejected_reason` in the file's frontmatter so the verdict carries its evidence. |