JWT access, refresh-session controls, tenant-scoped requests.
Private build · deployed pre-launch
Case study · Aura
Ship the infrastructure.
Gate the activation.
Aura is a private multi-tenant social-content SaaS whose backend and data infrastructure were deployed before launch. I built tenant isolation, provider-routed generation, billing and metering paths, and a retryable publishing system—then kept public launch, real billing, and automatic live posting deliberately disabled.
Verified private release · 0.5.2.0
Deployed engineering, without launch theater.
265 tests passedGitHub Actions at private master d18186b
Backend deployedHealth-checked API and database infrastructure
Activation gatedNo public UI, live billing, or automatic posting loop
The evidence is intentionally split: implementation and deployment are verified; adoption and launch outcomes are not claimed.
Tenant and data boundary
Every capability starts with ownership.
The architecture keeps tenant identity attached to data access, provider credentials, usage, billing events, and publish attempts. The public diagram shows boundaries, not private schemas or deployment identifiers.
Content, strategy, queue, metering, and billing decisions retain user ownership.
Encrypted provider material and explicit gates sit before external effects.
Publishing state machine
The request path never performs the send.
A publish request claims work atomically and records an outbox event. A dispatcher performs the external effect later; attempt tokens make stale or duplicate events no-ops, and failed sends require manual requeue.
01
PendingDraft is eligible but has no external effect.
02
ClaimedA lock serializes competing queue mutations.
03
Outbox eventTransactional record survives request completion.
04
Attempt tokenStale and duplicate events become no-ops.
05 · gated
Send or holdFailures stop for manual review; automation remains disabled pre-launch.
Synthetic example
Product evidence without operational exposure.
This invented draft demonstrates the decision surface: content can be generated and queued, but external action stays visibly separated and gated. No live account, customer content, or private screenshot is shown.
Generation selects configured providers through one routing boundary instead of hardcoded model calls.
Usage and plan access are evaluated before work reaches an external adapter.
A failed send does not silently retry into an unknown external state.
Synthetic example · invented data
Weekly product insightAwaiting activation
“A reliable automation system makes the stop conditions as visible as the happy path.”
Tenant scoped · usage recorded · publish attempt not enabledHold
Verified / not claimed
Pre-launch means the boundary stays visible.
| Area | Status | Public claim |
|---|---|---|
| Backend and database | Verified | Deployed and health-checked private infrastructure |
| CI evidence | Verified | 265 tests passed at release 0.5.2.0 |
| Public frontend | Not launched | No public UI or demo |
| Billing and automatic posting | Gated | Implemented paths; real activation intentionally disabled |
| Customers, users, revenue | Not claimed | No adoption or commercial outcome claims |