Introducing Dossiers
Human-curated narrative groupings of SME knowledge.
The story layer on top of atomic expert insights.
They think in stories.
A Subject Matter entry says: “Material 638876A has the wrong description.”
Another says: “Orphan materials hide financial exposure.”
A third says: “The OR tracks implants on paper.”
Individually useful. But together they tell a bigger story:
the material data foundation is fragile, and each gap amplifies the next.
A Dossier is a narrative container
What a Dossier is not
| Concept | What it does | Executable? |
|---|---|---|
| Subject Matter | Atomic expert observation or check | Optional (Level 1) |
| Dossier | Narrative grouping of Subject Matter | No — pure metadata |
| Thesis | Testable business question with evidence scoring | Yes — SQL verdicts |
| Perspective | Algorithmic health score from signal findings | Yes — SQL aggregation |
| Tag | Flat label for filtering | No |
Tags are anonymous and flat. Bundles have a curator, a narrative, ordered membership, and a lifecycle.
The m:n Relationship
One entry, many dossiers. One dossier, many entries.
Subject Matter is independent. Dossiers depend on Subject Matter — never the reverse.
Subject Matter lives independently — dossiers are an optional layer
◆ Material Data Quality
- Wrong description (638876A)
- Orphan material investigation
- OR paper tracking
◆ OR Workflow Gaps
- OR paper tracking
- CC format change
- Midnight case split
“OR paper tracking” belongs in both bundles. Forcing it into one loses context.
Most entries will never belong to any dossier — and that’s fine.
Same pattern as every compiler
curated bundles
validate + cross-ref
generate SQL
tag:smebit
registry + memberships
tri-lingual metadata
notes + sort order
A Dossier in 30 lines
Three New Views
List page • Detail page • Cross-references on Subject Matter detail
Navigable from both directions
◆ Dossier → Subject Matter
- Full narrative text
- Curator card (name, role, date)
- Ordered member list
- Per-member curator notes
- Category + verdict badges
- Click through to Subject Matter detail
❖ Subject Matter → Dossiers
- “Part of” section on detail page
- Linked bundle titles
- Click through to bundle detail
- Tri-lingual display
- Sidebar nav with ◆ icon
- No bundle? No section shown
Why this shape, not another
| Decision | Choice | Rationale |
|---|---|---|
| Not executable | Metadata-only | That’s what theses are for |
| Flat, not nested | No hierarchy | Nesting creates taxonomies — premature |
| m:n, not 1:n | One entry, many dossiers | Knowledge belongs to multiple stories |
| Cross-tenant | scope.tenant_id: null | System knowledge spans hospitals |
| dbt tag | smebit (existing) | Builds automatically, no rebuild.sh changes |
| Note field | String or dict | Pragmatic: English-only or full tri-lingual |
Where Dossiers sit
narrative groupings
atomic knowledge
findings
verdicts
root causes
Subject Matter anchors to the analytical pyramid (signals, theses) through optional links.
Dossiers sit alongside, providing narrative — not computation.
A Dossier is narrative.
The difference between a list of facts and a story
is someone who decided what belongs together and why.