ProjectFlowPro
Menu

Case study · Workflow engine

Workflow authority: governed AI-assisted delivery

In daily use · coordinating the operator's project sessions and verifying their work against evidence

AI coding agents are fast but hard to trust. My delivery process makes every unit of work produce sealed, verifiable evidence; an independent AI reviewer rules on it; nothing advances without that ruling; and only a person decides on credentials, spending or anything irreversible. The result is auditable delivery instead of unchecked automation.

Direction
Operator
  • Business requirements
  • Scope and priorities
  • Approval decisions
PWSProject Workflow System
  • Organise work and assignments
  • Coordinate project sessions
  • Track evidence and decisions
Project workstreams
Software applicationsProduct build and integration
Website systemsGeneration and infrastructure
Review and assuranceEvidence and quality gates
Report · review · decide
Conceptual Illustration How work is directed and reported back; not a capture of the software.

Purpose

PWS is the external coordinator across my projects: it decides what work happens, relays between me and every project session, and verifies claims against their artifacts.

The problem

AI coding agents are fast but hard to trust. Several projects running at once need one authority that decides what happens next and checks every claim against evidence.

What it contributes

Workflow authority over every project session. BWS carries its messages and review bundles through the browser.

Principal capabilities

  • Backend

    A dependency-free TypeScript engine in which the filesystem is the source of truth. Work advances through run and round lifecycles under a reviewer-only control contract; writers publish atomically, and readers act only on completed files.

  • Verification

    Each unit of work is sealed into an immutable bundle whose SHA-256 identity covers the source state. The publisher runs the validations itself, records real exit codes and refuses to publish if the code changes mid-process. Rulings are final per bundle identity; corrections need a new one.

  • Integrations

    A browser transport delivers each bundle to an independent reviewer with an at-most-once submission guarantee.

    Browser Workflow System (BWS)

Implementation evidence

  • Engine implemented and tested (documented).

Back to Project workflow and communication

Visual evidence

Direction
Operator
  • Business requirements
  • Scope and priorities
  • Approval decisions
PWSProject Workflow System
  • Organise work and assignments
  • Coordinate project sessions
  • Track evidence and decisions
Project workstreams
Software applicationsProduct build and integration
Website systemsGeneration and infrastructure
Review and assuranceEvidence and quality gates
Report · review · decide
Conceptual Illustration How work is directed and reported back; not a capture of the software.

Part of

Browser Workflow System (BWS)

The browser transport between projects and coordinators.

Other case studies in this project

  • Reliability

    Exactly-once channels

    When two programs hand work to each other through files and a socket, a crash or a retry can make the same message go out twice. These channels make every request claimable exactly once and resumable after a crash, and the message-sending sequence is proven to send at most once.

    Implemented · tested (documented) · runs on the operator's workstation

  • Review & assurance

    Engineering Review & Assurance System

    A provenance-first review surface: every claim about the state of a project shows where it came from, and approval can only come from an authorised reviewer, never from the system being reviewed.

    Review surface implemented · 971 proof assertions executed across its 17 specified parts