TERMINUS

Surfaces execution-substrate posture without substituting architecture validation (catalog-terminus-validator).

LiveCatalogue status

ObservingRuntime posture

ExecutionJob substrate observer: queues, leases, approvals adjacency, and messaging fabric counters for the tenant runtime.

Open console Book a Demo

Expanded capabilities

Observe ExecutionJob substrate: queues, leases, approvals adjacency
Surface messaging fabric counters without dispatching
Pin RECORD_ONLY findings for substrate attention
Stay observing-only — no send, publish, or approval decisions
Complement architecture validation (terminus-validator) without replacing it

How they learn & improve

TERMINUS improves which substrate signals matter from operator pins — it never ‘heals’ queues by skipping governance.

Read tenant ExecutionJob and adjacency counters.
Pin findings when leases/approvals pressure needs attention.
Recalibrate alert keys after human-applied learning candidates.

How they work together

TERMINUS watches the runtime floor while HERMES watches cross-stage flow and WORKFLOW owns durable transitions.

WORKFLOW (persisted execution)Observes persisted job/run state.
HERMESCorrelates substrate pressure with flow health.
Approval queueShows adjacency to pending human decisions.
Terminus (architecture validation)Separates substrate observation from architecture optimisation.

Practical benefits

Know when workers are stuckOps sees lease pressure before customers feel silent failures.
Approvals adjacencyQueue depth next to pending approvals explains why work isn’t moving.
Pins without panic automationRECORD_ONLY pins create operator attention — not auto-cancels of jobs.

Learning and improvement stay human-visible: candidates are RECORD_ONLY until an operator reviews and applies them. Sensitive sends, publishes, and approvals never run silently.

TERMINUS

Expanded capabilities

How they learn & improve

How they work together

Practical benefits

Related agents