Ordivon Host
Replace the cognition or process without replacing the admitted semantic work claim—and without copying foreign owner truth into Host.
The durable semantic work-continuity component for Ordivon. Host preserves what work is being continued and what was last claimed, while cognition, physical execution, source currentness, external occurrence, and domain acceptance stay with their own owners.
- Projected status
- Operational owner-trusted local engineering component; pre-1.0 public interface
- For
- Builders and Agent workflows that need semantic work to survive conversation/session replacement without adopting a workflow platform, central coordinator, Runtime proxy, or generic cognition host.
- Evidence for status
- The 0.3 contraction removed unconsumed Goal coordination, foreign execution, legacy execution workloads, generic capability policy, and Runtime-integration residue. Current 0.4.x then makes external semantic continuity first-class: one WorkingCheckpoint can survive client replacement with revision-coherent resume and exact response-loss replay, while every Runtime/Git/domain hint remains explicitly subject to owner-native revalidation.
Question this project must answer
Which bounded semantic work claims must survive session replacement, and which Runtime, Git, Provider, or domain facts must instead be revalidated with their native owners?
Current operating model
Standing in this projection
Operational owner-trusted local engineering component; pre-1.0 public interface
Operational with schema-v5 Journal/CAS and exactly six public MCP Tools. Host is intentionally narrower than its historical designs: it is not a universal coordination ontology, scheduler, executor, Runtime client, source engine, cognition host, or cross-owner truth service.
Capability evidence
What this project owns
Facts, products, or methods maintained here.
- Task identity and revisioned projection
- Host Journal/CAS admission
- WorkingCheckpoint external continuity
- Opaque extension durability
- Host-local integrity, inspection, and deployment receipts
What it leaves elsewhere
Responsibilities and claims outside its boundary.
- No universal coordinator or scheduler
- No model–Tool/cognition execution
- No Runtime proxy or source mutation
- No foreign currentness or domain-world truth
Questions and current judgments