Skip to main content

Choco Platform: Staging-Ready Milestone

What Shipped

The Choco documentation platform — a verifiable, CRDT-native, MCP-first system — has crossed from architecture phase to staging-ready deployment across all critical services.

By the Numbers

MetricValue
Services with CI pipelines5 active (path-filtered, per-service)
ExternalSecrets configured10 (covering all production secrets via AWS SM)
Database migrations8 (PostgreSQL + ClickHouse schemas)
NATS JetStream streams11 (2 with infinite retention for compliance/monetization)
Helm values files12 (covering all deployable services)
Flux HelmReleases (staging)8 services deployed to choco-staging namespace
Acceptance test steps implemented99 (zero TODOs remaining in 6 feature files)
Go-live checklist items60+ across 10 categories

Architecture Highlights

  • Golden Ticket singleton (golden-press): Ed25519 signing, advisory lock(42), anti-gaming rules, max 5 tickets system-wide — now with aligned schema and integration tests
  • Event consumer framework (choco-consumers): 7 real PostgreSQL/HTTP/OTel adapters replaced log-only stubs — ready for ClickHouse/Tantivy swap at scale
  • TypeScript SDK (@choco/sdk): 50+ API methods, PKCE OAuth, WebSocket CRDT, golden ticket types, 20 tests
  • Zero-trust networking: Linkerd mesh with 8 service profiles, per-route timeouts, retry budgets disabled for writes

What’s Next

Production deployment requires: EKS cluster provisioning, DNS configuration (choco.tools → gateway, api.choco.tools → ALB), secret ceremony for Ed25519 keys, and the go-live checklist sign-off from 4 roles. The E2E smoke test runs nightly against staging.