Template-defined structure
Sections, per-section analytical intents, regulatory domain coverage, and plain-language mandates come from your program's memo template - versioned, and snapshotted when a project memo is created.
§ Platform - CORE Programs
CORE Programs: program-by-program automation, human-in-the-loop.
There is no fixed memo. Your program defines its own memo templates - sections, analytical intents, regulatory domain coverage, section mandates, output structure - and CORE routes each section through the right specialist, evidence package, program rules, and review path before it becomes memo language. The model proposes; the analyst accepts, edits, or rejects under cite-or-decline controls.
The section determines the team, the evidence, and the rules.
A repayment section, collateral section, eligibility section, and risk section should not be drafted by the same undifferentiated AI call. CORE assembles the support package at runtime: accepted facts, source files, prior sections, internal credit policy, platform regulatory context, section mandate, and writing standards. The analyst assembles the evidence; the receipt proves what the model saw.
Section -> analyst pair -> policy + regulatory support -> proposal§ Program Controls
What happens before a sentence is proposed.
Locked or flexible, heading by heading
Every heading in the template is individually locked or flexible. Lock the outline, or let the model expand it - heading by heading, the analyst decides where model judgment is permitted.
Analyst + supervisor pair
Each program can route section work to a specialist analyst and supervisor pattern, so drafting and review follow the credit shop's operating model.
Credit policy agent
CORE brings the tenant's underwriting program, covenants, thresholds, risk weights, and credit-policy overlay into the section package.
Regulatory agent
The platform regulatory layer retrieves the dated rule chunks that belong to the section's intent, with citations preserved.
Runtime support package
The draft receives evidence, tables, policy context, regulatory context, prior sections, analyst notes, and the section mandate.
Analyst-owned proposal
The model proposes memo language. The analyst accepts, edits, or rejects it before it becomes the memo record.
Generation trace
Routing, inputs, model, prompt package, output, proposal, and human decision are preserved so the work can be replayed later. Risk evaluates the policy; the memo inherits the result - it cannot recalculate its way around it.
§ Fit
One judgment engine. Any credit program.
Conventional, private credit, government-guaranteed, or specialty: each program configures its own evidence, policy, analysis, reviewers, and outputs without rebuilding the platform.
01
Section-level routing by program, analytical intent, evidence need, and reviewer role
02
Configurable analyst and supervisor review patterns for each credit program
03
Tenant credit policy support for thresholds, covenants, scorecards, exceptions, overlays, and risk weights
04
Optional regulatory and program-rule context, with dated source material and citations preserved
05
Accepted facts, source files, tables, prior decisions, and analyst notes assembled for generation
06
Multiple memo and deliverable templates under one borrower file
07
Generation receipts preserving the evidence package, policy, model, proposal, and human action
08
Risk decisions carry into the memo instead of being rediscovered or overridden during generation
§ Path
How a memo section moves
Lock the section
The analyst chooses the section, evidence set, instructions, and review mode before generation starts.
Summon the support
CORE resolves the analyst pair, credit policy context, regulatory context, evidence, prior sections, and section mandate.
Draft the proposal
The generation engine drafts from scoped evidence, policy rules, and cited regulations. Large evidence packs are planned and chunked instead of silently dropping files.
Review and roll up
The analyst accepts, edits, or rejects the proposal. Supervisor review can then pressure-test the memo across sections.
§ Next Step
Bring the section your team hates drafting.
We will show how CORE routes it, grounds it, reviews it, and keeps the decision trail intact.