Home Contact
Universal Substratev1.4
/
For agents Markdown

38. Configuration compiler, physical-model registry, and operating-envelope solver

A configuration is not certified merely because its parts are listed. The compiler materializes the exact installed graph, validates ports and topology, propagates resource/control/safety paths, evaluates effectivity and operating-envelope predicates,…

Concept & directionLNK

A configuration is not certified merely because its parts are listed. The compiler materializes the exact installed graph, validates ports and topology, propagates resource/control/safety paths, evaluates effectivity and operating-envelope predicates, invokes registered quantitative solvers and emits a minimal proof graph for every capability result.

Diagram of a deterministic capability compiler consuming configuration, operational state, function authority and operating-envelope facts, then returning available, unavailable or indeterminate capability with proof.
Picture 12

Unknown input and compiler error remain distinct; neither can authorize execution.

#38.1 Effective graph materialization

Table
Deterministic graph compilation
compile(configurationId, contextCheckpoint, packLock):
  verify configuration, registry and pack digests
  materialize item occurrences, ports, connections, software and calibrations
  evaluate effectivity predicates using four outcomes TRUE/FALSE/UNKNOWN/ERROR
  reject duplicate exclusive occupancy and forbidden composition cycles
  validate frames, joints, geometry and configuration-specific transforms

  for each realized connection:
    unify port family, medium/carrier, direction, dimension and protocol
    intersect voltage/current/pressure/flow/speed/torque/load/range constraints
    require a non-empty operating intersection and declared protection/failure behavior

  build structural, support, energy, material, thermal, data, control,
        kinematic, safety and utility subgraphs
  identify strongly connected components; require a registered solver for each loop
  propagate source availability, conversion paths, observability, authority,
        fault overlays and environmental/resource prerequisites to a fixed point
  evaluate registered quantitative constraints and operating envelope
  emit CapabilityCompilationReceipt and minimal explanation DAG
OutcomeDefinitionAuthorization meaning
TRUEall required facts established and every required solver converged inside its validity domainmay contribute to authorization; never authorizes alone
FALSEat least one required condition is established false or a hard contradiction existscapability unavailable
UNKNOWNrequired fact absent, stale, conflicted, withheld or too uncertainfail closed; request evidence or fallback
ERRORinvalid definition/input, resource limit, unsupported operator or solver non-convergencefail closed; engineering incident

For allOf: FALSE dominates, then ERROR, then UNKNOWN, otherwise TRUE. For anyOf: TRUE dominates, then ERROR, then UNKNOWN, otherwise FALSE. Negation maps TRUE/FALSE and preserves UNKNOWN/ERROR. Pack evaluation is stratified; recursion through negation is rejected.

#38.2 Port and connection unification

Constraint familyExamplesFailure code
topologicaloutput-to-input, source/sink, fan-out, exclusive slot, bus membershipRTR-CONFIG-TOPOLOGY
carrier/mediumelectricity AC/DC, fuel grade, hydraulic fluid, air/water/data/protocolRTR-CONFIG-MEDIUM
dimensionalvoltage/current, torque/speed, pressure/flow, force/displacementRTR-CONFIG-DIMENSION
rangecontinuous/peak limits, temperature, pressure, voltage, RPM, load and durationRTR-CONFIG-RANGE
geometryconnector, shaft alignment, gauge, mounting pattern, clearance and motion envelopeRTR-CONFIG-GEOMETRY
timing/protocolbus rate, message set, synchronization, latency, update and watchdogRTR-CONFIG-PROTOCOL
protectionfuse/breaker/relief/guard/interlock, fault containment and disconnectRTR-CONFIG-PROTECTION
authorityinstaller approval, software license, key/certificate, release-to-serviceRTR-CONFIG-AUTHORITY

#38.3 CapabilityCompilationReceipt

Table
Capability result with machine-checkable explanation
CapabilityCompilationReceipt {
  compilationId, compilerVersion, compilerBinaryDigest,
  configurationId, configurationDigest, contextCheckpoint,
  registryLockDigest, domainPackLockDigest,
  requestedCapabilities[], realizedGraphDigest,
  resultByCapability[{capabilityId, outcome, limitingConstraints[],
                      proofNodeRefs[], unresolvedFacts[], marginSetRef?}],
  solverRuns[], findingCodes[], resourceUsage,
  startedAt, completedAt, outputDigest
}

ProofNode {
  nodeId, ruleOrSolverRef, outcome, inputNodeRefs[], inputRecordRefs[],
  constraintValues?, explanationTermRef, sensitiveEdgePolicy
}

The public explanation is a redacted projection of this DAG. Redaction must not
change the underlying outcome, and a non-interference test must prove hidden
facts cannot be inferred through node counts, errors or timing classes.

#38.4 Physical-model registry

