Forward-deployed product + AI systems

Recovered a live member platform without sacrificing trust.

Spiral Combat had a release-drift problem: customer-facing features were displaced and 19 public reader records were missing from a shared data store that also contained private records. The recovery restored the public assets, preserved the private rows, and added a safer production release gate.

Michael's role: product choices, safety boundaries, deployment decisions, and release acceptance.

Spiral Combat protected reader interface showing the Codex reading experience and member controls
Protected reader experience · release evidence capture
332 / 332 Automated tests passed
19 Public reader assets restored
0 Private rows changed
2 Paying-member sessions verified

The operating problem

The release could not be treated as a normal redeploy.

A stale release had displaced member-platform features. The same recovery also had to restore public reader records in a shared reader_assets store without deleting or rewriting two private records. A broad overwrite would have been faster, but it would have violated the trust boundary.

The real work was not “make the page come back.” It was to identify the customer promise, define what must remain untouched, restore only the missing public data, prove the release against live member paths, and leave a safer release mechanism behind.

Four decisions that changed the outcome

Detect. Protect. Restore. Prove.

  1. 01 · Detect

    Separate release drift from product failure.

    The working features still existed in the correct lane; the production release had fallen behind them.

  2. 02 · Protect

    Set the private-data boundary before repairing anything.

    Two private rows had to remain byte-stable while the missing public assets were restored.

  3. 03 · Restore

    Use a merge-only repair.

    Exactly 19 public rows were restored. No existing rows were deleted, and no private row was changed.

  4. 04 · Prove

    Promote only after customer-path evidence.

    Tests, protected readers, core tools, two paying-member sessions, runtime checks, and rollback all passed.

Honest ownership

What Michael led—and what the engineering agents did.

This is evidence of forward-deployed operating judgment. It is not a claim that Michael personally wrote every line of production code.

Michael Yap

Product and operating lead

  • Defined the member promise and acceptance criteria.
  • Set the merge-only private-data boundary.
  • Chose the production proof and rollback requirements.
  • Made the release and customer-risk decisions.
Codex-managed engineering agents

Implementation and verification

  • Reconciled the release lane and implemented the recovery.
  • Built and ran tests, guards, smoke checks, and automation.
  • Produced technical readbacks and deployment receipts.
  • Kept optional provider and customer-write paths disabled.

The system Michael had to reason across

One customer experience, six connected boundaries.

Evidence, not adjectives

What the release receipt actually proves.

Proved
  • The July 20 production release passed 332 automated tests.
  • Exactly 19 missing public reader rows were restored.
  • Two private rows remained byte-stable after the repair.
  • Protected readers and the Board, Bet Plan, and Fighter Vault loaded.
  • Two paying-member sessions received full Fight Intelligence access.
  • A rollback deployment and stricter production guard were recorded.
  • Member authentication and account-aware library access were reverified on July 21.
Not claimed
  • No revenue lift or customer-growth result is attributed to this release.
  • No claim that Michael personally authored all production code.
  • No claim that AI provider calls ran during the recovery.
  • No claim of permanent availability beyond the dated production checks.
  • No claim that a successful release proves conventional senior full-stack depth by itself.

Evidence basis: Spiral Combat Member Platform Recovery Coordination Receipt dated July 20, 2026; project README; Fight Intelligence Experience Release dated July 15, 2026; and Release Safety Standard. Production authentication and library access were rechecked in an authenticated session on July 21, 2026.

Hiring signal

Where this evidence is most relevant.

Forward-deployed AI or product

Ambiguous customer workflows, production constraints, and accountability beyond the demo.

AI systems and operations

Choosing where automation belongs, where human approval stays, and how failures stop safely.

Founder-operator or zero-to-one product

Connecting customer value, business judgment, system design, and practical execution.