Workflow

Flow 41 — Approved operation evidence to job and contract cost insight

Read approved Manufacturing actual-versus-baseline evidence by exact job, released product baseline, operation and immutable cost-rollup version, adding customer/contract context only when governed demand resolves uniquely.

Overview

Inventory meaning

Flow 41 is a read model over approved Flow 29/30 evidence and visible Flow 40 demand. It never allocates cost, changes a source fingerprint, creates a project/work order/demand, posts payroll/budget/GL/AP/AR/tax/payment/inventory valuation, or changes item identity, custody, current stock or stock ledger. Classified reads add audit facts only.

Responsible roles

Production Planner / Production Manager source evidence → Project / Contract Manager / Accountable Executive / Production reader read-only insight → Auditor reconciliation

Process

1
Use approved source
Include only the current independently APPROVED build cost-rollup and its immutable operation rows.
Read-only source
2
Pin exact job
Show build, Assembly work order, external job reference, released plan version and exact product baseline.
No job creation
3
Resolve demand context
Match assigned site + exact project + exact released baseline; one visible demand is unique, many remain ambiguous.
No allocation
4
Compare variance
Present planned versus actual minutes/cost by currency without combining currencies or mutable Item Master values.
No valuation
5
Drill evidence
Retain every operation attempt, execution, dispatch, rate-version ID and SHA-256 fingerprint.
Sources immutable
6
Audit isolation
Apply tenant/site/clearance scope and record classified reads while every operational and financial witness remains unchanged.
Audit fact only
READ ONLY

Role handoff

Production Planner / Production Manager source evidence → Project / Contract Manager / Accountable Executive / Production reader read-only insight → Auditor reconciliation

Detailed reference chapters

Job, contract and programme operational cost insight Build WIP/cost rollup and variance review Resource calendars, finite dispatch loading and operation cost evidence Customer estimates, outbound quotations and sales-order demand Manufacturing plan, execution evidence and authoritative as-built roles

Detailed steps

1
First complete Flow 29 operation cost evidence and independently approve the Flow 30 build rollup; draft, submitted and rejected rollups do not appear in Programme insight.
2
Open Programme → Job & contract cost insight with programme_cost:read. Filter by exact customer, project, contract, job/work-order reference or demand-association state.
3
Verify the exact build, Assembly work order, released manufacturing-plan version, product baseline and rollup version/fingerprint before interpreting any variance.
4
Where one governed demand line matches assigned site + project reference + exact released product baseline, read its customer, contract, order, quantity and required date. If multiple lines match, leave the build ambiguous and do not divide or assign cost.
5
Expand operations and reconcile planned/actual minutes and cost against every retained attempt, execution, dispatch, exact rate version and fingerprint.
6
As Auditor, prove permission denial and site/classification filtering, then compare current stock, stock ledger, custody, demand, Manufacturing sources and financial witnesses before/after the read. Only the expected classified-read audit may increase.

Field-by-field practice data

Use a disposable training tenant

Read one approved training build actual-versus-baseline by exact job and operation, prove unique then ambiguous customer-demand context, and reconcile zero operational or financial side effects. The page shows sample set A; the workbook includes independent A, B and C values.

Download all workflow samples (.xlsx)

Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.

Production Planner → different Production Manager

Verify the approved Manufacturing source

Open /manufacturing/cost-rollups

Open the completed training {{case}} build rollup and verify it is the current independently APPROVED version before Programme uses it.

Exact field name	Requirement	Sample value A	How to use it
Exact completed-operation build	Select existing	`TRAIN-A-BUILD-001`	Select the completed build with exact Flow 29 evidence.
Project reference	Read only	`TRAIN-A-PROJECT-001`	This must be the work order's stored project context.
Attributable explanation	Read only	`TRAIN-A approved operational variance evidence`	Confirm the source rollup explains its evidence without changing it.
Controlled rollup evidence	Read only	`TRAIN-A-COST-EVIDENCE.pdf v1`	Confirm the approved source carries controlled evidence.

Expected result: The exact build, job, plan, released baseline, rollup version, currency and source fingerprint are visible and immutable.

Project / Contract Manager

Read exact job actual versus baseline

Open /programme/cost-insights

Apply the exact work-order/project filter and reconcile the returned source identity and currency totals.

