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>
64 lines
2.8 KiB
Markdown
64 lines
2.8 KiB
Markdown
# Round 1 Summary: Local-Production Parity
|
|
|
|
**ALIGNMENT Score**: +156 (Velocity: +69) | **Panel**: 6 experts | **Status**: CONSTRAINT PIVOT
|
|
|
|
## Critical Update: User Rejected Tiered Architecture
|
|
|
|
The user has explicitly rejected the tiered/progressive disclosure model:
|
|
|
|
> "I do NOT like the tiered architecture. We want to be able to deploy at a moment's notice and have tested the same code that will run in prod locally."
|
|
|
|
**New Constraints (Round 2+):**
|
|
1. **New repo** - Greenfield Rust project
|
|
2. **Docker REQUIRED** - DynamoDB Local is mandatory, no SQLite fallback
|
|
3. **TRUE parity** - Same code runs locally and production
|
|
4. **No tiers** - Level 0-3 progressive disclosure is rejected
|
|
|
|
## Round 1 Convergence (Now Invalidated)
|
|
|
|
The panel had converged on:
|
|
- T0001 RESOLVED: Three-mode dashboard (LOCAL/STAGING/PRODUCTION)
|
|
- T0002 RESOLVED: Code path parity via same algorithms
|
|
- T0004 RESOLVED: Docker optional, `cargo build && ./blue install` default
|
|
|
|
**These resolutions are now INVALID.** Round 2 must reconverge under new constraints.
|
|
|
|
## Perspectives That Survive
|
|
|
|
| ID | Perspective | Status |
|
|
|----|-------------|--------|
|
|
| P0002 | Encryption algorithms must be identical | **KEPT** |
|
|
| P0004 | LocalSecretsProvider replaces Infisical locally | **KEPT** |
|
|
| P0010 | DashboardEnvelope pattern | **KEPT** |
|
|
| P0011 | Key hierarchy must be fully exercised locally | **KEPT** - Now mandatory |
|
|
|
|
## Perspectives That Must Change
|
|
|
|
| ID | Perspective | New Status |
|
|
|----|-------------|------------|
|
|
| P0005 | Two-minute onboarding rule | **RELAXED** - Docker setup acceptable |
|
|
| P0006 | DynamoDB Local has 99% parity | **ELEVATED** - Now required, not optional |
|
|
| P0008 | Full production parity unnecessary | **REJECTED** - User demands full parity |
|
|
| P0009 | Progressive disclosure (Level 0-3) | **REJECTED** |
|
|
|
|
## Tensions for Round 2
|
|
|
|
| ID | Tension | Status |
|
|
|----|---------|--------|
|
|
| T0001 | Dashboard decryption vs zero-knowledge | RESOLVED (kept) |
|
|
| T0002 | Full parity vs ergonomics | **REOPENED** - User chose full parity |
|
|
| T0003 | Auto-generated keys vs reproducible testing | OPEN |
|
|
| T0004 | Docker requirement vs simplicity | **RESOLVED** - Docker required |
|
|
| T0005 | Infisical SDK not exercised locally | OPEN |
|
|
| T0006 | **NEW** Greenfield repo scope and boundaries | OPEN |
|
|
|
|
## Key Question for Round 2
|
|
|
|
> Given Docker is REQUIRED and parity is NON-NEGOTIABLE, what is the minimal correct architecture for a new Rust repo that achieves true local-production encryption parity?
|
|
|
|
## Panel Evolution for Round 2
|
|
|
|
- **Retain**: Cupcake (Security), Palmier (QA), Cannoli (SRE)
|
|
- **Rotate out**: Scone (DevEx focus no longer primary), Macaron (simplicity position rejected)
|
|
- **Add from pool**: Database Architect (DynamoDB schema), Infrastructure Engineer (Docker setup)
|
|
- **Retain with changed focus**: Muffin (Platform - now Docker-required advocate)
|