COASE MCP Knowledge Layer

Institutional knowledge architecture for deterministic corporate finance modelling

  • 29services
  • 5practices
  • 10knowledge domains
  • 3source tiers
  • 4approval gates

01Purpose

Architectural purpose and scope

Generative AI is probabilistic. Institutional corporate finance requires deterministic modelling logic, verifiable provenance and reproducible audit trails.

The COASE Knowledge Layer (KL) is the versioned engineering repository underpinning all COASE financial modelling, advisory and recurring Fractional FP&A engagements. It operates as an indirect control plane: it codifies the firm’s authoritative accounting, valuation, financial and procedural logic without autonomously populating client models or issuing deliverables. Numerical execution remains exclusively within controlled calculation engines and financial models; professional judgement and sign-off remain with the responsible Partner.

SOURCES → KNOWLEDGE LAYER → MODEL, VIA MCP

Utility gate

A knowledge object enters the KL only if it maps directly to one of two node types.

Modelling Logic Node

A model driver or line-item behaviour

Its exact impact on financial statement line items, cash flows and balance-sheet integrity is formally specified.

Procedural & Governance Node

A verifiable advisory control, data request or deliverable requirement

Its control or deliverable criterion is unambiguously testable.

02Assurance

Institutional assurance framework

Five risk dimensions and the mechanism that controls each. The sections that follow document how every control is implemented.

  1. Calculation integrity

    Zero AI arithmetic

    Financial computations, ratio reconciliations and balance-sheet checks execute exclusively within controlled financial models and external deterministic calculation services. AI is strictly bounded to retrieval, comparison and structured drafting.

    05 MCP interface →
  2. Source provenance

    Paragraph-level traceability

    Every modelling rule and technical treatment is bound to an indexed primary source, with exact edition, effective date and paragraph anchors.

    03 Architecture →
  3. Data confidentiality

    Physical data segregation

    Client financials, credit files and contractual terms reside in isolated, access-controlled Engagement Workspaces that reference immutable KL snapshots through read-only pointers.

    03 Architecture →
  4. Audit reproducibility

    Bitemporal versioning

    Every rule tracks both the legal or accounting regime in force at the valuation date and the approved KL release. Any historical business plan, valuation or debt sustainability analysis can be reconstructed.

    04 Ontology →
  5. Governance & sign-off

    Mandatory Partner gate

    Draft content carries zero evidential weight and is invisible to engagement workflows. Production release requires automated schema validation, non-contradiction checks and audit-logged Partner approval.

    06 Governance →

03Architecture

System architecture and data boundary

The ecosystem enforces a strict architectural separation between the shared institutional knowledge base and client-specific execution environments.

Knowledge LayerShared · immutable releases
Component 1

Source Library

Catalogues institutional primary sources across three tiers. Each source is indexed with edition metadata, effective dates and paragraph-level anchors. Full-text indexed sources support verbatim passage binding; citation-only sources are flagged as non-binding until full-text ingestion is completed.

Component 2

Professional Knowledge

Stores atomic, reusable definitions, modelling rules, contextual accounting treatments, management-versus-contractual metric variants, review procedures and audit checklists across ten domains.

  • Financial Data
  • Planning
  • Treasury
  • Debt
  • Valuation
  • Transactions
  • Equity
  • Restructuring
  • Accounting & Regulatory Context
  • Model Quality
Component 3

Data & Benchmarks

Maintains structured numerical observations tagged with source provenance, observation period, geography, peer population, units and licensing or permitted use. Inclusion in any engagement requires an explicit comparability and relevance sign-off.

Component 4

Service Views

Exposes curated graph traversals for each of the 29 services, assembling the exact sequence of required data requests, analytical methodologies, modelling rules, quality checks and deliverable specifications.

CatalogueBrowse the 29 services

Read-only pointers to immutable KL release snapshots

No client data ingested, indexed or written back

Execution layerSegregated · client-isolated
Component 5

Engagement Workspaces

Physically and logically isolated, access-controlled workspaces holding client enterprise data, contractual definitions, engagement assumptions and deliverable drafts. Workspaces reference immutable KL release snapshots through read-only pointers.

Client data is never ingested into, indexed by, or written back to the KL.

Source Library: three tiers

Every modelling rule and technical treatment is bound to its primary source by edition, effective date and paragraph anchor.

Extract of sources processed ↗

Tier 3

Market evidence

The empirical sources used to calibrate assumptions. Examples include ECB yield curves, FRED time series and Damodaran datasets.

SourcesData, markets and benchmarks

04Ontology

Ontology, Cell taxonomy and bitemporal versioning

