PlaygroundFinancial services

Keystone Financial

Fictional companyFinancial services

A commercial lender running origination through servicing under delegated approval authority and exposure limits.

Modeled on

  • FIBO: Financial Industry Business Ontology — facility, obligor, and exposure concepts.
  • BIAN: Service domains — Credit Facility, Credit Decisioning, Collateral Administration.
  • Basel III: PD, LGD, EAD, and risk-weighted assets on the credit file and exposure.
  • ISO 20022: Payment instruction message types for disbursement.

The genome map

Roles in their reporting line, the process step by step with the role on each step, the rules on the steps they govern, and the resources the work acts on. Select a role to see what it reaches.

Roles Select a role to see its reach.

Credit Origination Operated by Chief Credit Officer

Request through funding, with the approval authority checked before anyone decides.

  1. 1 Take application Relationship ManagerApplication.Submit
  2. 2 Underwrite Credit AnalystCreditFile.Underwrite
    • Risk grading is independent
  3. 3 Check authority Credit AnalystApprovalAuthority.Read
  4. 4 Decide Credit Committee ChairApplication.Decide
    • Decision requires completed underwriting
    • Approval within delegated authority
  5. 5 Fund facility Loan Operations SpecialistFacility.Fund
    • Funding is operations
  6. 6 Recalculate exposure Loan Operations SpecialistExposure.Recalculate
    • Exposure limits are the credit officers

Resources

  • Application
  • Credit File
  • Facility
  • Approval Authority
  • Exposure

Three questions this genome answers

Each answer comes from the compiled genome alone. Pick another subject and the answer changes in place.

Chief Credit Officer, Credit Committee Chair may perform Application.Decide. The rule: Decision requires completed underwriting; Approval within delegated authority.

These steps wait for Credit Analyst:

  • Underwrite Credit Origination
  • Check authority Credit Origination

Chief Credit Officer, Credit Committee Chair, Relationship Manager act on Application, by a process step or under an access rule.

Every artifact from one genome

The same derivations and renderers the Playground runs, here for Keystone Financial at build time. Open it in the Playground to pick your own set.

Operations

How the work actually runs — who owns what, in what order, under which rules.

Process flow

The end-to-end sequence, each step with its owner.

Request through funding, with the approval authority checked before anyone decides.

  1. 1
    Take application
    Capture the request, the purpose, and the borrower’s existing relationship.
    Relationship ManagerApplication.Submit
  2. 2
    Underwrite
    Spread the financials, compute coverage, grade the risk, and recommend.
    Credit AnalystCreditFile.Underwrite
  3. 3
    Check authority
    Resolve who may decide this amount at this risk grade before it goes anywhere.
    Credit AnalystApprovalAuthority.Read
  4. 4
    Decide
    Approve, approve with conditions, or decline — inside the resolved authority.
    Credit Committee ChairApplication.Decide
  5. 5
    Fund facility
    Book the facility, satisfy conditions precedent, and disburse.
    Loan Operations SpecialistFacility.Fund
  6. 6
    Recalculate exposure
    Update borrower and sector exposure, and flag anything now over limit.
    Loan Operations SpecialistExposure.Recalculate

Owned end to end by Chief Credit Officer.

SOP / runbook

The same process as a numbered operating procedure.

PurposeRequest through funding, with the approval authority checked before anyone decides.
OwnerChief Credit Officer
TriggerA relationship manager submits a request.
  1. 1. Take application
    Capture the request, the purpose, and the borrower’s existing relationship.
    Performed by Relationship Manager
  2. 2. Underwrite
    Spread the financials, compute coverage, grade the risk, and recommend.
    Performed by Credit Analyst
  3. 3. Check authority
    Resolve who may decide this amount at this risk grade before it goes anywhere.
    Performed by Credit Analyst
  4. 4. Decide
    Approve, approve with conditions, or decline — inside the resolved authority.
    Performed by Credit Committee Chair
  5. 5. Fund facility
    Book the facility, satisfy conditions precedent, and disburse.
    Performed by Loan Operations Specialist
  6. 6. Recalculate exposure
    Update borrower and sector exposure, and flag anything now over limit.
    Performed by Loan Operations Specialist