Table
Versioned equations and computation receipt
PhysicsModelDefinition {
  modelId, version, modelFamily, equationSetDigest,
  stateVariables[], algebraicVariables[], inputs[], disturbances[], parameters[],
  constraints[], invariants[], eventGuards[], resetMaps[],
  supportedConfigurationPredicates[], validDomainRef,
  initializationProcedureRef, solverProfile,
  verificationEvidenceRefs[], validationEvidenceRefs[]
}

ComputationRun {
  runId, modelRef, exactInputRecordIds[], inputArtifactDigests[],
  configurationId, operationId?, validTime, dataCutoff,
  parameterSetDigest, solverBinaryDigest, solverOptions,
  randomSeeds[], convergenceReport, resultArtifactDigest,
  qualityDisposition, invalidatedBy[]
}
Domain familyReference equation/model obligations
rigid/multibodymass matrix, constraints/contact/friction, forces/torques, energy balance and integrator
road + RCwheel/ground speed, slip low-speed policy, tire/contact, grade/wind, gearing, braking and measurement boundary
railconsist/coupler forces, resistance, adhesion, brake propagation, route/gauge and signaling regime
marine/subsurface6-DOF inertia/added mass, hydrostatics, damping, current-relative speed, propulsion, buoyancy/ballast and pressure envelope
air + eVTOLair-relative state, atmosphere, aerodynamic coefficients, rotor/propulsor domain, ground effect, transitions and failure cases
lighter-than-airgas/air density, envelope volume/pressure/temperature, ballonet/ballast, tether, static lift and aerodynamic propulsion
spaceframe/epoch/time scale, gravity/perturbations, mass/propellant, thrust/attitude, covariance and propagator
robot/manipulatorkinematics/dynamics, joint/torque/thermal limits, singularity, collision, payload inertia and tool frame
tetheredtension-only/slack modes, length/payout, elasticity/catenary/drag, anchor margin, conductor limits and break dynamics
transforming hybridhybrid automaton with mode invariants, guards, intermediate hazards, reset map and active equation set
Table
Models are bounded claims
An equation can be correctly implemented and still be invalid for the current scale, Reynolds number, sea state, tire regime, propeller advance ratio, atmosphere, payload, structural mode or controller. Every output reports both numerical convergence and model applicability.

#38.5 Operating-envelope predicate AST

Table
Quantitative and stateful operating envelope
EnvelopeDefinition {
  envelopeId, version, applicableConfigurationPredicates[], modes[],
  entryPredicate, continuePredicate, hardExitPredicate,
  hysteresisPolicy, entryDwell, softExitDwell,
  requiredEvidenceFreshness, requiredProbabilityOrBound,
  monitorDefinitionRef, fallbackRef
}

Predicate := allOf | anyOf | not |
  compare(quantity, operator, threshold, uncertaintyPolicy) |
  within(value, interval) | rateWithin(value, interval) |
  geofence | routeSegment | modeIs | configurationHas |
  resourceRemaining | healthState | linkQuality |
  modelValidatedFor | customRegistered

For constraint g_i(x,c) <= 0:
  inside only when the declared uncertainty rule is satisfied.
  probabilistic profile: P(g_i <= 0) >= p_required.
  bounded profile: entire interval inside entry bound => TRUE;
                   entire interval outside exit bound => FALSE;
                   otherwise UNKNOWN.
  • Hard exit triggers immediately. Soft exit respects declared dwell. Entry uses stricter boundaries than continuation to prevent chatter.
  • Monitor output includes current outcome, normalized margin per constraint, limiting constraint, uncertainty, predicted time-to-exit, fallback deadline and source checkpoint.
  • Unknown is handled per constraint policy but cannot be silently treated as inside for a safety-critical capability.
  • Road friction/visibility, rail authority/braking, under-keel clearance/sea state, blimp lift/wind, submarine pressure/energy, robot workspace/collision, tether tension/anchor and spacecraft power/thermal/ephemeris all use the same predicate machinery with domain-specific terms.

#38.6 Digital-twin state and confidence vector

Table
Digital twin as an evidence-qualified estimate
TwinStateEstimate {
  twinId, physicalAssetId, configurationId,
  stateVectorDefinitionRef, estimateArtifactDigest,
  covarianceOrEnsembleArtifactDigest, observedAt, dataCutoff,
  estimatorDefinitionRef, modelDefinitionRef, parameterSetDigest,
  inputSegmentRefs[], latencyNs, unobservableStates[],
  divergenceTests[], applicabilityState, modelState
}

modelState in {
  UNVERIFIED, VERIFIED, CALIBRATED, VALIDATED_IN_DOMAIN,
  MONITORED, OUT_OF_DOMAIN, DIVERGED, INVALIDATED
}

Confidence is a vector, never one percentage:
  implementation verification; convergence; parameter identifiability;
  calibration recency; validation-domain coverage; input quality;
  observability; model-form uncertainty; domain proximity;
  clock freshness; divergence status.