Skip to content
ARCHYTASAI

TASK-FIN-102-01 · Task family

Credit agreement & amendment interpretation. Document navigation, clause precedence and contractual definitions.

Custom buildenvironment · ENV-FIN-102 Credit & Covenantrole · Credit Analyst

Overview. Identify the provisions that govern the test date, with clause references, and flag any ambiguity.

A borrower's facility has been amended more than once. The agent has to work out which provisions apply on a given test date: the original terms, a time-limited amendment, or neither.

Amendments often change a definition and a threshold together, and only for some test dates. An unsigned draft in the repository has no effect.

Value to the buyer

Credit work turns on which clause applies. Trains precise reading across document versions.

Specification. The task family, field by field.

spec · task/task-fin-102-01.yamlENV-FIN-102
task_id:
TASK-FIN-102-01
domain:
Credit Analysis & Private Credit
parent_environment:
ENV-FIN-102 · Credit & Covenant
target_role:
Credit Analyst
objective:
Identify the provisions that govern the test date, with clause references, and flag any ambiguity.
starting_context:
The original credit agreement, two executed amendments, an unsigned draft third amendment and the test date.
tools:
  • search_credit_documents
  • get_agreement
  • get_amendments
  • extract_covenant_terms
  • submit_monitoring_report
required_actions:
  • List every executed amendment and its effective terms
  • Determine which apply on the test date
  • Extract the operative definitions and threshold
  • Exclude unsigned drafts and say so
expected_outputs:
  • A provisions memo with clause references
  • The operative threshold and definitions
  • Any ambiguity flagged
interaction:
Single agent with tool access.
verification:
The operative provisions are compared with the seeded ground truth for the test date.
reward:
Applying superseded or draft terms scores zero. Credit for each correct provision and reference.
difficulty:
Calibrated against reference models during acceptance testing
task_horizon:
Multi-step, long-document navigation. Execution limits are agreed with the buyer.
delivery:
Task instances with seeded document sets, reference memos and verifier code.
commercial_unit:
Per validated task instance

Sample prompt. What the agent is asked to do, as a buyer would see it.

prompt · task-fin-102-01Example
Northbridge Credit's 2024 credit agreement sets a maximum total net leverage ratio of 4.50× and caps EBITDA add-backs at 10% of EBITDA. Amendment No. 1 changed the permitted-acquisitions basket. Amendment No. 2, signed August 15, 2026, changes the add-back cap and the leverage threshold for certain test dates. A draft Amendment No. 3 is in the repository. Determine which provisions govern the September 30, 2026 test date and document them.

Verification criteria. What the verifier checks, and how.

  • Amendment No. 2 applies

    Its terms cover test dates from September 30, 2026 to June 30, 2027.

  • Threshold

    Maximum total net leverage of 5.00× for the test date.

  • Add-back cap

    15% of EBITDA before add-backs, per the amended definition.

  • Amendment No. 1 scoped

    Identified as not affecting the leverage covenant.

  • Draft excluded

    Amendment No. 3 is unsigned and has no effect.

  • References

    Each provision cites the document and section.

Key failure modes. Where agents go wrong on this task.

  • Applying the original 4.50× threshold
  • Applying the amended threshold but the original add-back cap
  • Treating the draft amendment as effective

Other task families. The rest of Credit & Covenant, on the same FinanceWorld state.

Every environment is built to order. Tell us which workflow you need to train or evaluate, and where you are in the process.

Request sample tasksDiscuss custom developmentRequest technical integration detailsSee ways to buy