anti/DECNET
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(identity): resolve merge revocability + SSE open questions

Browse Source 
Open Question 1 (merge revocability): adopted. The clusterer will
clear merged_into_uuid on contradicting evidence and publish a new
identity.unmerged topic alongside the existing three identity.* topics
so subscribers on identity.> get it from day one.

Open Question 2 (AttackerDetail UX on identity_id change): adopted
SSE over refresh-on-focus. New endpoint will mirror the existing
topology mutator SSE (bus subscription on identity.>, JWT via ?token=,
snapshot-on-connect + live forward).

Risk 2 (API URL stability for soft-merged loser UUIDs): struck —
already shipped in commit dc3d08d (read-only API follows
merged_into_uuid and surfaces the canonical winner).
This commit is contained in:
anti
2026-04-26 07:33:36 -04:00
parent f6b83755eb
commit 943bb3a39d
1 changed files with 15 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
development/IDENTITY_RESOLUTION.md
View File

@@ -234,11 +234,9 @@ badge linking to `/identities/<uuid>`. No change otherwise.
re-attributed; previous identity remains as a soft-merged re-attributed; previous identity remains as a soft-merged
reference"). The `merged_into_uuid` chain is the audit trail. reference"). The `merged_into_uuid` chain is the audit trail.
2. **API URL stability.** Identity UUIDs that get soft-merged via 2. ~~**API URL stability.**~~ Resolved in commit `dc3d08d`: the
`merged_into_uuid` should still resolve at read-only API follows `merged_into_uuid` and surfaces the canonical
`/api/v1/identities/{uuid}` — return 301 to the winner, or return winner. Loser UUIDs resolve to the winner row.
the loser row with a `merged_into` link. Decide before the
clusterer ships.
3. **Schema-version lock-in for federation.** `schema_version=1` is 3. **Schema-version lock-in for federation.** `schema_version=1` is
what we ship. Any fingerprint added to the identity row post-v1 what we ship. Any fingerprint added to the identity row post-v1
@@ -263,19 +261,19 @@ badge linking to `/identities/<uuid>`. No change otherwise.
## Open Questions ## Open Questions
1. **Revocability of identity merges.** When the clusterer merges 1. ~~**Revocability of identity merges.**~~ **Resolved 2026-04-26:**
identities A and B into A (via `merged_into_uuid`), can a future merges are revocable. `identity.unmerged` topic ships in
evidence update split them back apart? Leaning yes — clear `decnet/bus/topics.py` alongside the existing three so subscribers
`B.merged_into_uuid`, re-link B's original observations. But that on `identity.>` get it from day one. Clusterer clears
leaks history (any subscriber that cached "B is gone" now sees B `merged_into_uuid`, re-links observations, publishes
alive again). May need an explicit `identity.unmerged` topic. `identity.unmerged` + a fresh `identity.formed` for the
Decide before the clusterer ships. resurrected side.
2. **`AttackerDetail` UX when `identity_id` changes.** If an operator 2. ~~**`AttackerDetail` UX when `identity_id` changes.**~~ **Resolved
has a tab open showing `attackers/X` with identity_id=A, and the 2026-04-26:** SSE channel modeled on the topology-mutator SSE.
clusterer rewrites it to identity_id=B, the page goes stale. New endpoint subscribes to `identity.>`, JWT via `?token=`,
Acceptable: stale tab, refresh on focus. Better: SSE channel snapshot-on-connect + live forward. `AttackerDetail` and
pushes the change. Decide alongside the clusterer. `IdentityDetail` consume it.
3. **`SessionProfile.identity_id` FK.** Does this PR sequence add it, 3. **`SessionProfile.identity_id` FK.** Does this PR sequence add it,
or does it wait for V2 keystroke dynamics? Leaning **wait** — the or does it wait for V2 keystroke dynamics? Leaning **wait** — the