ICPI Cutover Readiness

What Is Verified

The following are now verified with live local runtime checks:

• direct old-host vs new-host read parity
• direct old-host vs new-host protected-write denial parity
• direct old-host vs new-host successful authenticated write parity
• gateway fallback parity on reads
• gateway fallback parity on protected-write denials
• gateway fallback parity on successful authenticated write
• gateway cutover parity on reads
• gateway cutover parity on protected-write denials
• gateway cutover parity on successful authenticated write
• rollback by env flip back to fallback routing
• rollback confidence after successful authenticated ICPI writes

What Still Remains Risky

• verification used one seeded dev impersonation identity, not a broader user matrix
• verification used one representative ICPI upsert row family, not a bulk or multi-row ingestion batch