Skip to content

01 · Record

Record.

Borrower, co-borrower, employment, income, documents, conditions and your Rules, joined in one typed record. Every fact cites its page, and every change has an owner.

On the LOS or LMS you already run · or on ours

  • Borrower
  • Employment
  • Co-borrower
  • Documents
  • Conditions
  • Income
  • Rules
  • Decision

One record

Everything about the file, joined.

Not a folder of PDFs and a spreadsheet beside it. Each party, document, condition and rule is a typed part of the record, linked to the others, so every Agent and every person works from the same facts.

  • Borrower
  • Co-borrower
  • Employment
  • Income
  • Document
  • Condition
  • Rule
  • Decision
Record · PL-0001Personal loan
  • BorrowerSynthetic applicant1/1 verified
  • Co-borrowerJoint applicant1/1 verified
  • DocumentsPay stubs, statements, ID6/8 cited
  • ConditionsFrom your credit policy7/9 cleared
  • IncomeFrom pay stubs and statements2/2 verified
  • RulesYour credit policy24/24 applied

Synthetic file · one record, every part linked

The ontology

A lending ontology underneath.

Every kind of thing on a loan file, and every relationship between them, is defined once: a borrower provides a document, the document proves income, income satisfies a condition, a rule requires it. Agents and your team work from the same definitions, so a fact found once lands in the right place everywhere.

  • Borrower employed by Employment
  • Borrower earns Income
  • Borrower joint with Co-borrower
  • Document proves Income
  • Employment pays Income
  • Account receives Income
  • Document statement of Account
  • Income satisfies Condition
  • Rule requires Condition
  • Rule reads Document
  • Condition gates Decision
  • Example: a pay stub proves monthly income, which satisfies condition C-03, which gates the decision.

Who may change what

Proposing, checking, signing and writing are separate jobs.

Agents propose. The AI Reviewer checks. A person signs at the HITL Gate. Only then does an Integration make the one write, with its undo registered first.

Who may change what on the Record
RoleCanCan't
AgentReads the file and proposes, with a citationWrite to the record
AI ReviewerChecks each claim against the cited pageSee the Agent's reasoning
ApproverSigns at the HITL Gate, with a noteSkip the evidence
IntegrationMakes the one write, undo firstWrite anything unsigned

Citations

Every fact cites its page.

When an Agent reads a bank statement it records the value, the document and the page. Your team clicks through to the line it came from, and the AI Reviewer checks the same line before anyone signs.

Synthetic example · the record and the page it cites

FAQs

Questions about the Record

All questions
What is the Record?

The Record is one typed record of the loan: every party, document, rule, condition, and decision, joined by the lending ontology. Every fact on it cites the page it came from, so anyone can check it. Agents propose changes to it; only a signed change is written.

What does the AI Reviewer do?

The AI Reviewer is a second model that checks the Agent's work. It sees the claim and the cited page, never the Agent's reasoning, and says whether the page supports the claim. Anything it can't confirm goes to a person.

One claim, checked
  1. Agent cites the page
  2. AI Reviewer reads the same page
  3. Supported, or to a person
How is every run audited?

Every step of every run lands on the Audit log: what was read, what was cited, what the AI Reviewer said, who signed, and what was written. Each entry is hash-chained to the one before, so the log shows if anything was changed. You can show it to your team, your auditors, and your examiners.

Audit log entries for one write, each hash-linked to the last
  1. Run started
  2. Write intent
  3. Undo registered
  4. Write committed
  5. File check
Is my data secure with TaskSuite?

Yes. TaskSuite encrypts data at rest and in transit and uses role-based access control. Agents can't write to your systems: one integration makes each signed write, with its undo registered first. Each run is pinned to its workflow, citations are checked, and secrets come from the environment, never from the code.

See one of your loan files as a record.

We'll load a sample file into the Record and walk your team through every cited fact.