Update CLAUDE.md and PROJECT_REFERENCE.md for neighbourhood-centric architecture

lmiranda commented

2026-01-16 14:54:14 +00:00

Owner

Description

Update core project documentation to reflect the new neighbourhood-centric dashboard architecture, removing all TRREB references and documenting the new data model and sources.

Branch: feature/9-documentation

Reference: docs/changes/Change-Toronto-Analysis-Reviewed.md - Phase 2

Files to UPDATE

CLAUDE.md

Remove "Geographic Reality" section describing TRREB districts
Update "Star Schema" section with neighbourhood-centric model:
- dim_neighbourhood (158 neighbourhoods) as central dimension
- dim_cmhc_zone with neighbourhood mapping
- bridge_cmhc_neighbourhood for area weights
- fact_census, fact_crime, fact_amenities
Update "Data Model Overview" removing TRREB purchase facts
Update "DO NOT BUILD" section (remove TRREB-related warnings)
Update "Reference Documents" table (remove deleted docs)
Update sprint status to Sprint 9

docs/PROJECT_REFERENCE.md

Update architecture section for neighbourhood-based approach
Document new data sources:
- Toronto Open Data Portal (neighbourhoods, census, parks, schools, childcare)
- Toronto Police Portal (crime rates, MCI, shootings)
- CMHC (rental data with zone crosswalk)
Update star schema documentation
Remove TRREB PDF parsing architecture
Document 5-tab dashboard structure (Overview, Housing, Safety, Demographics, Amenities)

Acceptance Criteria

No references to TRREB districts, PDF parsing, or FactPurchases in CLAUDE.md
Star schema accurately reflects neighbourhood-centric design
New data sources documented with API references
PROJECT_REFERENCE.md architecture diagram updated (if applicable)
All internal document references are valid (no broken links to deleted docs)
Documentation is consistent with docs/changes/Change-Toronto-Analysis-Reviewed.md

Technical Notes

Use the implementation plan as the source of truth for the new architecture
Keep documentation concise - detailed specs are in the implementation plan
Preserve sections unrelated to Toronto dashboard (server info, common operations)

Sprint

Sprint 9 - Phase 2 (Documentation)

Labels: Type/Refactor, Priority/High, Efforts/M, Component/Docs

## Description Update core project documentation to reflect the new neighbourhood-centric dashboard architecture, removing all TRREB references and documenting the new data model and sources. **Branch:** `feature/9-documentation` **Reference:** `docs/changes/Change-Toronto-Analysis-Reviewed.md` - Phase 2 ## Files to UPDATE ### CLAUDE.md - [ ] Remove "Geographic Reality" section describing TRREB districts - [ ] Update "Star Schema" section with neighbourhood-centric model: - `dim_neighbourhood` (158 neighbourhoods) as central dimension - `dim_cmhc_zone` with neighbourhood mapping - `bridge_cmhc_neighbourhood` for area weights - `fact_census`, `fact_crime`, `fact_amenities` - [ ] Update "Data Model Overview" removing TRREB purchase facts - [ ] Update "DO NOT BUILD" section (remove TRREB-related warnings) - [ ] Update "Reference Documents" table (remove deleted docs) - [ ] Update sprint status to Sprint 9 ### docs/PROJECT_REFERENCE.md - [ ] Update architecture section for neighbourhood-based approach - [ ] Document new data sources: - Toronto Open Data Portal (neighbourhoods, census, parks, schools, childcare) - Toronto Police Portal (crime rates, MCI, shootings) - CMHC (rental data with zone crosswalk) - [ ] Update star schema documentation - [ ] Remove TRREB PDF parsing architecture - [ ] Document 5-tab dashboard structure (Overview, Housing, Safety, Demographics, Amenities) ## Acceptance Criteria - [ ] No references to TRREB districts, PDF parsing, or FactPurchases in CLAUDE.md - [ ] Star schema accurately reflects neighbourhood-centric design - [ ] New data sources documented with API references - [ ] PROJECT_REFERENCE.md architecture diagram updated (if applicable) - [ ] All internal document references are valid (no broken links to deleted docs) - [ ] Documentation is consistent with `docs/changes/Change-Toronto-Analysis-Reviewed.md` ## Technical Notes - Use the implementation plan as the source of truth for the new architecture - Keep documentation concise - detailed specs are in the implementation plan - Preserve sections unrelated to Toronto dashboard (server info, common operations) ## Sprint Sprint 9 - Phase 2 (Documentation) **Labels:** Type/Refactor, Priority/High, Efforts/M, Component/Docs