alkdev/alknet

0 Fork 0

Files

T

glm-5.2 1baa619ce9 docs(arch): decompose open-questions.md into per-OQ files under questions/

The monolithic open-questions.md (1310 lines, 47 OQs) was large enough to be
unmanageable, with high size variance (OQ-42 at 220 lines next to OQ-06 at 8).
Decomposed into one file per OQ under docs/architecture/questions/ (NNN-slug.md,
mirroring the ADR convention), with open-questions.md retained as the index:
theme-grouped tables plus a cross-theme Deferred/Blocked section that surfaces
the 6 deferred OQs with their Blocked-on conditions inline (the safe-exit
visibility surface). Per-OQ content moved verbatim; all 62 inbound links stay
valid (none used anchors). README's curated OQ summary dropped (now redundant
with the index tables).

Also seeds tasks/architecture/ with this task plus two follow-ups found during
the decompose: OQ-09/10 missing structured Blocked-on fields, and the
tasks/architecture/ blocker-task half of the Safe Exit protocol being
unenforced.

2026-07-06 16:07:59 +00:00

2.2 KiB

Raw Blame History

OQ-33: PeerId — Cryptographic Identity vs Stable Logical Identifier

Origin: ADR-029 Assumption 1, docs/research/alknet-call-peer-routing/findings.md §6.1
Status: resolved (2026-06-27 by ADR-030)
Door type: One-way (composition semantics), two-way (id source)
Priority: high
Resolution: PeerId is a logical identifier, decoupled from the cryptographic identity. It is not the raw fingerprint or API-key prefix — those change on key rotation, which would break every in-flight PeerRef::Specific and every ACL entry referencing that peer.

ADR-029 established the one-way door (PeerId is logical, not crypto) with a v1 UUID source as a no-storage workaround. ADR-030 supersedes the UUID source: Identity.id becomes PeerEntry.peer_id (stable across key rotation) on the fingerprint path, and PeerId = Identity.id from IdentityProvider resolution. The UUID workaround is removed — the stable logical id is the real thing, sourced from the auth system, not an ephemeral connection-assigned value.

The PeerEntry config model (peer_id, fingerprint, scopes, resources, display_name, enabled) lives in AuthPolicy. Key rotation is a single PeerEntry.fingerprint update — the peer_id, ACL entries, and PeerRef::Specific references stay stable. The no-DB posture is preserved (core has the trait + the in-memory ConfigIdentityProvider adapter; persistence adapters are additive separate crates, ADR-033).

The one-way door (preserved from ADR-029): PeerId is a logical id, not Identity.id (the fingerprint). This determines the PeerCompositeEnv key type, the PeerRef::Specific payload type, and the ScopedPeerEnv.peer_pinned entry shape. The source of the logical id (ADR-029's UUID → ADR-030's PeerEntry.peer_id) was the two-way-door remainder; it is now resolved.
Cross-references: ADR-009, ADR-014, ADR-015, ADR-017, ADR-021, ADR-027, ADR-029, ADR-030, OQ-34, OQ-35, client-and-adapters.md, operation-registry.md, auth.md

2.2 KiB Raw Blame History

OQ-33: PeerId — Cryptographic Identity vs Stable Logical Identifier

2.2 KiB

Raw Blame History