Key positions

The roles this operation needs and who reports to whom.

Credit Committee

  • Chief Credit Officer
    Owns the credit policy and the delegation grid.
    • Credit Committee Chair
      Decides anything above delegated authority.
      Decide
    • Relationship Manager
      Owns the borrower and brings the request.
      Take application
    • Credit Analyst
      Spreads the financials and grades the risk.
      UnderwriteCheck authority
    • Loan Operations Specialist
      Books, funds, and services the facility.
      Fund facilityRecalculate exposure

Each chip is a step of the process that role owns.

RACI matrix

Every step against every role — responsible, accountable, consulted.

StepChief Credit OfficerCredit Committee ChairRelationship ManagerCredit AnalystLoan Operations Specialist
Take applicationAR
UnderwriteACR
Check authorityAR
DecideARC
Fund facilityAR
Recalculate exposureAR

R responsible · A accountable · C consulted — derived from step owners, the process operator, and access rules.

Policies & rules

The constraints that govern each operation, stated as rules.

  • Decision requires completed underwriting condition

    Nothing is decided before the credit file carries a risk grade and a recommendation.

    Application.Decide
  • Approval within delegated authority access

    Only the committee decides — the relationship manager who sourced the deal never approves it.

    Application.Decide Credit Committee ChairChief Credit Officer
  • Funding is operations access

    Money moves through operations, not through the people who sold or approved the deal.

    Facility.Fund Loan Operations Specialist
  • Risk grading is independent access

    The grade is set by analysis, independent of the relationship it might disappoint.

    CreditFile.Underwrite Credit AnalystChief Credit Officer
  • Exposure limits are the credit officers access

    Concentration is a portfolio question, so it sits with the portfolio owner.

    Exposure.Recalculate Loan Operations SpecialistChief Credit Officer

Product

What gets built on top of it — the data, the screens, the API.

Data model

The entities, their fields, and how they relate.

Application SubmitDecideList

A credit request from a borrower, from submission through decision.

  • reference string required
  • amount number required
  • purpose enum required working-capital · equipment · real-estate · refinance
  • status enum required submitted · underwriting · approved · declined · funded
Credit File Underwrite

The analysis behind a decision — spreads, ratios, and the recommendation.

  • riskGrade enum required 1 · 2 · 3 · 4 · 5 · 6
  • debtServiceCoverage number
  • probabilityOfDefault number
  • lossGivenDefault number
  • exposureAtDefault number
  • recommendation enum required approve · approve-with-conditions · decline
Facility FundMonitor

An approved credit line or loan, with its terms and covenants.

  • facilityType enum required term-loan · revolver · letter-of-credit
  • committedAmount number required
  • rate number
  • maturity date
Approval Authority Read

The delegation grid — which role may approve up to which amount and risk grade.

  • limit number required
  • maxRiskGrade enum required 1 · 2 · 3 · 4 · 5 · 6
  • requiresSecondSignature boolean
Exposure Recalculate

Aggregate committed and outstanding exposure to one borrower or sector.

  • committed number required
  • outstanding number required
  • riskWeightedAssets number
  • concentration enum required within-limit · watch · over-limit

Screen map

Every route and the page it resolves to.

Shell: LendingShell

/pipeline
Origination Pipeline 🔒
Origination pipeline.
Application tablesummary
/credit-files/:id
Credit File Detail 🔒
Credit file.
Credit File formactions
/authority
Authority Grid 🔒
Delegation grid.
Approval Authority table
/facilities
Facility Book 🔒
Facility book.
Facility actions

Example UI

A working admin table and detail form, built from the fields.

