FDE BenchmarkPublic document reader
Available in sourcev0.1 · live public draft · official release pending

Canonical source view. This renders the bundled repository document as readable HTML. Source metadata remains in the repository, and relative document links remain inside this reader.

Outcome architecture proposal contract tests

Status: Proposed / not authorized

Run from the public benchmark repository root:

node --test docs/proposals/outcome-architecture/tests/outcome-contracts.test.mjs

The focused gate validates:

  • six strict JSON Schema 2020-12 proposal contracts;
  • five fixtures declared synthetic and shaped with synthetic identifiers, while explicitly denying that schema validation proves provenance and requiring an application/environment ingestion guard;
  • separation of factual production records, multidimensional capability profiles, and non-issued credential-tier candidates;
  • preservation of Insufficient Evidence without a numeric zero;
  • explicit, digest-bound rubric, evaluator, scoring-policy, competency-registry, and calculation-manifest lineage for every capability profile, with non-estimated dimensions unable to claim high support confidence;
  • exact corroborated production-fact ID and digest resolution for every production-record capability binding, with fact fields prohibited on other source classes;
  • rejection of global scores, psychometric-validation claims, assigned tiers, credential issuance, and signed credential payloads;
  • 13 property-bound, digest-verified evidence-readiness receipts, followed by a separate independent-method-review receipt and a later governance-decision receipt, while preserving the v0.1 prohibition and preventing circular readiness logic;
  • exact human-only, model-only, and human-with-AI condition coverage on a common scenario manifest;
  • multi-scenario and condition-applicable multi-metric battery structure with no observed baseline, comparative score, rank, or result; and
  • 44 adversarial mutations split between strict-schema and relational-invariant boundaries.

The relational checker is outcome-invariants.mjs. Passing the suite does not validate the construct, authorize a pilot, enable real-person data, approve a score, establish a credentialing body, or issue a credential.