System Guide

DAEPOLIS is institutional intelligence.

Reliance Forensics, forecasting and CJI are the leading products. Dependency analysis connects them across evidence, actors, arrangements, affected groups and outcomes. Decision Records preserve and govern the work when an institution chooses to rely.

Core Surfaces

The public site should map to the database and workflow objects, not just explain the analysis style.

Reliance Forensics

Reconstructs the claims, warrants, evidence, uncertainty and belief debt inside material an institution is being asked to rely on.

Forecasting

Turns warranted expectations into resolvable commitments with distributions, falsifiers, later outcomes and calibration memory.

CJI

Measures contribution, agency and lived outcomes across groups and time while keeping measurement validity separate from causal and predictive claims.

Dependency Intelligence

Connects reliance, forecasts and CJI through actors, arrangements, capabilities, alternatives, affected groups, outcomes and falsifiers.

Decision Records

Governance after reliance: durable records containing the elected decision, evidence state, objections, monitoring triggers, review authority and later outcome.

Document Ingestion Integrity

PDF and Office uploads must produce trusted extraction reports before the text can enter the untrusted-content boundary. Raw private files are not stored.

Brief Forensics

Existing consultant reports, AI memos, ESG briefs, policy papers, board papers, and investment notes can be decomposed into claims, warrants, implied priors, belief debt, missing counter-evidence, falsifiers, adversarial objections, and questions before reliance.

Institutional Dependency Intelligence

Companies, countries, buyer markets, sources, claims, contracts, portfolios, regimes, public agencies, vendors, and decision records can be audited as risk-bearing dependencies with separate materiality channels, evidence gaps, monitoring triggers, rhetorical downgrades, and next actions.

Personal Intelligence Surface

The post-login Surface is becoming the live instrument: users should be able to add observations, source snippets, reviewer objections, and monitoring deltas to specific nodes while the system preserves provenance, freshness, review state, and the verification chain.

Canonical Claim Ledger

Atomic claims with support status, evidence links, verification state, disputes, retractions, and resolved forecast outcomes.

Source Hardening

Evidence states distinguish provisional, source-assisted, source-grounded, contradicted, and missing-source material.

Review Workflow

Candidate claims, evidence, and hardening tasks can be challenged, approved, rejected, or returned for source work.

Forecast Register

Predictions carry probability distributions, reference-class context, red-team distribution sidecars, decisive unknowns, resolution criteria, Brier score, and calibration bins.

Surface Trust Layer

Trust capsules, append-only Surface events, role-specific record views, and node-level proof chains make the graph inspectable rather than decorative.

Exports And API

Brief PDFs, production packages, audit-trail exports, proof downloads, and enterprise data resources expose the same record spine.

Frontend Contract

Every finding should carry its proof and history.

DAEPOLIS turns institutional material into inspectable intelligence: ingestion quality, source states, claims, dependencies, affected groups, alternatives, forecast distributions, decisive unknowns, later outcomes, and revision history. The Surface keeps those objects connected rather than collapsing them into one persuasive answer.

The quality rule is simple: every proof, warning, score, uncertainty, repair, and remembered outcome must remain available at the point where a person is asked to rely on the finding.

01Intake Integrity

Documents enter as untrusted evidence, not authority.

PDF/Office extraction integrityUntrusted-content boundarySource packsHardening tasks
Show extraction quality, provenance, suspicious content, and review work before any audit treats the document as usable evidence.
02Claim And Evidence Core

Claims are separated from prose and kept provisional until supported.

Canonical claim ledgerSource-hardening statesSemantic collisionsEvidence gaps
Expose the support state, missing source class, contradiction path, and next hardening action beside the claim itself.
03Governed Memory

A Decision Record governs work only after reliance is elected.

Decision RecordsAppend-only eventsReview workflowOutcome ledger
Let users see who changed what, why the record moved, what remains disputed, and what later happened.
04Forecast And Calibration

Probability is a public object, not a sentence.

Prediction distributionsReference classesRed-team sidecarsCalibration surface
Show the distribution, outside-view class, adversarial disagreement, decisive unknowns, and update history instead of only one midpoint.
05Monitoring And Repair

The system should wake when reality changes.

Decisive unknownsMonitoring triggersLineage decayError memory
Turn uncertainty into watchable signals: what would change the judgement, what has gone stale, and what prior mistake should be reused.
06Surface Instrument

The graph is an operating surface over the record spine.

Trust capsulesRole-specific viewsSurface eventsSignal intake
Every node should answer why it matters, why it can be trusted, what is missing, what changed, and what role should do next.

Build Status

DAEPOLIS is launch-stage infrastructure. Some surfaces are live; others are deliberately staged because audit systems become credible by refusing to fake maturity.

Live now

Workbench intake, source packs, source-hardening states, claim verification, Brief Forensics, dependency intelligence, full-document ingestion integrity, Surface import/compilation, trust capsules, Surface events, role views, public ledger, prediction distributions, red-team sidecars, reference classes, decisive unknowns, calibration surface, outcome ledger, portfolio ingestion, proof paths, PDF exports, review queue, cohort access framing, and public methodology pages.

Next

UI probability update history, richer node-level public proof chains, stronger automated source verification, more real-data/entity saturation, improved live monitoring surfaces, and CJI production-panel data coverage.

Runway

Autonomous lawful source collection, workstation readiness expansion, screen-aware DAEPOLIS context, globe/network workstation, enterprise workflow integrations, and organisation-scoped operating configurations.

Operating Principles
Institutional intelligence is the product; a Decision Record governs it after reliance.
Weak evidence should be marked, not hidden.
Forecasts are useful only when reality can resolve them.
Human review, disputes, corrections, and retractions are part of the system, not an embarrassment.
Public institutional names stay private until explicit Stage 2 permission is granted.
Design Partner Cohort

Autumn 2026

The cohort tests real institutional decision records with source packs, claims, evidence, review workflow, exports, and ledger accountability. For access, contact daepolisanalysis@outlook.com.

Apply for cohort