6e8f0db6c0
- Add dialogue prompt file writing for audit/debugging - Update README install instructions - Add new RFCs (0053, 0055-0059, 0062) - Add recorded dialogues and expert pools - Add ADR 0018 dynamodb-portable-schema - Update TODO with hook configuration notes Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.5 KiB
[PERSPECTIVE P01: AAD portability is fully addressed by the converged Phase B specification]
The converged position adopts AAD = sha256(canonical_entity_address) with canonical address dialogue:{id}/entity:{type}/{subkey} -- backend-independent by construction. This is exactly the fix I proposed in R2 and it is correctly sequenced before the first encrypted write. TARTLET R1-T01 is resolved.
[PERSPECTIVE P02: Hash chain boundary is a Phase C migration detail, not a convergence blocker] My R2-P02 raised hash chain continuity across backend boundaries (signed migration-boundary events bridging terminal and genesis hashes). This concern is real but scoped to the migration protocol within Phase C, not to the envelope format defined in Phase B. The three-phase gate sequences it correctly: by the time migration occurs, the trait boundary and envelope spec already exist, and the migration-boundary event can be specified as part of the Phase C deliverable without blocking Phases A or B.
[RESOLVED TARTLET R1-T01] Canonical entity address AAD binding, adopted into Phase B with a round-trip exit gate across both backends, eliminates the encryption portability gap I identified in R1.
[CONCESSION: Hash chain boundary event does not require its own phase or gate] I initially framed hash chain continuity as a critical unsolved half of the portability problem. In the converged three-phase structure, it is a well-bounded implementation task inside Phase C's migration protocol, not an architectural decision requiring panel resolution.
[MOVE:CONVERGE]