SELECT COUNT(*) FROM erpb_sale_order_lines l JOIN erpb_sale_orders o ON o.name=l.order_name WHERE o.state='sale' AND ABS(l.price_unit-3905.52)>0.01

SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-053'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-053'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-053' AND decision_code='COMMIT_STANDPIPE_SHARED_PLAN'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-053' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-053 completed — COMMIT_STANDPIPE_SHARED_PLAN' AND body LIKE '%COMMIT_STANDPIPE_SHARED_PLAN%'

clone of agentic-labs/erp-bench task 2160_hard_17_shared_component_subassemblies_branch_assigned; instruction carried verbatim, scenario seeded from its own environment/scenario_data.json, ground truth derived from its solution/optimal_plan.json. The source boots a real Odoo in Docker and grades with odoolib; this runs on the world's Odoo-shaped surface and grades the same judgement as deterministic SQL state assertions (docs/PARITY.md)

Prompt:
**Priya Shah · Supply & Procurement · Teams**

Give Operations a build plan for the Standpipe and Hose packages where shared components are not promised twice.

The customer promises are live, but the material, supplier, budget, and factory records do not all refresh together. Work out the feasible options from the current world and explain the constraint that actually controls the promise. Record the supported disposition on the open finance case and send Controls a concise completion note.

Question: finance case work item

Question: finance case work item

FINCASE-053 completed — COMMIT_STANDPIPE_SHARED_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-053 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Join order priorities, shared-component demand, stock allocations, vendor capacity, branch lead times, and assembly calendars.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-053 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-053"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-053 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-053"}) + successful_required_calls + reads_before_write

Check metadata for lgr-053-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-053-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-053-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-053-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-053-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-053-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-053-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-053-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-053 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-053"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-053-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-053-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-053-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-053-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-053-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-053-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-053-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-053-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-053 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-053"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-053-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-053-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-053-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-053-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-053-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-053-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-053-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-053-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

A valid plan allocates each shared unit once and sequences packages against the constrained branch.

Reject the unsupported branch: Plan each customer order in isolation and double-book shared material.

Select `COMMIT_STANDPIPE_SHARED_PLAN` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `assembly_cost` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_accepted` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_rejected` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_purchased` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_manufactured` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-053 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Plan each customer order in isolation and double-book shared material.


SELECT COALESCE(SUM(l.qty),0) FROM erpb_sale_order_lines l JOIN erpb_sale_orders o ON o.name=l.order_name WHERE o.state='sale'

SELECT COALESCE(SUM(l.qty),0) FROM erpb_purchase_order_lines l JOIN erpb_purchase_orders o ON o.name=l.order_name WHERE o.state='purchase'

SELECT COALESCE(SUM(qty),0) FROM erpb_manufacturing_orders WHERE state='confirmed'

SELECT COUNT(*) FROM erpb_manufacturing_orders m WHERE m.state='confirmed' AND NOT EXISTS (SELECT 1 FROM erpb_workcenters w WHERE w.code=m.workcenter_code)

SELECT COUNT(*) FROM erpb_sale_order_lines l JOIN erpb_sale_orders o ON o.name=l.order_name WHERE o.state='sale' AND ABS(l.price_unit-5565.51)>0.01

SELECT COUNT(*) FROM erpb_purchase_orders p WHERE p.state='purchase' AND NOT EXISTS (SELECT 1 FROM erpb_sale_orders s WHERE s.state='sale' AND p.origin LIKE '%'||s.name||'%')

SELECT COUNT(*) FROM erpb_sale_orders WHERE state='sale' AND (commitment_date IS NULL OR commitment_date='')

SELECT COUNT(*) FROM erpb_purchase_orders WHERE state='purchase' AND (date_planned IS NULL OR date_planned='')

SELECT COUNT(*) FROM erpb_purchase_order_lines l JOIN erpb_purchase_orders o ON o.name=l.order_name WHERE o.state='purchase' AND NOT EXISTS (SELECT 1 FROM erpb_vendor_offers v WHERE v.partner_ref=o.partner_ref AND v.product_code=l.product_code)

