Doctrine Industries

System registry

Separate the powers

The system chain exists to prevent observation, modelling, evaluation, coordination, enforcement, and governance from collapsing into one opaque operator.

DI-SYS-LOOKOUT · observation

Lookout

specified

Observe external reality, acquire evidence, and preserve the provenance of each observation.

Authority boundary

Observation authority only; Lookout may record evidence but cannot evaluate, authorise, coordinate, or enforce action.

Dependencies

No system dependency declared.

Inputs

  • External events and conditions
  • Submitted records and source material

Outputs

  • Provenance-bearing evidence records
  • Observation gaps and acquisition warnings

Governing publications

DI-SYS-BLACKLINE · modelling

Blackline

defined

Convert evidence into explicit models of system state, uncertainty, relationships, and plausible trajectories.

Authority boundary

Modelling authority only; Blackline represents reality but cannot treat its model as reality or select an authorised outcome.

Dependencies

Lookout

Inputs

  • Provenance-bearing evidence records
  • Declared modelling assumptions

Outputs

  • Versioned system-state models
  • Uncertainty and contradiction registers

Governing publications

DI-SYS-VERDICT · evaluation

Verdict

defined

Evaluate claims, options, policies, and consequences against declared criteria and authority constraints.

Authority boundary

Evaluation authority only; Verdict may produce a reasoned assessment but cannot authorise itself or execute the selected action.

Dependencies

Blackline · Codex

Inputs

  • Versioned system-state models
  • Evaluation criteria and authority references

Outputs

  • Reasoned evaluations
  • Conditions, dissent, and unresolved uncertainty

DI-SYS-STRUCTURA · coordination

Structura

specified

Translate authorised decisions into coordinated actors, dependencies, tasks, interfaces, checkpoints, and evidence obligations.

Authority boundary

Coordination authority within an approved decision envelope; Structura cannot expand the originating mandate or perform enforcement.

Dependencies

Verdict · Codex

Inputs

  • Authorised decisions and conditions
  • Available actors, capabilities, and dependencies

Outputs

  • Governed execution plans
  • Dependency, checkpoint, and handoff records

DI-SYS-BALF · enforcement

Balf

prototyped

Enforce authorised boundaries, validate interventions, and preserve consequential state transitions in an auditable ledger.

Authority boundary

Narrow enforcement authority granted by an explicit mandate; Balf must refuse ambiguous, stale, or unauthorised intervention.

Dependencies

Structura · Codex

Inputs

  • Governed execution plans
  • Authorised intervention requests

Outputs

  • Accepted or refused interventions
  • Auditable enforcement and state-transition records

DI-SYS-CODEX · governance

Codex

specified

Govern canonical definitions, operators, rules, authority references, evidence classes, and admissible interpretations across the system chain.

Authority boundary

Reference authority within each published scope; Codex constrains interpretation but does not manufacture evidence or legitimate its own authority.

Dependencies

No system dependency declared.

Inputs

  • Approved doctrine and authority sources
  • Versioned amendments and decision records

Outputs

  • Canonical rules and definitions
  • Conformance and supersession relationships

Structural rule

No layer may silently absorb another.

Observation is not evaluation. A model is not reality. Evaluation is not authorisation. Coordination is not enforcement. Enforcement is not self-legitimating. Codex is not evidence that its own rules are correct.

Read the system definition