How every persona connects to every other: who provisions whom, who hands data to whom, and who is blocked waiting on whom. Details per persona live in persona-01 through persona-06. Confidence markers per README.md; the arrows below are each backed by the evidence in those files.
Reading guide
Orange arrows are provisioning: nothing exists until FT Admin creates it, which is why the QC script runs the admin section first and why 7 of its 11 environment objects are admin-gated. Grey arrows are the operating loop, and the money path reads left to right along the bottom half: the producer’s scans fill the programme pool (Activated), the retailer reserves from that pool and nominates a manufacturer, the manufacturer links scans and proposes a claim with the amount only they can know, the retailer confirms and hands the resulting QR certificate to the public verifier. The owner’s contribution is content (certificates, documents, wording) flowing onto everyone’s evidence packs, and uptake data flowing back.
Who blocks whom: the retailer cannot claim without a manufacturer proposal (in the PO flow), the manufacturer cannot propose without a shared nomination AND scannable sessions, the producer cannot produce without registration, pigment and (for SDU flows) devices — and every one of those prerequisites is an FT Admin action. The auditor and the neutral Tier 2/3 participants are the quiet load-bearing actors: their scans and waybill pairs are what the supply-chain map and chain of custody are made of, though they never touch a claim.
Two personas the QC script does not test but the code enforces: the auditor (scan-only role, force-signed-out of the dashboard) and the public verifier (token-gated pages, revoked banners). Details in persona-06-additional-roles.md.