[ORESoftware]

Purpose

Provide independent *-test organization evidence for ORESoftware/api-docs#92 and its first-class TypeSpec / JSON Schema authority model.

Exact immutable inputs

• API Docs candidate: ORESoftware/api-docs@f6bc8771365ee79cf72d53d640ea5c296b0e2dd1;
• canonical TJSV: ORESoftware/typespec-json-schema-validator@93dd73cb246a09b0a1c62d7192cc62ca6ecbe405.

Five independent authority pairs

The canary runs compiler-backed TJSV admission for docs discovery, HTTP request surfaces, ORES RPC config, form validation, and form-validation admission profiles.

For each pair it requires:

• TypeSpec and authored Draft 2020-12 JSON Schema both report independently-authored authority with precedence none;
• TypeSpec is transpiled through the official emitter to a dedicated generated JSON Schema witness;
• generated Schema B is comparison evidence only and the generated/authored comparison actually executes;
• differential probes execute with zero divergences/refusals;
• Contract IR is admissible, downstream-derived and non-editable;
• the generated JSON Schema witness exists;
• neither API Docs nor TJSV source is rewritten.

The HTTP request contract also executes its committed instance corpus; RPC uses its complete declaration mapping and intentional numeric int64 strategy.

Exact-head evidence

At canary head 5b3366fe89ba3c4a017074ac656077b7e8b6518a, all PR workflows are green. Run 34668384018 executed the full peer-authority job stepfully, including Compile TypeSpec and compare every API Docs peer authority and Prove authored API Docs sources were not rewritten.

Diagnostic artifact upload is best-effort and cannot override semantic admission.

Tracking: DEN-3828 / DEN-3938.

[linear-code]

DEN-3828