This is the one thing the certification proves: a customer registers a camera, the stream starts on its own, the AI catches a theft against the customer's own threshold, and the customer is told and can watch the clip. Click a stage to see what runs behind it, what production is doing today, and which test steps prove it.
As-built data flow
Solid green edges work in production today. Dashed red edges are broken at the service boundary. Dotted amber edges work but not in the shape the test needs. Click a component to see its edges and the steps that exercise it.
Latest activity
What the team has marked, confirmed, approved or signed most recently — so anyone joining async can see where things stand.
One relay, eight legs. Each leg has a lead who drives it and a verifier who confirms it; nothing starts until the previous gate is signed. Most steps need two people, not necessarily at the same time: the owner executes and marks P, then a different role presses Confirm whenever they get to it — the board carries the hand-off. Open “Who is involved, leg by leg” to see who owes what; pick a leg to work it. Marks are shared with the team when sync is on.
Who is involved, leg by leg
Found by reading the eight repositories and the GCP projects against the plan. A gap is closed by a deployed fix, or waived by the Test lead with the affected steps marked N/A. G-01 to G-08 block Legs 3–5 outright.
Everything the relay is waiting on you for, given the name and role in the header: steps to execute, marks to confirm as verifier, gaps you own, and — for the Test lead — approvals and gates. Work it top to bottom; each row jumps to the item.
Production safety rules
Acknowledged by every owner at Gate 0. There is no staging environment. Tick = done by whoever did it; the Test lead then approves each item.
Team & ownership
Names entered here are used to auto-select a role when that person types their name in the header, and appear on the sign-off.
Certification criteria
Test data cleanup optional
Not required for certification. Either clean up, or keep the test org as a permanent production canary — criterion 12 only needs the decision recorded.