kapi context confirm
kapi confirm <id>Confirm a proposal, which makes its rule binding at the severity it carries and writes it where the rest of kapi reads it: the project's terms, its voice profile, or its content memory.
The write goes into the committed file the recipe binds, so "git diff" shows the decision like any other change.
Edit the rule as you confirm it with --use and --severity, and widen it past the point its evidence was seen at with --widen-to.
Try it
Runs in your browser against a small sample file. Edit the command before running, or press Run to execute it as shown.
kapi context confirm 7Flags
| Flag | Type | Default | Description |
|---|---|---|---|
| --note | string | why | |
| --project, -p | string | path to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted) | |
| --severity | string | change how hard the rule bites: minor or neutral report, anything else fails a check | |
| --use | string | change what the rule says to write instead | |
| --widen-to | string | widen as you confirm: "workspace", or the name of an axis the rule should stop being specific about |
More examples
kapi context confirm 7 --use "content memory" kapi context confirm 7 --severity critical kapi context confirm 7 --widen-to workspace← Back to the Command Reference