Skip to content

Can an outside developer reproduce the checker from the specification?

This doorway provides one bounded clean-room task. No foreign attempt has occurred yet.

Trial 0.2-r5 is ENGINEERING_COMPLETE. Instrument integrity is ESTABLISHED. External counters remain 0/0/0/0 · r0.

What this check cannot tell you

The profile and Trial 0.2-r5 instrument use team-authored synthetic promises, cases, expected projections, implementations, evidence, keys, witness roots, rail observations, and settlement roles. No two-mirror publication set, cold-reader calibration, or foreign checker attempt has occurred, and recruitment readiness remains blocked. Surface completeness is relative to named frozen schemas, AL-* rules, and protected fields; it does not cover every open-world interaction. Foreign authorability, independent reproduction, institutional handling, operational separation, and marginal decision value remain blocked. Recruitment is an investigator-selected, uncompensated convenience sample and does not establish economic adoptability or representative demand. Source-to-image correspondence remains NOT_COMPUTED without a reproducible rebuild. The evidence does not establish worldly truth, complete denominators, external collateral encumbrance, custody, collectibility, legal enforceability, organizational independence, production safety, actuarial calibration, or mainnet readiness. Bitcoin is an optional rail adapter and does not evaluate predicates. External A/J/I/W and replay counts remain 0/0/0/0 and r0.

Your task in seven steps

  1. Download the r5 checker envelope.
  2. Verify the archive and trial root with the separately supplied coordinator context.
  3. Implement the public checker contract without prohibited project source.
  4. Publish a credential-free source repository and frozen commit.
  5. Build a Linux/amd64 OCI image exposing /checker/verify.
  6. Freeze source, build recipe, dependencies, image digest, and access statement.
  7. Submit the frozen artifacts for one isolated blind execution.

Download the r5 checker envelope · Open the standalone doorway · Inspect the human-visible contract

What you receive

The deterministic bundle supplies the frozen specification, closed schemas, public conformance cases and expected public projections, canonicalization and signature vectors, and the generic checker contract. The HTML has no hosted assets, scripts, fonts, analytics, or network dependencies.

Checker archive: sha256:5cf42dd7c6bf4ef6cda4623da8a083935c9a868a74d4401ff1be8f3ab146b92f
Publication archive: sha256:ae8d804593dadbbb28238643dc29349daf432d410d557b6b089b58e70fe1dbb6

What you must return

Return a public HTTPS Git repository, an advertised forty-character commit, deterministic source-tree commitment, build recipe, dependency manifest, Linux/amd64 OCI digest, and signed access statement. A source assertion does not establish that the frozen image was rebuilt from that source.

What you will never be shown

Before source freeze, the distribution excludes the Assurance Linker reference implementation, reference checkers, author compiler, generators, mutations, scoring capsule, hidden inputs, and hidden answers. The source state is CLEAN_ROOM_ONLY.

What success establishes

Exact agreement on the committed unseen corpus would establish that one foreign checker reproduced the protected consequence decisions under the frozen profile, cases, and separately supplied verification context.

What success does not establish

Trial 0.2-r5 tests investigator-selected, uncompensated volunteer feasibility. It does not establish economic adoptability or representative developer demand.

A matching checker would not establish worldly truth, trustlessness, production safety, legal enforceability, organizational independence, or representative demand.

Current readiness and downloads

Mirror evidence is BLOCKED_PENDING_TWO_ANONYMOUS_RETRIEVALS. Cold-reader calibration is BLOCKED_PENDING_THREE_READERS. Candidate precommitment is BLOCKED_PENDING_INTERLEAVED_NINE_CANDIDATE_ROUND. No candidate has been contacted.

Marginal decision value

BLOCKED

Foreign authorability

BLOCKED

Independent reproducibility

BLOCKED

Institutional handling

BLOCKED

Operational separation

BLOCKED

Bundle manifest · Readiness · Dimensional results · Recruitment frame

Two roots; one inherited semantics

The semantic root commits to 16 inherited consequence inputs. The r5 ceremony root commits to 8 publication, provenance, scoring, and recruitment controls. R5 preserves the r4 semantic-root bytes exactly. A semantic change would require new primary and reserve corpora.

Semantic root: sha256:ebdbbf6646a4e00b007675b44eaac6aca81d2be6be075d37055648c2ec0ce0bf
Ceremony root: sha256:d5a5d5b43cde86f136b1625c3ceb9cb04e72fd4117dd574edf5eb751fe83f6b9
Trial root: sha256:17e72628d742bfa5583b7a0a4ec681dd72428aedad561224007f1e0c570ab2e6

Semantic root · Ceremony root · Signed trial envelope

Why r5 exists

R4 remained pre-recruitment. It did not resolve anonymous public source retrieval, did not bind deployment projection bytes through two delivery domains, and exhausted one candidate stratum before trying the next. R5 corrects those ceremony defects without changing the inherited consequence semantics. No calibration, contact, blind attempt, reveal, qualifying external evidence, or unsafe consequence occurred.

R4 correction · Source-provenance policy · Complete static bundle

Contingent “no shared code” result

Mirrors

Same content-addressed bundle from two domains.

Stranger

Source commit and OCI digest frozen before hidden input.

Scoring

Protected unseen projection compared by the frozen capsule.

BLOCKED_PENDING_FOREIGN_ATTEMPT