Files
resolutionflow/.ai
Michael Chihlas 5085bb47c2
All checks were successful
Mirror to GitHub / mirror (push) Successful in 6s
CI / backend (pull_request) Successful in 10m3s
CI / frontend (pull_request) Successful in 5m34s
CI / e2e (pull_request) Successful in 9m26s
docs(ai): handoff state after /escalate unification through HandoffManager
Records 029680a — every escalation now funnels through HandoffManager
regardless of which URL it entered through, so /escalate from
EscalateModal produces the full set of artifacts (handoff row,
AppNotification, SSE event, Slack/Teams via notify, per-user emails,
documentation, PSA push) and the bell-icon notification opens the
magic-moment screen end-to-end. Notes the legacy SessionBriefing branch
+ flowpilot_engine.escalate_session as orphaned, scheduled for removal
after pilots have run a couple of weeks on the unified path.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-04-27 22:29:40 -04:00
..

.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.)