01 · Request
The business event
Reconcile the synthetic CRM, project, and finance ledgers; prepare the weekly operating brief; identify variance drivers, risks, and three accountable decisions; hold distribution for Managing Director approval.
ILLUSTRATIVE WORKFLOWFictional sample data · Fieldstone Service Works
Close the week with three accountable decisions.
What changed this week, why did it change, and which decisions must be made before Monday?
This is an illustrative, deterministic workflow using fictional data. It represents governed AI-assisted work; it is not connected to a client system and does not make an unobserved model call. A real deployment would use client-approved connections, permissions, field scopes, failure handling, and audit controls.
Deterministic walkthrough
Ready
State 1/1 · reducer phase1.1
01 · Request
Current
02 · Sources
Held
03 · Work
Held
04 · Decision
Held
05 · Output
Held
06 · Destination
Held
07 · Receipt
Held
Skip removes the timed sequence, never the human decision. The proposed artifact remains inspectable while destination writes stay held.
Current
02 · Sources
Permission scope, before work.
Sample CRM aggregates
read-only · Synthetic aggregate fixed at 16:00 UTC
Permitted fields
pipeline_movement, stage_count, account_ref
Excluded
person_record, message_body, private_notes
Sample project ledger
read-and-approved-write · Synthetic extract fixed at 15:55 UTC
Permitted fields
project_ref, milestone_status, capacity_band, delivery_risk, monday_priority
Excluded
team_identity, client_content, private_note
Sample finance aggregates
read-only · Synthetic aggregate fixed at 15:50 UTC
Permitted fields
invoice_timing_band, cash_timing_band, reconciliation_total
Excluded
bank_detail, customer_identity, transaction_memo
Sample policy library
read-only · Fictional policy version POL-7
Permitted fields
reporting_definitions, freshness_thresholds, approval_rules
Excluded
historic_client_report, unapproved_metric
03 · Work and validation
Represented work, with rules visible.
AI-assisted classification, synthesis, or drafting is represented inside this fixed sequence. No model is called on this page; the rules and outputs below are deterministic.
01 · Operations
Resolve source versions and freshness
Compare each fixed synthetic extract with the visible reporting tolerance.
Validation: Every section shows its source version and freshness state.
02 · Product
Reconcile shared account and project references
Join only generated identifiers and expose unmatched records.
Validation: Every included movement has one traceable generated reference.
03 · Finance
Calculate deterministic weekly movements
Calculate the fixed changes without filling missing values or inventing totals.
Validation: Aggregate totals reconcile before a distribution decision is offered.
04 · Governance
Separate fact, variance, risk, and decision
Label each brief item by evidence class and retain provisional status where needed.
Validation: Commentary never appears as a ledger fact.
05 · Operations
Prepare Monday priorities and three decisions
Assign each fictional decision to an accountable role and a visible next action.
Validation: Exactly three decisions have a role owner and Monday action.
06 · Operations
Pause at the Managing Director gate
Present the brief, accessible metrics, risks, decisions, and intended destinations.
Validation: Distribution and priority writes remain held until approval.
Deterministic rules
- — Join only generated account and project references.
- — Do not invent a missing ledger value.
- — Exclude movements outside the visible freshness tolerance.
- — Do not distribute the brief before Managing Director approval.
Inspect exception paths
04 · Human decision
Managing Director holds the gate.
Review the weekly brief, three decisions, and Monday priorities.
05 · Output
Inspect the proposed business artifact.
Inspectable artifact
Weekly operating brief
draft · rev.1
Accountable: Managing Director
Pipeline quality improved, delivery risk is concentrated in three generated projects, and three role-owned decisions are required before Monday.
- Pipeline movement
- +6% illustrative
- Milestones on plan
- 18 of 21
- Delivery risks
- 3
- Decisions
- 3
- Created
- 31 Jul 2026, 16:00 UTC
- Updated
- 31 Jul 2026, 16:00 UTC
- Decision 2 owner
- Operations Lead
| Measure | Prior week | Current week | Takeaway |
|---|---|---|---|
| Qualified pipeline index | 100 | 106 | Quality improved |
| Milestones on plan | 17 of 21 | 18 of 21 | One recovered |
| Delivery risks | 2 | 3 | Decision required |
| Invoice timing on plan | 90% | 92% | Within policy band |
Accessible metric view
- Qualified pipeline index106
- Milestones on plan18 of 21
- Invoice timing on plan92%
Assumptions
- The fixed aggregate definitions match the fictional policy version.
- The late project extract remains within the visible provisional tolerance.
Limitations
- All metrics are generated and are not measured Dissfam or client outcomes.
- No real finance, customer, project, or team record is represented.
Value statement: illustrative, not measured — this shows the represented operating outcome, not a claimed client result.
06 · Destination
Every write — and non-write — stays visible.
sample-knowledge-record
Sample knowledge record
held
No weekly brief was stored.
sample-team-update
Sample team update
held
No team update was queued.
sample-project-ledger
Sample Monday priorities
held
No Monday priority was written.
operating-receipt
Operating receipt
held
A stopped operating receipt recorded the non-actions.
07 · Receipt
The operating record.
Receipt RCP-WOR-0031 issues only after a completed, rejected, or blocked terminal outcome. It will record the represented sources, rules, validations, human decision, destinations, exceptions, and actions not taken.
Existing accepted destinations
See how Dissfam scopes work, or bring a real business problem to a human-led conversation.
Complete static summary — works without animation or JavaScript
ILLUSTRATIVE WORKFLOW
The whole represented operating loop.
This is an illustrative, deterministic workflow using fictional data. It represents governed AI-assisted work; it is not connected to a client system and does not make an unobserved model call. A real deployment would use client-approved connections, permissions, field scopes, failure handling, and audit controls.
Step 01 · Operations
Resolve source versions and freshness
Compare each fixed synthetic extract with the visible reporting tolerance.
Validation: Every section shows its source version and freshness state.
Step 02 · Product
Reconcile shared account and project references
Join only generated identifiers and expose unmatched records.
Validation: Every included movement has one traceable generated reference.
Step 03 · Finance
Calculate deterministic weekly movements
Calculate the fixed changes without filling missing values or inventing totals.
Validation: Aggregate totals reconcile before a distribution decision is offered.
Step 04 · Governance
Separate fact, variance, risk, and decision
Label each brief item by evidence class and retain provisional status where needed.
Validation: Commentary never appears as a ledger fact.
Step 05 · Operations
Prepare Monday priorities and three decisions
Assign each fictional decision to an accountable role and a visible next action.
Validation: Exactly three decisions have a role owner and Monday action.
Step 06 · Operations
Pause at the Managing Director gate
Present the brief, accessible metrics, risks, decisions, and intended destinations.
Validation: Distribution and priority writes remain held until approval.
Inspectable artifact
Weekly operating brief
draft · rev.1
Accountable: Managing Director
Pipeline quality improved, delivery risk is concentrated in three generated projects, and three role-owned decisions are required before Monday.
- Pipeline movement
- +6% illustrative
- Milestones on plan
- 18 of 21
- Delivery risks
- 3
- Decisions
- 3
- Created
- 31 Jul 2026, 16:00 UTC
- Updated
- 31 Jul 2026, 16:00 UTC
- Decision 2 owner
- Operations Lead
| Measure | Prior week | Current week | Takeaway |
|---|---|---|---|
| Qualified pipeline index | 100 | 106 | Quality improved |
| Milestones on plan | 17 of 21 | 18 of 21 | One recovered |
| Delivery risks | 2 | 3 | Decision required |
| Invoice timing on plan | 90% | 92% | Within policy band |
Accessible metric view
- Qualified pipeline index106
- Milestones on plan18 of 21
- Invoice timing on plan92%
Assumptions
- The fixed aggregate definitions match the fictional policy version.
- The late project extract remains within the visible provisional tolerance.
Limitations
- All metrics are generated and are not measured Dissfam or client outcomes.
- No real finance, customer, project, or team record is represented.
Human decision
Review the weekly brief, three decisions, and Monday priorities. Approve the brief, queue the sample team update, store Monday priorities, and issue a receipt.
Edit, ask, and reject remain separate outcomes; no downstream write occurs without the person named as accountable.
Exception truth
- recoverable · PROJECT_EXTRACT_LATE
One synthetic project-ledger extract is late but inside the visible tolerance. - blocked · FINANCE_RECONCILIATION_FAILED
The synthetic finance totals fail reconciliation.
Destination and receipt
- — Sample knowledge record: held until approval
- — Sample team update: held until approval
- — Sample Monday priorities: held until approval
- — Operating receipt: held until approval
Receipt RCP-WOR-0031 records writes and non-writes at every terminal outcome.