Michael Chihlas
0d81e62ac4
PR #165 (legal/contact pages + MarketingFooter) merged as ba45cfe.
All code blockers for self-serve cutover are now on main.
Records the real Stripe live-mode activation blocker: user does not
yet have an EIN for ResolutionFlow, LLC, and Stripe requires a tax
ID before it will activate live mode. Applying via IRS.gov 2026-05-13.
Mailing-address decision (2026-05-12): user will enter their home
address into the Stripe business profile temporarily so live-mode
isn't blocked on the P.O. Box. This is a private Stripe field. The
public-facing TODO in ContactPage.tsx and PoliciesPage.tsx stays
"available on request" until the P.O. Box is purchased — explicitly
DO NOT put the home address on the public site. Stripe accepts
updating the address later without re-verification, so swapping
in the P.O. Box when it arrives is non-disruptive.
Nothing on the code side blocks live-mode flip. Apex DNS at
Namecheap remains pending but only matters once Stripe runs its
site-verification step, which happens after the business-profile
fields are accepted.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
.ai/ — dual-agent handoff system
ResolutionFlow uses two coding agents: Claude Code (primary) and OpenAI Codex (resume when Claude hits session or weekly limits). This directory holds the shared state that lets either agent start a session with full context.
Files
| File | Holds | Written when | Read when |
|---|---|---|---|
| PROJECT_CONTEXT.md | Stable repo truth: stack, structure, SaaS shape, ConnectWise, coding standards, frontend patterns, critical lessons | Only when the repo's shape changes | Every session start |
| CURRENT_TASK.md | The single active task: goal, DoD, assumptions, out-of-scope | On task start; status updates during work | Every session start |
| HANDOFF.md | Exact resume point: branch, where you left off, next steps, blockers | On session end / context-window limit | Every session start (most important) |
| TODO.md | Backlog of work NOT currently active | When deferring or queueing work | Only when CURRENT_TASK.md is complete |
| DECISIONS.md | Append-only architectural decision log | When an architectural choice is made | Skim top entries each session |
| SESSION_LOG.md | Append-only chronological history | On session end | Only when broader context is needed |
Agent-specific tooling lives at the repo root:
- ../CLAUDE.md — Claude Code's tooling (GitNexus, gstack slash commands, Claude trailer)
- ../AGENTS.md — OpenAI Codex's tooling (grep/rg fallbacks, Codex trailer)
Both root files contain an identical shared-protocol block. If you edit one, edit the other.
The handoff ritual
At session end (limit hit, task complete, or user stop): update HANDOFF.md to reflect the new resume point, update CURRENT_TASK.md status if it changed, append to DECISIONS.md if you made an architectural call, append a session entry to SESSION_LOG.md, and WIP-commit any dirty working tree with wip(handoff): <one-line> unless told otherwise. Don't push.
How to invoke a resume
Tell the agent:
Read CLAUDE.md (or AGENTS.md) and follow its instructions.
The agent will read its root file, which directs it to .ai/PROJECT_CONTEXT.md, .ai/CURRENT_TASK.md, and .ai/HANDOFF.md before doing anything else.
Recovery
The previous monolithic CLAUDE.md is recoverable via:
git show pre-ai-handoff:CLAUDE.md
(Tag pre-ai-handoff on commit e110fed — the snapshot taken before this migration.)