SELECT COALESCE(SUM(l.qty*l.price_unit),0) FROM erpb_purchase_order_lines l JOIN erpb_purchase_orders o ON o.name=l.order_name WHERE o.state='purchase'

SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-054'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-054'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-054' AND decision_code='COMMIT_DRY_PIPE_PLAN'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-054' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-054 completed — COMMIT_DRY_PIPE_PLAN' AND body LIKE '%COMMIT_DRY_PIPE_PLAN%'

clone of agentic-labs/erp-bench task 2161_hard_17_shared_component_subassemblies_branch_assigned; instruction carried verbatim, scenario seeded from its own environment/scenario_data.json, ground truth derived from its solution/optimal_plan.json. The source boots a real Odoo in Docker and grades with odoolib; this runs on the world's Odoo-shaped surface and grades the same judgement as deterministic SQL state assertions (docs/PARITY.md)

Prompt:
**Priya Shah · Supply & Procurement · Teams**

Work out the earliest feasible Dry Pipe Sprinkler portfolio and identify whether material or workcenter capacity controls it.

The customer promises are live, but the material, supplier, budget, and factory records do not all refresh together. Work out the feasible options from the current world and explain the constraint that actually controls the promise. Leave the open finance case in the exact supported state and give Controls an audit-ready handoff.

Question: finance case work item

Question: finance case work item

FINCASE-054 completed — COMMIT_DRY_PIPE_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-054 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Net shared components across orders, compare replenishment dates, and load each routed operation into compatible capacity.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-054 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-054"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-054 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-054"}) + successful_required_calls + reads_before_write

Check metadata for lgr-054-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-054-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-054-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-054-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-054-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-054-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-054-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-054-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-054 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-054"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-054-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-054-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-054-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-054-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-054-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-054-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-054-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-054-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-054 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-054"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-054-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-054-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-054-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-054-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-054-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-054-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-054-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-054-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The completion promise follows the later of material availability and the fully loaded critical route.

Reject the unsupported branch: Use supplier lead time alone or assume unlimited factory capacity.

Select `COMMIT_DRY_PIPE_PLAN` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `assembly_cost` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_accepted` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_rejected` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_purchased` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_manufactured` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-054 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use only when the required evidence intersection is incomplete or conflicting.

Use supplier lead time alone or assume unlimited factory capacity.

verifiers/vcode.py (binary reward; all checks must pass)

answer_checks: submitted fields graded by type with tolerances

trace_checks: required servers visited, reads precede submission

state_checks: writes_only anti-hack veto plus SQL over the world left behind


SELECT COUNT(*) FROM erpb_sale_order_lines l JOIN erpb_sale_orders o ON o.name=l.order_name WHERE o.state='sale' AND ABS(l.price_unit-8748.9)>0.01

SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-055'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-055'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-055' AND decision_code='COMMIT_FOAM_DELUGE_PLAN'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-055' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-055 completed — COMMIT_FOAM_DELUGE_PLAN' AND body LIKE '%COMMIT_FOAM_DELUGE_PLAN%'

clone of agentic-labs/erp-bench task 2168_hard_17_shared_component_subassemblies_branch_assigned; instruction carried verbatim, scenario seeded from its own environment/scenario_data.json, ground truth derived from its solution/optimal_plan.json. The source boots a real Odoo in Docker and grades with odoolib; this runs on the world's Odoo-shaped surface and grades the same judgement as deterministic SQL state assertions (docs/PARITY.md)

Prompt:
**Priya Shah · Supply & Procurement · Teams**

Build a feasible Foam Deluge portfolio plan and show how shared-component scarcity changes the order sequence.

The customer promises are live, but the material, supplier, budget, and factory records do not all refresh together. Work out the feasible options from the current world and explain the constraint that actually controls the promise. Update only the scoped finance case, verify what persisted, and close the loop with Controls.

SELECT COALESCE(SUM(l.qty),0) FROM erpb_sale_order_lines l JOIN erpb_sale_orders o ON o.name=l.order_name WHERE o.state='sale'

