Skip to content

Wiki maintenance

This page defines how the team keeps Rephrased docs useful while engineers and designers update them through a coding agent or manual Markdown edits.

Required page metadata

Every normal page under Rephrased Wiki/wiki/ should have front matter. The same three fields apply to the lead development log at Rephrased Wiki/DEVLOG.md (MkDocs Devlogs → Lead development log).

---
owner: Gabriel Li
status: draft
last-reviewed: 2026-05-08
---

Use:

  • draft for new or unreviewed pages.
  • stable for reviewed pages that match the current plan or implementation.
  • partial for pages that intentionally document incomplete systems.
  • needs-review when an AI or teammate updates a page but the owner has not reviewed it yet.

The lead log does not use ## Change history — its dated entries are the history. Still keep owner, status, and last-reviewed current in front matter. Append to an existing date section when more work lands the same day instead of adding a second header for that date.

Required change history

Every wiki page under Rephrased Wiki/wiki/ should end with:

## Change history

- 2026-05-08 — Gabriel Li — Added baseline change history section for weekly wiki maintenance.

Add newest entries at the top of the section.

Use one entry per calendar date. If multiple edits land the same day, combine them into a single bullet instead of stacking duplicate dates.

What counts as a history entry

Log meaningful changes:

  • new design decision
  • system behavior change
  • source document import
  • outdated information corrected
  • ownership, status, or review update
  • page creation or major reorganization

Do not log typo-only, formatting-only, or trivial link cleanup unless it changes discoverability.

Coding agents

Agents must keep owner, status, last-reviewed, and ## Change history accurate on pages they edit. They should call wiki_query before inventing project facts, and devlog when a session changes systems or C++.

Do not ask engineers to run wiki skills by name.

Weekly audit checklist

Once per week, scan the wiki and report:

  • pages missing owner, status, or last-reviewed (include Rephrased Wiki/DEVLOG.md)
  • pages missing ## Change history
  • pages marked draft, partial, or needs-review
  • pages not reviewed in the last 14 days
  • broken local links
  • docs that mention systems or files that no longer exist
  • new implementation work that lacks matching wiki updates

The weekly audit should produce a short report first. Do not bulk-edit pages until owners approve the recommended fixes.

Change history

  • 2026-08-13 — Gabriel Li — Agents keep wiki metadata via MCP/devlog; dropped skill-file paths.
  • 2026-05-23 — Gabriel Li — Lead DEVLOG.md included in required front matter with change-history exception; generic coding-agent wording; .agents/skills path noted; one entry per date rule for change history and lead DEVLOG.
  • 2026-05-09 — Gabriel Li — Documented coordination with devlog-entry when wiki paths appear in devlog “Wiki touched” lists.
  • 2026-05-08 — Gabriel Li — Added wiki maintenance workflow for per-page change history and weekly audits.