Origination Pipeline Decide
RefBorrowerAmount ($K)PurposeStatus
KF-2291Harbor Machine Works1450equipmentunderwriting
KF-2292Delta Grain Co-op3200working-capitalapproved
KF-2293Fairlane Properties8750real-estatesubmitted
KF-2288Union Freight620refinancefunded
Application detail

API surface

The endpoints, grouped by namespace, with their operations.

Lending/api/lending

Origination, underwriting, and servicing operations.

  • GET /api/lending/applications Application.List Origination pipeline.
  • POST /api/lending/applications Application.Submit Open a credit file.
  • POST /api/lending/applications/{id}/decide Application.Decide Record a decision.
  • GET /api/lending/credit-files/{id} CreditFile.Read The analysis.
  • GET /api/lending/authority ApprovalAuthority.Read The delegation grid.
  • POST /api/lending/facilities/{id}/fund Facility.Fund Disburse a facility.
  • GET /api/lending/facilities/{id}/covenants Facility.Monitor Covenant state.

Technology

Where it runs and who can reach it.

Architecture diagram

The cells this runs on and what talks to what.

LendingWeb
nextjs 15
Pipeline, credit file, and authority surfaces.
KeystoneFinancial.Product.Web
OriginationService
nestjs 10
Applications and decisions.
KeystoneFinancial.Product.Api
AuthorityService
express 4
Resolves delegated authority before any decision is written.
KeystoneFinancial.Operational
ServicingService
nestjs 10
Funding, covenants, and exposure.
KeystoneFinancial.Product.Api
LendingDb
postgres 16
Applications, files, facilities, exposure.
KeystoneFinancial.Product.Core
  • LendingWeb → OriginationService pipeline
  • OriginationService → AuthorityService authority check
  • OriginationService → ServicingService application.approved
  • ServicingService → LendingDb depends-on
  • OriginationService → LendingDb depends-on

Environment topology

Dev, staging, and production, with the providers behind each.

dev
Synthetic borrowers.
Providers
AzurecloudOracleExadatadatabase
Cells
none
staging
Core banking sandbox.
Providers
AzurecloudOracleExadatadatabasePingIdentityauth
Cells
none
prod
Live book.
Providers
AzurecloudOracleExadatadatabasePingIdentityauthSwiftmessaging
Cells
LendingWebOriginationServiceAuthorityServiceServicingServiceLendingDb

Access-control matrix

Which role may perform which operation, derived not declared.

OperationChief Credit OfficerCredit Committee ChairRelationship ManagerCredit AnalystLoan Operations Specialist
Application.DecideApproval within delegated authority✓✓
CreditFile.UnderwriteRisk grading is independent✓✓
Facility.FundFunding is operations✓
Exposure.RecalculateExposure limits are the credit officers✓✓
No access rule governs
Application.SubmitApplication.ListCreditFile.ReadApprovalAuthority.ReadFacility.Monitor

Derived, not declared — this is the list an audit asks about.

Make yours

Start from Keystone Financial and change what differs, or pick another company as your template. Three ways in:

  1. 1. Download the template

    The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.

    Download Keystone Financial as JSON
  2. 2. Start an agent from it

    Paste this into an agent that has the DNA MCP server connected. It drafts your model in the conversation and saves only when you ask.

    Use the DNA MCP server (https://agents.dna.codes) to help me model how my company works.
    Start from the Keystone Financial genome at https://dna.codes/genome/financial.json. It is an example company, not mine.
    Read its roles, process steps, rules and resources, then ask me how my company differs.
    Draft my company's operating model in this conversation, as structure/v1 and behaviour/v1 documents, and use `validate` on each draft.
    Do not save anything: call `apply` only when I ask you to save.
  3. 3. Join the waitlist

    The hosted product runs your model for your team and your agents.

Which of these sounds like you? Pick as many as apply.

The most useful box on this page. Rough is fine, and “nowhere, honestly” is a real answer and a common one.

We reply by hand, usually within a day. No sequence, no drip, no spam.