System Settings Reference
Reference for the settings that control how company work is captured, routed, reviewed, and recorded.
Settings define how company work moves through the system. They are written to be read by people first: configuration exists to keep operating boundaries visible, not to hide decisions in technical files.
| Setting | Description |
|---|
| Required request fields | The fields that must be present before work can be routed. |
| Default proof standard | The evidence required for common types of work. |
| Acceptance criteria templates | Reusable criteria for reports, reviews, interface work, or recurring tasks. |
| Setting | Description |
|---|
| Authorized requesters | The roles allowed to create or assign work. |
| Review required for | Actions that must pause for approval. |
| Blocked actions | Actions the system should never perform in this workspace. |
| Setting | Description |
|---|
| Default route | The preferred person, agent, model, or tool path. |
| Sensitive context route | A safer path for confidential company context. |
| Fallback route | What happens when the preferred path is unavailable. |
| Setting | Description |
|---|
| Proof destination | Where evidence is stored. |
| Memory write-back policy | Which outcomes should update company memory. |
| Retention scope | How long proof and work records remain available. |
Settings should make review explicit. If an action is sensitive, expensive, external, or irreversible, it should have a visible review rule.
