Note

    Maggie Todo Intake Dossier

    Maggie Todo is a Markdown-first aggregate todo and context-layer repository for Maggie-owned work, personal follow-ups, cross-project manual tasks, evidence, and generated local dashboard views. It is intentionally not a live app or website; its primary runtime surface is a local static dashboard generated from markdown todo sources.

    Document Metadata

    • title: Maggie Todo Project Intake
    • description: Source-backed project dossier for importing the Maggie Todo aggregate repo into Hyphenomenon.
    • status: active
    • lastUpdated: 2026-05-23 14:55 EDT (America/New_York, UTC-04:00)
    • owner: Product/Engineering

    Project Intake - Maggie Todo

    1) Executive Summary

    Maggie Todo is a Markdown-first aggregate todo and context-layer repository for Maggie-owned work, personal follow-ups, cross-project manual tasks, evidence, and generated local dashboard views. It is intentionally not a live app or website; its primary runtime surface is a local static dashboard generated from markdown todo sources.

    2) Project Type and Domain

    • Project type: initiative
    • Domains: builder, entrepreneur
    • Primary audience: Maggie as operator/reviewer
    • Public posture: repo-backed context system with local dashboard output

    3) Repository and Live URLs

    • GitHub repo: https://github.com/maggielerman/maggie-todo
    • Local repo path: /Users/maggielerman/Documents/MAGGIE TODO
    • Dashboard: /Users/maggielerman/Documents/MAGGIE TODO/DOCS/TODOS/dashboard.html
    • Tracking doc for this Hyphenomenon batch: /Users/maggielerman/Documents/MAGGIE TODO/DOCS/PROJECTS/active/0002_hyphenomenon-intake.md

    4) Product/User Journey Summary

    The operator records loose todos in DOCS/TODOS/inbox.md, personal or recurring items in DOCS/TODOS/personal.md, and project-owned follow-ups in DOCS/PROJECTS/. The repo uses literal MAGGIE TODO: callouts for Maggie-owned manual work, approvals, external dependencies, evidence gathering, credentials, or unresolved decisions. npm run todo:build regenerates the local dashboard and todo index after edits.

    5) Architecture and Stack Summary

    • Source format: Markdown docs under DOCS/
    • Generated surfaces: DOCS/TODOS/dashboard.html and DOCS/TODOS/todo-index.json
    • Build command: npm run todo:build
    • Supporting scripts: scripts/todos/build-dashboard.mjs, scripts/docs/manifest.mjs, scripts/docs/check-links.mjs
    • Governance files: AGENTS.md, CHANGELOG.md, ROADMAP.md, DOCS/PROJECTS/README.md

    6) Key Workflows and Operational Flows

    • Quick capture: add loose items to DOCS/TODOS/inbox.md.
    • Project follow-up: move project-owned items into a numbered project doc.
    • Evidence preservation: store screenshots, exports, proof, and manual review artifacts under DOCS/evidence/.
    • Dashboard refresh: run npm run todo:build to regenerate local dashboard outputs.
    • Hyphenomenon queue: use DOCS/PROJECTS/active/0002_hyphenomenon-intake.md to track intake tasks and dependencies.

    7) AI Context: Prompts, Chats, Agent Workflows

    The source thread 019e55e2-01e7-7e31-a0c5-38bdd6671cdf created the aggregate repo and defined the first Hyphenomenon intake queue. That thread explicitly blocked screenshot intake until Hyphenomenon supported first-class image evidence.

    8) Supporting Docs and External Resources

    Hydration Source Artifacts

    PathSource URLTypeRationale
    README.mdGitHubmarkdownDefines the repo purpose, source-of-truth docs root, todo format, dashboard, and evidence tree.
    DOCS/README.mdGitHubmarkdownSummarizes the canonical context-layer root and primary surfaces.
    DOCS/PROJECTS/active/0002_hyphenomenon-intake.mdGitHubmarkdownTracks the specific Hyphenomenon intake queue and screenshot dependency.
    DOCS/TODOS/dashboard.htmlGitHubtextGenerated local dashboard surface for todo review.
    DOCS/evidence/active/0002-hyphenomenon-intake/images/codex-feedback-screenshot-2026-05-23.pngGitHubimageDurable screenshot evidence for the screenshot-specific intake task.

    No .docx or .pdf artifacts were present in the source repo during this intake pass.

    9) Screenshot Gallery (with relative links + captions)

    • [Codex feedback screenshot](/Users/maggielerman/Documents/MAGGIE TODO/DOCS/evidence/active/0002-hyphenomenon-intake/images/codex-feedback-screenshot-2026-05-23.png) - Screenshot evidence for the Hyphenomenon image-evidence dependency.

    10) Candidate Import Nodes and Relationships

    • Project: maggie-todo
    • Chat: maggie-todo-aggregate-repo-and-hyphenomenon-intake-batch-019e55e2
    • Image evidence: codex-feedback-screenshot-2026-05-23
    • Relationship: the chat created the repo and queue; the project owns the dashboard/tracking context; the image evidence artifact proves the screenshot-specific task and links back to the chat and project.

    11) Risks, Gaps, and Unknowns

    • The dashboard is a local file, not a public web URL.
    • The source screenshot includes local operational context and should remain a durable evidence object with explicit provenance rather than a generic decorative screenshot.
    • Raw Codex transcript text is not rendered publicly by this intake.

    12) Handoff Checklist for Hyphenomenon Import

    • Confirmed source repo path and GitHub remote.
    • Confirmed tracking doc and dashboard paths.
    • Preserved screenshot evidence with checksum parity against the original Downloads image.
    • Added first-class image evidence support before screenshot intake.
    • Apply intake records to the knowledge backbone when environment verification passes.
    • Verify /projects/maggie-todo, /chats/maggie-todo-aggregate-repo-and-hyphenomenon-intake-batch-019e55e2, and /image-evidence/codex-feedback-screenshot-2026-05-23 after apply.