LINABounded
Commands reference
Current voice and command vocabulary, scoped to shipped runtime authority.
Command contract
Commands are allowed to navigate, explain, and request approved routes. They are not a second implementation of Core authority. If a command cannot be backed by a real runtime path, it must fail honestly.
Navigation
| User asks | Runtime behavior |
|---|---|
| Open work | Open the current workspace Work stage. |
| Open story | Open the selected story reader or work item panel. |
| Show source graph | Open the source graph for the current work item. |
| Open settings | Move to the workspace settings stage. |
Inspection
| User asks | Runtime behavior |
|---|---|
| What is unverified? | Summarize current statement review gaps from available workspace state. |
| What source is missing? | Explain missing source bindings when the story context provides them. |
| Can I create the Trust File? | Open or explain Trust File readiness without bypassing review gates. |
| Explain this statement | Describe the statement/source relationship and current review status. |
Bounded actions
| User asks | Runtime behavior |
|---|---|
| Search corpus | Use the Core-gated RAG path; no direct authenticated RPC access. |
| Regenerate | Start the approved route when available; durable writes remain Core-owned. |
| Create setup | Assist workspace setup without inventing memberships or signer state. |
| Close | Close panels or overlays without mutating durable state. |
Not valid release commands
Direct database/RPC writes from LINA
Signer-registry writes outside the Core route
Impact metric success from placeholder tools
Trust File approval without human/Core review gates
Parked visual research surfaces as active product functionality