Capability Map¶
bijux-canon-runtime turns lower-layer outputs into governed runs by applying
manifest authority, execution policy, verification arbitration, causal
recording, persistence, and replay acceptance. Its capabilities concern who
may do what under which retained evidence.
flowchart LR
manifest["manifest + tenant + policy"]
resolve["dataset + dependencies + plan"]
execute["mode-specific execution"]
verify["verification + arbitration"]
freeze["finalized causal trace"]
persist["DuckDB + artifact payloads"]
replay["verdict + semantic diff"]
manifest --> resolve --> execute --> verify --> freeze --> persist --> replay
Authority and execution capabilities¶
| Capability | Owning area | Produced evidence |
|---|---|---|
| Manifest authority | contracts/, model/flows/ |
flow, tenant, agents, dependencies, gates, determinism, replay policy |
| Dataset admission | dataset contracts and planning | exact descriptor, deprecation decision, dataset identity |
| Dependency resolution | application planner | normalized ordered steps and immutable plan hash |
| Environment capture | observability capture and classification | environment, package, resolver, and policy fingerprints |
| Mode selection | preparation and execution policy | plan, dry-run, live, observe, or unsafe semantics |
| Authority-bearing context | runtime/context.py, core/authority.py |
permitted effects, tenant, budgets, store identity |
| Lower-layer execution | step, retrieval, reasoning, and agent executors | correlated outputs, errors, evidence, claims, tool calls |
| Budget enforcement | runtime budget and entropy models | resource and entropy use, exhaustion, refusal or warning |
Verification, persistence, and replay capabilities¶
| Capability | Owning area | Produced evidence |
|---|---|---|
| Causal recording | trace recorder and event causality | ordered events, hashes, causal tags, checkpoints |
| Verification | verifier orchestration and rules | per-engine findings, violated rules, targets, costs |
| Arbitration | verification arbitration | policy fingerprint, participating engines, final decision |
| Trace finalization | execution lifecycle finalizer | immutable trace, certifiability, termination state |
| Incremental persistence | migration-owned DuckDB store | runs, steps, events, tools, artifacts, evidence, claims, entropy |
| Resume | lifecycle preparation and state tracker | restored indices and state after the last completed checkpoint |
| Artifact lineage | artifact contracts and store | immutable identity, hash, producer, parentage, tenant, scope |
| Replay analysis | replay support and observability analysis | envelope comparison, semantic diff, acceptability verdict |
| Drift analysis | correlation, invariants, comparative analysis | earliest structural, temporal, dataset, policy, or content divergence |
Mode capability boundary¶
Plan mode resolves authority without allocating a run. Dry run exercises the recording and persistence path with simulated effects. Live mode requires verification coverage. Observe mode governs evidence supplied by an external execution. Unsafe mode records reduced guarantees and remains distinguishable from live authority.
| Mode | May invoke configured effects | Required authority/evidence | Claim supported |
|---|---|---|---|
| plan | no | valid manifest, dataset, policy declarations and dependency resolution | an immutable plan can be resolved; no run or effect claim |
| dry-run | simulated only | execution store plus declared simulation behavior | recording/persistence path under simulation, not live integrations |
| observe | no control over host effects | host-supplied events plus applicable verification policy | governance of the events actually supplied, not omitted activity |
| live | yes, through configured integrations | store, policy, budgets, adapter authority, effect receipts and verification | governed execution for the recorded integrations and rules |
| unsafe | effects under explicitly reduced guarantees | store and visible relaxed-policy declaration | retained execution evidence that is not equivalent to governed live work |
Mode is part of the result identity. A successful plan cannot be promoted to a run, a dry-run trace cannot certify live permissions, and an unsafe result cannot be relabelled after execution.
Composition capability¶
Runtime combines planning, execution, verification, persistence, recovery and replay through the installed v2 application-service composition:
| Composition | Current status | Evidence-backed interpretation |
|---|---|---|
| manifest admission and plan resolution | implemented | can be exercised without lower-package live calls |
| runtime behavior with injected executor seams | implemented and package-tested | establishes runtime authority, failure, verification and replay semantics |
| installed canonical live composition | implemented and installed-workflow tested | the v2 application service loads canonical ingest, index, reason, and agent adapters |
| HTTP v2 workflow and replay | implemented through durable jobs | shares application behavior, failures, pagination, and workspace authority with Python and CLI |
| HTTP v1 flow run and replay | contract validation with 501 response |
legacy schema/error compatibility, not execution |
The compatibility packages delegate to the canonical implementations and do not create extra capability. End-to-end claims remain bound to installed-wheel tests that execute the typed services without source-tree imports.
Interface availability¶
Python, CLI, and HTTP v2 provide governed application-service execution and
read-side inspection. The separately hosted v1 compatibility module provides
probes but returns 501 Not Implemented for flow run and replay. Schema
presence alone remains compatibility evidence, not execution evidence.
Runtime cannot undo external effects, reconstruct omitted host events, or make a passing verification rule set equivalent to factual truth. See Invariants for authority laws and Known limitations for execution, determinism, verification, persistence, and deployment boundaries.