Home / Workshop / Labs

Interactive workbenches

Blueprint Labs.

Six workbenches, live. One story runs through all of them.

Open a workbench*:

Development Workbench

Open the approved story. Start story with AI to reveal code and controls.

Open Development Workbench →Open this S3 file: development-demo.html

QA Workbench

Run the suite. Watch PRIV-CHILD-001 fail on a consent defect.

Open QA Workbench →Open this S3 file: qa-demo.html

Release Workbench

Request promotion. The gate refuses. Then clear it.

Open Release Workbench →Open this S3 file: release-demo.html

Observability Lab

Replay fourteen days of production and watch the signal write NP-AUTH-338.

Open Observability Lab →Open this S3 file: blueprint/observability.html

Documentation Lab

Scan the record for drift, then refuse the one claim it cannot make.

Open Documentation Lab →Open this S3 file: blueprint/documentation.html

Available now · Phase 2

Requirements Workbench

Type a use case. The Harness returns a reviewable story with controls and evidence. Nothing leaves the page.

NP Product Requirements WorkbenchLocal demo
Verified session
● Signed inRole: Product managerWorkspace: NP-FAMILY-042
1 · Write use caseBusiness language, not Jira fields.
2 · AI interpretMap policies and controls.
3 · Human approveProduct, security, privacy, legal.
4 · Stage deliveryJira-ready story and evidence.

Product team input

Write the use case.

AI compliance & policy catalogue

Proposed for human review. Not a claim of legal compliance.

Child-data / consentCredential securityAccessibilityPrivacy & legal review
Ready to interpret the use case.

AI interpretation

Jira-ready delivery pack

NP-FAMILY-042

Run it to produce the story, its controls, and the evidence request.

EpicFamily account registrationProposed
StoryParent registration with controlled credentialsDraft
AI obligation mapPrivacy, credential security, accessibility.Human review required

Story output

Parent registration with controlled credentials

As a parent, I want to create a secure account so that I can manage our family wishlist.

Awaiting AI interpretation
Acceptance criteriaGiven compliant credentials and required consent, then registration can proceed.
Central controlsPassword policy, one-way storage, privacy, and accessibility controls await mapping.
EvidenceReview, policy check, QA run, and release evidence will be requested.
AUTH-PASS-016AUTH-PASS-017PRIV-CHILD-001A11Y-BASE-001

Open the full Requirements Lab → Global Compliance →

Available now · Phase 3

Development Lab

The Harness pulls the story’s skills and controls, drafts the code and tests, then waits for a developer’s review.

NP Development LabDeveloper workspace · local demo
Verified engineering session
● Signed inRole: Developer / ownerStory: NP-AUTH-321
1 · Start storyLaunch the approved work package.
2 · AI interpretPull skills and control packs.
3 · Generate & testDraft code and unit tests.
4 · Review & evidenceDeveloper owns approval.
NP-AUTH-321

Approved story

Parent registration with controlled credentials

As a parent, I want to create a secure account so that I can manage our family wishlist with appropriate verification and consent.

  • Context and criteria, from the approved work package.
  • Skills: implementation, secure coding, unit testing, observability.
  • Controls: AUTH-PASS-016, AUTH-PASS-017, PRIV-CHILD-001, A11Y-BASE-001.

Ready. Nothing is written to a repository.

AI engineering package

Implementation and unit tests

From the approved story, current skills, and central controls.

Waiting to start
AUTH-PASS-016AUTH-PASS-017PRIV-CHILD-001A11Y-BASE-001
// Generated from NP-AUTH-321 — illustrative only
export async function registerParent(input) {
  
  
  
}
Policy testRejects a weak credential.Waiting
Storage testUses one-way storage only.Waiting
Consent testBlocks before consent.Waiting
Access testReturns accessible errors.Waiting
AI interpretationAwaiting story start
Control enforcementAwaiting generated checks
Unit-test evidenceAwaiting AI test run
Developer approvalAwaiting accountable review

Open the full Development Lab →

Available now · Phase 4

QA Lab

Criteria and controls become executable tests. The suite finds a real defect: a draft written before consent. The story is blocked.

  • Four suites, derived from the story’s own criteria
  • A failing PRIV-CHILD-001 consent check with a full trace
  • Apply the fix and re-run to publish green evidence

Open the QA Workbench →

NP Quality Assurance LabLive

The screen asks properly. The system saves anyway.

Credential policy · passed
Credential storage · passed
Consent before persistence · failed
Accessible validation · passed

Available now · Phase 5

Release Lab · the promotion gate

QA’s failing evidence reaches the gate. Six controls run; the third refuses. Fix it and the same gate promotes by canary.

  • Six machine gates, each with a named accountable owner
  • Refused on child-data evidence — no waiver on the screen
  • Gates after the block are marked not evaluated

Open the Release Workbench →

NP Release & Promotion GateLive

An obligation is real only if something refuses to proceed without it.

Static analysis · passed
Test evidence · passed
Child-data consent · refused
Gates 4–6 · not evaluated

Available now · Phase 6

Observability & Learning Lab

The shipped control holds. Production shows what it cost, and the signal drafts the next story.

  • Four agreed signals — two compliance, two product
  • An SLO burn alert tied to an outcome, not a server metric
  • A proposed story, NP-AUTH-338, raised by evidence rather than a meeting

Open the Observability Lab →

The control was correct. Four hundred wishes a day were lost anyway.

Available now · Cross-cutting

Documentation Lab · the record that can be shown to be wrong

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.

  • Five registered documents, each derived from a control, a decision, or a build
  • A missing decision record for the choice that cost 412 wishes a day
  • A COPPA compliance claim held for refusal — accepting the document is blocked until it is dealt with

Open the Documentation Lab →

NP Documentation & RecordsLive

A runbook that is wrong is worse than a runbook that is missing.

ADR-014 · never written
RB-WISH-07 · contradicts the build
PRIV-NARR-002 · claim refused
API-REG-001 · no drift

* The production workbench is internal — reachable over the corporate VPN only. This public page is a local demonstration.