SELECT COALESCE(SUM(l.qty),0) FROM erpb_purchase_order_lines l JOIN erpb_purchase_orders o ON o.name=l.order_name WHERE o.state='purchase'

SELECT COALESCE(SUM(qty),0) FROM erpb_manufacturing_orders WHERE state='confirmed'

SELECT COUNT(*) FROM erpb_manufacturing_orders m WHERE m.state='confirmed' AND NOT EXISTS (SELECT 1 FROM erpb_workcenters w WHERE w.code=m.workcenter_code)

SELECT COUNT(*) FROM erpb_purchase_orders p WHERE p.state='purchase' AND NOT EXISTS (SELECT 1 FROM erpb_sale_orders s WHERE s.state='sale' AND p.origin LIKE '%'||s.name||'%')

SELECT COUNT(*) FROM erpb_sale_orders WHERE state='sale' AND (commitment_date IS NULL OR commitment_date='')

SELECT COUNT(*) FROM erpb_purchase_orders WHERE state='purchase' AND (date_planned IS NULL OR date_planned='')

SELECT COUNT(*) FROM erpb_purchase_order_lines l JOIN erpb_purchase_orders o ON o.name=l.order_name WHERE o.state='purchase' AND NOT EXISTS (SELECT 1 FROM erpb_vendor_offers v WHERE v.partner_ref=o.partner_ref AND v.product_code=l.product_code)

SELECT COALESCE(SUM(l.qty*l.price_unit),0) FROM erpb_purchase_order_lines l JOIN erpb_purchase_orders o ON o.name=l.order_name WHERE o.state='purchase'

Question: finance case work item

Question: finance case work item

FINCASE-055 completed — COMMIT_FOAM_DELUGE_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-055 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Allocate scarce shared inputs by dated commitments, test supplier alternatives, and schedule parallel subassemblies through final assembly.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-055 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-055"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-055 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-055"}) + successful_required_calls + reads_before_write

Check metadata for lgr-055-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-055-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-055-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-055-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-055-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-055-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-055-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-055-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-055 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-055"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-055-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-055-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-055-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-055-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-055-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-055-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-055-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-055-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-055 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-055"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-055-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-055-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-055-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-055-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-055-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-055-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-055-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-055-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The committed sequence must protect the feasible priority set and leave unsupported demand visibly constrained.

Reject the unsupported branch: Spread scarce components pro rata without checking whether any order can actually complete.

Select `COMMIT_FOAM_DELUGE_PLAN` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `assembly_cost` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_accepted` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_rejected` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_purchased` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_manufactured` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-055 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Spread scarce components pro rata without checking whether any order can actually complete.


SELECT COUNT(*) FROM erpb_sale_order_lines l JOIN erpb_sale_orders o ON o.name=l.order_name WHERE o.state='sale' AND ABS(l.price_unit-4143.04)>0.01

SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-056'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-056'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-056' AND decision_code='COMMIT_FACP_PLAN'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-056' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-056 completed — COMMIT_FACP_PLAN' AND body LIKE '%COMMIT_FACP_PLAN%'

clone of agentic-labs/erp-bench task 2170_hard_17_shared_component_subassemblies_branch_assigned; instruction carried verbatim, scenario seeded from its own environment/scenario_data.json, ground truth derived from its solution/optimal_plan.json. The source boots a real Odoo in Docker and grades with odoolib; this runs on the world's Odoo-shaped surface and grades the same judgement as deterministic SQL state assertions (docs/PARITY.md)

Prompt:
**Priya Shah · Supply & Procurement · Teams**

Tell Operations when the Fire Alarm Control Panel portfolio can realistically ship and what must be bought or shifted to make it happen.

The customer promises are live, but the material, supplier, budget, and factory records do not all refresh together. Work out the feasible options from the current world and explain the constraint that actually controls the promise. Carry the decision through the governed case record and leave Controls a reproducible completion message.

Question: finance case work item

Question: finance case work item

FINCASE-056 completed — COMMIT_FACP_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-056 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Join demand, shared electronics stock, qualified suppliers, lead times, workcenter skills and calendars, budgets, and final-assembly dependencies.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-056 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-056"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-056 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-056"}) + successful_required_calls + reads_before_write

