The laboratory's submission (flow 03, S6) does not arrive as an email attachment: it lands on the evaluation project's reports card, and the authority is notified. One project, one place to look. When every dispatched request stands fulfilled, the evaluation can begin.

This is the substantial model-driven work of the evaluation. Each test report opens section by section (two samples times the assigned forms in the walkthrough's example), every row carrying its provenance: which sample, which run, which reading. The acceptance rules are the Recommendation's own, and the derived verdicts are computed from the model, never hand-tallied. The officer reviews and passes each section with its evidence in view; a row that fails the model's rule says so, in the open.

Before the report is accepted, the review period opens: the project's participants (the laboratory, the applicant) can raise comment threads on the report, the parties are notified, and the threads must resolve before the decision completes. An open thread refuses the finalization with the thread named. Consultation is no longer a side channel of phone calls; it is a first-class, cone-gated part of the record. This surface is the newest build in the flows program, and the seeded worked example's report predates it, so the step carries the live link: open the submitted report of the walkthrough's own drive (the laboratory's submission in flow 03) and the review-period panel stands there.

The evaluation report's basic information pre-fills from what the applicant, the authority, and the laboratory already entered; the binding machinery never asks twice. The authority's own examinations (the authority information with the application number bound from the record, the synopsis, the inscriptions, the marking, the software, the documentation) are recorded from the workspace, each an act with its own evidence.

The synopsis composes itself from the authority's section verdicts and the accepted reports. Re-executing the verdicts re-runs the model's arithmetic over the evidence (the arithmetic authority), and the suggested verdict is exactly what the model computes. The officer finalizes at the suggested verdict with the mandatory rationale: the decision is the authority's, and the record shows what it was computed from. Where the evidence is missing, the machinery says INDETERMINATE rather than guessing.

The certificates desk lists the finalized evaluations ready to issue. The issuance form shows exactly what the signature will cover (the certified scope the evaluation's verdicts support, the scheme, the expiry, the remarks, the rendered preview) before the officer types the signer passphrase. The signature is the officer's attributed act over the organization's key, on the audit chain, and the certificate is CNML-signed at issue: data, not a scanned PDF. The walkthrough's capture stops at the form; the signing itself is the one act the scripted drive never performs, so the demo's register story stays the seeded one.

From the project's certificate card the authority submits the certificate for BIML registration (PD-05 §5.1); it walks to PENDING_REGISTRATION and lands in the BIML officer's registration inbox. The officer reviews the particulars and the evidence chain and registers: the certificate is ACTIVE and the registration record feeds the public register. The scheme's recorded direction (decided by the program on 2026-08-28) is auto-publish on verified intake, the register's trust resting on the signature and receipt machinery with the human surfaces as read postures; the demo's single-instance posture today presents the officer's register act, and this page names both honestly.

The register's public face needs no sign-in: the ACTIVE certificate's number, dates, and status are readable by anyone (market surveillance, buyers, other authorities), per B 18:2025 §14.8. The number resolves against the BIML-registered copy, and the same public posture backs the verify page in flow 05. The certificate's loop is closed: applied, tested, evaluated, signed, registered, and publicly checkable.