Board: Note Type System Audit

board-180-note-type-audit Board

active board

Project

Board: Note Type System Audit

Parent

forgejo_admin/claude-custom #180 — Spike: Note type system audit and target hierarchy design. Too broad for a single agent pass — decomposed into 7 research spikes.

User Stories

TBD — this spike's job is to produce the target stories. Starting hypotheses:

Role	Key	Story	Success Metric
PM (Betty Sue)	clean-types	I want every note type to have a complete enforcement chain (template + SOP + hook) so agents can't create non-compliant notes	100% chain coverage for active types
Developer	minimal-taxonomy	I want a minimal, unambiguous type system so I can quickly categorize work	<10 active types, 0 overlapping categories
Platform owner	organic-planning	I want project → board → ticket → sub-board hierarchy so planning grows organically through parent-child	No plan/phase/milestone types needed

Architecture

Components this audit touches:

arch:schemas — pal-e-docs/src/pal_e_docs/schemas.py NoteType Literal (17 values)
arch:models — pal-e-docs/src/pal_e_docs/models.py BoardColumn enum (missing validation column)
arch:routes — pal-e-docs/src/pal_e_docs/routes/notes.py status validation per type
arch:note-conventions — documented taxonomy (stale, 12 types vs 17 in code)
arch:hooks — claude-custom hooks/ enforcement hooks
arch:templates — 15 template-* notes in pal-e-docs

Acceptance Criteria

All 7 research spikes completed with structured evidence
Target type set agreed (Lucas approval)
Target hierarchy documented
Follow-up Forgejo issues created for the refactor

Kanban

Sub-tickets are research spikes. Each returns a structured report. Spikes 1-5 are independent and parallelizable. Spike 6 synthesizes. Spike 7 produces issues.