SELECT state FROM erp_payment_runs WHERE run_id='PR-00001'

SELECT GROUP_CONCAT(invoice) FROM (SELECT invoice FROM erp_payment_run_lines WHERE run_id='PR-00001' AND disposition='paid' ORDER BY invoice)

SELECT COUNT(*) FROM erp_payment_run_lines WHERE run_id='PR-00001' AND disposition='rejected'

SELECT reason_code FROM erp_payment_run_lines WHERE run_id='PR-00001' AND invoice='5521-OPS'

SELECT disposition FROM erp_payment_run_lines WHERE run_id='PR-00001' AND invoice='OSINV-5555'

SELECT ROUND(total_paid,2) FROM erp_payment_runs WHERE run_id='PR-00001'

SELECT closed FROM erp_vend_trans WHERE invoice='OSINV-5521'

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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-001' AND decision_code='REJECT_DUPLICATE_RELEASE_CLEAN'

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

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

docs/HARD-LAYER-DESIGN.md M1/M3/M4/M5/M7; chaos pattern 8 (near-duplicate invoice numbers, ~1.5% duplicate-payment leakage) in research/domain-workflows.md; disbursement controls in research/external/articles/vendor-master-bec-fraud--afp-truist.md

Prompt:
**Robin Vale · Treasury · Teams 08:05, Friday 6 March**

Before the office-supplies run leaves the bank, tell Robin which documents can safely be paid and what must be stopped.

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.

SELECT ROUND(SUM(net_amount),2) FROM erp_payment_run_lines WHERE disposition='paid'

Question: finance case work item

Question: finance case work item

FINCASE-001 completed — REJECT_DUPLICATE_RELEASE_CLEAN

Question: finance case work item

Resolve immutable work item FINCASE-001 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 proposed run, settled AP history, purchase-order identity, the current duplicate-control revision, and the vendor statement.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-001-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-001-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 resent document matches a previously settled invoice on vendor, purchase order, and amount while the similar clean invoice does not.

Reject the unsupported branch: Reject every invoice with a repeated amount or trust the proposal without checking settled history.

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

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

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

deterministic answer check: contains_all

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

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

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

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

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

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

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

answer_checks: submitted fields graded by type with tolerances

trace_checks: required servers visited, reads precede submission

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


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-002' AND decision_code='REOPEN_RETURNED_RECEIVABLE'

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

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

gap found in repo sweep (research/external/repos/INDEX.md): payment failure after settlement — ACH returns/reversals

Prompt:
**Robin Vale · Treasury · Teams 07:48**

Tell Treasury what the Lamna return reverses and what balance Collections should now work.

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-002 completed — REOPEN_RETURNED_RECEIVABLE

Question: finance case work item

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

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

exact policy metadata and full-document reads

Join the bank return reference to settlements and the still-open customer transactions at the same effective date.

source-system reads before the governed write

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

exact Gmail message and attachment reads

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-002-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-002-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 bank has returned a payment that the ERP still treats as applied, so the linked receivable must be reopened in the decision record.

Reject the unsupported branch: Use the stale ERP balance or add the return to every open invoice.

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

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

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

deterministic answer check: contains_all

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

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

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

Use the Dynamics generic action surface to move only FINCASE-002 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 the stale ERP balance or add the return to every open invoice.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-003' AND decision_code='RESTATE_AND_HOLD_CERTIFICATION'

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

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

escalated variant of bank_rec/ach-return-mar 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: gap found in repo sweep (research/external/repos/INDEX.md): payment failure after settlement — ACH returns/reversals

Prompt:
**Robin Vale · Treasury · Teams 07:48**

Can the Lamna balance be certified after the control review, and which reconciliation exception must remain open?

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-003 completed — RESTATE_AND_HOLD_CERTIFICATION

Question: finance case work item

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

Establish the effective reconciliation policy, match the return to its exact settlement, and separate the accounting balance from the unresolved control exception.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-003-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-003-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 balance can be restated, but certification remains held until the returned settlement is reflected by the ledger owner.

