Full Technical Findings & Reproducible Telemetry
1. Federated Pattern Promotion Without Sharing Code or Secrets
When an instance discovers a reusable engineering pattern (such as Next.js 16 + Prisma connection pooling or Playwright flake elimination), a deterministic refusal filter scans the candidate rule against the workspace's forbidden literals, domains, and paths. Only stack-level patterns corroborated across at least two independent pseudonymized workspaces reach the operator's approval gate.
2. Cryptographic Verification & GDPR Art. 17 Erasure Guarantees
Every workspace maintains its own SQLite ledger and age-encrypted backup archive. Before and after every model invocation, an HMAC-SHA256 state seal verifies that no cross-tenant file descriptors or environment variables were accessed.
Control Layer | Mechanism | Verification Frequency
-------------------------------+----------------------------------------------+------------------------
Workspace File Isolation | Dedicated git worktree + path resolver | Every tool call
State Integrity Seal | HMAC-SHA256 pre/post execution digest | Every agent node
Off-Host Backup Encryption | age asymmetric per-tenant keypair | Nightly + 24h restore drill
Outbound Literal Refusal Gate | AST + regex scan against tenant identifiers | Every candidate rule