MESHTEN LAB•Agent Governance & Safety
October 9, 2026•Field Case Study
A Speed Fix Introduced a Potential Tenant-Isolation Defect, and Independent Review Blocked It
A throughput change introduced a potential tenant-isolation defect. Independent review classified it as P0 and blocked deployment.
Core Finding:A throughput change introduced a potential tenant-isolation defect. Independent cross-model review classified it as P0 and blocked deployment. Across three review reports, 1 P0 and 16 P1 findings were recorded. The upgrade was not deployed.
Builder Test Suite
Passing
The builder's tests passed but missed the potential tenant-isolation defect.
Round 1 Verdict
BLOCK (1 P0, 4 P1)
Adversarial review caught 1 P0 tenant-isolation defect and 4 P1 defects; static checks caught 2 P2 warnings.
Upgrade commit to first remediation
about 25 minutes
Upgrade committed at 17:45, review report generated at 17:56, and first remediation committed at 18:10 (local time), about 25 minutes after the upgrade commit.
Round 2 Verdict
BLOCK (7 P1)
0 P0 defects; 4 P1 defects from adversarial review and 3 P1 secret-shaped literals in test files flagged by static scanning.
Empirical Findings Table
One upgrade, three review rounds, one P0 and 16 P1s blocked before merge, zero deployed| Telemetry Metric | Measured Value | Context & Observability |
|---|---|---|
| Builder Test Suite | Passing | The builder's tests passed but missed the potential tenant-isolation defect. |
| Round 1 Verdict | BLOCK (1 P0, 4 P1) | Adversarial review caught 1 P0 tenant-isolation defect and 4 P1 defects; static checks caught 2 P2 warnings. |
| Upgrade commit to first remediation | about 25 minutes | Upgrade committed at 17:45, review report generated at 17:56, and first remediation committed at 18:10 (local time), about 25 minutes after the upgrade commit. |
| Round 2 Verdict | BLOCK (7 P1) | 0 P0 defects; 4 P1 defects from adversarial review and 3 P1 secret-shaped literals in test files flagged by static scanning. |
| Round 2 Recurring Classes | 3 of 4 | Three of four findings recurred in narrower variations after the initial patch. |
| Round 3 Verdict | BLOCK (5 P1) | 0 P0 defects; 5 P1 defects identified during adversarial review. |
| Production Deployment | 0 Deployed | The upgrade was not deployed. |
Engineering Action Directives
- Performance changes need direct tests of tenant-isolation invariants.
- Passing throughput tests did not establish tenant isolation in this incident.
- In this incident, independent review found a defect missed by the builder's tests. We did not compare same-model and cross-model reviewers.
- Review findings need remediation and another independent review.
Methodology Boundaries & Limits
- Single incident (n=1): This analysis examines one service upgrade authored by one builder model family and inspected by one reviewer model family; it does not measure an aggregate vulnerability catch rate.
- The reviewer identified the potential P0 through code inspection; no live exploit was run.
- Unmerged branch state: The upgrade remains on an unmerged feature branch pending resolution of all outstanding high-severity findings.