Reject the unsupported branch: Repeat the original balance answer and close the review without applying the current certification rule.

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

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

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

deterministic answer check: contains_all

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

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

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

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

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

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

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

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

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

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


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-004' AND decision_code='CLASSIFY_RECONCILING_ITEMS'

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

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

research/finance-agent-workflows.md wf#1; grading taxonomy = Microsoft recon-agent buckets (Matched / Discrepancy / bank-only / books-only)

Prompt:
**Robin Vale · Treasury · Teams 09:05**

What actually explains the late-February bank-to-books differences, and which items should remain open?

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-004 completed — CLASSIFY_RECONCILING_ITEMS

Question: finance case work item

Resolve immutable work item FINCASE-004 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 each bank line with the ledger and timing window, then classify only supported fees, timing items, or true errors.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-004-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-004-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 unmatched population contains distinct timing and bank-charge causes that must not be netted into one unexplained variance.

Reject the unsupported branch: Force the statement and ledger totals to agree through one plug.

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

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

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

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

deterministic answer check: contains_all

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

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

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

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

Force the statement and ledger totals to agree through one plug.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-005' AND decision_code='HOLD_RECONCILIATION_SIGNOFF'

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

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

escalated variant of bank_rec/statement-divergence-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#1; grading taxonomy = Microsoft recon-agent buckets (Matched / Discrepancy / bank-only / books-only)

Prompt:
**Robin Vale · Treasury · Teams 09:05**

Is the February reconciliation ready for sign-off under the current close policy?

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-005 completed — HOLD_RECONCILIATION_SIGNOFF

Question: finance case work item

Resolve immutable work item FINCASE-005 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 the item-level match, identify the effective sign-off threshold, and determine whether each aged exception has an owner and evidence.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

At least one exception needs the current control treatment before the reconciliation can be certified.

Reject the unsupported branch: Rely on the preparer's earlier classification or the superseded aging threshold.

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

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

deterministic answer check: contains_all

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

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

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

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

Rely on the preparer's earlier classification or the superseded aging threshold.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-006' AND decision_code='ISSUE_COUNTERPARTY_LEVERAGE_VIEW'

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

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

financebenchmark:business_brief (section schema incl. internal AR/AP fusion) converted from LLM-judge rubric to structured fields; ratios from user-brief Caterpillar example

Prompt:
**Robin Vale · Treasury · email, Tue 07:55**

Give Credit a defensible Caterpillar leverage view and say whether our own books show a trading relationship.

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-006 completed — ISSUE_COUNTERPARTY_LEVERAGE_VIEW

Question: finance case work item

Resolve immutable work item FINCASE-006 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 filing identity, concept definitions, period and unit metadata, the brief policy, and both customer and vendor masters.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-006-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-006-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 filed debt and equity series support the leverage calculation, while the internal masters determine relationship status independently.

Reject the unsupported branch: Treat a name match or a single filing fact as the complete brief.

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

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

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

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

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

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

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

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

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

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

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

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

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

Treat a name match or a single filing fact as the complete brief.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-007' AND decision_code='CERTIFY_REVISED_LEVERAGE_SECTION'

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

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

escalated variant of business_brief/brief-caterpillar 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: financebenchmark:business_brief (section schema incl. internal AR/AP fusion) converted from LLM-judge rubric to structured fields; ratios from user-brief Caterpillar example

Prompt:
**Robin Vale · Treasury · email, Tue 07:55**

Can the Caterpillar leverage section pass controls review, or does its source treatment need correction?

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-007 completed — CERTIFY_REVISED_LEVERAGE_SECTION

Question: finance case work item

Resolve immutable work item FINCASE-007 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 filing revisions and units to the effective brief policy, then independently recheck internal counterparty 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-007 and use its current subject and status as the scope anchor.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-007-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-007-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 section may be certified only from same-basis annual facts and an explicit internal-master search.

