Conformance, computed against the running build
Two reports over one project, from opposite directions. The conformance criteria below are computed: they fold the gate verdicts this build genuinely verifies through lone's web-build conformance model, and report everything they cannot verify as not assessed — never as met. The strong WCAG 2.2 AA / OWASP ASVS claim is emitted only when every gating criterion passes, so this report can never overclaim on its own. The claims registry underneath is the other half: what a person asserts about this system and grades by hand, each claim carrying its gap and a link to the code behind it.
machine-readable report ↗︎ · claims.jsonld · the signed build provenance
Conformance
Partial conformance: automated DOM checks clean; WCAG 2.2 AA (manual audit) not supplied; OWASP ASVS Level 2 not supplied; Core Web Vitals (p75) not supplied; Baseline Widely Available not supplied; runtime reliability not supplied.
15/37 criteria met · 1 unmet · 21 not assessed · Bounded Systems Web-Build Conformance Standard v1.0.0
html 2/2 met
html: 2/2 met
accessibility 4/6 met
accessibility: 4/6 met (2 not assessed)
- met WAI-ARIA author requirements WAI-ARIA 1.2 · author conformance lone static checks clean (no findings) evidence
- met WCAG 2.2 AA (automated subset) WCAG 2.2 · AA (automated subset) lone static checks clean (no findings) evidence
- met axe serious/critical violations axe-core · serious/critical 0 serious/critical violations evidence
- not assessed WCAG 2.2 AA (manual audit) WCAG 2.2 · AA (manual) no manual WCAG 2.2 AA audit supplied evidence
- not assessed WCAG 2.2 AAA (selected) WCAG 2.2 · AAA (selected) no AAA attestation supplied (optional) evidence
- met Agent heuristic accessibility review ARIA/WCAG (machine heuristic) · agent heuristic (recommended) agent heuristic pass clean — 7 page(s), 0 warning(s). AGENT/STATIC HEURISTIC — NOT AT-user testing; a11y.wcag22-aa-manual stays not-assessed. evidence
design 0/5 met
design: 0/5 met (5 not assessed)
- not assessed Palette contrast (design tokens) WCAG 2.2 + APCA · AA (token-level) no palette-token report supplied evidence
- not assessed Typography tokens WCAG 2.2 · AA (token-level) no typography-token report supplied evidence
- not assessed Target size (interactive tokens) WCAG 2.2 · AA (token-level) no target-size report supplied evidence
- not assessed Effective contrast under opacity WCAG 2.2 · AA (token-level) no opacity-contrast report supplied evidence
- not assessed Token likeness hygiene Design-system hygiene · recommended no token-likeness report supplied evidence
security 1/3 met
security: 1/3 met (2 not assessed)
- not assessed OWASP ASVS Level 2 OWASP ASVS 5.0.0 · L2 no OWASP ASVS attestation supplied evidence
- met known critical/high vulns OWASP ASVS 5.0.0 · zero critical/high 0 known critical/high vulns evidence
- not assessed HSTS preload RFC 6797 / hstspreload.org · preloaded no HSTS preload status supplied evidence
performance 0/1 met
performance: 0/1 met (1 not assessed)
- not assessed Core Web Vitals (p75) Core Web Vitals · p75 mobile + desktop no Core Web Vitals field data supplied evidence
compatibility 0/1 met
compatibility: 0/1 met (1 not assessed)
- not assessed Baseline Widely Available Baseline · Widely Available no Baseline result supplied evidence
reliability 0/1 met
reliability: 0/1 met (1 not assessed)
- not assessed runtime reliability Bounded Systems reliability bar · — no runtime reliability report supplied evidence
semantic 2/5 met
semantic: 2/5 met (3 not assessed)
- met JSON-LD 1.1 + SHACL conformance JSON-LD 1.1 / SHACL · conforms JSON-LD 1.1 conforms to SHACL shapes (0 violating blocks) evidence
- not assessed CommonMark conformance CommonMark · conforms no CommonMark report supplied evidence
- met AI-readability llms.txt convention · recommended llms.txt present, links resolve, Markdown siblings exposed evidence
- not assessed OpenAPI 3.2 + JSON Schema 2020-12 OpenAPI 3.2 / JSON Schema 2020-12 · conditional no OpenAPI report supplied (only applies if an API is published) evidence
- not assessed Atom feed (RFC 4287) RFC 4287 · recommended no feed report supplied (optional) evidence
seo 1/1 met
seo: 1/1 met
- met Technical SEO Search-engine technical guidelines / RFC 9309 · clean canonical/titles/robots/sitemap clean, 0 broken internal links evidence
integrity 4/9 met
integrity: 4/9 met (5 not assessed)
- not assessed SLSA provenance + in-toto SLSA / in-toto · present + signed + verified no SLSA/in-toto provenance supplied evidence
- met Reproducible build Reproducible Builds · reproducible build is byte-reproducible evidence
- met SPDX SBOM SPDX · present + valid + complete + signed SPDX SBOM present, valid, complete, and signed evidence
- met Content digests (RFC 9530) RFC 9530 · recommended Repr-Digest headers present (RFC 9530) evidence
- met Signed release manifest Bounded Systems release bar · present + signed release manifest present and signed evidence
- not assessed IPFS CID recorded IPFS / CIDv1 · recommended no IPFS CID report supplied (optional) evidence
- not assessed HTTP correctness (RFC 9110) RFC 9110 · recommended no RFC 9110 HTTP report supplied (optional) evidence
- not assessed OpenSSF Scorecard OpenSSF Scorecard · score ≥ 7.0 no OpenSSF Scorecard result supplied evidence
- not assessed SLSA build level SLSA · ≥ target (default L3) no SLSA build level supplied evidence
cognitive 1/3 met
cognitive: 1/3 met (1 unmet, 1 not assessed)
- met Interface-complexity budget (W3C COGA-derived) W3C COGA (derived) · budget (recommended) lone static checks clean (no findings) evidence
- unmet COGA Obj-5: Focus budget (attention proxy) W3C COGA Making Content Usable — Objective 5 · Obj-5 proxy (recommended) not-yet-met: readingGrade threshold exceeded, avgSentenceLength threshold exceeded, jargonDensity threshold exceeded. AGENT/STATIC PROXY for COGA Obj-5 — NOT COGA usability testing with cognitive disabilities. Do NOT mass-rewrite content — editorial is the maintainer's call; gate reports honestly. evidence
- not assessed COGA usability testing W3C COGA · manual (recommended) no COGA usability testing supplied (optional) evidence
The claims registry
Every claim this project makes about itself, with the grade it holds, the gap that grade leaves open, and a link to the code that backs it. Rendered from the same signed graph the site publishes at claims.jsonld — the sentences below are that file's, not a summary of it.
-
c1
Docs generate from source and fail CI on drift.
-
c2
guest-room's behaviour specs execute against the engine.
-
legibility
The landing page passes the legibility gate.
Gap — The gate measures budgets and banned words, so it can show the page did not regress. It cannot show the page lands: the cold-read scenarios are judged by a model on demand (npm run coldread), by hand and never in the build. That judge is Opus — a ceiling test, so a red run is strong evidence and a green one is weak. The comprehension test itself is one outside human and is not automated.
-
c3
A git-write carries a verifiable in-toto / SLSA provenance derivation — signed per-actor, content-addressed in a derivation ledger, checked fail-closed at the merge gate.
Gap — Emission and enforcement are opt-in (a signer plus require-signed) until Sigstore lands; without them the push is bare. Verified mechanisms: ocap-provenance/slsa.ts, prx verify.ts/merge-guard.ts, anchored-chain.
-
c4
The agent never holds the credential — a broker daemon does.
Gap — On macOS the door is TCP loopback — weaker than unix-socket possession; isolation is the container plus daemon discipline, not a hardened sandbox. Verified: keeperd/daemon.ts holds the key; claude-box is credential-free.
-
c5
prx and claude-box converge onto one guest-room door runtime.
Gap — Convergence is in progress — prx wires the seams in-process today; the out-of-process door runtime is the direction, not yet at scale.
-
c6
Contracts stay honest between components as they evolve.
Gap — Inter-contract enforcement is the open problem this whole project is aimed at — a bet, stated as direction, not a solved result.