Concept image. Normative behavior lives in spec/.
| Document | Purpose |
|---|---|
| Architecture | System boundaries, package map, and execution paths |
| Runtime model | Normative roles, states, routing, usage, and storage boundary |
| Protocol | Normative request, events, errors, usage, and extensions |
| OpenAPI | Machine-readable HTTP surface |
| Roadmap | Completed v0.1 scope and explicitly deferred work |
| Document | Purpose |
|---|---|
| Provider adapters | Safe adapter configuration and provider-specific behavior |
| Adding a provider | Public evidence and conformance checklist |
| Gateway integration | Authentication, tenant, quota, and usage boundary |
| Model catalog | Versioned capability snapshots and model discovery diff |
| Testing | Reproducible local, SDK, container, and security verification |
| v0.1.0 verification | Release gate results and explicit residual limits |
| v0.1.0 release notes | Shipped scope, verification summary, and platform limitation |
| Document | Purpose |
|---|---|
| Threat model | Shared data-plane assets, threats, and deployment controls |
| Provider evidence | Dated public sources used by clean-room adapters |
| Security policy | Vulnerability reporting and supported security boundary |
| Public contribution policy | Data safety, compatibility, and verification requirements |
The four editorial images under assets/ were generated through AnyCap and optimized to 1600 x 900
JPEG for GitHub delivery. Each image has a neighboring .prompt.md file containing its public
prompt, generation request ID, processing record, and independent image-read result. Exact protocol
facts remain in Mermaid, OpenAPI, tests, and normative text rather than generated pixels.