Skip to content
draft Visibility internal Owner erik@uvilo.com Approver _ Created _ Updated _

Knowledge Consistency README Consolidation

Per Spec S10.1, README.md and AGENTS.md pairs in Forge folders were evaluated for content overlap. Where overlapping, content was consolidated into AGENTS.md and the README.md was eliminated.


Pair 1: Forge/README.md + Forge/AGENTS.md

Folder: Forge/

README.md content summary:

  • Welcome and overview of Forge
  • Section 1: How to Access Forge Chat (login instructions)
  • Section 2: What Is Forge? (core areas and departments)
  • Section 3: Where Files Go (table mapping work types to folders)
  • Section 4: How Projects Work (lifecycle, key rules)
  • Section 5: Browsing the Docs
  • Section 6: What to Do When You’re Stuck (troubleshooting)
  • Section 7: Key Principles (git, durable work-products, human sovereignty)

AGENTS.md content summary:

  • Brief intro to Forge as an agentic system
  • Key Files and Systems (structured links)
  • Reference Docs (structured links)
  • Skills (platform and project lifecycle)
  • Projects (identity, recovery, todos)

Decision: Consolidated — README.md eliminated.

Rationale: Significant content overlap in the “what is Forge” and “key files” descriptions. AGENTS.md had richer structure with related skills, documents, and knowledge sources. Per S10.1, AGENTS.md serves as the canonical context file.

Content merged into AGENTS.md:

  • “How to Access Forge Chat” → new “Accessing Forge” section
  • “Where Files Go” table → new “Where Files Go” section (merged verbatim)
  • “What to Do When You’re Stuck” → new “Troubleshooting” section (with Page Manager spawn pattern from Task 4)
  • “Key Principles” → new “Key Principles” section (merged verbatim)

Content eliminated:

  • README.md intro (duplicated by AGENTS.md intro)
  • Section 2 “What Is Forge?” (core areas list — captured by AGENTS.md Key Files, Reference Docs, and Skills sections)
  • Section 4 “How Projects Work” (duplicated by AGENTS.md Projects section)
  • Section 5 “Browsing the Docs” (general browsing info, not unique value)

Pair 2: Forge/Forge_Project/README.md + Forge/Forge_Project/AGENTS.md

Folder: Forge/Forge_Project/

README.md content summary:

  • Brief intro to Forge Project
  • Key Files (links to Forge Project Workflow and User Guide)
  • Skills (link to Workflow §2)

AGENTS.md content summary:

  • Brief intro to Forge Project
  • Key Files (links to Forge Project Workflow and User Guide)
  • Full Skills table (all 18 lifecycle skills with phase mapping)

Decision: Consolidated — README.md eliminated.

Rationale: Near-total content overlap. Both files listed the same Key Files. AGENTS.md was strictly richer — it had the full skills table whereas README.md only linked to Workflow §2. The only unique content was one sentence in the README intro about optimizing for agent context efficiency, which was merged into the AGENTS.md intro.

Content merged into AGENTS.md:

  • README intro sentence: “It provides a standardized lifecycle for projects — directed and supervised by people and executed by agents — optimizing for agent context efficiency, clean separation between phases, and systematic knowledge extraction” — merged into AGENTS.md intro paragraph.

Content eliminated:

  • README.md intro (subsumed by merged AGENTS.md intro)
  • Key Files section (identical to AGENTS.md Key Files section)
  • Skills section (AGENTS.md Skills table is strictly richer)