Command is not intent
Action verbs still need purpose, constraints, authority, and stop conditions before execution is safe.
Even a command deck needs an intent boundary.
Urgency, authority tone, and action verbs do not automatically create safe authorization. XEMATIX separates the command from the authorized route before any system acts.
One engine. Many scenarios. Same pre-execution boundary.
COMMAND_DECK / INTENT_BOUNDARY
Human language received
Meaning and limits structured
Route allowed, held, or refused
Load a command example and inspect how XEMATIX separates urgency from authorization.
Action verbs still need purpose, constraints, authority, and stop conditions before execution is safe.
Safe range, shields, defensive posture, crew safety, and abort conditions remain attached to the action.
Visible checks and stop conditions determine whether the route proceeds, pauses, or escalates.
Signal present
Boundary unresolved
2 checks / 1 stops
Choose a command scenario or enter your own instruction. The shared deterministic engine will expose the allowed route, blocked route, required checks, and stop conditions.
Start here. Choose a starter prompt or write your own instruction, then interpret it into a bounded receipt before anything is treated as authorization.
Authority tone is not an execution model. Safety constraints and stop conditions must travel with the command.
The command deck keeps the route unresolved until operational limits are explicit.
Detected
Human approval required
medium
Clarify intent
Divert power to engines and pursue the unknown vessel immediately.
The command language contains a bounded operational request that can be evaluated for authorization.
This surface makes the blocked execution vector, required checks, stop conditions, and approval state explicit before anyone treats the receipt as permission.
These actions remain outside the current command authority boundary.
These checks keep the interpretation tied to the original command.
These conditions halt the execution vector before unsafe or invented execution.
Human approval required.
The execution vector is shown in decision order so the visitor can see where XEMATIX authorized, clarified, blocked, or rerouted the command.
The system classified the command before considering authorization.
The command has enough operational shape for bounded handling.
Human review or authority confirmation remains part of the execution vector.
Execution remains bounded by visible blocked actions, checks, and stop conditions.
Execution boundary unresolved: range, safety limit, or abort condition is missing.
Divert power to engines and pursue the unknown vessel immediately.
These diagnostics stay visible as supporting evidence beneath the command verdict.
These layers sit beneath the verdict and governance surfaces so the execution vector can be audited without becoming the first thing the visitor has to decode.
Clarify the delegated pursue and divert request for Unknown Vessel before any execution vector is authorized.
The missing authority, audience, or approval details for Unknown Vessel are resolved before execution.
Clarify unresolved language and missing review conditions before permitting any execution vector.
These are the actions the current envelope allows or blocks before execution in the command-deck control surface.
Human approval remains part of the route.
This makes the receipt exportable, inspectable, and ready to sit upstream of later command-deck control surface behavior.
{
"rawInstruction": "Divert power to engines and pursue the unknown vessel immediately.",
"normalizedInstruction": "Divert power to engines and pursue the unknown vessel immediately.",
"status": "needs_clarification",
"interpretation": {
"speechAct": "delegated_request",
"actionability": "actionable",
"executableIntentDetected": true,
"summary": "The command language contains a bounded operational request that can be evaluated for authorization."
},
"grounding": {
"matchedPhrases": [
"pursue",
"Divert",
"unknown vessel",
"vessel",
"engines"
],
"missingOperationalElements": [],
"sourceNotes": [
"The interpretation stays tied to quoted phrases from the submitted instruction."
]
},
"anchor": {
"purpose": "Clarify the delegated pursue and divert request for Unknown Vessel before any execution vector is authorized.",
"accountableOrigin": "Starship Command",
"constraints": [
"Do not expand scope beyond the declared request.",
"Do not treat unresolved command language as authorization.",
"Do not pursue or divert resources beyond the declared range and abort conditions."
]
},
"projection": {
"desiredOutcome": "The missing authority, audience, or approval details for Unknown Vessel are resolved before execution.",
"successCriteria": [
"The missing authority, audience, or review conditions are made explicit before execution.",
"The safe route remains traceable to the declared purpose and constraints.",
"Human review requirements remain visible in the receipt."
]
},
"pathway": {
"strategy": "Clarify unresolved language and missing review conditions before permitting any execution vector.",
"targetSystems": [
"command-deck control surface"
],
"rationale": [
"The command implies urgent pursuit or resource diversion without enough safety constraints or abort conditions."
]
},
"actuator": {
"allowedActions": [
"Clarify intent",
"Prepare command review packet",
"Export receipt"
],
"blockedActions": [
"Pursue or divert resources without a safety boundary and abort condition",
"Expand scope beyond the declared request"
],
"executionTargets": [
"Unknown Vessel",
"Vessel",
"Engines"
]
},
"governor": {
"requiredChecks": [
"Confirm the receipt matches the original command.",
"Confirm the range limit, safety constraints, and abort condition before pursuit."
],
"stopConditions": [
"Stop until an explicit pursuit abort condition is declared."
],
"humanApprovalRequired": true
},
"ambiguity": {
"terms": [
"immediately",
"unknown"
],
"questions": [
"What safe range, pursuit limit, and abort condition governs the command?"
],
"assumptionsDetected": [
"Urgency is being treated as command authorization."
]
},
"risk": {
"level": "medium",
"categories": [
"urgent pursuit or resource diversion"
]
},
"provenance": {
"demoVersion": "intent-receipt-mvp-v1",
"generatedAt": "2026-08-31T10:19:42.079Z",
"method": "deterministic",
"operatingContextId": "starship-command",
"operatingContextLabel": "Starship Command"
}
}Needs clarification: Execution boundary unresolved: range, safety limit, or abort condition is missing.
intent-71973f6b
2026-08-31T10:19:42.079Z
Human approval required
Detected
The export preserves the received command, detected command intent, and Governor conditions.
Divert power to engines and pursue the unknown vessel immediately.
The exported receipt carries the command language, speech-act interpretation, grounded execution vector, and bounded checks forward as an inspectable handoff.
The visual context changes. The five-layer intent envelope and exportable receipt remain the same.
What did the human actually mean?
What outcome defines success?
What strategy is authorized?
What actions may the machine perform?
What blocks, pauses, or escalates execution?
This generic command scenario demonstrates the command pattern without relying on fictional universes or scenario-specific decision logic. The baseline page remains the detailed public reference for receipt anatomy, export behavior, and the public implementation boundary.