ACCEPTANCE WORKBENCH · PREPARE WITH YOUR TEAM

Decide what “working” means before anyone builds.

Trace an illustrative report, break it on purpose, then write your own criteria and the conditions under which your team would not proceed. Nothing you type leaves this page unless you export it or bring it to a Briefing.

Mode 1 · Example

Keep one report current, from its sources to sign-off.

Illustrative workflow: a finance team rebuilds its quarterly investor report by hand from four systems. Here it is as a living report in one shared workspace: figures stay linked to approved sources, a source change arrives as a suggestion rather than an overwrite, and the owner approves before anything issues. Below is the acceptance sheet the team agrees before it goes live.

Illustrative workflow · scripted example, not a live bolde. session or client

See the complete workflow

What you run today

Fund accounting system
Document store
CRM
Email

What the workflow does

The work, after

Quarterly summary Example review
Report item	Review state
Portfolio figure	Linked to its source record
Investor commentary	Edited by the analyst
Source refresh	Suggested update · awaiting review
Owner approval	Recorded in activity history

The report owner decides whether it is ready to issue.

Example input: Finance records from four approved systems
Expected output: A living quarterly investor report with cited figures, kept current each quarter
Review owner: Customer report owner

Example review rule: when a source changes, propose the update to a person; never overwrite their edit, and never issue without the owner’s approval.

Each report figure links to its approved source record.
People edit the report directly; each commentary line keeps its source link.
A source change arrives as a suggestion and does not overwrite a person’s edit.
An agent suggestion counts only after a person approves it, and the approval is recorded.

Not product UI, client evidence, signed acceptance criteria, or an operative SOW. The customer and ASG agree actual criteria before the Build.

Illustrative. Sample workflow, not a client.Fund accounting, documents, CRM and email feed four stages: connect approved sources, draft the living report, refresh as sources change and approve in the shared workspace. Each stage fills one row of the report at right and is held to one check on the acceptance sheet below it.

Who is in the workspace

Report ownerOwner · grants access, approves
Finance analystCan edit the report
Investor relations leadCan comment on commentary
Drafting agentSuggests only · approved sources only

Belonging to the workspace does not make the report public. The agent sees only the sources and items approved for it.

Activity history records who joined, access changes, edits, suggestions and approvals.

Living documents, slides and spreadsheets keep their figures and citations current as approved sources change, without overwriting your edits.Planned — claim-20, open in the Trust Center
Details
Owner
CTO
Status
Planned
Required evidence
A product release record for bolde. Evergreen. bolde.ai/features lists Evergreen as a planned release target within one month (snapshot 2026-10-21).
Not confirmed for your deployment.
A shared workspace brings people, agents and work together; owners set view or edit access, and an agent suggestion becomes an edit only when a person approves it.On request — claim-21, open in the Trust Center
Details
Owner
CTO
Status
On request
Required evidence
A dated release or deployment record for bolde. Space. bolde.ai/features lists Space as Phase I, in progress or shipping now (snapshot 2026-10-21); no record has been verified for this site.
Not confirmed for your deployment.

The pattern follows how bolde.ai describes bolde. Evergreen and bolde. Space. Status for each is on bolde.ai.

Which bolde. components are involved?

Component release status is on bolde.ai.

Mode 2 · Make it fail

Break the example on purpose.

Each failure stops the report in a stated place, with a named person deciding what happens next. There is no score.

Remove a source
Unsupported in this example
Cannot establish
Where the commentary came from, once the document store is disconnected.
Who decides
The report owner.
What permits progress
Reconnect the source, or take the unsupported lines out of the report.
Records disagree
Unresolved: owner decides which record governs
Cannot establish
Which of two conflicting records is correct for the portfolio figure.
Who decides
The report owner, under the rule agreed in configuration.
What permits progress
The owner records which source governs; the row is checked again.
Source changes after an edit
Suggested, not applied: the edit stands
Cannot establish
Whether the analyst’s wording or the refreshed source should govern the commentary.
Who decides
The analyst who made the edit, then the report owner.
What permits progress
A person accepts or declines the suggested update; both choices go into the activity history.
Agent reaches past its scope
Blocked: outside the approved sources
Cannot establish
Anything from a source the drafting agent was not approved to read.
Who decides
The report owner, who sets what the agent may see.
What permits progress
The owner approves the source for the agent, or the agent works without it.
Withhold approval
Returns to Build; decision kept
Cannot establish
That the report is ready to issue.
Who decides
The report owner. Nothing issues on their behalf.
What permits progress
The decision stays on the record and the work returns to Build until the criteria are met.

Mode 3 · Your criteria and conditions

Write what would have to be true.

Your team writes the acceptance criteria and the conditions under which you would not proceed. ASG does not fill these in for you.

DRAFT — YOUR WORDS, NOT A CONTRACT

Workflow

One workflow, in a sentence. Describe it in general terms. No client names or confidential data needed.

Systems

The systems it touches today, by type. Press Enter or comma to add each one.

What would prove it works?

What result would show your team the deployment is useful? Describe it in general terms. No client names or confidential data needed.

Acceptance rows

One example per row: what goes in, what should come out, who reviews it and what counts as pass.

Input exampleExpected outputWho reviewsCriterion

Do not proceed unless…

Conditions your team sets. Each can link to a claim to show what ASG can evidence today.

Condition 1: do not proceed unlessRelated claim

Compare the two paths

Leave either side blank. Continuing as you are is a legitimate outcome.

Continue the current workflowEvaluate an ASG deployment

Your working notes. ASG never sees them unless you send them. This is not legal or security advice.

Mode 4 · What ASG can show today

0 of 18 claims verified.

Link a condition to a related claim and its current status appears beside it, read from the same ledger as the Trust Center. A claim's verified wording appears only after a dated owner check and recorded evidence. Until then you see the proposed wording, its status and "Not confirmed for your deployment."

Discuss one workflow with a principal →