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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-021' AND decision_code='ASSIGN_SUBLEDGER_BREAK'

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

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

research/finance-agent-workflows.md wf#2 (close checklist + subledger tie-out); chaos: workbook vs ERP divergence

Prompt:
**Sam Rivera · Controller · Teams 18:20**

Which February subledger is blocking close, what is the exact break, and who has to clear it?

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

Question: finance case work item

Question: finance case work item

FINCASE-021 completed — ASSIGN_SUBLEDGER_BREAK

Question: finance case work item

Resolve immutable work item FINCASE-021 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 control accounts, subledger totals, close-task ownership, and cut-off evidence at the same close 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-021 and use its current subject and status as the scope anchor.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-021-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-021-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 non-tied subledger and its accountable owner must be identified without netting it against clean ledgers.

Reject the unsupported branch: Spread the total variance across all subledger owners.

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

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

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

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

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

deterministic answer check: contains_all

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

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

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

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

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

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

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

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

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

Spread the total variance across all subledger owners.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-022' AND decision_code='HOLD_SUBLEDGER_PACKAGE'

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

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

escalated variant of close_mgmt/subledger-tieout-feb via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: research/finance-agent-workflows.md wf#2 (close checklist + subledger tie-out); chaos: workbook vs ERP divergence

Prompt:
**Sam Rivera · Controller · Teams 18:20**

Can the February subledger package be certified under the current close-control revision?

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

Question: finance case work item

Question: finance case work item

FINCASE-022 completed — HOLD_SUBLEDGER_PACKAGE

Question: finance case work item

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

Reconcile the break, its aging, owner evidence, and the operative sign-off threshold rather than relying on the prior checklist.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-022-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-022-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 package remains on hold if the identified break lacks the required resolution evidence even when other ledgers tie.

Reject the unsupported branch: Use the superseded tolerance or mark every close task complete.

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

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

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

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

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

deterministic answer check: contains_all

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

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

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

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

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

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

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

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

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

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

Use the superseded tolerance or mark every close task complete.

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

answer_checks: submitted fields graded by type with tolerances

trace_checks: required servers visited, reads precede submission

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


SELECT COUNT(*) FROM erp_collection_letters WHERE account='US-008' AND letter_code='3' AND letter_date='2026-03-02' AND status='Sent'

SELECT COUNT(*) FROM erp_collection_letters WHERE account='US-008'

SELECT fee FROM erp_collection_letters WHERE account='US-008' AND letter_code='3'

SELECT on_hold FROM erp_customers WHERE account='US-008'

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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-023' AND decision_code='ISSUE_NEXT_DUNNING_STEP'

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

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

Explanation: Letter 2 was sent 14 days ago and SPINV-002 remains unpaid, so letter 3 posts with its $40 fee; the oldest past-due item is at 47 days, below the ~75-day credit-hold threshold, so no hold yet.

