Compiled execution
- RunContext is the runtime authority.
- Plan compilation and validation precede execution.
- CLI and HTTP use the same compiled entrypoint.
- Policy, execution and verification evidence remain inspectable.
SPINE is a RunContext-governed orchestration runtime and multi-agent backbone. Its adopted compiled path separates planning, policy, execution and verification while keeping broader experimentation surfaces explicitly outside that production path.
task -> SkillCompiler -> PlanArtifact -> PlanValidator and policy tags -> execute_compiled_plan(...) -> PlanExecutor -> RunContext evidence and result state Exposed through: - CLI: python -m spine.orchestrator execute ... - HTTP: POST /api/orchestrator/execute
cmd_runOODALoop.run()run_scenario.pyImplemented surfaces are not presented as adopted compiled transports merely because they exist.
| Claim | Evidence class | Boundary |
|---|---|---|
| Compiled CLI and HTTP execution path | Implemented and documented in current private source | Not re-executed by this static showcase change |
| RunContext authority inversion and plan validation | Source and public showcase documentation | Current proof page summarizes, it does not replace the source contracts |
| 7-tier memory and broader supporting systems | Implemented/source-documented | Some backends are optional and environment-dependent |
| 3650+ tests | Source README claim at the pinned source head | No new test run was performed during publication |
| Seven public interactive demos | Public showcase tree | Demos are explanatory; they are not a production runtime |
Freshness rule: this page is the dated recruiter-facing evidence entry. The larger showcase remains valuable feature and design documentation, but it is a point-in-time public projection and does not imply that every later private-source capability has been republished.