Define dashboard reference boundary and canon strategy

Problem

Decide which third-party dashboard artifacts stay external, which lessons should be distilled into Dataface guidance, and which Dataface-authored examples should become first-class exemplars inside the repo.

Context

• The team studies many external dashboards, but there is no rule for what becomes canon versus inspiration.
• Internal examples should be durable teaching assets, not a mixed pile of screenshots and links.
• The decision affects docs, example repos, AI prompts, and what reviewers treat as authoritative.

Possible Solutions

• A - Keep all references external and rely on reviewers to remember what matters: low-maintenance, but weak as a shared canon.
• B - Copy admired third-party dashboards directly into the repo as examples: immediate visibility, but poor IP and authorship boundaries.
• C - Recommended: define a boundary where third-party artifacts stay as references, lessons are distilled into guidance, and only Dataface-authored examples become canonical exemplars.

Plan

1. Classify current references into external inspiration, distilled guidance, and repo canon.
2. Define criteria for promoting an example into first-class canonical status.
3. Propose storage locations for external notes, distilled lessons, and canonical exemplars.
4. Document the strategy and apply it to an initial reference set.

Implementation Progress

QA Exploration

• [ ] QA exploration completed (or N/A for non-UI tasks)

Review Feedback

• [ ] Review cleared