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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-043' AND decision_code='REPORT_BIRCH_OVERDUE_BANDS'

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

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

Prompt:
**Casey Morgan · AR & Collections · Teams**

Give Collections Birch Company's overdue breakdown by aging band as of the frozen date.

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. Update only the scoped finance case, verify what persisted, and close the loop with Controls.

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_cust_trans WHERE account IN ('US-027') AND txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) > 0

Question: finance case work item

Question: finance case work item

FINCASE-043 completed — REPORT_BIRCH_OVERDUE_BANDS

Question: finance case work item

Resolve immutable work item FINCASE-043 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 the exact customer and classify each open remainder by due-date age at the same as-of date.

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-043 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-043-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-043-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-043-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-043-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-043-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-043-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-043-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-043-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-043-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-043-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-043-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-043-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 customer aging must be rebuilt from live open transactions and exact day bands.

Reject the unsupported branch: Use invoice dates or a similarly named customer.

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

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

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

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

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

Use the Dynamics generic action surface to move only FINCASE-043 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 invoice dates or a similarly named customer.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-044' AND decision_code='REPORT_180_PLUS_EXPOSURE'

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

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

clone of microsoft/FinanceBenchmark erp_qa (AR / Aged Balance); question verbatim, ground truth recomputed in-world (docs/AUDIT.md A3)

Prompt:
**Casey Morgan · AR & Collections · Teams**

Quantify the USMF receivables aged 180 days or more and identify the contributing accounts.

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. Carry the decision through the governed case record and leave Controls a reproducible completion message.

SELECT COUNT(*) FROM erp_cust_trans WHERE txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) > 180

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_cust_trans WHERE txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) > 180

Question: finance case work item

Question: finance case work item

FINCASE-044 completed — REPORT_180_PLUS_EXPOSURE

Question: finance case work item

Resolve immutable work item FINCASE-044 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 exact long-dated bucket definition to all open customer remainders at the frozen date.

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-044 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-044-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-044-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-044-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-044-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-044-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-044-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-044-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-044-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-044-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-044-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-044-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-044-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 items meeting the 180-day due-date test belong in the reported tail.

Reject the unsupported branch: Treat every past-due item as 180-plus or stop at the first result page.

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

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

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

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

Use the Dynamics generic action surface to move only FINCASE-044 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 items meeting the 180-day due-date test belong in the reported tail.

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

Treat every past-due item as 180-plus or stop at the first result page.

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 status FROM erp_finance_cases WHERE case_id='FINCASE-045'

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-045' AND decision_code='REPORT_BIRCH_LIVE_AGING'

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

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

Prompt:
**Casey Morgan · AR & Collections · Teams**

Give the credit team Birch Company's complete aged balance and explain any snapshot mismatch.

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. 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-045 completed — REPORT_BIRCH_LIVE_AGING

Question: finance case work item

Resolve immutable work item FINCASE-045 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 customer identity, derive live buckets, and reconcile the batch snapshot refresh timestamp.

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-045 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-045-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-045-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-045-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-045-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-045-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-045-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-045-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-045-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-045-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-045-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-045-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-045-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 live transaction calculation controls when the snapshot is stale or incomplete.

Reject the unsupported branch: Repeat the snapshot row without checking its run date.

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

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

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

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

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

Use the Dynamics generic action surface to move only FINCASE-045 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.

Repeat the snapshot row without checking its run date.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-046' AND decision_code='BUILD_WEEKLY_AP_DUE_SET'

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

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

clone of microsoft/FinanceBenchmark erp_qa (AP / AP Invoices); question verbatim, ground truth recomputed in-world (docs/AUDIT.md A3)

Prompt:
**Priya Shah · AP Manager · Teams**

Which USMF vendor invoices truly need payment this week, and what total cash should Treasury reserve?

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. Leave the open finance case in the exact supported state and give Controls an audit-ready handoff.

SELECT COUNT(*) FROM erp_vend_trans WHERE txn_type='Invoice' AND closed=0 AND due_date BETWEEN '2026-03-02' AND '2026-03-08'

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_vend_trans WHERE txn_type='Invoice' AND closed=0 AND due_date BETWEEN '2026-03-02' AND '2026-03-08'

Question: finance case work item

Question: finance case work item

FINCASE-046 completed — BUILD_WEEKLY_AP_DUE_SET

Question: finance case work item

Resolve immutable work item FINCASE-046 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

Filter open vendor obligations by the governed payment week, due date, settlement status, and company.

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-046 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-046-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-046-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-046-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-046-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-046-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-046-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-046-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-046-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-046-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-046-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-046-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-046-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 reserve includes only eligible open remainders due inside the exact window.

Reject the unsupported branch: Use invoice dates or include every open AP document.

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

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

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

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

Use the Dynamics generic action surface to move only FINCASE-046 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 invoice dates or include every open AP document.


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-2771.11)>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-047'

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-047' AND decision_code='COMMIT_PORTABLE_POWER_PLAN'

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

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

clone of agentic-labs/erp-bench task 2141_hard_15_parallel_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 feasible supply plan for the Portable Power Station portfolio and state the binding constraint.

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.

Question: finance case work item

Question: finance case work item

FINCASE-047 completed — COMMIT_PORTABLE_POWER_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-047 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 open demand, multilevel BOMs, stock, purchase lead times, workcenter calendars, supplier capacity, and customer budgets before committing linked records.

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-047 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-047-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-047-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-047-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-047-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-047-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-047-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-047-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-047-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-047-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-047-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-047-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-047-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 chosen make-and-buy plan must cover feasible demand without exceeding capacity, stock, or approved spend.