The KL is structured as a typed knowledge graph governed by a formal ontology. Entities are linked through directed, typed relationships, each carrying provenance metadata and review status.

Entities

  • Sources
  • Paragraphs
  • Metrics
  • Treatments
  • Modelling Rules
  • Controls
  • Benchmarks
  • Services

Typed relationships

  • SUPPORTED_BY
  • GOVERNS_LINE_ITEM
  • APPLIES_TO
  • DEPENDS_ON
  • SUPERSEDES
  • VALIDATED_BY

The Cell as the unit of development

Institutional disputes frequently arise from definitional drift between financial statements, management plans and credit agreements. The KL addresses it by engineering knowledge in Cells: the atomic intersection of four coordinates.

Coordinate 1

Financial aggregate or line item

Examples
  • Net Financial Position
  • EBITDA
  • Deferred Tax Assets
  • DSCR
Coordinate 2

Jurisdiction and accounting framework

Examples
  • Italy / OIC
  • EU / IFRS
Coordinate 3

Metric variant

Three variants
  • Statutory
  • Management / Adjusted
  • Contractual / Covenant
Coordinate 4

Service context

Mapped across
  • 10 domains
  • 29 services

ResultCodifying by Cell guarantees cross-domain consistency: a single financial aggregate’s accounting treatment, cash-flow impact, covenant sensitivity and audit check are resolved simultaneously rather than in silos.

Bitemporal control and impact analysis

Every node and relationship maintains two time dimensions. Together they support two operational guarantees.

Time dimension

Effective time

The period during which a statute, accounting standard or market rule is legally or technically in force.

Time dimension

Release version

The immutable KL release tag under which the node was approved.

Guarantee

Historical reproducibility

Any past valuation, restructuring plan or model audit can be reconstructed using the exact KL release and statutory regime in force at the original valuation date.

Guarantee

Automated impact analysis

When a primary source is revised or superseded, graph traversal immediately flags every dependent Modelling Logic Node, Service View and active Engagement Workspace affected by the change.

05MCP interface

MCP interface and retrieval architecture

The KL operates as a versioned knowledge service exposed to authorised host applications through a Model Context Protocol (MCP) server. Interoperability is standardised across three primitives.

MCP Resources

Read-only context

Stable, versioned URIs exposing approved nodes, paragraph-level source excerpts, metric definitions and Service Views.

MCP Tools

Typed execution

Schema-validated endpoints for hybrid retrieval, impact analysis, citation verification and delegation to external deterministic calculation services: model checks, ratio reconciliations and formula validation.

MCP Prompts

Constrained workflows

Pre-configured, auditable prompt templates for comparative treatment analysis, gap identification and technical drafting within approved boundaries.

Pre-retrieval governance and hybrid GraphRAG

Security and governance are never delegated to prompt instructions. Hard filters are enforced at the server layer before any token enters the language model context window.

  1. Step 1 · before retrieval

    Hard pre-retrieval filters

    • Access controlEngagement-level permissions
    • Approval statusAPPROVED only for production engagements
    • Jurisdiction
    • Accounting framework
    • Effective date
  2. Step 2 · context assembly

    Hybrid retrieval

    • Structured metadata filtering
    • Lexical search
    • Dense vector retrieval
    • GraphRAG multi-hop traversal
  3. Step 3 · language model

    Bounded AI scope

    • Structured retrieval
    • Cross-framework comparison
    • Technical drafting
    • No arithmeticDelegated to deterministic calculation services
  4. Step 4 · every response

    Structured evidence payload

    • Node and KL release identifiers
    • Exact source edition and paragraph-level citations
    • Explicit applicability conditions and boundary constraints
    • Surfaced gaps, missing evidence or unresolved modelling assumptions

06Governance

Governance, validation protocol and AI controls

Nodes follow a strict state machine. Draft nodes carry zero evidential weight, are invisible to engagement queries and cannot support client deliverables.

  1. DRAFT

    Zero evidential weight. Excluded from production queries.

  2. SCHEMA_VALIDATED

    Automated checks cleared. Excluded from production queries.

  3. APPROVED

    The only state that production engagements can query.

  4. DEPRECATED

    Excluded from production queries.

Promotion gate

A node is promoted to APPROVED only when four mandatory gates are cleared.

Gate 1

Functional and mathematical definition

For Modelling Logic Nodes, the exact impact on financial statement line items, cash flows and balance-sheet integrity is formally specified. For Procedural Nodes, the control or deliverable criterion is unambiguously testable.

Gate 2

Paragraph-level provenance

Every normative or technical claim is bound to a verified source identifier and paragraph anchor.

Gate 3

Deterministic validation

