Institutional intelligence for decisions that must survive scrutiny.
DAEPOLIS tests what an institution can rely on, what observable future would confirm or weaken the view, and how contribution, agency and lived outcomes change across groups and time. Dependency analysis connects the evidence; Decision Records preserve the work after reliance.
Evidence comes before prose. Unsupported claims stay provisional.
Analysis becomes structured records, not disposable text.
Predictions need dates, resolution criteria, and later scoring.
The system focuses upward on institutions, contracts, public power, and lawful accountability.
What It Is
DAEPOLIS is a structured intelligence workbench for cases where ordinary prose is too loose: public contracts, democratic stress, platform dependency, transition risk, defence end-use exposure, institutional capture, and source-heavy accountability work.
A Translation Layer
It takes rough material and proposes ledger structure: candidate claims, entities, timelines, source gaps, hardening tasks, falsifiers, and monitoring triggers.
A Method Engine
It routes each question through relevant methods instead of firing every framework. Turkey transition and NHS FDP playbooks now load when those case families appear.
An Accountability Surface
It keeps claims, evidence, confidence, review status, predictions, and later resolutions visible so judgement can be audited rather than merely admired.
Who Should Use It
DAEPOLIS is for people who need defensible judgement under institutional pressure, not quick summaries.
Public-interest lawyers and litigators
Turn contracts, filings, decisions, and public records into claim registers, source gaps, falsifiers, and evidence plans.
Journalists and investigators
Convert messy leads into structured hypotheses, actor maps, timelines, source priorities, and publishable accountability questions.
NGOs, unions, and watchdog teams
Track institutional pressure, procurement dependency, democratic-agency risks, and the evidence needed for lawful civic action.
Responsible capital and public-sector boards
Assess exposure, end-use risk, vendor lock-in, reputational risk, governance options, and decision gates before a problem hardens.
How To Use It
Begin with the mission and arrangement, reconstruct what must be true, expose who depends on what and who experiences the outcome, then define the evidence or forecast that can change the assessment.
Frame The Mission And Reliance Question
Name the mission, beneficiaries, intended outcome, actor who may rely, stakes, decision horizon, and what evidence would change the view.
Describe The Arrangement And Add Evidence
Add the provider, technology, contract, safeguards, alternatives, notes, documents, URLs, source packs, clauses, or investigation questions. Everything remains provisional until reviewed.
Reconstruct Assurance, Dependency, And Consequence
The system reconstructs the principal assurance and its warrants, then connects claims, dependencies, practical capabilities, affected groups, alternatives, mechanisms, evidence gaps, and falsifiers.
Define A Test And Govern Reliance
The Surface exposes findings, comparisons, people and outcomes, evidence and history. Resolvable questions become forecasts; a Decision Record is attached only when the institution elects to rely.
What You Get Back
A DAEPOLIS output is designed to be used in a meeting, source review, board discussion, newsroom workflow, legal scoping note, or civic campaign.
DAEPOLIS is not legal, investment, medical, or official government advice. It does not replace external verification. It is not a private-person targeting tool, a surveillance system, or a way to launder unsourced assertions into authority.
The best use is upward-facing accountability: institutions, companies, states, contracts, public offices, data systems, funding flows, laws, and infrastructure.
Current Status
The platform is usable for institutional investigations and reliance audits backed by inspectable records. Some automation is deliberately staged until the underlying objects and empirical coverage are stable.
Decision Records, Brief Forensics, dependency intelligence, full-document PDF/Office ingestion checks, source packs, source-hardening states, claim verification, review queue, public ledger, prediction distributions, red-team sidecars, calibration surface, decisive unknowns, outcome ledger, Surface trust capsules, role views, append-only Surface events, public proof paths, PDF exports, and enterprise API resources.
The remaining quality gap is saturation and operations: richer real source/entity coverage, stronger live monitoring automation, UI probability update history, more public Surface proof chains, and CJI real-data panel expansion.
The workstation layer: screen-aware DAEPOLIS context, autonomous lawful source collection, map/network workstation, organisation-specific configurations, and external workflow integrations after the record spine is dense enough.
Bring a real case.
The strongest test is a live institutional question with sources, uncertainty, and consequences.