Connect the artefacts without losing the review boundary.

Each workflow starts with synthetic data, names the handoff between tools and stops where factual, operational or legal judgment is required.

WORKFLOW INDEX / RELEASE 0.5

Three routes through the bench.

No workflow submits, uploads, messages, crawls or stores your records.

014 STAGES

Move from one collection surface and one controlled draft to a traceable local review record without mistaking structural cues for approval.

Inspectable outcome: A reviewed notice version, an exported linter record and a decision log that explains which cues were accepted, rejected or escalated.
Boundary: This workflow cannot observe the rendered prominence, surrounding interface, user understanding, product behaviour or validity of consent.

024 STAGES

Carry one confirmed processing activity through systems, instructed providers and event-based lifecycle decisions while keeping unknowns visible.

Inspectable outcome: A reconciled inventory row, linked processor evidence and an owner-approved retention record with testable deletion tasks.
Boundary: This workflow does not discover systems, read contracts, classify legal roles, prescribe retention periods or execute deletion.

034 STAGES

Turn bounded software metadata into testable questions, gather human and technical evidence, then update the inventory with confirmed facts.

Inspectable outcome: A version-linked triage export, an owner interview record and an updated inventory row that distinguishes confirmed flows from rejected hypotheses.
Boundary: This workflow does not infer runtime behaviour from package names, conduct interviews, crawl systems or establish legal compliance.

OPERATING PRINCIPLES

Practise with the labelled fictional scenario, then use one minimised process, system or document version.

Do not fill a required cell with a guess. Assign the question to an owner and return after evidence review.

Record which source, tool version and export belong together under your organisation’s own controls.