Where we are

A focused product first.
A platform only after the reuse is proved.

The shared engine carries the control pattern. Every application still needs its own sources, rules, authority, connections and outcome. What follows reduces that configuration over time — without pretending it has already disappeared.

The product path

Stage one is where we are
  1. 01 · Current build Governed product proof Persistent work, useful outputs, human decisions, receipts and return visits across two bounded financial-services workflows. One carries hosted, independently reviewed evidence.
  2. 02 · Next Design-partner pilot Configure one firm's sources, rules, authority, connections and outputs. Measure the outcome against a baseline recorded before anything is deployed.
  3. 03 · Target Repeatable product More workflows, faster onboarding. New organisations reach value through configuration, with security, support and service controls around the engine.
  4. 04 · Direction Platform Domain experts add governed modules across sectors while the shared runtime and receipt semantics stay unchanged.

Stages three and four are targets, not delivered claims. The platform claim depends on repeated customer evidence, domain-swap tests, and expert-authored workflows that do not require a new engine path. None of those has been done.

The control structure, in six parts

A view of it, not an inventory

The workflow supplies the domain content — your sources, your rules, your checks. Provenact supplies the control structure around it, and that structure is what carries from one job to the next. It is the reason a second workflow should cost less than the first, and the thing the platform claim will stand or fall on.

01–02 · Control the basis

What may enter, and which rules apply

Controlled inputs Admit approved, versioned sources and retain their scope and provenance.
Executable rules Propose reviewable rules, dates, exclusions and conflicts for a person to approve.

03–04 · Control the work

What the system may do, and when it must stop

Bounded execution Run calculations, reconciliation, drafting and tool calls inside the approved scope.
Verification and refusal Apply evidence and policy checks. Missing proof produces a stop, not a pass.

05–06 · Control the decision

Who may decide, and what the firm retains

Human authority Route exceptions and overrides to the authorised person, and record the basis.
Decision evidence Keep lineage, checks, approvals and boundaries together in one decision receipt.

Six groupings, not six features. The implementation plan carries twenty-four capabilities — fourteen in the shared engine, built once, and ten configured per product. What is above is how they group, not what they are. Demonstrated in bounded reference workflows; every customer workflow still needs its own approved rules, evidence contract and checks, and that configuration is measured in hours rather than assumed away.

Demonstrated

Nine rule summaries inspectable, downloadable and reloadable byte-identically. Versioned model-profile approvals hosted. Source understanding and preparation-only authority. Restoration of prior saved work. Journey parity accepted under independent review — visual and journey parity, not integrated data flow.

Open, and named

No useful saved communications output has yet passed examination. Model replacement is unproved. Full integrated prototype parity is incomplete. The workflow selection gate — two firms confirming materially similar repeated steps — is not met. No measured accuracy, hours saved or cost saving is claimed anywhere on this site.

What the firm keeps

Every correction becomes part of your operating memory.

Exceptions do not disappear once resolved. Each becomes an approved instruction, attached to a named person and a version. After a few cycles that is a written record of how your firm actually decides — and it is the part you keep.

Approved operating memory · illustrative Fictional firm
  • R-014Orders handled excludes trades booked after the 17:00 cut-offA. Whitfield · 12 Mar
  • R-021AUM is taken from the quarter-end valuation file, not the daily feedA. Whitfield · 14 Mar
  • R-033Any movement over 25% needs a recorded explanation before sign-offR. Deane · 2 Jun
  • R-041Revenue reconciles to the ledger, not to the management packR. Deane · 4 Jun

It is yours

Text, not weights

Readable, editable, exportable. Change the model next year and it survives intact, because it was never in the model.

It compounds

The next job starts further ahead

Source, authority and evidence structures carry forward. Each new workflow still receives its own substantive rules and checks.

It outlives people

If they leave, it stays

What lives in one experienced person's head becomes text the firm owns. A new compliance officer inherits it, not a handover call.

Illustrative, from a fictional firm — the structure is real; the first instructions are written by hand, with you.

What it refuses to do.

Missing evidence produces an exception and stops. It is never inferred as a pass. A conclusion with no traceable basis is not offered as a conclusion at all.

Nothing is filed, sent or executed by the system. The same signatory, with the same authority, still signs.

Request a working session One recurring decision. Ninety minutes. Design-partner conversations only.
P. Every act, proven