Spike: Note type system audit and target hierarchy design #180

New issue

Open

opened 2026-03-28 01:26:22 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-28 01:26:22 +00:00

Contributor

Type

Spike

Lineage

Standalone — discovered during session reviewing note-conventions drift vs schemas.py vs actual database usage.

Repo

forgejo_admin/claude-custom (cross-repo: also touches pal-e-docs schemas, routes, hooks)

Question

Which of the 17 note types in schemas.py justify the full enforcement chain (type → template → SOP → hook), what is the target hierarchy (project → board → ticket → sub-board), and should architecture + user-story become first-class note types?

What to Explore

Seven research spikes, five parallelizable:

Type census — count notes per type, active vs cold, orphan types with 0 board-type notes
Chain coverage — for each type, does a template exist? SOP? Hook?
Doc breakdown — sub-classify the 257 doc notes by slug prefix and tags. Which clusters emerge?
reference vs doc — read sample reference notes, compare to doc. Meaningful distinction or merge?
Legacy weight — how many plan/phase/todo/issue notes are cold? Can we remove those types from the enum?
Hierarchy design — given the vision (project → board → ticket → sub-board, arch + user-story as types), draft target type set and hierarchy rules
Migration scope — what code changes (schemas.py, routes, hooks, note-conventions) are needed?

Spikes 1-5 are independent. Spike 6 synthesizes 1-5. Spike 7 produces scoped issues.

Success Criteria

Question is answered with evidence (not opinion)
Target type set defined with rationale for each include/exclude
Target hierarchy documented (project → board → ticket flow)
Architecture + user-story type decision made with pros/cons
Follow-up Forgejo issues created for the actual refactor work
note-conventions update scoped

Time-box

1 session (2026-03-27). If unanswered: document findings, escalate remaining questions.

project-pal-e-agency — project this affects
note-conventions — the convention that needs updating
convention-validation-pipeline — the axiom: type → template → SOP → hook

### Type Spike ### Lineage Standalone — discovered during session reviewing note-conventions drift vs schemas.py vs actual database usage. ### Repo `forgejo_admin/claude-custom` (cross-repo: also touches pal-e-docs schemas, routes, hooks) ### Question Which of the 17 note types in schemas.py justify the full enforcement chain (type → template → SOP → hook), what is the target hierarchy (project → board → ticket → sub-board), and should architecture + user-story become first-class note types? ### What to Explore Seven research spikes, five parallelizable: 1. **Type census** — count notes per type, active vs cold, orphan types with 0 board-type notes 2. **Chain coverage** — for each type, does a template exist? SOP? Hook? 3. **Doc breakdown** — sub-classify the 257 `doc` notes by slug prefix and tags. Which clusters emerge? 4. **reference vs doc** — read sample reference notes, compare to doc. Meaningful distinction or merge? 5. **Legacy weight** — how many plan/phase/todo/issue notes are cold? Can we remove those types from the enum? 6. **Hierarchy design** — given the vision (project → board → ticket → sub-board, arch + user-story as types), draft target type set and hierarchy rules 7. **Migration scope** — what code changes (schemas.py, routes, hooks, note-conventions) are needed? Spikes 1-5 are independent. Spike 6 synthesizes 1-5. Spike 7 produces scoped issues. ### Success Criteria - [ ] Question is answered with evidence (not opinion) - [ ] Target type set defined with rationale for each include/exclude - [ ] Target hierarchy documented (project → board → ticket flow) - [ ] Architecture + user-story type decision made with pros/cons - [ ] Follow-up Forgejo issues created for the actual refactor work - [ ] note-conventions update scoped ### Time-box 1 session (2026-03-27). If unanswered: document findings, escalate remaining questions. ### Related - `project-pal-e-agency` — project this affects - `note-conventions` — the convention that needs updating - `convention-validation-pipeline` — the axiom: type → template → SOP → hook