Dartmouth Advisory Partners — Living Policy Architecture

DRAWING 003 · SHEET 03/07

How it runs — The Compiler Pipeline

Scale 1:1

Rev 2.0 · 2026-05-26

Dartmouth Advisory Partners

↓ Architecture detail in 003A · 003B · 003C · 003D

DRAWING 003A · SHEET 03/07

Platform Architecture

Scale 1:1

Rev 2.0 · 2026-05-26

Dartmouth Advisory Partners

↓human interpretation↓

↓signed PIS↓

↓compiles↓

· runtime ↓

· emitted artifacts ↓

· reads in place ↓

· CI/CD ingest ↓

Click any node for spec detail

DRAWING 003B · SHEET 03/07

Three Deployment Modes

Scale 1:1

Rev 2.0 · 2026-05-26

Dartmouth Advisory Partners

Mode A

DAP-hosted (API)

Fastest time to value

DAP Cloud

· Policy Compiler
· Runtime (Overture / FALCON / Resolve)
· LLM inference

↓ HTTPS API

Customer

· Data lake (replicated to DAP)

Mode B

Hybrid

Balanced cost & sovereignty

DAP Cloud

· Policy Compiler
· PIS template library + update channel

↓ API (light)

Customer VPC

· DAP Runtime
· Inference (API or local — customer choice)
· Customer data lake (in-place)
· Audit evidence store

Mode C

Full local

Maximum sovereignty & cost control

DAP Cloud (update channel only)

· Episodic: regulatory diffs, compiler updates, signed PIS templates

↓ light, episodic

Customer VPC (everything)

· Policy Compiler
· DAP Runtime
· Local LLM (Llama / Mistral / Qwen / fine-tune)
· Customer data lake
· Audit evidence store

What the customer pays

Mode A

Mode B

Mode C

Cost profile

Per-decision billed by DAP

Maint + light compute

Flat Maintenance only

Data sovereignty

Data replicated to DAP

Data stays in VPC

100% — data never leaves

API calls to DAP

Continuous (every decision)

Moderate (compiler runs)

Episodic (updates only)

Inference compute

DAP cloud, billed

Customer choice (API or local)

Customer's local LLM

Deployment time

Weeks

Weeks–months

Months

Best fit

SaaS-comfortable firms

Mid-market FSI

Pension / sovereign / FSI

Mode is contractually defined per scope

DRAWING 003C · SHEET 03/07

Local Model Data Flow

Scale 1:1

Rev 2.0 · 2026-05-26

Dartmouth Advisory Partners

◇ Customer Perimeter (VPC / on-prem / sovereign cloud)

Everything inside this boundary stays inside this boundary. No egress except the lightweight update channel.

Data Lake

Customer-owned

· S3 · ADLS · Snowflake
· Databricks · BigQuery

Read in-place by Runtime

Local LLM

Customer-hosted

· Llama 3.3 · Mistral Large
· Qwen · DeepSeek · fine-tune

OpenAI-compatible endpoint

DAP Runtime

(Overture / FALCON / Resolve)

· Reads data lake
· Calls local LLM
· Writes audit pack

↑ reads (no copy)↑↓ inference round-trip↓ compiled artifacts

★ Policy Compiler ★

Customer-hosted (in-VPC private)

· Emits artifacts → DAP Runtime

Signed PIS Corpus

customer-owned · multi-party-attested policy intent

· Authored in Policy Studio
· Versioned · immutable per signed version

← audit pack← signs PIS

Audit Evidence Store

customer-owned

· SOC 2 · SOX · ISO · ISAE evidence packs

Auditors read directly — no DAP involvement

Policy Studio

customer-hosted

· Where compliance + legal + ops author PIS

Multi-party sign-off with cryptographic attestation

◇ All inference compute runs here — on customer hardware, against customer data

Every decision, every artifact emission, every audit pack: customer's local LLM × customer's local data lake × DAP runtime in customer VPC. DAP does not see customer data. Customer is not billed per-decision compute by DAP.

DAP Cloud

(thin, episodic only)

Regulatory diffs

When SEC / ESMA / CSSF / FINMA / CSA / CIRO updates

Compiler updates

Bug fixes, new emitter targets, capability extensions

PIS template library

Subscribed regulatory-content templates (optional)

⟿ Signed payloads · Mutual TLS · audited

Guarantees

·Customer data never leaves customer perimeter
·DAP never sees customer transactions
·100% inference cost on customer hardware
·DAP bills flat Maintenance only
·No per-decision compute markup
·Air-gap-compatible deployment supported

Customer data never leaves customer perimeter

DRAWING 003D · SHEET 03/07

Cost Control by Deployment Mode

Scale 1:1

Rev 2.0 · 2026-05-26

Dartmouth Advisory Partners

Cost component

What the customer pays

Mode A — API

DAP-hosted

Mode B — Hybrid

Split deployment

Mode C — Local

Full customer perimeter

Capability Transfer Fee

One-time, at go-live

$750k – $2.5M

Policy Maintenance Subscription

Annual recurring

$480k – $1.6M / yr

Per-decision compute

Variable, volume-driven

Billed by DAP

$42/1k Overture · $3,800/cycle FALCON

Customer choice

API rate OR customer local LLM cost

Zero from DAP

Customer's own LLM on own hardware

Outcomes Override (optional)

Performance-linked, capped

≤ 15–25% of Maint.

Cost predictability

CFO-budgetable?

Variable with volume

Mostly flat

Flat — fully budgetable

DAP API call frequency

Per business-day shape

Every decision

Per compile / artifact run

Episodic — when source docs change

Mode A

“Run it for me.”

· Fastest go-live
· No infra burden on customer
· Pay per use
· Highest variable cost exposure

Mode B

“Run runtime locally, keep DAP compiler.”

· Data stays in VPC
· Customer chooses inference path
· Balanced cost & ops
· Mid-market sweet spot

Mode C

“We host everything. Update us when needed.”

· 100% data sovereignty
· 100% cost predictability
· 100% inference compute = customer's
· FSI / sovereign / pension default

CFO-budgetable in every mode; gold = customer-friendliest column