v3.14.1 - the documents the model reads

Five findings from reading the documents a session actually opens, rather than the files a test can run.

The contract said the opposite of the schema. v3.14.0 moved evidence records to evidenceRegister in the schema, the validator and the exemplar plan, and left output-contract.md, which is the one of the four a session opens. Invariant 22 still sent acceptedEvidence ids to sourceRegister, a list of citations that cannot hold an evidence record. A plan following the contract produced output the schema then rejected.

The method list offered two states. Four lines below a gate that argues at length for three, the rendering template gave available and unavailable only, so a method whose prerequisites nobody had confirmed was written up as checked and failed, or as checked and passed. It uses the three the output contract already named.

The gate dimensions were short by two. decision-rules.md listed version, ports, source type and capacity, and not the recovery model or log chain that DMS-MODE refuses on. The rule told a reader to gate the fallback without saying what against, and it now names the case: refusing online DMS on a source in SIMPLE and then offering log shipping, which P03-001 refuses for the same reason.

The crosswalk bridged neither field. recovery_model and log_chain_status have been typed on the advisor side since v3.11.0 and fed P03-001 and P09-001 on the consumer side since the catalog shipped. The table between them named neither, so a handoff dropped both and the consumer asked again for what it had been told.

The validator never read what an answer returned. It checked whether a question fed a row, so UNKNOWN could sit under confirmed. An obligation could also be dismissed as not_applicable with no condition named, and the owed rows could be switched off by carrying the path in selectedMethodPath and omitting the alias the code happened to read. questionsAsked is typed, questions.json supplies the effects per consumer, and six mutations hold it.

73 gates, 117 scenarios, 3625 prerequisite checks.