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 Take application
- 2 Underwrite
- Risk grading is independent
- 3 Check authority
- 4 Decide
- Decision requires completed underwriting
- Approval within delegated authority
- 5 Fund facility
- Funding is operations
- 6 Recalculate exposure
- 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.
- 1Take applicationCapture the request, the purpose, and the borrower’s existing relationship.
- 2UnderwriteSpread the financials, compute coverage, grade the risk, and recommend.
- 3Check authorityResolve who may decide this amount at this risk grade before it goes anywhere.
- 4DecideApprove, approve with conditions, or decline — inside the resolved authority.
- 5Fund facilityBook the facility, satisfy conditions precedent, and disburse.
- 6Recalculate exposureUpdate borrower and sector exposure, and flag anything now over limit.
Owned end to end by Chief Credit Officer.
SOP / runbook
The same process as a numbered operating procedure.
- 1. Take applicationCapture the request, the purpose, and the borrower’s existing relationship.Performed by Relationship Manager
- 2. UnderwriteSpread the financials, compute coverage, grade the risk, and recommend.Performed by Credit Analyst
- 3. Check authorityResolve who may decide this amount at this risk grade before it goes anywhere.Performed by Credit Analyst
- 4. DecideApprove, approve with conditions, or decline — inside the resolved authority.Performed by Credit Committee Chair
- 5. Fund facilityBook the facility, satisfy conditions precedent, and disburse.Performed by Loan Operations Specialist
- 6. Recalculate exposureUpdate 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 OfficerOwns the credit policy and the delegation grid.
- Credit Committee ChairDecides anything above delegated authority.Decide
- Relationship ManagerOwns the borrower and brings the request.Take application
- Credit AnalystSpreads the financials and grades the risk.UnderwriteCheck authority
- Loan Operations SpecialistBooks, 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.
| Step | Chief Credit Officer | Credit Committee Chair | Relationship Manager | Credit Analyst | Loan Operations Specialist |
|---|---|---|---|---|---|
| Take application | A | R | |||
| Underwrite | A | C | R | ||
| Check authority | A | R | |||
| Decide | A | R | C | ||
| Fund facility | A | R | |||
| Recalculate exposure | A | R |
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.
- Approval within delegated authority access
Only the committee decides — the relationship manager who sourced the deal never approves it.
- Funding is operations access
Money moves through operations, not through the people who sold or approved the deal.
- Risk grading is independent access
The grade is set by analysis, independent of the relationship it might disappoint.
- Exposure limits are the credit officers access
Concentration is a portfolio question, so it sits with the portfolio owner.
Product
What gets built on top of it — the data, the screens, the API.
Data model
The entities, their fields, and how they relate.
SubmitDecideListA 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
UnderwriteThe 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
FundMonitorAn 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
ReadThe 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
RecalculateAggregate 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/credit-files/:id/authority/facilitiesExample UI
A working admin table and detail form, built from the fields.
| Ref | Borrower | Amount ($K) | Purpose | Status |
|---|---|---|---|---|
| KF-2291 | Harbor Machine Works | 1450 | equipment | underwriting |
| KF-2292 | Delta Grain Co-op | 3200 | working-capital | approved |
| KF-2293 | Fairlane Properties | 8750 | real-estate | submitted |
| KF-2288 | Union Freight | 620 | refinance | funded |
API surface
The endpoints, grouped by namespace, with their operations.
/api/lendingOrigination, underwriting, and servicing operations.
- GET
/api/lending/applicationsApplication.List Origination pipeline. - POST
/api/lending/applicationsApplication.Submit Open a credit file. - POST
/api/lending/applications/{id}/decideApplication.Decide Record a decision. - GET
/api/lending/credit-files/{id}CreditFile.Read The analysis. - GET
/api/lending/authorityApprovalAuthority.Read The delegation grid. - POST
/api/lending/facilities/{id}/fundFacility.Fund Disburse a facility. - GET
/api/lending/facilities/{id}/covenantsFacility.Monitor Covenant state.
Technology
Where it runs and who can reach it.
Architecture diagram
The cells this runs on and what talks to what.
KeystoneFinancial.Product.WebKeystoneFinancial.Product.ApiKeystoneFinancial.OperationalKeystoneFinancial.Product.ApiKeystoneFinancial.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.
Access-control matrix
Which role may perform which operation, derived not declared.
| Operation | Chief Credit Officer | Credit Committee Chair | Relationship Manager | Credit Analyst | Loan Operations Specialist |
|---|---|---|---|---|---|
Application.DecideApproval within delegated authority | ✓ | ✓ | |||
CreditFile.UnderwriteRisk grading is independent | ✓ | ✓ | |||
Facility.FundFunding is operations | ✓ | ||||
Exposure.RecalculateExposure limits are the credit officers | ✓ | ✓ |
Application.SubmitApplication.ListCreditFile.ReadApprovalAuthority.ReadFacility.MonitorDerived, 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. Download the template
The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.
Download Keystone Financial as JSON2. 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. Join the waitlist
The hosted product runs your model for your team and your agents.