patrick/Polaris
Watch
1
0
Fork
You've already forked Polaris
 0
Code Issues 27 Pull requests 4 Projects Releases Packages Wiki Activity Actions

docs: remove tooling as a catalogue entity #48

Merged
patrick merged 1 commit from feature/docs-remove-tooling into main 2026-09-11 09:27:37 +00:00
Conversation 0 Commits 1 Files changed 13 +83 -31
patrick commented 2026-09-11 09:27:09 +00:00
Owner
Copy link

Removes Tooling as a crew-capability/catalogue concept across the working docs.

What changed

  • Glossary & scope (02-roles-and-glossary.md, 01-goals-and-scope.md): dropped the Tooling glossary entry and every "skills, tooling" pairing; crew capability is now skill-only.
  • Data model (08-data-model.md): removed tooling, service_type_tooling, crew_tooling tables and their ERD edges.
  • API (09-api.md): removed the /tooling catalogue endpoint.
  • Validator/lifecycles (04-lifecycles.md): removed the E_TOOLING_MISSING rule.
  • Scenarios (03-scenarios.md): removed the tooling_missing reason code and its S09 branch, S13's tooling-union note, S16's catalogue-values list wording, and E12's wording.
  • Engine (05-planning-engine.md): capability constraint is now skill-only.
  • UX (06-ux.md): Catalogue and Crews pages no longer list tooling.
  • Roadmap/plan (11-roadmap.md, 12-implementation-plan.md): removed crew_tooling from the M2/PH1.1 scope.
  • CLAUDE.md hard-rule 4 updated to match (catalogue values = service types, skills, reason codes).
  • Added docs/adr/0001-remove-tooling-catalogue.md recording the decision reversal, plus a pointer to docs/adr/ from docs/README.md.

Related

Forgejo tickets #9 (PH1.1) and #14 (PH1.6) were also updated to drop crew_tooling/tooling from their acceptance criteria, ahead of this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LoNrSy7Reyp7evkfcdHeLX

Removes Tooling as a crew-capability/catalogue concept across the working docs. ## What changed - **Glossary & scope** (`02-roles-and-glossary.md`, `01-goals-and-scope.md`): dropped the Tooling glossary entry and every "skills, tooling" pairing; crew capability is now skill-only. - **Data model** (`08-data-model.md`): removed `tooling`, `service_type_tooling`, `crew_tooling` tables and their ERD edges. - **API** (`09-api.md`): removed the `/tooling` catalogue endpoint. - **Validator/lifecycles** (`04-lifecycles.md`): removed the `E_TOOLING_MISSING` rule. - **Scenarios** (`03-scenarios.md`): removed the `tooling_missing` reason code and its S09 branch, S13's tooling-union note, S16's catalogue-values list wording, and E12's wording. - **Engine** (`05-planning-engine.md`): capability constraint is now skill-only. - **UX** (`06-ux.md`): Catalogue and Crews pages no longer list tooling. - **Roadmap/plan** (`11-roadmap.md`, `12-implementation-plan.md`): removed `crew_tooling` from the M2/PH1.1 scope. - **CLAUDE.md** hard-rule 4 updated to match (catalogue values = service types, skills, reason codes). - Added **`docs/adr/0001-remove-tooling-catalogue.md`** recording the decision reversal, plus a pointer to `docs/adr/` from `docs/README.md`. ## Related Forgejo tickets #9 (PH1.1) and #14 (PH1.6) were also updated to drop `crew_tooling`/tooling from their acceptance criteria, ahead of this PR. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01LoNrSy7Reyp7evkfcdHeLX 
Drop Tooling as a crew-capability/catalogue concept across the working
docs (glossary, ERD and tables in 08-data-model.md, /tooling endpoint in
09-api.md, E_TOOLING_MISSING validator rule, tooling_missing reason code
and S09 handling, engine capability constraint, UX Catalogue/Crews pages,
and the M2/PH1.1 scope in 11-roadmap.md and 12-implementation-plan.md).
Crew capability is now expressed by Skill alone.

Recorded as ADR 0001 since this reverses a previously documented decision.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LoNrSy7Reyp7evkfcdHeLX
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
in-progress
A session has assigned itself and is actively working this

  
in-review
PR open, waiting on review/merge

  
ready-for-agent
Self-contained ticket an agent can pick up

  
seam-request
Ad-hoc cross-boundary fix/gap found while working another ticket, not a docs/12 plan row

No labels
in-progress
in-review
ready-for-agent
seam-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
patrick/Polaris!48
No description provided.