Quick Reference

The sidebar follows the operating chain — Registry → Integration → Scheduling → Governance → Administration, with Message Protocol beside Integration. All 27 models are reachable.

Group Theme Models
Registry blue ApplicationInstance · Connector · CanonicalEntity · EntityOwnership · EntityMapping · HealthCheck
Integration purple EventDefinition · EventMessage · RouteDefinition · FieldMapping · DeliveryAttempt · DeadLetterItem
Message Protocol purple Subscription · RouteDecision · Acknowledgement · MessageReconciliation (see 04)
Scheduling green ActionDefinition · JobDefinition · Schedule · JobExecution · SyncCheckpoint · RetryPolicy
Governance red ControlDefinition · ControlExecution · GovernanceException · ExceptionAction
Administration gray AuditRecord

The exploration demo data — the orchestrator instance (port 5050)

This is the data of the orchestrator instance (also the live orchestrator.dslcore.net). Network instances hold their own data: orchestrator_r9 (the work_supply network) is loaded from its manifest and fills with messages as the network runs — see 04 — Message Protocol; orchestrator_work_supply (work_supply_00) is loaded from that network's system.manifest.yaml (its entity_sync section).

The seed wires the Exploration Assurance Suite (eis / epa / elwpm) together and walks the four spec acceptance flows. 103 rows across the 23 entity-sync models (the message-protocol tables stay empty in this instance).

Registered applications

Code Type Status Role in the story
orchestrator Infrastructure Healthy The control plane itself
eis DSLCore Healthy Producer of screening.opportunity.approved
epa DSLCore Degraded Downstream assurance; its finance import is stale
elwpm DSLCore Healthy Authoritative for tenement licence state
erp External Unknown Owns budget actual_cost; connector timing out
gis Legacy Disabled Legacy inbound webhook, awaiting migration

The four flows in the data

Flow What to look at Result
1 — Screening approval fans out EVT-0001 → two DeliveryAttempt rows (routes RTE-SCREENING-APPROVED-EPA / -ELWPM) Both Succeeded; project PRJ-COPPERFIELD upserted into EPA and ELWPM
2 — Licence risk propagates Job evaluate_elwpm_obligations (EXE-0002) emits EVT-0002; route RTE-LICENCE-RISK-EPA Delivered to EPA as a project risk (condition complianceRisk in [High,Critical] met)
3 — Reconciliation finds a mismatch CTL-TENEMENT-RECON execution CEX-0002 (Fail) on tenement E70/1234 Raises EXC-0001 (High) — EPA copy drifted from ELWPM
4 — Correction is verified Rerun CEX-0003 (Pass); EXC-0001 actions Created→…→Verified→Closed Exception Closed; verified by rerun-and-pass

Supporting detail worth clicking

  • Duplicate handling — EVT-0001-DUP is Ignored / duplicate=true (dedup by event_sid).
  • Dead letter — EVT-0004 fails 3/3 deliveries (503) → one DeadLetterItem (Open) → integration exception EXC-0003 (Acknowledged).
  • Freshness — checkpoint EPA-FINANCE-IMPORT is Stale (~52h) → CTL-FINANCE-FRESH fails (CEX-0004) → data-quality exception EXC-0002 (Investigating, still open).

Key demo codes

Code Meaning
CON-DSLCORE DSLCore internal HTTP connector (bidirectional, bearer token)
PRJ-COPPERFIELD The exploration project shared across eis/epa/elwpm
E70/1234 The tenement reconciled between ELWPM (authoritative) and EPA
RETRY-STANDARD / RETRY-FAST 3-attempt / 2-attempt back-off policies
SCH-HEALTH / SCH-OBLIGATION / SCH-RECON 5-min health / daily 06:00 obligation eval / daily 07:00 reconciliation
EXC-0001..0003 The three governance exceptions (Closed / Investigating / Acknowledged)

Status vocabularies (enums)

  • ApplicationInstance.operational_status — Unknown · Healthy · Degraded · Unavailable · Disabled
  • EventMessage.status — Received · Queued · Processing · Delivered · PartDelivered · Failed · DeadLetter · Ignored
  • DeliveryAttempt.status — Pending · Running · Succeeded · Failed · Skipped · DeadLetter
  • DeadLetterItem.status — Open · Retrying · Resolved · Ignored
  • Schedule.schedule_type — Cron · Interval · OneTime · · misfire_policy — RunImmediately · Skip · Reschedule
  • JobExecution.status — Queued · Running · Succeeded · Failed · TimedOut · Cancelled · Skipped
  • SyncCheckpoint.status — Unknown · Current · Stale · Failed
  • ControlDefinition.control_type — Existence · Absence · Reconciliation · Freshness · Timeliness · Threshold · Completeness · Cardinality · State · Sequence
  • ControlExecution.status — Queued · Running · Pass · Fail · Error · Skipped
  • GovernanceException.status — Open · Acknowledged · Investigating · Remediation · Resolved · Verified · Closed · Accepted
  • Severity (controls & exceptions) — Low · Moderate · High · Critical

Rules of thumb

  • The orchestrator never holds master business data. If you find yourself wanting to store the content of a domain record here, store a mapping or an event instead and let the owning app hold the record.
  • Authoritative owner is single. For any entity/field/effective period there is exactly one authoritative application (EntityOwnership). Everything else is a replicated copy that a reconciliation control can check.
  • A finding is not fixed until a control says so. Drive exceptions to Resolved, then let the rerun move them to Verified before Closed.
  • Secrets are references. Connectors carry a credential_reference (secret://…) — never a raw secret value.
  • Definitions here, execution in the engine. Routes, subscriptions, controls and schedules are definitions; an instance started with ORCHESTRATOR_ENGINE=1 executes them and records every attempt, execution and exception here (see the Overview's build status).
  • Follow one flow by its correlation. Every message of one business flow carries the same correlation id — filter Event Messages by it, or watch the control panel's message flow.