The moment the applicant submits (flow 01, S6), the application appears here: the Recommendation it cites, the applicant, a summary, and how long it has waited. The queue is ordered oldest first, so nothing waits silently at the bottom of a pile. This is the authority's desk at its most honest: every application that needs a decision, visible, with its age on the row.

One click and the whole file is there: the applicant, the instrument with its classified attributes, the samples declared, the documentation checklist as submitted, and the timeline of every act so far. The action bar offers exactly the acts the state machine allows at this moment (request samples, accept, reject), never a button the record would refuse. Nothing is re-typed anywhere in this flow: what the applicant bound in the wizard is what the officer reviews.

Rejection is a first-class act, not a deletion. Try to reject without a reason and the act refuses: the scheme requires the reason (PD-05 §4.2.2/§4.2.4, whose refusal grounds run to "other clearly identified reasons"), the form stays open, and nothing happens silently. With the reason typed, the rejection lands on the audit chain and the applicant is notified with the reason attached. Try it on the demo: open any waiting application from the queue, choose Reject, and try to confirm empty; the warning names the clause.

Type evaluation needs physical samples (PD-05 §4.2.5), so the officer issues the sample request from the review with its particulars. The applicant ships (their side of this act is in flow 05), the officer registers each arriving receipt with its serial and condition, and the accept act stays closed until the samples are received: the pre-acceptance sample stop, so no application is ever accepted on paper alone.

The accept is the pivot of the whole scheme. It creates the Evaluation Project, the shared dataspace every later act lives on: the application record, the samples, the laboratories, the test requests, the test reports, the evaluation, and at the end the certificate. The applicant gains the view of their project's record at this moment (the cone: their own project, the restricted fields honestly hidden), and the laboratory will join it on the accepted assignment in flow 03. One project, three parties, no parallel copies.

The fee negotiation between the authority and the applicant runs outside the system, as it does today: by email, by phone, by procurement. What the platform keeps is the evidence of the agreement: the signed contract or quotation uploads to the record as a document with its attested SHA-256, marked as the agreement's evidence, visible to exactly the parties and the scheme's oversight. Today the upload anchors on the pre-application engagement; the project-anchored upload (the agreement evidence on the Evaluation Project itself) is built and in review on the platform's integration branch, and this page will carry its capture when it ships. The doctrine never changes either way: the negotiation stays human, the evidence stays on the record.

Which tests, on which samples, at which laboratory: the dispatch builder crosses the model's test forms with the samples selected for the evaluation (R 60-3 §4.7, the selection recorded with its justification) and assigns each cell to a laboratory. One test request is composed per laboratory, the plan names every assignment it makes, and out-of-round rows are reported, never silently dropped. The laboratory picker answers from the laboratories' scopes, so a request cannot land where it cannot be performed.

The samples have to travel too, and the scheme is honest about who carries them: the authority ships them to the laboratory, or the applicant ships them directly. The decision is a recorded act on the project (who ships, with what custody), and the custody chain then tracks every hop: shipped, in transit, received at the bench. With the request issued and the samples in transit, the laboratory's inbox has the work, which is the first scene of flow 03.