Chat

    Maggie Todo Orchestrator V1 Hardening and Cross-Repo Todo Scan

    Codex thread that defined Maggie Todo as a top-level Codex orchestration layer, hardened its Markdown-first project/checkpoint contract, moved the initial setup docs to completed, and scanned local repos for actionable Maggie-owned todo blockers.

    Highlights

    • Defined Maggie Todo as an index, checkpoint, and reminder layer for Codex work while keeping deep implementation state in each source repo.
    • Added a v1 project-doc contract with source repo pointers, branch/readback fields, latest checkpoints, evidence links, and explicit blockers.
    • Moved the initial Maggie Todo aggregate and Hyphenomenon intake setup docs to completed after preserving their purpose.
    • Scanned local source repos for actionable `MAGGIE TODO:` callouts and created blocked aggregate reminder docs for the real source-repo blockers.

    Source conversation

    Chat Transcript
    Private

    This transcript is not public. You can request access below; requests are reviewed before anything is shared.

    Created artifacts

    ProjectMaggie Todo orchestrator v1 contract

    Markdown-first repo contract and project-template fields for status readbacks, latest checkpoints, source repo pointers, blockers, and evidence.

    ProjectCross-repo Maggie TODO blocked docs

    Blocked aggregate reminder docs for actionable Maggie-owned blockers in four source repos, with template/example noise filtered out.

    Actions and follow-ups

    Actions Taken

    • Updated Maggie Todo repo instructions, README, project index, project template, roadmap, changelog, generated dashboard, todo index, and docs manifest.
    • Retrofitted the initial active project docs with the new readback/checkpoint structure, then moved them to completed after operator confirmation.
    • Added blocked aggregate docs for actionable Maggie-owned blockers in rps-etsy, shopify-headless, family-shapes-cannonical, and faire-lead-ops.
    • Verified the Maggie Todo source repo with npm run todo:check and git diff --check.

    Actions Outstanding

    • Re-check source repo state before relying on the May 25 blocker scan, because several source repos had local dirty state or branch drift at the time.
    • Build a read-only cross-repo scan/digest workflow only after the lightweight Markdown contract proves useful.

    Source extracts

    “
    Orchestrator boundary
    deep work would remain in the relevant repos
    “
    V1 execution approval
    if not, pursue the 2-4 hour v1 path
    “
    Future scope discipline
    moving forward we should typically write a new project for this type of task

    Decisions

    • Keep Maggie Todo as the Codex index/checkpoint/reminder layer; source repos remain the deep implementation truth.
    • Start with a 2-4 hour v1 docs-and-contract hardening pass instead of building a new app or automation system.
    • Treat future scope expansions of this kind as new project docs rather than folding them into an older setup project.
    • Copy only actionable source-repo blockers into Maggie Todo and leave source repos as the detailed truth.