7.4 Local Loopback Viewer & CISO Subprocessor Exemption
chinwag viewer --loopback 127.0.0.1:5487Why Chinwag's zero-knowledge architecture qualifies for CISO Tier-1 Subprocessor Exemption and how the local chinwag ui viewer decrypts state exclusively on your machine.
7.4 Local Loopback Viewer & CISO Subprocessor Exemption
chinwag viewer --loopback 127.0.0.1:5487
Enterprise security reviews stall for months when an AI dev-tool vendor asks for read/write OAuth scopes to your GitHub repositories or routes plaintext source code through multi-tenant cloud databases.
Chinwag is architected so that Chinwag's cloud relay never possesses your decryption keys and never processes plaintext source code, prompts, diffs, or file paths.
The 5 × 4 Cryptographic Visibility Matrix
| Data Artifact | On Developer / CI Host | In Transit (iroh / Edge / .cwcard.png) | On Chinwag Cloud Relay | In GitHub Projects v2 / Linear |
|---|---|---|---|---|
| Source Code & Git/jj Diffs | Plaintext in local Shadow jj | X25519MLKEM768 + ChaCha20Poly1305 Ciphertext | Opaque Ciphertext Only (Zero keys) | Never transmitted (or link-only) |
| Agent Prompts & Bus Messages | Plaintext in local .chinwag/state.crdb | CHWGHPKE v2 + Dual K1+K2 Ed25519 | Opaque Ciphertext Only (0 retention after ACK) | Never transmitted |
| File-Scope Leases & Repo Paths | Plaintext globs (crates/auth/**) | Keyed BLAKE3 32-byte T_coalesce | Blinded 32-Byte Digest Only | Optional (Configurable per org) |
| CI Compiler / Stack Traces | Plaintext in runner memory | Sealed in CHWGHPKE v2 envelope | Opaque Ciphertext Only | Pass/Fail status badge only |
| Weekly Learning Flywheel | Auditable via inspect-flywheel | Signed 128-Byte numeric struct | 64B Numeric Counters + 64B Sig | Aggregated ◈ Chips & SURV % |
Local Loopback Workbench (chinwag ui)
When you inspect live agent conversations, diffs, .codegraph blast radius, or 176/176 UI gate screenshots in the Chinwag Workbench (chinwag ui), 100% of decryption and rendering happens locally on your machine:
chinwag uibinds strictly to the local loopback interface and reads your local SQLite/CRDB state (.chinwag/state.crdb) and OS Keychain (~/.chinwag/signing/).- Encrypted
CHWGHPKEv2 frames arriving from remote teammates or cloud CI runners are verified (0.09ms) and decrypted inside the local Rust process. - No plaintext DOM state, source diff, or session token is ever uploaded to a cloud dashboard.
Why CISOs Grant Tier-1 Subprocessor Exemption
Under GDPR Article 28, SOC 2 Type II, HIPAA, and ISO 27001 frameworks, a cloud transit provider that processes exclusively end-to-end encrypted ciphertext (where the customer holds sole custody of all X25519MLKEM768 private keys in hardware/OS keychains) operates as a zero-knowledge cryptographic conduit:
- Zero Plaintext Custody: A breach or subpoena of Chinwag's Cloudflare Edge relay yields only
X25519MLKEM768ciphertext and blinded32-byteBLAKE3hashes. - Zero GitHub Code Read Scope Required:
chinwag board initrequires onlyproject(for GitHub Projects v2 column updates) or Linear issue state tokens · neverreposource-code clone permissions on our cloud servers. - Instant Cryptographic Offboarding: Rotating your org vault key via
chinwag bond rotate-org-keyimmediately invalidates all historical key-agreement epochs.
Next Steps
- Next:
A.509Sovereign Agent PKIX Passports (draft-spector-a509-agent-pkix-00) - Ready for a tool your CISO will approve in one afternoon? Reserve Your Organization Credit Pack →
Blinded Commitments & 128B Flywheel
How Chinwag routes encrypted frames using blinded 32-byte BLAKE3 commitments (T_coalesce) and improves model routing with a 128-byte zero-code telemetry struct.
A.509 Agent Passports
Cryptographic identity, capability scoping, and mandatory conversation instance addressing (<SEAT>#<INSTANCE>) for autonomous AI coding agents.