Check metadata for lgr-056-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-056-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-056-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-056-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-056-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-056-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-056-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-056-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-056 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-056"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-056-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-056-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-056-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-056-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-056-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-056-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-056-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-056-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-056 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-056"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-056-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-056-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-056-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-056-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-056-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-056-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-056-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-056-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The feasible promise reflects both the latest material arrival and qualified loaded capacity, with linked make-and-buy records.

Reject the unsupported branch: Promise from nominal routing time or buy from an unqualified faster supplier.

Select `COMMIT_FACP_PLAN` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `assembly_cost` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_accepted` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `orders_rejected` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_purchased` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `units_manufactured` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-056 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Promise from nominal routing time or buy from an unqualified faster supplier.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-057'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-057'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-057' AND decision_code='RESOLVE_EXPENSE_FILE'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-057' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-057 completed — RESOLVE_EXPENSE_FILE' AND body LIKE '%RESOLVE_EXPENSE_FILE%'

A. Okonkwo's Chicago lodging is inside every per-line limit - receipt attached, business purpose stated, 306.20 a night against a 350 cap - but it was incurred 2025-12-08 and first substantiated 2026-02-19, 73 days later, outside the 60 day fixed-date safe harbour, so it falls out of the accountable plan and is paid through payroll as W-2 wages rather than reimbursed tax-free.

port of TheAgentCompany research/external/repos/TheAgentCompany/workspaces/tasks/finance-expense-validation (expense extract + a rules file, find the mis-stated lines, report a per-category rollup). Kept: the spreadsheet-plus-policy surface and the rollup deliverable. Changed: the source grades keyword-to-category matching over 1,000 synthetic rows, which is arithmetic volume, so the port replaces the volume with one judgement — every one of the 13 lines passes the per-line test and the file is still wrong. Policy limits are grounded in research/external/articles/te-expense-audit--{gsa-mie-breakdown,gsa-perdiem-faq,ecfr-accountable-plan,irs}.md (GSA CONUS M&IE tiers and the 75% first/last-day rule, the 12-hour one-day gate, work-location locality rule, provided-meal exceptions, and the 26 CFR 1.62-2 60-day substantiation safe harbour with W-2 consequence). Differs from expense_audit/te-sample-feb, which tests per-line limits (meal cap, business class, missing receipt) and grades a violation count — here no line breaks a limit; and from expense_audit/threshold-shaving-h1, which grades a cross-period behavioural pattern over compliant claims — here the finding is a single line's date arithmetic and its payroll consequence. docs/HARD-LAYER-DESIGN.md M3 (non-collapse), M4 (money re-derivation off the rate table, never the claimed figure), M5 (the provided meal and the venue city live only in email, not in the extract).

Prompt:
**Dev Bhatt · Payroll & Expense Lead · Teams 09:20**

Sign off the February expense file only after identifying every supported exception and its payroll impact.

This is blocking today's operating review. The obvious screen may be stale and similarly named records exist, so give me the current supported position, the realistic alternatives, and the source identities behind it. Record the supported disposition on the open finance case and send Controls a concise completion note.

SELECT ROUND(SUM(json_extract(cells,'$[6]')),2) FROM sheet_rows WHERE file='expense-extract-2026-02.xlsx' AND row_no>1 AND julianday(json_extract(cells,'$[8]')) - julianday(json_extract(cells,'$[3]')) > 60

duplicate
missing receipt
no receipt
over the cap
exceeds the cap
business class

Question: finance case work item

Question: finance case work item

FINCASE-057 completed — RESOLVE_EXPENSE_FILE

Question: finance case work item

Resolve immutable work item FINCASE-057 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Join claims, receipts, attendees, dates, policy revision, approvals, and payroll cutoff treatment item by item.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-057 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-057"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-057 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-057"}) + successful_required_calls + reads_before_write

