1Principles
ValuesBeliefsControls
Files can't think for you.
- Issue management in markdown worked at 5 issues. It breaks at 20.
- Queryable beats readable. Structured beats formatted.
- The routing decision is the actual work, not the logging.
| Problem | Question | Decision |
|---|---|---|
| Issues pile up unrouted | Fix, PRD, or story? | Codify the decision tree in CLI |
The Vision
Markdown file growing unwieldy while CLI command returns instant results
2Performance
ValuesBeliefsControls
Six issues, zero queries.
| Metric | Target | Now |
|---|---|---|
| Issue creation time | <30s | ~8 min |
| Query response | <500ms | Manual search |
| Unrouted issues | 0 | Unknown |
| Migration loss | 0 rows | N/A |
| Problem | Question | Decision |
|---|---|---|
| Can't count what you can't query | What's the real issue volume? | Build CRUD CLI first |
The Vision
Dashboard showing issue counts by severity and PRD with trend lines
3Platform
ValuesBeliefsControls
Extend, don't rebuild.
| Exists | Extend | Build |
|---|---|---|
priority_problems table | Add severity, page, prd_slug | issue-cli.ts |
planning_issue_links | Keep for plan linkage | Decision routing |
agent-comms.ts pattern | Follow architecture | Migration script |
| Problem | Question | Decision |
|---|---|---|
| Eng built tables that don't match spec | Extend or replace? | Extend with columns |
The Vision
Architecture: priority_problems table with new columns highlighted, issue-cli connecting to it
4Protocols
ValuesBeliefsControls
Create, route, resolve, repeat.
CREATE --> ROUTE --> FIX / PRD / STORY --> RESOLVE --> MEASURE
^ |
└──────── Issue count feeds priority ranking ──────────┘
| Problem | Question | Decision |
|---|---|---|
| No decision framework | When is an issue a new PRD? | Decision tree in CLI route command |
The Vision
Flowchart: create issue, route decision (fix/PRD/story), resolve with evidence, feed back to prioritise-prds
5Players
ValuesBeliefsControls
Commissioners need speed, not forms.
| Job | Struggling Moment | Hidden Objection |
|---|---|---|
| Log issue fast | Formatting markdown, git pushing | "The file works fine" |
| Route work | No framework, ask human every time | "Routing is judgment, not logic" |
| Read fix queue | Scanning unstructured file | "I know where to look" |
| Problem | Question | Decision |
|---|---|---|
| Commissioners avoid logging | Make it <30s? | CLI-first, UI later |
The Vision
Split: commissioner typing CLI command left, engineer querying filtered results right
1 / 5