Automated checks verify ontology compliance (schema and relationship constraints), bitemporal metadata completeness and non-contradiction with existing approved nodes.

Gate 4

Partner sign-off

Direct, audit-logged approval by a responsible Partner.

Segmented AI task allocation

LLM usage within the KL engineering pipeline is strictly tiered and bounded, to exclude full-document hallucination and uncontrolled drift.

Small / fast models

Ingestion

Automated metadata tagging, taxonomy classification and structural segmentation during ingestion.

Mid-tier models

Drafting

Initial drafting of atomic nodes and relationship proposals, strictly from paragraph-level extracts.

Frontier models

Alignment and audit

Complex ontology alignment, cross-framework comparative checks such as OIC versus IFRS deltas, and pre-review consistency audits.

RuleLLMs operate exclusively on segmented, paragraph-level extracts, never on unparsed full documents. All AI-generated artefacts remain non-authoritative until cleared by deterministic validation and Partner approval.

Security and audit trail

Every MCP request is authenticated against engagement-level permissions. Immutable audit logs record what backs each engagement output, ensuring full inspectability for internal review, statutory auditors and institutional counterparties.

Logged for each engagement output

  • KL release version
  • Retrieved node IDs
  • Query filters
  • Tool invocations
  • External calculation service versions

07Use cases

Where the intersections matter

The critical work sits between disciplines: a treatment that is valid in one context can distort another. These composite mandate scenarios illustrate the dependency structures the KL is designed to support.

Cross-border M&A

One acquisition. Four financial perimeters.

OIC–IFRS conversion, purchase price allocation and acquisition financing.

Accounting · Valuation · Tax · Debt

An IFRS buyer acquires an OIC industrial group with capitalised development expenditure, material leases and a financing agreement using its own EBITDA and net-debt definitions.

Knowledge intersection

OIC–IFRS bridge · IAS 38 development criteria · IFRS 16 lease measurement · IFRS 3 allocation · IAS 12 tax bases · valuation methodology · SPA and financing definitions.

Coupled model effects

Link the conversion bridge to comparable EBITDA and enterprise value, identifiable net assets and goodwill, deferred tax, the equity purchase-price bridge and post-deal covenant capacity.

Consistency constraint

A lease treatment must remain coherent across earnings, multiples, debt deductions and contractual ratios. Acquisition accounting, price mechanics and covenant definitions require separate bindings.

Decision outputReconciled acquisition model with traceable valuation, purchase-price and financing sensitivities.

Distressed refinancing

A debt solution. Across cash, earnings and capital.

Conditional debt relief, repayment restructuring and downside viability.

Liquidity · Insolvency · Tax · Accounting

A distressed group negotiates tax-debt relief and lender rescheduling while its short-term liquidity depends on delayed supplier payments and uncertain collections. The plan also supports asset carrying values.

Knowledge intersection

CCII procedural conditions · OIC 19 debt accounting · applicable tax treatment · OIC 9 impairment · corporate-capital constraints · creditor terms · treasury and covenant methodology.

Coupled model effects

Bind legal effectiveness and creditor conditions to debt recognition, tax effects and repayment schedules. Reconcile the 13-week forecast with the integrated plan, debt-service coverage, impairment sensitivities and equity movements.

Consistency constraint

Negotiated relief, accounting recognition and cash settlement have distinct triggers. Viability must remain testable when relief is delayed, collections deteriorate or deferred supplier payments unwind.

Decision outputConditional restructuring scenarios connecting liquidity, capital requirements and financing feasibility.

Industrial carve-out

Reported margin. Standalone economics.

Inventory absorption, capitalised revamping, separation costs and debt capacity.

Operations · Accounting · Tax · Transactions

An industrial division shows margin expansion despite flat sales. The perimeter includes accumulated inventory, capitalised revamping, a claimed tax incentive, shared infrastructure and a post-separation investment programme.

Knowledge intersection

OIC 13 inventory measurement · OIC 16 or IAS 16 asset criteria · incentive eligibility evidence · production and cost-allocation methods · carve-out perimeter · valuation and financing definitions.

Coupled model effects

Connect production volumes and absorbed costs to earnings quality; capitalisation and incentive evidence to asset and cash adjustments; separation assumptions to standalone margins, working capital, capex and debt service.

Consistency constraint

The same adjustment can affect EBITDA, inventory, tax, investment needs and the equity bridge. Every effect must be assigned to the correct perimeter and period without duplication.

Decision outputStandalone operating and financing model linking earnings quality to valuation and capital requirements.

Composite scenarios for illustration. They are not results of actual engagements.

08Engine Tools

Engine Tools