wave-2 writes on the D365 hold/letter machinery (research/finance-agent-workflows.md wf#10); dunning ladder AR-SOP-003

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

Take exactly the next permitted collections step for Sparrow Retail and explain why it is due now.

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.

Question: finance case work item

Question: finance case work item

FINCASE-023 completed — ISSUE_NEXT_DUNNING_STEP

Question: finance case work item

Resolve immutable work item FINCASE-023 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 live overdue balance, prior letters and dates, customer status, and the current dunning ladder.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-023-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-023-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 current position permits one specific next letter and no broader credit action.

Reject the unsupported branch: Skip a letter level or place a broad hold without the required condition.

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

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

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

deterministic answer check: contains_all

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

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

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

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

Skip a letter level or place a broad hold without the required condition.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-024' AND decision_code='RESOLVE_MEADOW_BILLING_STATUS'

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

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

email attachment (shared AP/AR mailbox), corroborated by the manual invoice log spreadsheet

novel: chaos patterns 'invoices existing only in email' (68% manual keying) + 'Excel-only manual log' (research/domain-workflows.md §3)

Prompt:
**Sam Rivera · Controller · Teams 08:05**

Determine whether Meadow was invoiced, what remains due, and what follow-up is justified.

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.

Question: finance case work item

Question: finance case work item

FINCASE-024 completed — RESOLVE_MEADOW_BILLING_STATUS

Question: finance case work item

Resolve immutable work item FINCASE-024 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 counterparty across email, subsidiary books, and ERP rather than treating absence in one system as absence everywhere.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-024-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-024-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 authoritative invoice evidence and open balance determine whether a scoped follow-up is needed.

Reject the unsupported branch: Create a replacement invoice solely because the ERP search is empty.

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

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

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

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

deterministic answer check: contains_all

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

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

Use the Dynamics generic action surface to move only FINCASE-024 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 a replacement invoice solely because the ERP search is empty.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-025' AND decision_code='CERTIFY_BILLING_WITH_SYSTEM_EXCEPTION'

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

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

escalated variant of cross_system/email-invoice-meadow via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: novel: chaos patterns 'invoices existing only in email' (68% manual keying) + 'Excel-only manual log' (research/domain-workflows.md §3)

Prompt:
**Sam Rivera · Controller · Teams 08:05**

Can Meadow's February billing be certified after the cross-system control review?

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-025 completed — CERTIFY_BILLING_WITH_SYSTEM_EXCEPTION

Question: finance case work item

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

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

exact policy metadata and full-document reads

Apply the effective system-of-record hierarchy to the email evidence, books record, ERP gap, and customer identity.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-025-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-025-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.

Certification must state the authoritative record and preserve any system-integration exception separately.

Reject the unsupported branch: Choose whichever system shows the most convenient balance.

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

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

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

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

deterministic answer check: contains_all

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

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

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

Choose whichever system shows the most convenient balance.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-026' AND decision_code='ASSIGN_INTERCOMPANY_DIFFERENCE'

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

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

ICINV-03 ($22,500) — received by the subsidiary 2026-03-01 but not yet booked (in transit)

research/finance-agent-workflows.md wf#7; chaos primitive: system A learned the truth before system B

Prompt:
**Sam Rivera · Controller · Teams 17:02**

Tell the controller what each side says for February intercompany and isolate the real source of the difference.

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.

Question: finance case work item

Question: finance case work item

FINCASE-026 completed — ASSIGN_INTERCOMPANY_DIFFERENCE

Question: finance case work item

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

Align legal entity, period, currency, invoice and settlement records across the parent ERP and subsidiary books.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-026-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-026-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 residual must be explained by matched transaction-level timing or classification evidence, not a net plug.

Reject the unsupported branch: Use one entity's ledger as the truth for both sides.

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

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

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

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

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

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

deterministic answer check: contains_all

Use the Dynamics generic action surface to move only FINCASE-026 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 one entity's ledger as the truth for both sides.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-027' AND decision_code='HOLD_INTERCOMPANY_SIGNOFF'

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

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

escalated variant of cross_system/intercompany-tieout-feb via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: research/finance-agent-workflows.md wf#7; chaos primitive: system A learned the truth before system B

Prompt:
**Sam Rivera · Controller · Teams 17:02**

Is the February intercompany package ready for sign-off under the effective policy?

This is blocking today's operating review. The obvious screen may be stale and similarly named records exist, so give me the current supported position, the realistic alternatives, and the source identities behind it. 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-027 completed — HOLD_INTERCOMPANY_SIGNOFF

Question: finance case work item

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

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

exact policy metadata and full-document reads

Reperform both-ledger matching, test the residual against the current threshold, and verify counterparty acknowledgement and ownership.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-027-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-027-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 package is held when a supported difference lacks the required evidence or owner despite an explainable total.

Reject the unsupported branch: Apply the superseded netting threshold to close the item.

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

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

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

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

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

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

deterministic answer check: contains_all

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

Apply the superseded netting threshold to close the item.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-028' AND decision_code='ISSUE_GROUP_EXPOSURE'

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

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

novel: data-chaos pattern 'subsidiary AR lives outside the ERP' (research/domain-workflows.md §3); FB has no cross-system tasks

Prompt:
**Sam Rivera · Controller · Teams 10:41**

Give Treasury one defensible Adventure Works group exposure number without double counting.

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

SELECT ROUND(SUM(amount-settled),2) FROM erp_cust_trans WHERE account='SYNCUS-0002' AND txn_type='Invoice' AND closed=0

Question: finance case work item

Question: finance case work item

FINCASE-028 completed — ISSUE_GROUP_EXPOSURE

Question: finance case work item

Resolve immutable work item FINCASE-028 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 related customer identities across ERP and subsidiary books, then net only linked credits, payments, and duplicate 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-028 and use its current subject and status as the scope anchor.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-028-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-028-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.

Group exposure is the deduplicated open amount across authoritative systems and legal entities.

Reject the unsupported branch: Sum every name match across systems without entity or document reconciliation.

Select `ISSUE_GROUP_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 `erp_open_balance` conclusion in the discovered reporting schema using its declared type and scale.

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

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

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

Sum every name match across systems without entity or document reconciliation.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-029' AND decision_code='RESTATE_CUTOVER_EXPOSURE'

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

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

grow: escalated from cross_system/total-ar-adventure-group (haiku passed 2/2 -> too_easy). Escalations: +sheet-only side invoice (email-corroborated), +stale AR-summary distractor that must be ignored, walk 6->10.

Prompt:
**Sam Rivera · Controller · Teams 10:41**

Rebuild Adventure Works exposure including the CES cutover paperwork and explain every adjustment to the first view.

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. 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-029 completed — RESTATE_CUTOVER_EXPOSURE

Question: finance case work item

Resolve immutable work item FINCASE-029 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 migration correspondence, legacy and current customer identities, open documents, credits, and cutover status.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-029-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-029-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 migrated records not already represented in the current ledger adjust group exposure.

Reject the unsupported branch: Add all legacy paperwork to the current balance.

Select `RESTATE_CUTOVER_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 `erp_open_balance` conclusion in the discovered reporting schema using its declared type and scale.

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

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

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

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

Add all legacy paperwork to the current balance.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-030' AND decision_code='CORRECT_WATCHLIST_DRIFT'

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

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

chaos patterns 'spreadsheet version drift' + '1 in 3 CFOs distrust close data' (research/domain-workflows.md §3); enabled by sheets formula-cell support (Graph serves cached values, like real Excel)

Prompt:
**Sam Rivera · Controller · Teams 08:31**

Check the CFO's watchlist number, explain the formula drift, and state the corrected exposure.

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

Question: finance case work item

Question: finance case work item

FINCASE-030 completed — CORRECT_WATCHLIST_DRIFT

Question: finance case work item

Resolve immutable work item FINCASE-030 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 workbook formulas and cached values with live ERP balances and the governed watchlist definition.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-030-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-030-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 tracker must be corrected from source balances when its cached formula result no longer reflects the included accounts.

Reject the unsupported branch: Trust the displayed workbook total because the formula cell exists.

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

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

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

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

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

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

deterministic answer check: contains_all

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

Trust the displayed workbook total because the formula cell exists.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-031' AND decision_code='REPORT_TRUE_OVERDUE_AP'

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

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

financebenchmark:erp_qa/AP Overdue (user-brief example; GT computed in-world)

Prompt:
**Robin Vale · Treasury · Teams 08:52**

Give Treasury the AP amount truly overdue today and distinguish it from invoices merely due soon.

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

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

Question: finance case work item

Question: finance case work item

FINCASE-031 completed — REPORT_TRUE_OVERDUE_AP

Question: finance case work item

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

Use the frozen business date, open vendor transactions, due dates, settlements, and entity scope.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-031-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-031-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 open amounts with due dates before today belong in overdue AP.

Reject the unsupported branch: Sum every open invoice or rely on a paginated first screen.

Select `REPORT_TRUE_OVERDUE_AP` 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_overdue_ap` conclusion in the discovered reporting schema using its declared type and scale.

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

deterministic answer check: contains_all

Use the Dynamics generic action surface to move only FINCASE-031 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 open amounts with due dates before today belong in overdue AP.

Sum every open invoice or rely on a paginated first screen.