Evidence-backed case studies
Research papers argue; case studies prove a run happened. Explore how Nexartis deploys autonomous agent waves, verifies multi-repo pull requests, and seals every step with Ed25519 cryptographic receipts.
The .23 Release: Synchronized Hardening Across 23 Repositories
How Nexartis used 4 isolated local-mac cubicles and parallel OzzyDev worktree waves to harden 23 core repositories, synchronize SDK dependencies, and eliminate merge collisions.
The Case Study Contract
Every published study adheres to the Nexartis four-point evidence standard:
- 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
Autonomous multi-package delivery across Streamcube, BroadcastCubi, Showrunner, and Kraken Durable Objects, verified through automated ABI regression drives and live playback testing.
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.