Context: Person scopes are established as canonical identity (Decision 6c06cf0) for auth linking, assignment, and pending discussion topics. However, agents still retrieve stale facts from call notes because there's no canonical location for entity facts (start dates, roles, status).
Trigger: Friction 434afce - agent reported Wessel's start date as "Jan 15" (from Dec 16 call notes) when it had been updated to "February" in a later decision. The decision existed but didn't formally supersede the call note, and there was no canonical "current truth" to check.
Options:
relates_to Person, agents query Person's linked decisionsstart_date: Feb 2025, what happens when it changes again?supersedes relationship apply to Person field updates?| Approach | Pros | Cons |
|---|---|---|
| Structured fields on Person | Fast lookup, clear canonical source | Schema changes, manual updates |
| Decisions as Person children | Flexible, self-documenting | Need to synthesize from multiple decisions |
| Summary field on Person | Human-readable, flexible | Can become stale, no structured query |
| Backlinks from decisions | Uses existing infra | Agents must traverse and synthesize |
Context: Person scopes are established as canonical identity (Decision 6c06cf0) for auth linking, assignment, and pending discussion topics. However, agents still retrieve stale facts from call notes because there's no canonical location for entity facts (start dates, roles, status).
Trigger: Friction 434afce - agent reported Wessel's start date as "Jan 15" (from Dec 16 call notes) when it had been updated to "February" in a later decision. The decision existed but didn't formally supersede the call note, and there was no canonical "current truth" to check.
Options:
relates_to Person, agents query Person's linked decisionsstart_date: Feb 2025, what happens when it changes again?supersedes relationship apply to Person field updates?| Approach | Pros | Cons |
|---|---|---|
| Structured fields on Person | Fast lookup, clear canonical source | Schema changes, manual updates |
| Decisions as Person children | Flexible, self-documenting | Need to synthesize from multiple decisions |
| Summary field on Person | Human-readable, flexible | Can become stale, no structured query |
| Backlinks from decisions | Uses existing infra | Agents must traverse and synthesize |