Mission Control · Overview DEMO ENVIRONMENT
Organization
—
Canonical scope
Mission
—
No mission context
Mission Version
—
No baseline
Authority Boundary
NONE
No operational authority
Mission Status
NO DATA
Activate canonical dataset
Objectives
0 / 0
No objective model loaded
Engineering Readiness
—
Planning → verification
Assurance Posture
—
Evidence / verification
Mission Status Authoritative Projection
No mission context loaded
Activate the canonical dataset from the foundation controls. Mission Control will then project the selected mission object rather than maintain a separate state.
Operational Guardrails Control Plane
State Source
—
Awaiting mission dataset
Telemetry Freshness
—
Awaiting telemetry layer
Execution Boundary
—
External command path disabled
Evidence
—
Mission lineage not loaded
Mission Control can observe the mission and initiate controlled workflow transitions in later updates, but it does not bypass planning, simulation, verification or authorization.
Mission Lifecycle Position MODEL → PLAN → OPTIMIZE → SIMULATE → VERIFY → STATE → REPLAN → EXECUTE
01
MODEL
Not loaded
02
PLAN
Not loaded
03
OPTIMIZE
Not loaded
04
SIMULATE
Not loaded
05
VERIFY
Not loaded
06
STATE
Not loaded
07
REPLAN
Not loaded
08
EXECUTE
Not loaded
Mission Objectives Mission Model
Objective model not loaded
Mission objectives will appear here once the canonical mission dataset is active.
Mission Lineage Versioned Dependencies
MISSION
—
No object context
ARCHITECTURE
—
No dependency
PLAN
—
No dependency
SIMULATION
—
No dependency
VERIFICATION
—
No dependency
Mission Event History Projection of Canonical Events
No mission events loaded
Activate the canonical dataset to inspect mission history.
Canonical Foundation Source of Truth · KMAP-SEED-V1
Mission Baseline Foundation Context
Dataset Integrity Deterministic Seed
Demo data is synthetic and non-operational. It exists to demonstrate product behavior, lineage and governance—not to represent live spacecraft state or flight authorization.
Assurance Chain Shared Dependency Graph
Canonical Object Ledger Click Any Object to Inspect Provenance
ObjectIDStateVersionRelation
Deterministic Scenarios Reproducible Fixtures
Mission Registry Organization / Program Scope
No mission dataset loaded
Activate the canonical dataset from Mission Control Overview to populate the registry.
Mission Model Selected Mission Object
No selected mission
Mission identity, version, state, phase and objectives will be shown here.
Engineering & Assurance Current Mission Readiness
No readiness projection
Planning, optimization, simulation and verification status will be projected from the canonical seed.
Mission Dependencies Object References
Objectives Mission Definition
Mission Controls Governed Actions
Context
—
Active mission object
Authority
—
External command path remains disabled
Next Gate
—
Derived from assurance chain
Scenario
SCN-001
Golden mission lifecycle fixture
Mission Control actions are deliberately limited in this update. Opening the active mission, inspecting lineage and changing context are available; live operations, replanning and execution remain downstream capability gates.
Operational ContextMISSION · STATE · PLAN · AUTHORITY
Active AlertsEVENT / IMPACT / RESPONSE
Current PlanBASELINE + DERIVED DISPOSITION
Resilience Control ChainSCN-002
Recent Operational EventsRUNTIME / SYNTHETIC
Control BoundaryAUTHORITY / EXECUTION
Current StateOBSERVED · DERIVED · MODELED · PREDICTED · OPERATIONAL
State LayersSOURCE OF TRUTH
State ChangesSCN-002 EVENTS
Plan / State LineageBASELINE REMAINS RECONSTRUCTABLE
Replanning Context
AUTHORITATIVE BASELINE
Anomaly / Impact
STATE CHANGE
Candidate Replans
FEASIBILITY + VERSION TRACE
The prior authorized baseline is never overwritten. This workspace creates derived candidate objects. Any action that could affect mission operations must pass simulation, verification and governed decision handling before it can reach Mission Control.
Execution ContextSOURCE PLAN · DECISION · AUTHORITY
Current Execution StateGATED STATE MACHINE
Execution ChainSCN-003
Action PackageSIMULATED ACTIONS
Preconditions & GuardrailsEXECUTION GATES
Execution TimelineRUNTIME EVENTS
Resulting Mission StateSTATE RECONCILIATION
Execution Evidence & LineageAUDITABLE DISPOSITION
Operator ControlsNO EXTERNAL COMMAND PATH
Update 15 closes the operational loop after planning and governed decision handling: approved action package → deterministic precondition checks → simulated execution → resulting-state reconciliation → evidence. The execution authority remains SIMULATED_ONLY.
Fleet Operational Picture
SCN-005 / SYNTHETIC FLEET
Selected Asset
MEMBER STATE / RELATIONS
Fleet Registry
6 MEMBERS / 3 MISSIONS / 4 GROUND NODES
SYNTHETIC / NON-OPERATIONAL
Mission Threads
CROSS-ASSET PRIORITY
Fleet Exceptions
TRIAGE QUEUE
Fleet Priority & Allocation
OBJECTIVES + CONSTRAINTS
Candidate Fleet Schedules
DERIVED / SIMULATED
Fleet State Lineage
PACKETS → MEMBERS → MISSIONS → PRIORITY → PLAN → FLEET STATE
Update 17 keeps member-level observed and derived state distinct from fleet-level operational publication. The canonical mission baseline is not mutated; all schedule candidates are synthetic derived artifacts.
Asset Registry Canonical Configuration Layer
SYNTHETIC / NON-OPERATIONAL
Spacecraft Registry ASSET ID · VERSION · STATE
Activate DEMO DATA to load the canonical spacecraft registry.
Asset Detail Identity / Configuration / Relations
Select an asset to inspect its canonical configuration, state layers, evidence and dependencies.
Assets are authoritative inputs to engineering and later mission operations. This update exposes inventory, exact configuration references, lifecycle state, relationships and evidence. It does not bypass planning, simulation, verification or authorization.
Asset Registry Canonical Configuration Layer
SYNTHETIC / NON-OPERATIONAL
Vehicles Registry ASSET ID · VERSION · STATE
Activate DEMO DATA to load the canonical vehicles registry.
Asset Detail Identity / Configuration / Relations
Select an asset to inspect its canonical configuration, state layers, evidence and dependencies.
Assets are authoritative inputs to engineering and later mission operations. This update exposes inventory, exact configuration references, lifecycle state, relationships and evidence. It does not bypass planning, simulation, verification or authorization.
Asset Registry Canonical Configuration Layer
SYNTHETIC / NON-OPERATIONAL
Payloads Registry ASSET ID · VERSION · STATE
Activate DEMO DATA to load the canonical payloads registry.
Asset Detail Identity / Configuration / Relations
Select an asset to inspect its canonical configuration, state layers, evidence and dependencies.
Assets are authoritative inputs to engineering and later mission operations. This update exposes inventory, exact configuration references, lifecycle state, relationships and evidence. It does not bypass planning, simulation, verification or authorization.
Asset Registry Canonical Configuration Layer
SYNTHETIC / NON-OPERATIONAL
Ground Stations Registry ASSET ID · VERSION · STATE
Activate DEMO DATA to load the canonical ground stations registry.
Asset Detail Identity / Configuration / Relations
Select an asset to inspect its canonical configuration, state layers, evidence and dependencies.
Assets are authoritative inputs to engineering and later mission operations. This update exposes inventory, exact configuration references, lifecycle state, relationships and evidence. It does not bypass planning, simulation, verification or authorization.
Asset Registry Canonical Configuration Layer
SYNTHETIC / NON-OPERATIONAL
Fleets Registry ASSET ID · VERSION · STATE
Activate DEMO DATA to load the canonical fleets registry.
Asset Detail Identity / Configuration / Relations
Select an asset to inspect its canonical configuration, state layers, evidence and dependencies.
Assets are authoritative inputs to engineering and later mission operations. This update exposes inventory, exact configuration references, lifecycle state, relationships and evidence. It does not bypass planning, simulation, verification or authorization.
Architecture
—
Canonical architecture state
Requirements
00
Mission requirements in canonical seed
Hard Constraints
00
Deterministic checks required downstream
Asset Configurations
00
Exact versions consumed by architecture
Architecture BaselineCanonical / Awaiting dataset
No engineering context
Activate DEMO DATA to project the canonical architecture baseline.
Release GatesArchitecture Readiness
No gate projection
Readiness is derived from the canonical architecture and asset configuration records.
Mission Objectives → RequirementsTraceability
No traceability graph
Mission objectives and engineering requirements appear here when the canonical dataset is loaded.
Authoritative Asset InputsExact Configuration
No asset inputs
Architecture consumes exact asset/version references from the Assets domain.
System Architecture ChainMission → Asset → Interface → Downstream
Architecture topology not loaded
The visual model is synthetic and illustrates dependency structure, not physical spacecraft geometry.
Constraint RegisterHard / Policy
No constraints loaded
Deterministic constraints are consumed by Planning and later engineering engines.
Baseline Plan
—
Published mission plan
Candidates
00
Alternative plan fixtures
Review Focus
—
Working review state only
Execution Gate
BLOCKED
Verification + authorization remain downstream
Plan PortfolioBaseline + Candidates
No plans loaded
Activate DEMO DATA to load PLAN-DEMO-001 and candidate fixtures A/B.
Selected Plan ReviewNo focus
Select a plan
Review focus is a local demo state and does not change the authoritative selected plan.
Plan ComparisonConstraint-aware trade space
Comparison unavailable
Candidate comparison is populated from deterministic plan fixtures in the canonical seed.
Mission Activity SequencePlan Structure
No plan sequence
A synthetic mission activity sequence will appear once the plan context is loaded.
Downstream Dependency GateBefore Execution
Gate not evaluated
Planning produces candidates; optimization, simulation, verification and authorization remain required.
Plan LineageProvenance
No lineage
Plan references will show mission version, architecture, constraints, assets and downstream runs.
Run
—
No dynamics fixture loaded
Orbit Context
—
Synthetic reference only
Ground Contacts
—
Mission support windows
Downstream
BLOCKED
Optimization depends on dynamics context
Reference GeometryFD-RUN-DEMO-001
No dynamics context
Activate DEMO DATA to load the synthetic reference orbit and mission windows.
Contact WindowsGround Segment
No contacts loaded
Ground-station records are consumed from the authoritative asset layer.
Propagation / Activity ContextMission → Plan → Dynamics
No timeline context
Select a canonical plan to see the synthetic activity sequence consumed by downstream engineering.
Engineering BoundaryAuthority
Flight Dynamics in this demo represents a deterministic reference calculation layer. The result is inspectable and traceable, but it is not a flight-certified trajectory solution and cannot cross the execution boundary.
Run
—
Canonical optimization fixture
Candidates
—
Baseline + alternatives
Feasibility
—
Constraint posture
Selected Fixture
—
Current comparison focus
Optimization RunOPT-RUN-DEMO-001
No optimization run
Activate DEMO DATA to load the canonical optimization fixture.
Objective StackWeighted Objectives
No objective stack
The optimizer consumes the mission's weighted objectives.
Candidate ComparisonConstraint + Resource Posture
No candidates loaded
Planning candidates will appear here once the canonical dataset is active.
Constraint EvaluationHard / Policy
No constraints loaded
Optimization uses the same immutable constraints as Planning.
LineageMission → Plan → Dynamics → Optimization
No lineage loaded
Optimization lineage will appear here.
Optimization Context
SCN-018 / FLEET-DEMO-017 DERIVED
Objective Stack
WEIGHTED / EXPLICIT
Resource Budget & Constraints
HARD / POLICY / CURRENT MARGINS
DERIVED / SYNTHETIC / NON-OPERATIONAL
Candidate Schedule Portfolio
MULTI-OBJECTIVE / SIMULATED
Trade-off Evaluation
OBJECTIVE / RESOURCE / DISRUPTION
Feasibility Simulation
PRE-EXECUTION
Selected Schedule
GOVERNED DERIVED ARTIFACT
Optimization Lineage
FLEET STATE → RESOURCES → OBJECTIVES → CANDIDATES → SIMULATION → DERIVED PLAN
Update 18 never overwrites the approved fleet or mission baseline. Every optimization output is a derived candidate until feasibility and governance gates are satisfied.
Publication Gate
VALIDATED SCHEDULE / NO EXTERNAL COMMAND
Nominal Run
—
SIM-RUN-DEMO-001
Off-Nominal
—
SIM-RUN-OFF-001
Scenario Focus
—
Local review focus
Evidence Ready
—
Verification consumes run outputs
Scenario PortfolioSynthetic Fixtures
No scenarios loaded
Activate DEMO DATA to load the canonical scenarios.
Selected ScenarioNo focus
Select a scenario
Nominal and off-nominal runs share the same mission baseline but test different modeled conditions.
Scenario InputsAssets + Plan + Telemetry Fixtures
No inputs loaded
Inputs are derived from the canonical mission, selected plan, asset versions and telemetry fixtures.
Run ResultDeterministic Fixture
No result loaded
Run a scenario in demo mode to append a runtime event.
Verification DependencyDownstream Gate
Verification not reached
Simulation results must be inspectable before verification can consume them.
Verification Run
—
VERIF-RUN-DEMO-001
Checks
—
Requirements + constraints
Result
—
Canonical verification fixture
Execution Gate
BLOCKED
Authorization remains separate
Verification ChecklistVERIF-PLAN-DEMO-001
No verification context
Activate DEMO DATA to load the canonical verification checklist.
Evidence InputsRequired Artifacts
No evidence inputs
Verification consumes the selected plan, dynamics, optimization and simulation records.
Release GateAuthority Boundary
Gate not evaluated
Verification does not grant flight authority.
Engineering LineageModel → Plan → Optimize → Simulate → Verify
No lineage loaded
Verification lineage will appear here once the canonical dataset is active.
Twin Model
—
Model registry
Snapshot
—
—
Synchronization
—
Canonical snapshot state
Authority
—
External commands never enabled
Canonical mission topology
Stylized scene / not physics
DEMO VIEW
Activate DEMO DATA to render the canonical twin scene.
SC-DEMO-001 KMAP EO-01 PAY-DEMO-001 Earth-Imaging Payload GS-DEMO-001 Primary Contact GS-DEMO-002 Secondary Contact REFERENCE BODY VISUAL CONTEXT ONLY Render coordinates are explanatory. They are not trajectory, attitude, pointing, or command data.
Twin context
State / provenance
Activate DEMO DATA to inspect synchronized twin context.
Twin composition
Mission architecture → model → snapshot
Published models
00
Canonical twin model records
Model version
—
Approved digital-twin baseline
Snapshot state
—
Latest canonical snapshot fixture
Mission binding
—
Selected mission context
Model registry
Canonical records
Model detail
Select a record
Select the digital-twin model to inspect its version, scope, synchronization source, and downstream dependencies.
Model topology
System model composition
Fleet
—
—
Members
—
Active spacecraft members
Ground Nodes
—
Supporting ground records
Fleet State
—
Canonical aggregation record
State matrix
Observed → operational
ObjectTypeObservedDerivedModeledPredictedOperationalSource
Fleet dependencies
Configuration links
State interpretation
Authority boundary
SCN-002 · Controlled anomaly fixture
Update 14 uses synthetic telemetry only. The anomaly is observed first; plan change is blocked until impact assessment, simulation, verification and governed decision handling.
BOUNDARY SIMULATED_ONLY
Stream
—
—
Packet quality
—
—
Freshness
—
—
Feed state
—
—
Telemetry stream
—
BATTERY STATE · SOURCE TM-BAT-001
Packet feed
Simulated live cadence
TEL-STREAM-DEMO-001TEL-PKT-DEMO-001DC-DEMO-001SIMULATED_ONLY
Telemetry trust boundary
Data ≠ authority
Observed: telemetry fixture Derived: quality / freshness Modeled: Digital Twin Predicted: not asserted here Operational authority: SIMULATED_ONLY
Current Operational State
FUSED STATE / SCN-004
State Layers
AUTHORITY CLASSIFICATION
Telemetry Packet Stream
OBSERVED INPUT
Event Correlation
TIME + ASSET + MISSION CONTEXT
Derived Health & Impact
DETERMINISTIC DERIVATIONS / NO UNSOURCED CLAIMS
State Lineage
PACKET → EVENT → STATE → PLAN CONTEXT
Operational Trust Boundary
DATA ≠ AUTHORITY
Observed
Telemetry / Events
Direct fixture inputs. Timestamped and source-bound.
Derived
Quality / Health
Computed from explicit rules and current packets.
Modeled
Twin / Plan Context
Contextual references used for interpretation only.
Operational
SIMULATED_ONLY
No external command path. State publication is demo-local.
Update 16 establishes the state-fusion layer that later fleet operations and autonomy workflows can rely on. The authoritative baseline and external systems remain untouched.
0 records
RecordClassValue / stateQualitySourceContext
READ_ONLY_PROJECTIONSOURCE_IDS_VISIBLENO_CANONICAL_MUTATION
Query contract
Traceability
Mission context
—
Dataset
DC-DEMO-001 · Synthetic telemetry dataset
Time basis
KMAP synthetic UTC fixture epoch
Results are projections over canonical seed records. Selecting a row opens its source identifiers and authority boundary.
Explorer scope
Update 09
TelemetryEventsRunsMission stateTwin snapshot
Telemetry points
—
Source telemetry point records
Good quality
—
Derived from point quality fields
Warnings
—
Nominal + anomaly fixtures separated
Events
—
Canonical event log projection
Signal distribution
Source: TEL fixtures
—
Run / state summary
Cross-domain projection
Analytical lineage
No hidden numbers
Report builder
Read-only generated view
Template
Mission Data & Readiness
Mission
—
Source scope
Mission · Engineering · Twin · Telemetry · Evidence
Authority
SIMULATED_ONLY
Generate creates a runtime report artifact for this demo session. It does not mutate the canonical mission, plan, telemetry, twin, or governance records.
Current report state
Projection
Latest artifact
NONE
No runtime report generated.
Report library
0 source-aligned reports
EVID-DEMO-001VERIF-RUN-DEMO-001TWIN-SNAP-DEMO-001TEL-PKT-DEMO-001
Active Model
—
Governed planning-support model
Evaluation
—
Representative / safety evaluation state
Inference
—
Structured output, validation-aware
Authority
—
Model output does not grant execution authority
Model registry
VERSIONED / CONTROLLED
Model detail
SELECTED
Evaluation gate
MI-1 / MI-2 / MI-8
Deployment lifecycle
DEV → EVAL → STAGE → PROD
Engineering assurance boundary
NO DIRECT AI → COMMAND PATH
AI may assist
Model selection, planning, optimization support and interpretation.
Structured outputs only.
Deterministic truth
Engineering validators, constraints, simulation and verification.
Required for consequential decision classes.
Authority
Approval / autonomy policy resolves what may actually execute.
Confidence is not authority.
Candidate
—
Structured decision candidate
Validation
—
Deterministic engineering boundary
Authority
—
Policy-derived authority ceiling
Decision
—
Approval / execution status
Decision pipeline
CONTEXT → VALIDATION → AUTHORITY → RECORD
Current candidate
DEC-CAN-DEMO-001
Candidate comparison
PLAN-CAN-A-001 / PLAN-CAN-B-001
Policy evaluation
DECISION CLASS + AUTHORITY
Decision record
DEC-DEMO-001
Execution boundary
CONTROLLED PATHWAY
No direct AI-to-command path. A consequential decision must carry governed context, freshness/quality state, structured constraints, deterministic validation, applicable simulation/verification evidence, authority policy and the required approval before controlled execution. This demo remains simulated only.
Active Policy
—
Mission-scoped policy
Current Ceiling
—
Maximum authority currently permitted
Execution Classes
00
Explicitly mapped decision classes
Status
—
Suspend / downgrade remains available to authorized roles
A0–A5 authority ladder
V11 DEMO VOCABULARY
V11 resolves the demo vocabulary using the enterprise authorization contract: A0 Observe, A1 Recommend, A2 Approve, A3 Supervised Execute, A4 Bounded Autonomous, A5 Program Autonomy. The detailed Mission Intelligence source defines the underlying control model but leaves production enforcement policy deployment-specific.
Authority matrix
DECISION CLASSES
Guardrails
EXPLICIT / OBSERVABLE
Readiness
NEXT LEVEL EVIDENCE
Intervention & recovery
FAIL-CLOSED
Customer Context
TENANT / PROGRAM / WORKSPACE
Workspace Boundary
ISOLATION / SCOPE
Enterprise Workspace Topology
TENANT → PROGRAM → WORKSPACE → MISSION → CONTROL PLANE
Identity & Access Registry
IDENTITY → ROLE → SCOPE → ENTITLEMENT
User / ServiceRoleScopeAutonomy CeilingDecision
Enterprise access is evaluated as a conjunction of identity, role, scope, object state and policy. Cross-workspace access is denied by default in this fixture.
Entitlements
PRODUCT CAPABILITIES
Environment Guardrails
DEMO / DEV / STAGING / PROD
Enterprise Policy Bundle
ENT-POL-020 / VERSIONED
The policy bundle composes workspace isolation, mission scope, autonomy ceilings, data handling, audit retention, connector boundaries and change-control requirements. Policy state is versioned and evidence-linked.
Service Identity
CONTROLLED INTEGRATION ACCESS
Control Change
PROPOSAL / APPROVAL
Approval Chain & Enterprise Gate
NO SILENT MUTATION
Change request
No proposal loaded
Create a synthetic proposal to demonstrate the controlled enterprise change path.
Approval sequence
Enterprise Control Lineage
CONTEXT → BOUNDARY → IDENTITY → ENTITLEMENT → ENVIRONMENT → POLICY → CHANGE → APPROVAL → EVIDENCE
Update 20 adds the enterprise control plane around the mission system. Customer controls govern access to the existing KMAP lifecycle; they do not replace mission baselines, engineering verification, operational state or governed-autonomy boundaries.
Autonomy Context
SCN-019 / RPLAN-PUB-018 INPUT
Authority Envelope
POLICY / TIME-BOUND / EXPLICIT
A0–A5 Authority Ladder
AUTONOMY CEILING IS POLICY-BOUND
The demo requests A4 for one explicit low-risk decision class. A4 is not reached by model confidence; it becomes effective only after policy, precondition, verification and authorization gates are satisfied. A5 remains disabled in this fixture.
Decision-Class Authority Matrix
CLASS → CEILING → PRECONDITIONS → RECOVERY
Preconditions & Guardrails
FAIL CLOSED
Recovery & Intervention
SUSPEND / DOWNGRADE / ESCALATE
Bounded Autonomy Candidate Portfolio
GENERATED WITHIN APPROVED CLASS
Execution Envelope
ALLOWED ACTIONS / LIMITS / ROLLBACK
Autonomy Lineage
CONTEXT → POLICY → CLASS → GUARDS → CANDIDATE → VERIFY → AUTHORIZE → EXECUTE → EVIDENCE
The canonical mission and approved schedule remain immutable. Update 19 only creates a derived autonomy action package and an outcome/evidence record; it never bypasses the existing engineering, verification or governance layers.
Autonomy Control Gate
NO EXTERNAL COMMAND PATH
Decision Log
—
Append-only reconstruction record
Sequence
00
Required reconstruction stages
Decision
—
Linked selected / approved decision
Evidence
—
Mission Evidence reference
Decision reconstruction
AUTHORITATIVE SEQUENCE
Decision context
SELECTED LOG
Version & policy references
REPRODUCIBILITY
Reconstruction boundary
MODEL RATIONALE ≠ VALIDATION ≠ AUTHORITY
LayerRecorded sourceMeaningAuthority
Model outputMODEL-DEMO-PLN-001 / INF-DEMO-001Structured recommendation / candidate generation.None by itself
Engineering validationVERIF-RUN-DEMO-001Deterministic verification evidence.Required gate
PolicyPOL-DEMO-001Maps decision class to permitted authority.Ceiling
Human decisionDEC-DEMO-001Approved decision record in simulated environment.A2 simulated
Package
—
No canonical evidence loaded
Evidence Items
00
Source-linked mission evidence
Traceability
—
Bidirectional support / impact chain
Integrity
—
Scope + provenance + version context
Evidence package
EVID-DEMO-001
Evidence lifecycle
CONTROLLED
Capture → validate → classify → link → review → approve/reject → freeze → package/publish → retain/archive → retrieve. The demo exposes the lifecycle as a read-only control model.
Evidence explorer
0 records
Traceability matrix
UPSTREAM / DOWNSTREAM
Governance controls
EG-1 → EG-9
Recorded Events
00
Authoritative demo audit history
Critical Actions
00
Approvals / execution / governance
Integrity
—
Actor + target + correlation context
Retention
—
Protected historical record
Audit explorer
0 events
Object history
SELECT EVENT
Audit requirements
IMMUTABLE TRAIL
Control Set
—
No compliance record loaded
Evidence-linked Controls
00
Control → evidence relationships
Open Findings
00
Historical finding state preserved
Exceptions
00
Explicit authority + expiry required
Compliance overview
COMP-DEMO-001
Control model
REQUIREMENT → CONTROL → EVIDENCE
Controls & evidence
SOURCE-ALIGNED
Finding lifecycle
PRESERVE HISTORY
Governance boundary
AI ASSISTED / HUMAN AUTHORITY
Active Baseline
—
Published mission baseline
Tracked Versions
00
Cross-domain reproducibility references
Change Set
—
Explicit rationale / affected objects
Integrity
—
Immutable history / exact-version approval
Version graph
0 versions
Version detail
SELECT NODE
Diff / compare
NO HISTORY REWRITE
Version inventory
CROSS-DOMAIN
Connection
—
Canonical demo integration reference
Contract State
—
Schema / compatibility check
Authority
—
External API cannot bypass KMAP governance
Mode
SIMULATED
No production command path is enabled
API catalog
VERSIONED / GOVERNED
InterfacePurposeScopeStateAuthority
API access is an integration boundary, not an authority shortcut. Queries, jobs, events and controlled commands remain subject to mission scope, authorization, validation, freshness and policy.
Contract context
SELECTED INTERFACE
Integration rail
REQUEST → GOVERN → EXECUTE
Active
—
Seeded connections in healthy state
Degraded
—
Failure fixture retained intentionally
Selected
—
Current connection context
Safe behavior
NO FALSE GREEN
Failure remains visible to dependent domains
Connection inventory
HEALTH / FRESHNESS / SCOPE
ConnectionPurposeStateDependency impactSource
Health monitor
SELECTED
Failure handling
SCN-014 / DEGRADED
Negative fixture
INT-FAIL-DEMO-001
Secondary connector unavailable. The failure is recorded as an integration event and must not be represented as healthy.
FAILED
A retry request in this demo records an attempted recovery event; it does not silently convert the failed fixture to ACTIVE.
Integration Context
CUSTOMER / PROGRAM / BOUNDARY
Interoperability Policy
V20 ENTERPRISE CONTROLS
Integration Rail
CONTRACT → MAP → ADAPTER → EVENT → STATE → EVIDENCE
Interface Registry
SYSTEMS / CONTRACTS / SCOPE
InterfaceSource / TargetContractModeStateAuthority
Contract Context
SELECTED CONTRACT
Semantic Mapping
CANONICAL ↔ EXTERNAL
Adapter Health
FRESHNESS / LATENCY / ERROR / DRIFT
Interoperability Test Harness
NEGATIVE FIXTURE / NO FALSE GREEN
Interoperability is an exchange boundary, not an authority shortcut. External systems may exchange approved data and events through governed contracts; production spacecraft command execution is not enabled in this fixture.
Lineage
SCN-021 EVIDENCE CHAIN
Mission Product Rail
CONTEXT → TEMPLATE → BUNDLE → INTEGRATION → OPERATING MODE → GOVERNANCE → VALIDATE → APPROVE → PUBLISH
Customer Context
V20 ENTERPRISE WORKSPACE
Product Readiness
VERSIONED RELEASE GATE
Mission Product Archetypes
SYNTHETIC CATALOG / SIX CUSTOMER PATTERNS
MP-TPL-COMM-01
Commercial Mission
Mission Engineering + Planning + Simulation · ceiling A2
Mission workspace / evidence-led planningEN-MA · EN-PL · EN-SM · EN-VF
MP-TPL-FLEET-02
Constellation Fleet
Fleet Operations + Resource Optimization · ceiling A4 BOUNDED
Fleet workspace / governed autonomyMC-FL · EN-RS · MI-GA · IN-IO
MP-TPL-PRIME-03
Prime Program
System-of-Systems + Verification + Evidence · ceiling A3
Program workspace / multi-team controlsEN-MA · EN-VF · MI-DC · AD-EW
MP-TPL-LUNAR-04
Lunar / Deep Space
Simulation + Twin + Assurance + Controlled Autonomy · ceiling A3
High-assurance mission workspaceDT-3D · DT-SM · EN-SM · MI-GA
MP-TPL-GROUND-05
Ground / Data Infrastructure
Interoperability + Telemetry + Operational State · ceiling A1
Integration workspace / service boundaryIN-IO · DA-TEL · DA-OS · EG-ME
MP-TPL-SOV-06
Government / Sovereign
Multi-mission Governance + Decision + Evidence · ceiling A3
Sovereign workspace / controlled federationAD-EW · MI-DC · EG-AU · IN-IO
Customer Product Contract
CONFIGURATION MANIFEST
Capability Bundle
COMPOSED FROM KMAP MODULES
Integration & Operating Profile
V21 INTEROPERABILITY + GOVERNED OPERATING CONTEXT
Governance & Evidence
V20 POLICY + V22 DECISION CONTEXT
Readiness Checks
FAIL-CLOSED
Customer Mission Scenarios
DERIVED APPLICATION SURFACES
ScenarioCustomer PatternPrimary ValueRequired ContextAuthorityRelease
Customer-specific mission products are configuration manifests, not separate command systems. Each package references governed KMAP modules, approved integrations, explicit policy boundaries and evidence requirements.
Product Lineage
SCN-023 EVIDENCE CHAIN
Decision Rail
CONTEXT → EVIDENCE → QUESTION → SIGNALS → OPTIONS → TRADE-OFF → UNCERTAINTY → REVIEW → RECORD
Mission Context
V20 / V21 GOVERNED CONTEXT
Decision Readiness
CONTROLLED REVIEW GATE
Evidence Frame
STATE / PLAN / RESOURCE / INTEROPERABILITY / TWIN
Decision Question
MISSION OBJECTIVE + CONSTRAINTS
Signal Synthesis
CORRELATED MISSION INTELLIGENCE
Candidate Options
POLICY-COMPATIBLE DECISION SET
Trade-off Evaluation
MISSION VALUE / RESOURCE / CONTINUITY / DISRUPTION
CandidateMission valueResource marginFleet continuityDisruptionPolicy ceilingFeasibility
Uncertainty & Coverage
CONFIDENCE IS NOT AUTHORITY
Human Review
RECOMMENDATION → APPROVAL
Decision Lineage
SCN-022 EVIDENCE-BACKED RECORD
Decision Center produces reviewable recommendations and controlled decision records. It does not bypass the V20 enterprise controls, V21 interoperability contracts, V19 autonomy authority ladder or V15 execution boundary. All artifacts in this fixture are synthetic and SIMULATED_ONLY.
Organization
—
Canonical tenant context
Program
—
Current mission program
Users
—
Seeded role identities
Mission scope
—
Scope resolves before authority
Organization hierarchy
TENANT → PROGRAM → MISSION
Scope boundary
AUTHORIZATION INPUT
Organization identities
ROLE ASSIGNMENTS
UserRoleMission scopeAuthority source
Identity
—
Selected seeded identity
Role
—
Canonical role assignment
Scope
—
Organization / mission boundary
Decision
—
Demo authorization evaluation
Users
IDENTITY REGISTRY
UserRoleIDScope
Access evaluation
SELECTED USER
Permission decomposition
IDENTITY → SCOPE → OBJECT → STATE → POLICY
Environment
DEMO
Synthetic / non-operational
Authority
SIMULATED_ONLY
No real spacecraft command path
Classification
—
Current fixture classification
Change state
—
Settings are proposed before application
Workspace settings
DEMO CONFIGURATION
Data presentation
Presentation only; does not alter canonical data.
Failure visibility
Always show degraded state
Keeps integration failures observable.
Read-only demo boundary
Canonical records immutable
Actions emit simulated events instead of real mutations.
Audit verbosity
Controls demo inspection detail.
Governance defaults
CANONICAL BOUNDARIES
Change proposal
NO SILENT MUTATION
Controlled change
Settings proposal is a demo event
Saving records the proposed configuration and references the selected organization/workspace. It does not mutate production policy, mission state, or security controls.
PROPOSAL
Customer Readiness Rail
CONTEXT → PRODUCT → OPERATE → INTELLIGENCE → AUTONOMY → INTEGRATE → GOVERN → SCALE → ACCEPT → HANDOFF
Customer Mission Context
V20 / V23 CUSTOMER BOUNDARY
System Readiness Gate
V14 → V24 BASELINE
Complete KMAP Capability Surface
ENGINEERING / OPERATIONS / INTELLIGENCE / GOVERNANCE / INFRASTRUCTURE
Customer Acceptance Matrix
EVIDENCE-LINKED ACCEPTANCE CRITERIA
CriterionSource layerExpected stateEvidenceGate
Reference Customer Demo Packages
SCN-025 REFERENCE FLOWS
Customer Handoff Manifest
VERSIONED / AUDIT-LINKED
Customer Readiness Controls
FAIL-CLOSED / NO COMMAND AUTHORITY
Reference readiness baseline loaded from the completed Update 14–24 control surfaces. Update 25 remains a synthetic customer-handoff demonstration and does not represent a production deployment.
Customer Readiness Lineage
SCN-025 EVIDENCE CHAIN
Production Readiness Rail
CONTEXT → TOPOLOGY → CAPACITY → RELIABILITY → RESILIENCE → OBSERVE → DEPLOY → RECOVER → PUBLISH
Production Context
V20 / V23 ENTERPRISE BOUNDARY
Reliability Targets
SYNTHETIC SLO PROFILE
Reference Production Topology
EDGE → API → ORCHESTRATION → WORKERS → STATE / EVIDENCE
Capacity & Workload Model
MISSION / FLEET / EVENT SCALE
Workload classCurrentPeak targetHeadroomScaling ruleState
Reliability Guardrails
FAIL-CLOSED / CONTROLLED DEGRADATION
Failure & Recovery Scenarios
NEGATIVE FIXTURES
No failure injected. Production architecture remains nominal in the synthetic fixture.
Observability & Control Plane
METRICS / TRACES / LOGS / AUDIT
Production Readiness Gate
SCN-024 RELEASE CONTROL
Architecture Lineage
SCN-024 EVIDENCE CHAIN
KMAP V21 · UPDATE 21 COMPLETE · INTEGRATIONS & INTEROPERABILITY
KMAP V20 · UPDATE 20 COMPLETE · CUSTOMER WORKSPACE & ENTERPRISE CONTROLS
KMAP V19 · UPDATE 19 COMPLETE · GOVERNED AUTONOMY
KMAP V18 · UPDATE 18 COMPLETE · RESOURCE OPTIMIZATION
KMAP V17 · UPDATE 17 COMPLETE · FLEET OPERATIONS
KMAP V22 · UPDATE 22 COMPLETE · MISSION INTELLIGENCE & DECISION CENTER
KMAP V25 · UPDATE 25 COMPLETE · FULL CUSTOMER-READY KMAP