Plan: Knowledge System Consolidation

plan-2026-02-28-knowledge-system-consolidation Plan

plan completed

Project

Vision

The single coordination hub for the pal-e AI agency. Matures the knowledge system from "functional" to "properly indexed." Every note has a type, a status, and a project. Tags return to their proper role: topic classification.

Projects & Repos Touched

Project/Repo	Platform	Role
pal-e-docs (app)	Forgejo	Schema changes, API route updates, convention docs
pal-e-docs-mcp	Forgejo	Expose note_type/status query params
claude-custom	Forgejo	Skills and hooks updated to use new query params
All 22 repos	Forgejo	README updates pointing to pal-e-docs page notes

Phases

See child phase notes: list_notes(parent_slug="plan-2026-02-28-knowledge-system-consolidation")

Summary: Phases 1, 2, 4 complete. Phase 2 absorbed into plan-2026-03-01-note-decomposition. Phases 3, 5, 6 are low priority.

Investigation Findings (2026-03-01)

Tag-based queries work fine functionally.
Session start hook has N+1 query problem (~16 HTTP calls).
Scope tags are vestigial (13 notes). Project FK already provides this.
Issues table is the highest-value schema change.
note_type/status columns correct but lower urgency.

Decisions Made

Decision	Rationale
Add note_type + status columns (Option B)	Proper indexing without table-per-type.
Issues earn their own table	Need repo FK, number, priority.
SOPs/plans/conventions stay as notes	Documents don't need fields beyond notes.
Tags retire type/lifecycle/scope roles	Replaced by note_type, status, project FK.
Merge bug into issue	Only 4 bugs. Slug convention distinguishes.
Keep convention separate from sop	Rules vs procedures.
README convention: point to pal-e-docs	Repos contain code + PRs only.