Project Detail - Spec Sections (per-project CSI)¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | Missing |
| Estimate | 1w (S) |
| Confidence | Medium |
| Linear | PIN-463 ↗ PIN-466 ↗ |
| Linear status | Done · +1 planned |
| Cycle | C16 |
| Design | |
| Linear epic | Project Management & Controls |
| Module | Projects ↗ |
Priority: Medium · Route: /projects/:id/detail?tab=spec-sections
Scope¶
Per-project CSI-format spec sections: the data layer and manual fallback UI behind the Submittal form's Spec Section field, sourced from uploaded spec-book documents or, on drawing-only projects, company CSI cost codes. Full AI parsing of uploaded specs into this list is a separate, larger epic still in Backlog. (Source: PIN-463, PIN-466.)
Acceptance criteria¶
- Spec sections sourced from the project's spec-book documents where present; CSI cost codes as fallback when there's no spec book
- PM can manually add / edit / remove spec sections per project (Project Settings) — covers gaps before AI parsing runs
- Each section tagged by source: AI-parsed, manual, or CSI-fallback
- Submittal form's Spec Section field pulls from the per-project list; Cost Code field pulls from the seeded CSI list
- Existing submittals with free-text spec-section values still display correctly
- AI auto-parsing of uploaded specs, AI-generated submittal register, and vendor compliance review remain a separate epic (backlog, needs a scoping spike first)
Conor's comments¶
Needs to be correctly categoized and searchable.
Notes¶
Manual only now; AI parsing = PIN-466 (backlog). Design canon omits this tab
Open question for Conor¶
- Design canon MISSING — no
.dc.htmlmaps to this page. Confirm the design source: reuse an existing module export, or schedule a dedicated design pass? (F2)