Skip to content
archived Visibility internal Owner erik@uvilo.com Approver _ Created 2026-06-27 Updated 2026-06-27

Forge Project Cleanup Execute State 4


  • ✅ Task 1 — Build the project system infrastructure inventory

    • ✅ Inventory published project Knowledge and Guides
    • ✅ Inventory project Skills
    • ✅ Inventory project work-product templates
    • ✅ Inventory project bot records, prompt records, and prompt versions
    • ✅ Inventory workflow schedules, Inngest functions, or phase triggers
    • ✅ Inventory todo lists/items used for human and agent gates
    • ✅ Inventory generated Astro/Starlight pages and sidebar entries
    • ✅ Inventory lifecycle files, phase files, run logs, verification reports, and audit reports
    • ✅ Save the complete inventory as Forge_Project_Cleanup_Infrastructure_Inventory.md
  • ✅ Task 2 — Collect verification evidence for each component type

    • ✅ Collect verification evidence for Knowledge and Guides
    • ✅ Collect verification evidence for Skills
    • ✅ Collect verification evidence for Templates
    • ✅ Collect verification evidence for Bot prompts
    • ✅ Collect verification evidence for Workflow triggers
    • ✅ Collect verification evidence for Todo items
    • ✅ Collect verification evidence for Generated pages/sidebar
    • ✅ Collect verification evidence for Lifecycle files
    • ✅ Record run/cost evidence
    • ✅ Append verification evidence to the infrastructure inventory document
  • ✅ Task 3 — Build the Charter alignment matrix

    • ✅ Read Forge_Charter.md in full
    • ✅ Create alignment matrix rows for each Charter principle/constraint
    • ✅ Update Research matrix rows to reflect post-cleanup state
    • ✅ Address any remaining ⚠️ Partial or ❌ Violation rows
    • ✅ Save the matrix as Forge_Project_Cleanup_Charter_Alignment.md
  • ✅ Task 4 — Record and resolve ambiguities

    • ✅ Review all work done in Plans 1-3 and Plan 4 for ambiguities
    • ✅ Create entries in Forge_Project_Cleanup_Ambiguities.md
    • ✅ Create todo items for any Pending ambiguities requiring user decision
    • ✅ Save the ambiguities document
  • ✅ Task 5 — Final acceptance verification

    • ✅ Verify acceptance criterion: active components reflect target state
    • ✅ Verify acceptance criterion: active references to flat-file todos and WIP recovery are absent
    • ✅ Verify acceptance criterion: all four project bots match canonical Knowledge
    • ✅ Verify acceptance criterion: project system inventory and verification evidence are complete
    • ✅ Verify acceptance criterion: Charter alignment has no unaddressed gaps
    • ✅ Verify acceptance criterion: every unresolved ambiguity has a durable entry and todo item
    • ✅ Verify acceptance criterion: project names follow naming convention
    • ✅ Verify acceptance criterion: human gates are user-configurable
    • ✅ Record verification results in Forge_Project_Cleanup_Verification.md
    • ✅ Build, commit, push
  • ✅ Task 6 — Update project README and AGENTS

    • ✅ Update Forge_Project_Cleanup_README.md
    • ✅ Update Forge_Project_Cleanup_AGENTS.md
    • ✅ Set status to review on all Plan documents
    • ✅ Build, commit, push