Outcome
Specify trusted delivery of separately released graphics/audio/content resources without allowing servers to deliver executable client code or shaders.
Scope and normative requirements
- Versioned manifest identity, server/release/content association, stable resource IDs, path-independent type, size, digest, compression, chunks, priority, dependencies, required notices metadata where applicable, and complete-manifest digest.
- Request/response/chunk/commit/cancel/resume semantics over dedicated prioritized QUIC streams with exact limits and integrity checks.
- Cache namespace/trust behavior tied to authenticated server identity and manifest/release; atomic publication only after full verification.
- Allowed resource types/formats and explicit prohibition of native code, scripts, dynamic libraries, arbitrary WGSL/shaders, paths, or configuration overrides.
- Eviction/offline/missing/corrupt/version mismatch and reconnect behavior.
Acceptance criteria
- Go/Rust fixtures and end-to-end tests cover empty/large manifests, missing/chunked/resumed resources, corruption, truncation, compression bomb, wrong identity/digest/type, stale manifest, slow peer, and disk failure.
- Bulk transfer cannot starve gameplay streams and all counts/bytes/ratios/queues are bounded.
- Client renderer sees only verified immutable provider entries.
- Manifests carry immutable release coordinates/digests but do not blanket-relicense assets.
- Security review covers path traversal, cache poisoning, resource exhaustion, downgrade, and server identity changes.
Dependencies and parallelization
Depends on transport #2/common types #3. Server resource service and client cache/provider build in parallel.
Licensing and scope boundary
Protocol schemas, specifications, fixtures, and generators are MIT. Verified original past work by an approved MIT provenance grantor may be migrated under the recorded provenance grant. Compiled content artifacts are specified by content-toolkit; this repository owns network contracts only.
Outcome
Specify trusted delivery of separately released graphics/audio/content resources without allowing servers to deliver executable client code or shaders.
Scope and normative requirements
Acceptance criteria
Dependencies and parallelization
Depends on transport #2/common types #3. Server resource service and client cache/provider build in parallel.
Licensing and scope boundary
Protocol schemas, specifications, fixtures, and generators are MIT. Verified original past work by an approved MIT provenance grantor may be migrated under the recorded provenance grant. Compiled content artifacts are specified by content-toolkit; this repository owns network contracts only.