Our proprietary tools automate time-consuming tasks and high-volume workloads across data preparation, model construction and reporting.

  • MIES
  • MA LAYERS
  • TANGE
  • BOOLE
  • NERVI
  • PIANO
Open the tools ↗

09FAQ

Technical FAQ

For IT security, compliance and model risk management teams.

Q1

Does client financial data ever enter the Knowledge Layer, get indexed in the knowledge graph, or get used to train external LLMs?

No. The architecture enforces a strict physical and logical boundary between the shared KL and client execution environments.

Zero ingestion

Client financials, credit files and contractual agreements reside exclusively in segregated, access-controlled Engagement Workspaces. They are never ingested into, indexed by, or written back to the KL.

Read-only reference

Engagement Workspaces query immutable KL release snapshots strictly through read-only pointers.

Zero training, ephemeral context

LLM inference operates under enterprise zero-data-retention terms. Models within the KL pipeline receive only segmented, paragraph-level excerpts of approved public or institutional sources, never full proprietary documents or unredacted client ledgers.

Q2

How do you prevent probabilistic LLM hallucinations from corrupting financial calculations, covenant tests or credit metrics?

By decoupling language processing from numerical execution. The KL enforces a Zero AI Arithmetic policy.

Deterministic execution

All financial computations, cash-flow reconciliations, balance-sheet integrity checks and ratio calculations execute exclusively inside controlled financial models and external deterministic calculation services invoked through typed MCP Tools.

Bounded AI scope

LLMs are restricted to structured retrieval, cross-framework comparison such as OIC versus IFRS deltas, and technical drafting strictly within pre-filtered, approved context.

Evidence payloads

Every output generated through the MCP server is required to return a structured evidence payload containing node IDs, KL release tags, exact paragraph-level source citations and explicitly surfaced assumptions. Claims without a bound source anchor are flagged as unsupported.

Q3

How are access permissions, approval states and regulatory boundaries enforced across the MCP server?

Through hard pre-retrieval filtering at the server layer. Security and governance are never delegated to prompt instructions.

Authentication and scope

Every MCP request is authenticated against engagement-level permissions before any query reaches the knowledge graph or vector store.

State isolation

Production engagements can exclusively query nodes in the APPROVED state. DRAFT, SCHEMA_VALIDATED and DEPRECATED nodes are excluded at the query-engine level and cannot enter the LLM context window.

Jurisdictional and temporal filtering

Jurisdiction, accounting framework (for example Italy / OIC or EU / IFRS) and effective date are applied as mandatory hard filters prior to GraphRAG traversal, preventing cross-regime contamination.

Q4

If a credit decision, valuation or restructuring plan is audited years later, can we reproduce the exact rules applied at that time?

Yes. The KL operates on a bitemporal versioning model paired with immutable audit logging.

Effective time

Every node records the exact period during which the underlying statute, accounting standard or market rule was legally or technically in force.

Release version

Every engagement pins its references to an immutable KL release tag.

Immutable audit trail

For every analytical step, the system logs the exact KL release version, retrieved node IDs, applied filters, MCP tool invocations and external calculation service versions. Statutory auditors, credit committees and regulators can reconstruct the exact normative and modelling logic in force on the original valuation date.

Q5

What happens when an accounting standard (OIC or IFRS), tax statute or regulatory guideline changes mid-engagement?

Graph-based impact analysis automatically flags affected logic and engagements.

Dependency traversal

Primary sources are linked to Modelling Logic Nodes, Service Views and active Engagement Workspaces through typed graph relationships (SUPPORTED_BY, DEPENDS_ON, SUPERSEDES). Updating or deprecating a source paragraph triggers an automated dependency traversal.

No silent overwrite

Every impacted modelling rule is flagged for review and re-validation, and active engagements pinned to the superseded rule receive an explicit change alert. Existing engagement snapshots are never silently overwritten; migrating an active engagement to a new KL release requires explicit Partner authorisation.

Q6

What is the operational and legal boundary between AI-assisted outputs and Partner accountability?

AI has zero signing authority. The KL operates strictly as an indirect control plane.

Mandatory Partner gate

No rule, accounting treatment or procedural check enters production in the KL without passing automated schema and non-contradiction validation, followed by audit-logged Partner sign-off.

Client deliverables

AI assists in locating authoritative treatments, checking consistency and surfacing missing evidence. Professional judgement, interpretation of contractual edge cases and final sign-off on all client models and deliverables remain exclusively with the responsible COASE Partner.

Further technical questions: [email protected]

Knowledge LayerContact

The method behind the work.

The Knowledge Layer underpins how COASE develops financial models, analysis and reporting for each assignment.