Requirements Workbench
Write a use case. Then Ask AI to build the review pack.
Open Requirements Workbench →Open this S3 file: requirements-demo.htmlSix workbenches, live. One story runs through all of them.
Open a workbench*:
Write a use case. Then Ask AI to build the review pack.
Open Requirements Workbench →Open this S3 file: requirements-demo.htmlOpen the approved story. Start story with AI to reveal code and controls.
Open Development Workbench →Open this S3 file: development-demo.htmlRun the suite. Watch PRIV-CHILD-001 fail on a consent defect.
Open QA Workbench →Open this S3 file: qa-demo.htmlRequest promotion. The gate refuses. Then clear it.
Open Release Workbench →Open this S3 file: release-demo.htmlReplay fourteen days of production and watch the signal write NP-AUTH-338.
Open Observability Lab →Open this S3 file: blueprint/observability.htmlScan the record for drift, then refuse the one claim it cannot make.
Open Documentation Lab →Open this S3 file: blueprint/documentation.htmlAvailable now · Phase 2
Type a use case. The Harness returns a reviewable story with controls and evidence. Nothing leaves the page.
Product team input
Proposed for human review. Not a claim of legal compliance.
AI interpretation
Run it to produce the story, its controls, and the evidence request.
Story output
As a parent, I want to create a secure account so that I can manage our family wishlist.
Available now · Phase 3
The Harness pulls the story’s skills and controls, drafts the code and tests, then waits for a developer’s review.
Approved story
As a parent, I want to create a secure account so that I can manage our family wishlist with appropriate verification and consent.
Ready. Nothing is written to a repository.
AI engineering package
From the approved story, current skills, and central controls.
// Generated from NP-AUTH-321 — illustrative only export async function registerParent(input) { assertPasswordPolicy(input.password, controls.AUTH_PASS_016); const credential = await hashWithArgon2id(input.password, policy.hashProfile); return accounts.create({ email: input.email, credential }); }
Available now · Phase 4
Criteria and controls become executable tests. The suite finds a real defect: a draft written before consent. The story is blocked.
PRIV-CHILD-001 consent check with a full traceThe screen asks properly. The system saves anyway.
Available now · Phase 5
QA’s failing evidence reaches the gate. Six controls run; the third refuses. Fix it and the same gate promotes by canary.
An obligation is real only if something refuses to proceed without it.
Available now · Phase 6
The shipped control holds. Production shows what it cost, and the signal drafts the next story.
The control was correct. Four hundred wishes a day were lost anyway.
Available now · Cross-cutting
The alert named a runbook. The runbook described behaviour that was never built. Scan the set, read the drafted corrections, and refuse the one sentence a generated document does not get to write about itself.
A runbook that is wrong is worse than a runbook that is missing.
* The production workbench is internal — reachable over the corporate VPN only. This public page is a local demonstration.