Reject the unsupported branch: Carry forward the previous average without checking the operative calculation policy.

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

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

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

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

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

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

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

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

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

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

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

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

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


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-008' AND decision_code='ISSUE_LEVERAGE_TREND_VIEW'

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

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

grow: escalated from business_brief/brief-caterpillar (haiku passed 2/2 -> too_easy). Escalations: per-year ratio fields, leverage classification requires reading the credit policy bands, walk 8->10.

Prompt:
**Robin Vale · Treasury · email, Tue 07:55**

Show Caterpillar's leverage year by year and explain the trend Credit should use, not just the average.

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.

Question: finance case work item

Question: finance case work item

FINCASE-008 completed — ISSUE_LEVERAGE_TREND_VIEW

Question: finance case work item

Resolve immutable work item FINCASE-008 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 each annual debt and equity fact by period, scale, and taxonomy, then check internal exposure separately.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-008-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-008-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 three annual ratios reveal the direction and dispersion that the average alone conceals.

Reject the unsupported branch: Report only the latest ratio or blend facts from different fiscal periods.

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

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

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

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

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

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

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

deterministic answer check: contains_all

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

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

Report only the latest ratio or blend facts from different fiscal periods.


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-009' AND decision_code='ISSUE_AMD_COUNTERPARTY_SNAPSHOT'

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

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

clone of microsoft/FinanceBenchmark business_brief item business_brief-007 (Advanced Micro Devices Inc); the JUDGEMENT is ported and FB's DSPy LLM-judge prose scoring is dropped per docs/INGESTION.md judgement_port. Figures recomputed from the frozen SEC XBRL snapshot; the internal_ar_relationship field is this world's addition — it is answerable only from the ERP, not the filings (scale/profitability @ 2025-12-27 (10-K); 3yr avg long-term D/E; no internal exposure (trap))

Prompt:
**Robin Vale · Treasury · email**

Prepare the AMD counterparty snapshot for the committee and flag what our internal relationship changes about the conclusion.

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-009 completed — ISSUE_AMD_COUNTERPARTY_SNAPSHOT

Question: finance case work item

Resolve immutable work item FINCASE-009 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 registrant, select same-period revenue, income, debt, and equity facts, and reconcile the name against internal masters.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-009-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-009-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 public ratios and internal exposure are separate evidence legs and both are required for the committee view.

Reject the unsupported branch: Assume a public-company name match proves an internal customer or vendor relationship.

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

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

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

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

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

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

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

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


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

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

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-010' AND decision_code='ISSUE_AAL_COUNTERPARTY_SNAPSHOT'

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

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

clone of microsoft/FinanceBenchmark business_brief item business_brief-158 (American Airlines Group); the JUDGEMENT is ported and FB's DSPy LLM-judge prose scoring is dropped per docs/INGESTION.md judgement_port. Figures recomputed from the frozen SEC XBRL snapshot; the internal_ar_relationship field is this world's addition — it is answerable only from the ERP, not the filings (scale/profitability @ 2025-12-31 (10-K); 3yr avg long-term D/E; internal exposure BRF-20 = 42132)

Prompt:
**Robin Vale · Treasury · email**

Give Treasury the American Airlines scale, profitability, and leverage picture on one comparable basis.

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-010 completed — ISSUE_AAL_COUNTERPARTY_SNAPSHOT

Question: finance case work item

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

Correlate registrant identity, fiscal period, units, debt definition, equity definition, and internal customer or vendor 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-010 and use its current subject and status as the scope anchor.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Read A1:F3 from fincase-010-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-010-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 same-basis annual filing facts produce a defensible ratio set; internal exposure is determined independently.

Reject the unsupported branch: Mix quarterly and annual facts or infer internal exposure from the issuer name.

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

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

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

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

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

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

deterministic answer check: contains_all

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

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

Mix quarterly and annual facts or infer internal exposure from the issuer name.