CASE STUDY · PRIVATE
ecosystem backends
Three private TypeScript backends: a versioned core package with semver and consumer checks, a better-auth integration, and a Supabase CMS that already speaks MCP.
Status ruling private, gate under NDA closed source, reviewable under NDA
Problem
The portfolio's public surface is Rust and static sites; the backend competence claim needed real, measured full-stack infrastructure behind it, and the client work that produced it is under NDA.
Build
- ecosystem-core: a versioned SDK organised around an injection contract, with build, typecheck, contract, semver, dist, ghost and consumer checks in its verify chain.
- ecosystem-auth: a better-auth integration whose suite is larger than its source tree: 209 test files against 8 source files.
- content-management: a Supabase CMS with an MCP surface (the same protocol the offers sell), migrations and a media pipeline.
Outcome
- 354 tests passing across the three repositories (242 + 28 + 84), every gate green at its pinned commit. None is on GitHub: closed source is the constraint, and naming it is what makes the claim checkable later.
- The honest form, per the operator's ruling: describe the architecture and the measurements, offer NDA review of the repositories and the gates, and never gesture vaguely at "internal projects".
Provenance
| ecosystem-core gate | 242 passed, 0 failed; verify chain exit 0 | npm test at 1f1be6e, 2026-10-22 |
|---|---|---|
| ecosystem-auth gate | 28 passed, 0 failed | npm test, 2026-10-22 |
| content-management gate | 84 passed across 6 files | npm test, 2026-10-22 |
Reproduce
NDA review shows the three repositories, the gates and the verify chain live. No public link exists, and this study does not pretend one does.
Private repository: a walkthrough is available on request instead of a link.
From the documentation
A backend trio (auth, core, integrations) shared by three TypeScript surfaces, so the auth surface is one contract and not three copies.
walkthrough knowledge, repository private
The core package is consumed as a pinned dependency by its surfaces, which is what keeps three products on one contract without a monorepo merger.
walkthrough knowledge, repository private