Company Commands
Operational commands for creating intents, checking status, reviewing proof, and approving staged work.
Niyatna commands are shortcuts into governed company work.
They should create or inspect structured intents; they should not bypass permissions, review gates, or proof requirements.
Command examples
| Command | Purpose |
|---|---|
/intent | Create a structured OpenIntent request from a company instruction. |
/assign | Assign an intent to a human, agent, or mixed path. |
/status | Show active work, owner, due date, and current gate. |
/proof | Open the evidence and report-back for an intent. |
/review | Mark a staged result as accepted, rejected, or needing revision. |
/memory | Query relevant company context for the active scope. |
/schedule | Create a follow-up or recurring workflow inside allowed boundaries. |
Command scoping
Commands run under the requester’s role and workspace scope. A finance lead, partner, auditor, client, and internal agent may see different actions because they have different boundaries.
Command rule
A command is not a shortcut around governance. If a command would create external side effects, modify sensitive data, or publish a result, it should pass through the right review gate first.