Scenario DemoShared deterministic engine

Starship Command Intent Receipt

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.

Pre-execution control route

COMMAND_DECK / INTENT_BOUNDARY

Command

Human language received

Intent Envelope

Meaning and limits structured

Governor

Route allowed, held, or refused

Urgency checked
Authority bounded
Stops visible
Why the boundary matters

Authority tone is not governance.

Load a command example and inspect how XEMATIX separates urgency from authorization.

Boundary 01

Command is not intent

Action verbs still need purpose, constraints, authority, and stop conditions before execution is safe.

Boundary 02

Safety constraints must travel

Safe range, shields, defensive posture, crew safety, and abort conditions remain attached to the action.

Boundary 03

The Governor must be explicit

Visible checks and stop conditions determine whether the route proceeds, pauses, or escalates.

Command boundary console

Before the machine acts, resolve the boundary.

Different operating context. Same XEMATIX algorithm.
Command received

Signal present

Execution boundary
Needs clarification
Authorized route

Boundary unresolved

Governor conditions

2 checks / 1 stops

Command Capture

Issue a command for governed interpretation.

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.

Command intake1 Receive2 Interpret3 Govern

Start here. Choose a starter prompt or write your own instruction, then interpret it into a bounded receipt before anything is treated as authorization.

Command scenarios
Choose one to load and interpret immediately.

Authority tone is not an execution model. Safety constraints and stop conditions must travel with the command.

Press Ctrl/Cmd + Enter
Command Verdict
Needs clarificationDelegated requestActionable

Execution boundary unresolved: range, safety limit, or abort condition is missing.

The command deck keeps the route unresolved until operational limits are explicit.

Executable intent

Detected

Review state

Human approval required

Risk level

medium

safe route

Clarify intent

Blocked actions: 2Required checks: 2Stop conditions: 1Missing elements: 0
Why this verdict
  • The command implies urgent pursuit or resource diversion without enough safety constraints or abort conditions.
High-risk verbsAmbiguity markers
Command Boundary

Separate the command language, interpretation, and safe route.

What the user said

Divert power to engines and pursue the unknown vessel immediately.

What the system detected

The command language contains a bounded operational request that can be evaluated for authorization.

  • Speech act: Delegated request
  • Actionability: Actionable
  • Matched phrases: pursue, Divert, unknown vessel, vessel, engines
What the system will allow
  • Clarify intent
  • Prepare command review packet
  • Export receipt
Governance Boundary

Verdicts and blockers stay visible before the envelope details.

This surface makes the blocked execution vector, required checks, stop conditions, and approval state explicit before anyone treats the receipt as permission.

Blocked

These actions remain outside the current command authority boundary.

  • Pursue or divert resources without a safety boundary and abort condition
  • Expand scope beyond the declared request
Required Checks

These checks keep the interpretation tied to the original command.

  • Confirm the receipt matches the original command.
  • Confirm the range limit, safety constraints, and abort condition before pursuit.
Stop Conditions

These conditions halt the execution vector before unsafe or invented execution.

  • Stop until an explicit pursuit abort condition is declared.
Approval

Human approval required.

  • A human checkpoint remains part of the governed execution vector.
Decision Ladder

Speech Act to Receipt

The execution vector is shown in decision order so the visitor can see where XEMATIX authorized, clarified, blocked, or rerouted the command.

Speech Act
Passed

Delegated request

The system classified the command before considering authorization.

Actionability
Passed

Actionable

The command has enough operational shape for bounded handling.

Authority
Needs clarification

command authority checkpoint active

Human review or authority confirmation remains part of the execution vector.

Constraints
Needs clarification

2 blocked / 2 checks / 1 stops

Execution remains bounded by visible blocked actions, checks, and stop conditions.

Receipt
Needs clarification

Needs clarification

Execution boundary unresolved: range, safety limit, or abort condition is missing.

Received Command

What the user actually said

Divert power to engines and pursue the unknown vessel immediately.

Command evidence
  • pursue
  • Divert
  • unknown vessel
  • vessel
  • engines
Command Trace

What the system detected and constrained

These diagnostics stay visible as supporting evidence beneath the command verdict.

Missing operational elements

  • none

Source notes

  • The interpretation stays tied to quoted phrases from the submitted instruction.

Open ambiguity

  • What safe range, pursuit limit, and abort condition governs the command?
Command Envelope Support

The envelope remains inspectable as supporting evidence.

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.

Anchor

Clarify the delegated pursue and divert request for Unknown Vessel before any execution vector is authorized.

  • 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

The missing authority, audience, or approval details for Unknown Vessel are resolved before execution.

  • 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

Clarify unresolved language and missing review conditions before permitting any execution vector.

  • command-deck control surface
  • The command implies urgent pursuit or resource diversion without enough safety constraints or abort conditions.

Actuator

These are the actions the current envelope allows or blocks before execution in the command-deck control surface.

  • Allowed: Clarify intent
  • Allowed: Prepare command review packet
  • Allowed: Export receipt
  • Blocked: Pursue or divert resources without a safety boundary and abort condition
  • Blocked: Expand scope beyond the declared request

Governor

Human approval remains part of the route.

  • Confirm the receipt matches the original command.
  • Confirm the range limit, safety constraints, and abort condition before pursuit.
  • Stop until an explicit pursuit abort condition is declared.
Command JSON

The same envelope remains visible as a machine-readable structure.

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"
  }
}
Command Receipt
Needs clarificationDelegated requestActionable
Command outcome

Needs clarification: Execution boundary unresolved: range, safety limit, or abort condition is missing.

Receipt ID

intent-71973f6b

Timestamp

2026-08-31T10:19:42.079Z

Review state

Human approval required

Executable intent

Detected

Semantic ledger note

The export preserves the received command, detected command intent, and Governor conditions.

Quoted command

Divert power to engines and pursue the unknown vessel immediately.

Command Receipt Summary

What the current command receipt now makes explicit

The exported receipt carries the command language, speech-act interpretation, grounded execution vector, and bounded checks forward as an inspectable handoff.

  • Speech act: Delegated request
  • Actionability: Actionable
  • Matched phrases: pursue, Divert, unknown vessel, vessel, engines
  • Missing elements: none
  • Purpose: Clarify the delegated pursue and divert request for Unknown Vessel before any execution vector is authorized.
  • Outcome: The missing authority, audience, or approval details for Unknown Vessel are resolved before execution.
  • Allowed actions: Clarify intent, Prepare command review packet, Export receipt
  • Blocked actions: Pursue or divert resources without a safety boundary and abort condition, Expand scope beyond the declared request
  • Required checks: Confirm the receipt matches the original command., Confirm the range limit, safety constraints, and abort condition before pursuit.
Same receipt anatomy

Different domain. Same boundary.

The visual context changes. The five-layer intent envelope and exportable receipt remain the same.

01

Anchor

What did the human actually mean?

02

Projection

What outcome defines success?

03

Pathway

What strategy is authorized?

04

Actuator

What actions may the machine perform?

05

Governor

What blocks, pauses, or escalates execution?

Canonical reference

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.

Back to baseline Intent Receipt