Exact field name	Requirement	Sample value A	How to use it
Job / work order	Optional	`TRAIN-A-AWO-001`	Use the exact work-order, external-job or build reference.
Project reference	Optional	`TRAIN-A-PROJECT-001`	Exact case-insensitive equality is used.
Baseline	Read only	`INR 1000.000000`	Read from the immutable Flow 30 baseline, not Item Master.
Actual	Read only	`INR 1125.000000`	Read the sum of every retained operation attempt.
Variance	Read only	`INR 125.000000 · 12.500000%`	Keep currency and threshold visible.

Expected result: The view shows only approved, assigned-site and clearance-visible evidence and creates at most the expected classified-read audit.

Project / Contract Manager / Accountable Executive

Confirm one unique demand context

Open /programme/cost-insights

With one visible Flow 40 demand line matching the assigned site, project and exact released baseline, inspect the association.

Exact field name	Requirement	Sample value A	How to use it
Unique demand context	Read only	`1 exact match for TRAIN-A`	Only one visible matching demand may be presented as unique.
Customer	Read only	`TRAIN-A-CUSTOMER`	Read from the exact governed demand line.
Contract	Read only	`TRAIN-A-CONTRACT-001`	Read from the exact governed demand line.
Project	Read only	`TRAIN-A-PROJECT-001`	Retain the exact job/demand project context.

Expected result: The customer/contract context is EXACT UNIQUE MATCH and no allocation, link or source mutation is created.

Project / Contract Manager

Confirm ambiguity remains unallocated

Open /programme/cost-insights

Use a disposable fixture with two visible demands sharing the same site/project/exact baseline and refresh the view.

Exact field name	Requirement	Sample value A	How to use it
Demand association	Optional	`AMBIGUOUS_MATCH for TRAIN-A`	Use the read-only filter to isolate unresolved context.
Ambiguous	Read only	`1 build / 2 visible demand candidates`	Review both candidates; do not treat either as assigned.
Customer	Read only	`TRAIN-A-CUSTOMER-1 / TRAIN-A-CUSTOMER-2`	Both possible customers remain contextual only.
Actual	Read only	`INR 1125.000000 once`	The total must not duplicate for each candidate.

Expected result: The association becomes AMBIGUOUS; both candidates remain visible and the build cost appears once without split or allocation.

Production Manager / Planner → Auditor

Drill immutable operation lineage

Open /programme/cost-insights

Expand each operation and reconcile planned/actual minutes and cost to every execution, dispatch, exact rate version and fingerprint.

Exact field name	Requirement	Sample value A	How to use it
Evidence version	Read only	`TRAIN-A-MCV-001 · v1`	Verify the immutable rollup version and source fingerprint.
Baseline	Read only	`10 min · INR 1000.000000`	Verify the exact plan operation baseline.
Actual	Read only	`12 min · INR 1125.000000 · attempt 1`	Reconcile the visible execution, dispatch, rate UUID and fingerprint lineage.

Expected result: All source IDs and fingerprints agree with Flow 29/30 and no evidence row is edited.

Auditor

Prove permission, scope and zero side effects

Open /programme/cost-insights

Retry without programme_cost:read, with an unassigned site and below the record clearance; then compare before/after domain witnesses for an authorised read.

Exact field name	Requirement	Sample value A	How to use it
Customer code	Read only	`TRAIN-A-CUSTOMER`	A user without programme_cost:read receives 403 rather than a misleading zero.
Demand association	Read only	`NO_MATCH`	Tenant, assigned-site and classification scope filter before demand resolution.
Unmatched	Read only	`0 hidden-site / above-clearance rows`	Confirm hidden data is absent while the authorised classified read adds only its audit fact.
Approved build rollups	Read only	`1 unchanged TRAIN-A source`	Manufacturing sources, demand, current_stock, stock_ledger, custody, identity, valuation, payroll, budget and accounting stay unchanged.

Expected result: Denied users receive no cost surface, hidden rows remain absent, classified reads are audited and every business/financial source count remains unchanged.

End state

One scoped, explainable operational cost view connects approved immutable build evidence to exact job/baseline context and, only when unique, governed customer/contract demand—without becoming allocation, valuation or accounting authority.