Determine current need, evidence sources and canonical modeling for four domains carried forward from retired bootstrap issues #5, #9, #10 and #11.
Audit and planning only.
Scope
For each domain, determine: current repository coverage, the canonical schema/model that already exists, available evidence sources, whether it is required for the current product roadmap, and whether it should become one or more later implementation issues.
| Domain |
Current state |
| cabin-types |
knowledge/cabin-types/ — README.md only |
| ship-systems |
knowledge/ship-systems/ — README.md only |
| operations |
knowledge/operations/ — README.md only |
| relationship index population |
knowledge/indexes/relationships.json — 968 bytes, 5 relation types, against 113 ships and a full ports/routes tree |
The relationship model is complete (knowledge/schema/relationship_graph.schema.json); only population is outstanding. The other three are genuinely unstarted.
Non-goals
- No bulk dataset population
- No invented entities
- No schema redesign unless the existing schema is proven insufficient
- No implementation
Acceptance criteria
- Coverage inventory, measured from the repository
- Source/evidence inventory
- Gap classification per domain
- Roadmap relevance per domain
- Recommended implementation split
Evidence gates
- Coverage counts measured, not estimated
- Each proposed source named, and its admissibility assessed against the current document-class and authority model (
src/timonelo/evidence/authority.py)
- A domain may be recommended for deferral — "needed" must be argued, not assumed
Context
Replaces bootstrap issues #5 (K-004 Relationship Model), #9 (K-008 Cabin Types), #10 (K-009 Ship Systems) and #11 (K-010 Operations), all of which were closed with no recorded acceptance criteria. This issue exists so that outstanding work is not lost in the retirement.
Labels audit and backlog were approved for this issue but do not exist in the repository.
Determine current need, evidence sources and canonical modeling for four domains carried forward from retired bootstrap issues #5, #9, #10 and #11.
Audit and planning only.
Scope
For each domain, determine: current repository coverage, the canonical schema/model that already exists, available evidence sources, whether it is required for the current product roadmap, and whether it should become one or more later implementation issues.
knowledge/cabin-types/—README.mdonlyknowledge/ship-systems/—README.mdonlyknowledge/operations/—README.mdonlyknowledge/indexes/relationships.json— 968 bytes, 5 relation types, against 113 ships and a full ports/routes treeThe relationship model is complete (
knowledge/schema/relationship_graph.schema.json); only population is outstanding. The other three are genuinely unstarted.Non-goals
Acceptance criteria
Evidence gates
src/timonelo/evidence/authority.py)Context
Replaces bootstrap issues #5 (K-004 Relationship Model), #9 (K-008 Cabin Types), #10 (K-009 Ship Systems) and #11 (K-010 Operations), all of which were closed with no recorded acceptance criteria. This issue exists so that outstanding work is not lost in the retirement.
Labels
auditandbacklogwere approved for this issue but do not exist in the repository.