Check metadata for lgr-057-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-057-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-057-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-057-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-057-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-057-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-057-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-057-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-057 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-057"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-057-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-057-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-057-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-057-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-057-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-057-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-057-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-057-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-057 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-057"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-057-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-057-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-057-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-057-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-057-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-057-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-057-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-057-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

Valid business expenses proceed; unsupported or misapproved items are separately held or recovered.

Reject the unsupported branch: Approve the file from aggregate spend or reject every unusual merchant.

Select `RESOLVE_EXPENSE_FILE` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `perdiem_due` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `conference_mie_rate` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `nonaccountable_amount` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `reimbursable_total` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `structural_exception_line` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `structural_exception_reason` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-057 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Approve the file from aggregate spend or reject every unusual merchant.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-058'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-058'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-058' AND decision_code='REPORT_SAMPLE_EXCEPTIONS'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-058' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-058 completed — REPORT_SAMPLE_EXCEPTIONS' AND body LIKE '%REPORT_SAMPLE_EXCEPTIONS%'

business class airfare requires VP pre-approval; economy is the standard

research/finance-agent-workflows.md wf#11 (T&E policy compliance sampling; Ramp-class agents claim >99% automation here)

Prompt:
**Sam Rivera · Controller · Teams 16:15**

Tell the controller which sampled expenses breach policy and the exact exposure.

Treat this as a live control decision rather than a lookup. Reconcile the relevant systems at their effective dates, call out any unresolved evidence gap, and do not make the numbers agree by changing unrelated records. Leave the open finance case in the exact supported state and give Controls an audit-ready handoff.

Question: finance case work item

Question: finance case work item

FINCASE-058 completed — REPORT_SAMPLE_EXCEPTIONS

Question: finance case work item

Resolve immutable work item FINCASE-058 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Apply the effective policy thresholds and evidence requirements to each sampled claim and approval.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-058 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-058"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-058 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-058"}) + successful_required_calls + reads_before_write

Check metadata for lgr-058-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-058-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-058-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-058-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-058-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-058-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-058-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-058-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-058 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-058"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-058-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-058-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-058-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-058-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-058-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-058-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-058-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-058-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-058 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-058"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-058-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-058-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-058-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-058-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-058-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-058-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-058-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-058-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

Only claims failing a current rule belong in the exception population.

Reject the unsupported branch: Flag every claim above a round-number amount or use a superseded threshold.

Select `REPORT_SAMPLE_EXCEPTIONS` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `violation_count` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `violating_report_ids` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `out_of_policy_amount` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `worst_violation_rule` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-058 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Only claims failing a current rule belong in the exception population.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-059'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-059'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-059' AND decision_code='CERTIFY_EXPENSE_SAMPLE'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-059' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-059 completed — CERTIFY_EXPENSE_SAMPLE' AND body LIKE '%CERTIFY_EXPENSE_SAMPLE%'

escalated variant of expense_audit/te-sample-feb via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: research/finance-agent-workflows.md wf#11 (T&E policy compliance sampling; Ramp-class agents claim >99% automation here)

Prompt:
**Sam Rivera · Controller · Teams 16:15**

Can the February sample be certified after controls review?

The earlier working paper is not a conclusion. Please determine what the current records actually support, including the viable option and any hold, then leave enough provenance for an independent reviewer to reproduce it. Update only the scoped finance case, verify what persisted, and close the loop with Controls.

Question: finance case work item

Question: finance case work item

FINCASE-059 completed — CERTIFY_EXPENSE_SAMPLE

Question: finance case work item

Resolve immutable work item FINCASE-059 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Reperform each test under the operative policy version and verify that exceptions have evidence, owner, and quantified impact.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-059 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-059"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-059 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-059"}) + successful_required_calls + reads_before_write

Check metadata for lgr-059-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-059-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-059-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-059-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-059-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-059-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-059-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-059-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-059 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-059"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-059-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-059-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-059-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-059-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-059-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-059-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-059-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-059-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-059 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-059"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-059-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-059-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-059-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-059-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-059-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-059-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-059-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-059-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The sample is certifiable only after current-rule exceptions are retained and clean claims are not over-flagged.

Reject the unsupported branch: Accept the original exception list without checking policy effectiveness.

