Eric Garcia 6e8f0db6c0 chore: add dialogues, RFCs, docs and minor improvements

- 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>

2026-02-26 08:51:56 -05:00

3.3 KiB

Raw Blame History

Round 3 Summary: Local-Production Parity (Final Convergence)

ALIGNMENT Score: +289 (Velocity: +46, Total: 289) | Panel: 3 experts | Status: 100% CONVERGED

Open Items Resolved

O0001: Test Vector Generation (Palmier)

RESOLUTION: Hybrid approach with three layers

Layer	Source	Purpose
1	NIST CAVP KAT	Verify AES-256-GCM primitives
2	Python `cryptography` reference	Envelope format conformance
3	Property-based tests	Round-trip fuzzing

Deliverables:

tests/crypto/test_aes_gcm_nist_kat.rs
tests/crypto/test_envelope_vectors.rs
scripts/generate_test_vectors.py (committed with hash)

O0002: Local Key Rotation (Cupcake)

RESOLUTION: Local keys are NEVER rotated

Rationale: Local development data is disposable. Adding rotation machinery for test data violates YAGNI.

Behavior:

If UMK changes/missing:
  1. CLI detects decrypt failure
  2. Prompts: "Reset local database? [y/N]"
  3. Yes → wipe + fresh key
  4. No → abort with recovery instructions

Documentation: Add clear warning that local data is not durable.

O0003: Crypto Audit + Trace Context (Cannoli)

RESOLUTION: Include trace_id with hash chain for tamper-evidence

struct CryptoAuditEvent {
    event_id: Uuid,
    timestamp: DateTime<Utc>,
    trace_id: String,          // For correlation
    span_id: String,
    operation: CryptoOp,
    key_id: String,
    principal: String,
    outcome: Outcome,
    previous_hash: String,     // Chain integrity
    event_hash: String,        // SHA-256(all above)
}

Constraints:

Append-only storage (PutItem only, no modify/delete)
Daily chain verification job
Alert on hash discontinuity

Final Convergence Checklist

Item	Status	Resolution
Docker required	✅ RESOLVED	Mandatory for all developers
DynamoDB Local only	✅ RESOLVED	No SQLite fallback
KeyProvider trait	✅ RESOLVED	LocalFile + AwsKms implementations
Test strategy	✅ RESOLVED	Two-layer + NIST KAT + property tests
Observability	✅ RESOLVED	Config-driven, same everywhere
DynamoDB schema	✅ RESOLVED	Single table, endpoint override only
Docker infrastructure	✅ RESOLVED	justfile + docker-compose.yml
Test vector generation	✅ RESOLVED	Hybrid: NIST + reference + property
Local key rotation	✅ RESOLVED	Never rotated, disposable
Audit trace correlation	✅ RESOLVED	Hash chain + trace_id

Expert Signals

Cupcake: [MOVE:CONVERGE] "O0002 resolved. Ready for final convergence check."
Palmier: [MOVE:CONVERGE] "O0001 resolved. Ready for implementation."
Cannoli: [MOVE:CONVERGE] "O0003 is resolved. Ready to proceed to implementation."

VERDICT: 100% CONVERGENCE ACHIEVED

Zero open tensions. Zero open items. All experts signal CONVERGE.

The dialogue has completed. Ready to draft final RFC for blue-encrypted-store crate.

Dialogue Statistics

Metric	Value
Rounds	3
Total Experts	10 unique
Perspectives Registered	28
Tensions Surfaced	6
Tensions Resolved	6
Open Items Resolved	3
Final ALIGNMENT Score	289

"True parity means the code you test is the code you ship."

3.3 KiB Raw Blame History