Station Contracts
Provider-independent execution capabilities that return evidence instead of owning projects
A Station is a registered person, device, specialist product, agent surface, or deterministic tool that accepts bounded Work Orders.
A Station declares:
station_id
capability_ids and versions
accepted input types
produced Artifact/Return types
locality/device requirements
permissions
authority
cost/resource class
verification contract
timeout/retry/rollback
privacy/storage
health
receipt schema
accessible representation
Examples include Codex, VideoBoss, a local model, a renderer, a desktop machine, or a human reviewer.
Principles
- Stations do not own Project Core.
- Provider-specific state remains behind an adapter.
- Unavailable state is truthful.
- A Station cannot expand authority.
- Every consequential Return includes evidence and cost.
- The Switchboard connects Stations; it is not another project database.
Routing
ZEKE selects a Station by capability, locality, privacy, cost, health, evidence requirement, and authority.
The user can inspect why a Station was selected and override within policy.
Station contracts let specialist products remain excellent in their domains while participating in one project and receipt system.
Source register
- N15-S01 — Glyphd V1 Canon Recovery and Gap Audit.
ZEKE-V1-CANON-RECOVERY-AND-GAP-AUDIT-v0.1.md - N15-S02 — Glyph Desk Master Specification.
GLYPH-DESK-MASTER-SPEC.v1.md - N15-S03 — POLYGLYPH/Glyphd shared-contract audit.
Pasted markdown (2).md