Two of the three layers are run by Krenn·IQ; only the §6 cross-model adversarial review is external. The layers: a constitution that fixes what may be called proven; a cross-model adversarial review, in which a model from another company challenges the public claims with executed commands; and reproducible conformance, an invariant suite whose CI result carries signed provenance. The Gate App’s decision record lives under Decision log.
GOVERNANCE §2 fixes the states a claim may hold (proved, derived, empirical, conjecture…). §6 fixes the constructor ≠ verifier rule: the builder of a claim cannot declare it proven. On this site: three labels. CLOSED: a locked test that cannot regress. BACKED: regenerates from a command and its hash matches. SCOPED: a declared estimate with its corpus and the artifact that would upgrade it. The proof ledger (28 entries) and the claim registry regenerate from code; the release blocks if a public number has no label.
Charter: GOVERNANCE.md, binding in direction, not yet legally executed · Responsible disclosure: SECURITY.md.
The §6 package holds 10 public claims, each with its evidence and a refutation procedure. A model of another family, xAI grok-4.7, directs; a script runs its commands under a read-only allow-list, no network, no writes, and returns the raw output unedited. Eight runs on 2026-10-13, about 4.5 million tokens; a ninth aborted when the credit ran out.
Transcripts and runner: research/section6_package/ · refutations frozen as tests: benchmarks/test_section6_refutations.py. Nothing is marked proved; a claim not refuted by one reviewer family stays empirical.
The conformance suite runs ten invariants: fail-closed, robustness, no model in the verdict, research-layer decoupling, quantum commitment, pharma admissibility, proof ledger, HOLD resolution, audit hash, surface isolation. It produces a reproducible result hash. In CI, on GitHub infrastructure, the result is signed keyless (Sigstore, Rekor) and published as an artifact. That signature is signed provenance: it shows which CI run produced the result. A signature over a CI result is not a scientific validation.
# run it yourself python3 benchmarks/conformance.py # verify the CI-signed result (artifact: capas-conformance-attestation) cosign verify-blob conformance_result.json \ --certificate conformance_result.pem --signature conformance_result.sig \ --certificate-identity-regexp 'github.com/fomv9354lve/capas-inteligentes' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com
Workflow: .github/workflows/conformance.yml · OpenSSF Best Practices badge: passing, self-certified with static and dynamic analysis · CodeQL and Scorecard weekly.