Orientation: the worker door
Nobody works on a site they have not been oriented to. Orientation is the module that makes that a record instead of a memory: the firm’s orientation content — a video and two questions the firm sets — completed by each worker under their own wallet, registered, and signed in against that register when they arrive. The project manager and the site superintendent read the register: who is oriented on this job, who is not, who has signed in.
The worker’s five steps
The firm sends the worker its orientation link. Register — the worker connects the wallet that is their identity on site and registers with their name (and the job, if the firm gave them one). View the modules — the page shows the modules the firm runs its work in: what they are being oriented into. The content loads for their wallet — the firm’s orientation video, filed by the firm and versioned, plays on the page. Two questions — multiple choice, set by the firm from its own content; both must be answered correctly. A wrong answer does not complete the orientation: the worker re-watches and tries again, as many times as it takes — the check is comprehension, not a trap. Sign in — on completion the worker lands in the firm’s Orientation register with their name, wallet, content version, quiz result and timestamps, and when they arrive on site they sign in against that entry.
The gate, stated plainly
The firm activates Orientation under the same rule as every module: 1 CST held for the module, in the firm’s wallet. Worker participation is open: a worker registering, watching, answering and signing in holds nothing — a casual worker is never asked to hold CST to watch a safety video. The worker’s wallet is identity on the register, nothing more. That treatment is deliberate, and it is the firm’s activation that carries the module.
The firm’s side
The firm loads its content once per company: the video (the master filed to the firm’s own vault under vault law, its playback copy on the site), the content version, and the two questions with their options and correct answers. The correct answers never leave the server — the worker’s page carries the questions and the options only. On completion, a completion certificate files itself to the firm’s vault as a system record — SHA-256 recorded, queued for anchoring, no upload credit, the same treatment as workflow run records — and its file number lands on the worker’s register entry. Content is the firm’s per company; the job each worker registers against is recorded on their own entry.
On the Northgate demonstration the flow ran with a fresh worker wallet holding nothing at all: registered against the job, answered one question wrong (the entry moved to In progress, completion refused), answered both right (Completed, certificate = vault file 7), signed in. The register entry reads Signed in, quiz 2/2 — the same record the PM and the superintendent read.
Orientation and safety
Orientation is a safety control, and it is wired like one: the register is the firm’s evidence that everyone on the job has seen the same content and passed the same check. An un-oriented worker on site is the exception this register exists to make visible — the PM and the site superintendent read oriented-versus-not from the register before the shift, not from memory after an incident.