Delivery case studies
Case studies record what a delivery team observed. Each card states its evidence maturity; partner-ready studies additionally publish immutable source references, receipts, repeatable verification, and explicit boundaries.
The .23 Release: Synchronized Hardening Across 18 Repositories
Internal account of using 4 local-mac cubicles and parallel Ozzy Dev worktree waves across 18 repositories. Repository counts and collision outcomes are team-reported while the public evidence packet is pending.
The Case Study Contract
Every partner-ready study adheres to the Nexartis four-point evidence standard. Internal dogfood may describe a measured run while its public evidence packet is still pending.
- Cites signed Ed25519 receipt IDs (
rc-…). - Pins live Git commit SHAs and GitHub PR URLs.
- Documents explicit negative boundaries & what is not claimed.
- Demonstrates zero split-brain or branch clobbering.
Ecosystem & Architecture Studies
Earned Coherence — Jade Planner × Ozzy Dev
Workspace C internal dogfood: approved planning intent in Jade becomes a SHA-pinned packet, lifecycle, mutation proposal, and offline-verifiable Trust receipt in Ozzy Dev. Template for every future Jade/Ozzy pair.
Autonomous Media Suite Delivery: Cloudflare Edge & Real-Time Sync
Internal account of multi-package delivery across StreamCube, BroadcastCubi, Showrunner, and Kraken Durable Objects. Regression and playback results are team-reported while the public evidence packet is pending.
Authoring an Evidence-Linked Case Study
Case studies reflect measured reality rather than hypothetical designs. Follow the established protocol when documenting a new platform milestone:
Register the study slug in $lib/case-studies.ts with stack tokens.
Reference an attested D1 workspace ULID and verifiable receipt id.
Confirm offline WebCrypto verification of the Ed25519 signature.
Explicitly detail the negative scope and what was not claimed.