System Settings Reference

Niyatna settings define how company work moves through the system.

They should be readable by humans first. Configuration exists to preserve operating boundaries, not to hide decisions in technical files.

---

Core setting groups

OpenIntent settings

• required_intent_fields: Fields that must exist before work can be routed.
• default_proof_standard: Evidence required for common workflow types.
• acceptance_criteria_templates: Reusable criteria for reports, reviews, UI work, or recurring tasks.

Role and permission settings

• authorized_requesters: Roles allowed to create or assign work.
• review_required_for: Actions that must pause for approval.
• blocked_actions: Actions the system should never perform under this workspace.

Route settings

• default_route: Preferred human, agent, model, or tool path.
• sensitive_context_route: Safer path for confidential company context.
• fallback_route: What happens when the preferred path is unavailable.

Proof and memory settings

• proof_destination: Where evidence is stored.
• memory_writeback_policy: Which outcomes should update company memory.
• retention_scope: How long proof and work records should remain available.

Settings rule

Settings should make governance explicit. If an action is sensitive, expensive, external, or irreversible, it should have a visible review rule.