Reject the unsupported branch: Create orders from aggregate demand without exploding subassemblies or checking capacity.

Select `COMMIT_PORTABLE_POWER_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-047 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.

Create orders from aggregate demand without exploding subassemblies or checking capacity.


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-5368.26)>0.01

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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-048' AND decision_code='COMMIT_LFP_MODULE_PLAN'

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

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

clone of agentic-labs/erp-bench task 2143_hard_15_parallel_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 how the LFP Energy Storage Module orders can be supplied on time and identify which branch of the plan constrains delivery.

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.

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-048 completed — COMMIT_LFP_MODULE_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-048 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

Trace every order through the multilevel product structure, on-hand stock, supplier terms, production routes, and workcenter availability.

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-048 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-048-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-048-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-048-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-048-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-048-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-048-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-048-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-048-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-048-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-048-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-048-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-048-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 executable plan is the least-cost feasible branch that covers dated demand and preserves order linkage.

Reject the unsupported branch: Buy or manufacture every shortage independently, double-counting shared stock.

Select `COMMIT_LFP_MODULE_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-048 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.

Buy or manufacture every shortage independently, double-counting shared stock.


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-2860.79)>0.01

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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-049' AND decision_code='COMMIT_PORTABLE_POWER_VARIANT_PLAN'

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

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

clone of agentic-labs/erp-bench task 2144_hard_15_parallel_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**

Resolve the second Portable Power Station portfolio without assuming the earlier product mix or capacities still apply.

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-049 completed — COMMIT_PORTABLE_POWER_VARIANT_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-049 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

Recompute demand, BOM quantities, stock reservations, supplier capacity, customer budgets, and production slots for this isolated world.

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-049 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-049-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-049-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-049-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-049-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-049-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-049-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-049-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-049-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-049-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-049-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-049-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-049-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 this world's dated constraints determine the purchase, manufacture, and sales records.

Reject the unsupported branch: Reuse quantities or suppliers from another benchmark task.

Select `COMMIT_PORTABLE_POWER_VARIANT_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-049 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.

Reuse quantities or suppliers from another benchmark task.


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-16199.21)>0.01

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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-050' AND decision_code='COMMIT_RACK_BATTERY_PLAN'

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

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

clone of agentic-labs/erp-bench task 2146_hard_15_parallel_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 Fulfillment an executable plan for the Modular Rack Battery orders and show where the critical path lands.

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.

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-050 completed — COMMIT_RACK_BATTERY_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-050 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

Compare parallel subassembly routes, shared inputs, vendor lead times, workcenter calendars, and customer commitments.

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-050 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-050-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-050-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-050-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-050-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-050-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-050-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-050-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-050-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-050-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-050-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-050-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-050-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 plan must synchronize branch completion at final assembly without overbooking a shared resource.

Reject the unsupported branch: Schedule final assembly from the fastest branch while ignoring slower dependencies.

Select `COMMIT_RACK_BATTERY_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-050 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.

Schedule final assembly from the fastest branch while ignoring slower dependencies.


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-5081.48)>0.01

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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-051' AND decision_code='COMMIT_LFP_CAPACITY_PLAN'

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

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

clone of agentic-labs/erp-bench task 2147_hard_15_parallel_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**

Find a feasible plan for this LFP module portfolio and explain how the larger order set changes capacity and purchasing.

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.

Question: finance case work item

Question: finance case work item

FINCASE-051 completed — COMMIT_LFP_CAPACITY_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-051 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 shared materials and workcenter time across all dated orders, then evaluate suppliers and budgets for residual shortages.

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-051 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-051-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-051-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-051-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-051-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-051-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-051-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-051-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-051-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-051-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-051-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-051-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-051-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 portfolio must respect the isolated demand mix and binding capacity branch.

Reject the unsupported branch: Scale another task's plan proportionally without recalculating discrete BOM and slot constraints.

Select `COMMIT_LFP_CAPACITY_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-051 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.


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-4284.53)>0.01

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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-052' AND decision_code='COMMIT_SOLAR_WALL_PLAN'

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

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

clone of agentic-labs/erp-bench task 2149_hard_15_parallel_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**

Plan the Solar Storage Battery portfolio through procurement and production, with a defensible completion date for every order.

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.

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-052 completed — COMMIT_SOLAR_WALL_PLAN

Question: finance case work item

Resolve immutable work item FINCASE-052 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

Explode each configuration, net common inventory once, compare vendor lead times, and reserve compatible workcenters by date.

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-052 and use its current subject and status as the scope anchor.

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

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

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

Check metadata for lgr-052-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-052-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-052-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-052-control-current"}) + successful_required_calls + reads_before_write

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

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

Use lgr-052-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-052-evidence-map"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

Open current operations message em-lgr-052-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-052-operations"}) + successful_required_calls + reads_before_write

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

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

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

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

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

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

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

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

Inspect Drive metadata for fincase-052-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-052-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-052-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-052-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 supported plan is the feasible linked network whose latest required branch meets customer and budget constraints.

Reject the unsupported branch: Place blanket purchase orders for every gross requirement.

Select `COMMIT_SOLAR_WALL_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-052 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.

Place blanket purchase orders for every gross requirement.