Select `CERTIFY_EXPENSE_SAMPLE` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `violation_count` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `violating_report_ids` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `out_of_policy_amount` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `worst_violation_rule` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-059 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Accept the original exception list without checking policy effectiveness.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-060'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-060'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-060' AND decision_code='ESCALATE_THRESHOLD_SHAVING'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-060' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-060 completed — ESCALATE_THRESHOLD_SHAVING' AND body LIKE '%ESCALATE_THRESHOLD_SHAVING%'

research/external/articles: Oracle Expenses threshold-shaving detector — claims in the 450-499 band against a 500 receipt threshold, more than 5 times in 6 months

Prompt:
**Sam Rivera · Controller · Teams 11:55**

Determine whether anyone is splitting claims to avoid approval and quantify the supported pattern.

I need the answer and the operational consequence, not a list of screens visited. Resolve conflicting versions and identities, use the effective rule, and make the smallest supported change without disturbing neighboring work. Carry the decision through the governed case record and leave Controls a reproducible completion message.

Question: finance case work item

Question: finance case work item

FINCASE-060 completed — ESCALATE_THRESHOLD_SHAVING

Question: finance case work item

Resolve immutable work item FINCASE-060 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Aggregate related claims by employee, merchant, date window, and business purpose under the anti-splitting rule.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-060 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-060"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-060 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-060"}) + successful_required_calls + reads_before_write

Check metadata for lgr-060-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-060-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-060-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-060-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-060-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-060-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-060-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-060-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-060 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-060"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-060-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-060-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-060-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-060-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-060-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-060-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-060-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-060-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-060 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-060"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-060-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-060-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-060-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-060-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-060-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-060-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-060-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-060-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

A repeated just-below-threshold pattern is escalated only when the linkage and period tests are met.

Reject the unsupported branch: Treat every claim below the approval threshold as suspicious.

Select `ESCALATE_THRESHOLD_SHAVING` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `shaving_employee` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `shaving_claim_count` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `shaving_total` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `detector_triggered` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-060 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Treat every claim below the approval threshold as suspicious.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-061'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-061'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-061' AND decision_code='ISSUE_SCALED_LMT_METRICS'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-061' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-061 completed — ISSUE_SCALED_LMT_METRICS' AND body LIKE '%ISSUE_SCALED_LMT_METRICS%'

closes tracked coverage gap tatqa.scale_unit (sim/coverage.py); NExTplusplus/TAT-QA grades `scale` (thousand/million/billion/percent) as a separately annotated field — research/evals-and-benchmarks.md; round-2 ledger row 28 (add a scale/unit field rather than widening tolerances until units stop mattering)

Prompt:
**Dana Kim · Credit Manager · Teams 15:40**

Give Credit Lockheed Martin's FY2024 sales and operating margin with the units impossible to misread.

I need a decision the team can use today, with the amounts, dates, and immutable record identifiers that support it. Some surrounding records came from an older review, so establish what is current before relying on them. Record the supported disposition on the open finance case and send Controls a concise completion note.

Question: finance case work item

Question: finance case work item

FINCASE-061 completed — ISSUE_SCALED_LMT_METRICS

Question: finance case work item

Resolve immutable work item FINCASE-061 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Resolve issuer, annual period, taxonomy concepts, reported scale, and the ratio denominator from the same filing basis.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-061 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-061"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-061 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-061"}) + successful_required_calls + reads_before_write

Check metadata for lgr-061-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-061-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-061-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-061-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-061-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-061-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-061-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-061-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-061 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-061"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-061-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-061-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-061-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-061-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-061-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-061-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-061-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-061-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-061 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-061"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-061-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-061-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-061-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-061-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-061-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-061-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-061-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-061-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The answer must preserve the filing's magnitude and calculate margin from compatible annual facts.

Reject the unsupported branch: Drop the unit label or mix millions with absolute dollars.

Select `ISSUE_SCALED_LMT_METRICS` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `revenue` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `revenue_scale` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `revenue_usd` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `operating_margin_pct` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `source_form` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

