What a Successful Code Scan Does Not Prove
A green scan is a rebuilt document, not a correctness certificate.
Read articleTopic
openapi
Why AI Fills Gaps but Cannot Invent Routes
The model has a narrow lane: fill named gaps, never create routes.
Read articleUnmounted Routers and Unreachable Routes
A defined route is not callable until its router is mounted.
Read articleTurning a Scanned Spec into Scenario Tests
The scanned spec is the starting point for connected scenario verification.
Read articleThe Four-Layer Reconciliation Explained
The layers move from the live database to the proposed change.
Read articleTable Status: Missing, Drift, Matched, Extra
The status makes the table-level comparison explicit.
Read articleStatic Scanning Without a Model Key
The deterministic scan works offline with no model or provider key.
Read articleReviewing Detected Routes Before Adopting a Spec
Treat the scanned document as a draft to verify before you adopt it.
Read articleRescanning Incrementally Without Losing Edits
The sidecar keeps rescans fast and your manual edits intact.
Read articleProven, Proven-Empty, and Gap Completeness Gates
The gate makes every value explicit, including confirmed emptiness.
Read articleModeling A2A with the x-a2a Extension
A vendor extension keeps the A2A details explicit and reviewable.
Read articleInferring Many-to-Many Link Tables
A join table is inferred from the shape, not forced into one side.
Read article