Tutorial: Reconcile approved job and contract operational cost
Read one approved build rollup from exact job and operation evidence through deterministic customer/contract demand context without allocating cost or posting finance.
Learning goal
Project / Contract Managers, Accountable Executives, Production Managers/Planners and auditors.
Complete Flow 41 and prove that a useful actual-versus-baseline view can remain a permission-scoped read model with explicit ambiguity and zero operational/financial authority.
Before you begin
- Use an authorised disposable training tenant
- One exact product-baseline build has complete Flow 29 evidence and an approved Flow 30 rollup
- The Assembly work order carries the training project reference
- Zero, one or two visible Flow 40 demand lines can be prepared for association tests
- The reader has programme_cost:read, assigned-site scope and sufficient clearance
Observation-first is the default. Do not create retained customer, procurement, receipt, inventory, Quality, Engineering or Manufacturing records merely to complete a tutorial.
Guided journey
- 1ManufacturingOpen /manufacturing/cost-rollups
Verify the approved source version
- Acting role
- Production Planner / different Production Manager
- What to do
- Open the approved current rollup and record its UUID/version, build, plan, exact released baseline, currency and SHA-256 source fingerprint.
- What you should observe
- Draft, submitted and rejected versions are not eligible for Programme insight.
May changeNothing during the read; the approved source already exists from Flow 30.
Must remain unchangedOperation attempts, rate versions, plan, build, WIP evidence, stock and finance remain unchanged.
- 2ProgrammeOpen /programme/cost-insights
Open the scoped programme view
- Acting role
- Project / Contract Manager
- What to do
- Filter by exact job/work order, project, customer or contract and compare the returned job/baseline/rollup IDs with the approved source.
- What you should observe
- Only assigned-site and clearance-visible approved rows appear; a user without programme_cost:read receives permission denial.
May changeA classified-read audit fact only where applicable.
Must remain unchangedNo outbox or domain record is created.
- 3ProgrammeOpen /programme/cost-insights
Interpret actual versus baseline
- Acting role
- Production Manager / Planner
- What to do
- Read planned and actual minutes/cost plus variance by currency; do not interpret operation-evidence WIP as current stock or inventory valuation.
- What you should observe
- Unlike currencies stay separated and values come from the immutable rollup rather than Item Master.
May changeNothing.
Must remain unchangedPayroll, budget, GL, AP/AR, tax, payment and valuation remain outside the view.
- 4ProgrammeOpen /programme/cost-insights
Prove unique demand context
- Acting role
- Project / Contract Manager
- What to do
- With exactly one visible same-site demand using the same project and exact baseline, verify customer, contract, order, quantity and date appear as EXACT UNIQUE MATCH.
- What you should observe
- The match rule is visible and no manufacturing or customer record gains a new link or allocation.
May changeClassified-read audit only.
Must remain unchangedDemand and build remain independent source records.
- 5ProgrammeOpen /programme/cost-insights
Prove ambiguity fails honest
- Acting role
- Project / Contract Manager
- What to do
- Add or inspect a second matching demand in the disposable fixture and refresh the view.
- What you should observe
- The build becomes AMBIGUOUS, candidates remain visible and cost is not split, duplicated or assigned to either contract.
May changeNothing from the cost-insight read.
Must remain unchangedApproved cost totals and both demand lines retain their original truth.
- 6Programme / Manufacturing / GovernanceOpen /programme/cost-insights
Drill and reconcile isolation
- Acting role
- Auditor
- What to do
- Expand operations and reconcile attempt, execution, dispatch, exact rate-version and fingerprint lineage, then compare zero-side-effect witnesses.
- What you should observe
- Every source remains attributable and immutable; only expected classified-read audit rows increase.
May changeRead audit only.
Must remain unchangedCurrent stock, stock ledger, custody, identities, demand, Manufacturing sources, outbox and every financial witness remain unchanged.