Skip to content
Uvilo OS
approved Visibility internal Owner erik@uvilo.com Approver _ Created _ Updated _

Knowledge Consistency Plan 4

Plan 4 — Knowledge File Frontmatter Corrections

Scope: Correct frontmatter across all Forge knowledge files: change status: approved to status: published in 6 files, remove created/updated/lastUpdated fields from 16 files, add missing approver field to 5 files, and add complete frontmatter to Forge/Forge_Project/AGENTS.md.

Spec sections covered: S2.1, S2.2, S2.3, S2.4, S10.2 (S10.2 is implemented by the same task as S2.2 — removing date fields from frontmatter).

Prerequisite: None.

Task 1 — Change Status from approved to published

Spec S2.1: “Six root-level knowledge files have status changed from approved to published:” — Forge_Charter.md, Forge_Agent_Architecture.md, Forge_Content_System.md, Forge_Document_Structure.md, Forge_Infrastructure.md, Forge_Setup.md.

Steps

  1. Edit Forge/Forge_Charter.md: change status: approved to status: published in frontmatter.
  2. Edit Forge/Forge_Agent_Architecture.md: change status: approved to status: published.
  3. Edit Forge/Forge_Content_System.md: change status: approved to status: published.
  4. Edit Forge/Forge_Document_Structure.md: change status: approved to status: published.
  5. Edit Forge/Forge_Infrastructure.md: change status: approved to status: published.
  6. Edit Forge/Forge_Setup.md: change status: approved to status: published.

Verify

  • grep -l 'status: approved' Forge/Forge_Charter.md Forge/Forge_Agent_Architecture.md Forge/Forge_Content_System.md Forge/Forge_Document_Structure.md Forge/Forge_Infrastructure.md Forge/Forge_Setup.md returns no matches
  • All 6 files have status: published in frontmatter

Task 2 — Remove created, updated, and lastUpdated Fields from Frontmatter

Spec S2.2: “Knowledge files do not maintain created or updated fields in YAML frontmatter. Creation and modification dates are sourced from the filesystem and git history, eliminating manual maintenance burden. The created, updated, and lastUpdated fields are removed from the frontmatter convention. Existing files with these fields have them removed during execution.” Also Spec S10.2: “Remove created, updated, and lastUpdated from the frontmatter convention. Use filesystem and git metadata as the source of truth for creation and modification dates.”

Affected Files (16 total — complete list)

Forge root (12 files):

  1. Forge/AGENTS.md
  2. Forge/Forge_Agent_Architecture.md
  3. Forge/Forge_Agent_Orchestration.md
  4. Forge/Forge_Agents_User_Guide.md
  5. Forge/Forge_Charter.md
  6. Forge/Forge_Content_System.md
  7. Forge/Forge_Document_Structure.md
  8. Forge/Forge_Infrastructure.md
  9. Forge/Forge_Markdown_MDX_Syntax.mdx
  10. Forge/Forge_Markdown_Syntax.md
  11. Forge/Forge_Setup.md
  12. Forge/README.md

Forge_Project root (4 files):

  1. Forge/Forge_Project/AGENTS.md
  2. Forge/Forge_Project/Forge_Project_User_Guide.md
  3. Forge/Forge_Project/Forge_Project_Workflow.md
  4. Forge/Forge_Project/README.md

Steps

  1. For each of the 16 files listed above, check the YAML frontmatter for created, updated, or lastUpdated fields.
  2. Remove any created, updated, or lastUpdated fields found in the frontmatter.
  3. Do not remove any other frontmatter fields (title, visibility, status, owner, approver).
  4. If a file has no date fields, no change is needed for that file.

Verify

  • grep -l '^created:' Forge/AGENTS.md Forge/Forge_Agent_Architecture.md Forge/Forge_Agent_Orchestration.md Forge/Forge_Agents_User_Guide.md Forge/Forge_Charter.md Forge/Forge_Content_System.md Forge/Forge_Document_Structure.md Forge/Forge_Infrastructure.md Forge/Forge_Markdown_MDX_Syntax.mdx Forge/Forge_Markdown_Syntax.md Forge/Forge_Setup.md Forge/README.md Forge/Forge_Project/AGENTS.md Forge/Forge_Project/Forge_Project_User_Guide.md Forge/Forge_Project/Forge_Project_Workflow.md Forge/Forge_Project/README.md returns no matches
  • grep -l '^updated:' [same 16 files] returns no matches
  • grep -l '^lastUpdated:' [same 16 files] returns no matches

Task 3 — Add Missing approver Field

Spec S2.3: “All knowledge files have complete frontmatter per the convention above. Specifically, the following files have missing approver fields added:” — Forge_Agent_Architecture.md, Forge_Content_System.md, Forge_Infrastructure.md, Forge_Setup.md, AGENTS.md.

Steps

  1. Edit Forge/Forge_Agent_Architecture.md: add approver: "" to frontmatter if missing.
  2. Edit Forge/Forge_Content_System.md: add approver: "" to frontmatter if missing.
  3. Edit Forge/Forge_Infrastructure.md: add approver: "" to frontmatter if missing.
  4. Edit Forge/Forge_Setup.md: add approver: "" to frontmatter if missing.
  5. Edit Forge/AGENTS.md: add approver: "" to frontmatter if missing.

Verify

  • All 5 files have an approver field in frontmatter (value may be empty string "")
  • grep -l 'approver' Forge/Forge_Agent_Architecture.md Forge/Forge_Content_System.md Forge/Forge_Infrastructure.md Forge/Forge_Setup.md Forge/AGENTS.md returns all 5 files

Task 4 — Add Complete Frontmatter to Forge_Project AGENTS.md

Spec S2.4: “Forge/Forge_Project/AGENTS.md has complete frontmatter (title, visibility, status, owner, approver).”

Steps

  1. Edit Forge/Forge_Project/AGENTS.md: ensure the YAML frontmatter contains all required fields: title, visibility, status, owner, approver.
  2. Add any missing fields with appropriate values: title (document title), visibility: internal, status: published (or draft if not yet published), owner: "erik@uvilo.com", approver: "".
  3. If no frontmatter exists, add a complete frontmatter block at the top of the file.

Verify

  • Forge/Forge_Project/AGENTS.md has YAML frontmatter with all 5 required fields: title, visibility, status, owner, approver

Task 5 — Build, Commit, and Push

Spec S2.1–S2.4, S10.2: This Plan implements knowledge file frontmatter corrections. After all tasks are complete, commit and push the changes. Per Known Infrastructure Context, npm run build is expected to fail; proceed with git operations regardless.

Steps

  1. Run npm run build from the repo root. This is known to fail. Proceed regardless.
  2. git add all 16 modified knowledge files listed in Task 2, plus Forge/Forge_Project/AGENTS.md.
  3. git commit -m "Plan 4: Knowledge file frontmatter corrections (S2.1-S2.4, S10.2)"
  4. git push origin dev

Verify

  • All modified files are committed and pushed to dev
  • git log --oneline -1 shows the commit

Plan 4 Completion Criteria

  • All 6 files listed in Task 1 have status: published (not approved)
  • All 16 files listed in Task 2 have no created, updated, or lastUpdated fields in frontmatter
  • All 5 files listed in Task 3 have an approver field in frontmatter
  • Forge/Forge_Project/AGENTS.md has complete frontmatter with all 5 required fields
  • Changes committed and pushed to dev

Dependencies

  • Requires: None
  • Blocks: None