Use the Dynamics generic action surface to move only FINCASE-061 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Drop the unit label or mix millions with absolute dollars.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-062'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-062'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-062' AND decision_code='ISSUE_CALDERWOOD_INCOME_VIEW'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-062' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-062 completed — ISSUE_CALDERWOOD_INCOME_VIEW' AND body LIKE '%ISSUE_CALDERWOOD_INCOME_VIEW%'

port of research/external/repos/TheAgentCompany/workspaces/tasks/finance-create-10k-income-report (extract income-statement figures from 10-K Item 8 for multiple years, compile a structured table, and derive the year-over-year percentage change). The source's plumbing does not port: its ownCloud folder-navigation checkpoint, its written /workspace/net_income_report.csv, and its LLM-judged RocketChat message to David Wong are all environment-specific, and its checkpoint 4 graded an exact CSV cell set. Here the workbook becomes the frozen filings server (filings_companies/filings_facts/filings_documents, seeded as tasks/finance_qa/scale-trap-lmt does), the column structure becomes submit_answer fields, the CSV-shape checkpoint becomes the required_servers/reads_before_submit trace checks, and the derived percentage change is graded as revenue_growth_pct alongside a derived margin. The source's own trap - 'net income ... in section/item 8' and 'the name of registrant as specified in its charter' - is kept and sharpened: docs/HARD-LAYER-DESIGN.md M3 (non-collapse), M4 (the margin and the growth rate are recomputed from revenue and the line items, never read off a stated figure) and M5 (the governing basis lives only in FRP-02)

Prompt:
**Marta Ilyin · FP&A Manager · Teams 09:20**

Build the Calderwood FY2025 income view for the board comparison and explain any nonstandard taxonomy mapping.

This is blocking today's operating review. The obvious screen may be stale and similarly named records exist, so give me the current supported position, the realistic alternatives, and the source identities behind it. Leave the open finance case in the exact supported state and give Controls an audit-ready handoff.

SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='CostOfRevenue' AND fy='2025' AND period_end='2025-12-31'

SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='GrossProfit' AND fy='2025' AND period_end='2025-12-31'

SELECT (SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='ProfitLoss' AND fy='2025' AND period_end='2025-12-31') - (SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='NetIncomeLossAttributableToNoncontrollingInterest' AND fy='2025' AND period_end='2025-12-31')

SELECT ROUND(100.0*(SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='OperatingIncomeLoss' AND fy='2025' AND period_end='2025-12-31')/(SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='Revenues' AND fy='2025' AND period_end='2025-12-31'),4)

SELECT ROUND(100.0*((SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='Revenues' AND fy='2025' AND period_end='2025-12-31')/(SELECT value FROM filings_facts WHERE cik='0009900413' AND concept='Revenues' AND fy='2025' AND period_end='2024-12-31')-1),4)

Question: finance case work item

Question: finance case work item

FINCASE-062 completed — ISSUE_CALDERWOOD_INCOME_VIEW

Question: finance case work item

Resolve immutable work item FINCASE-062 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Join the synthetic registrant, filing accession, annual concepts, units, signs, and internal comparison policy.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-062 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-062"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-062 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-062"}) + successful_required_calls + reads_before_write

Check metadata for lgr-062-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-062-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-062-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-062-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-062-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-062-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-062-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-062-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-062 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-062"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-062-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-062-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-062-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-062-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-062-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-062-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-062-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-062-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-062 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-062"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-062-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-062-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-062-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-062-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-062-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-062-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-062-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-062-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The board view uses same-period filed facts with explicit mapping for any company-specific concept.

Reject the unsupported branch: Substitute a similarly named public registrant or infer missing facts.

Select `ISSUE_CALDERWOOD_INCOME_VIEW` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `revenue` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `cost_of_revenue` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `gross_profit` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `operating_income` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `net_income` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `operating_margin_pct` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `revenue_growth_pct` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `source_form` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

Use the Dynamics generic action surface to move only FINCASE-062 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use only when the required evidence intersection is incomplete or conflicting.

Substitute a similarly named public registrant or infer missing facts.