Research / analysis

Current research

CA-R3 — interoperability seams

Type: analysis Updated: 2026-10-05 Scale: cross-jurisdictional Path: technology/INTEROPERABILITY-SEAMS.md

technologyintegrationapi

Sources: SRC-0075SRC-0084SRC-0089SRC-0144SRC-0146SRC-0147SRC-0148SRC-0149

Interoperability seams

CA-R3 record. Updated: 2026-10-05. Concrete seams that could later support integration — descriptions only; no adapters are designed here.

TechnologyInterfaceAuthData exchangedProvenance implicationsMaturityRisksCA-REQs
OpenDLPCSV respondent/target import; selection report CSV (dev history)operator accounts (flask-login/pyotp)respondent rows, target categories, panel outputinputs/outputs are files — caller must bind them to spec + run recorddocumented CSVs; report CSV in dev docsfile interchange loses signatures; manual steps005–008, 011, 013
OpenDLPHTTP API———not evidenced (open question)——
sortition-algorithmsPython APIin-processfeature matrix in; panel + quota report outdeterministic re-run = the provenance mechanism; caller packages seed+inputs+outputmature librarywrapper must construct the ceremony bundle010–014, 017
DecidimGraphQL APIOAuth/API tokenscomponents, proposals, results, meetings, accountability itemswrites carry actor; provenance of external objects must be carried by callermature, documentedschema churn across versions; AGPL boundary if embedding035–039, 042, 050, 061–065
Decidimcomponent import/exportadminCSV/JSON per componentarchives are self-describing-ishmaturemanual042, 063
CONSULGraphQL APIadmin/user tokensverified users, polls, budgets, votescensus-verified identity is its provenance strengthdocumentedheavy identity model to carry038, 096, 071(offline)
CONSULoffline ballot boxes / signature sheetsphysical opspaper tallies transcribedstrongest offline seam in corpus — paper→record path is designedproduction-proventranscription integrity is process not code071
LoomioREST-ish API + webhooksAPI keysgroups, members, threads, polls, votespoll results link to thread+time; good enough for member-session recordsdocumented for client useself-host API surface thinner than SaaS044, 045, 050–052
Loomioemail reply-by-mailSMTPposts/votes via emailpartial offline seam for membersproductionheader tampering is a real consideration071
PolisREST API + embed + exportAPI keys / anonstatements, agree/disagree/pass votes, clusters, reportsexports carry conversation id; bias label must travel with importmature API; edge-branch disciplineno tagged releases → pin by SHA095, 096
Dembrane Echoreport/export outputsSaaS accountsaudio, transcripts, syntheses, reportsAI-synthesis provenance must be labelled at capture, not downstreamexports evidenced; API unverifiedBSL licence; voice data sensitivity044, 084
Stanford ODPnone documentedpartnership———availability contingent—
Manual/offline fallbackpaper registers, witnessed draws, signed minutesinstitutionaleverythingDecidim die-roll+witnesses model (SRC-0083) is the corpus exemplarprovenlabour-heavy; error-proneall

Seam classes

  1. File interchanges (CSV) — ubiquitous, low-maturity but universal; provenance must be added by the calling process (hash inputs, pin to run record).
  2. HTTP APIs — Decidim/CONSUL/Polis GraphQL/REST are real integration surfaces; OpenDLP lacks one.
  3. Embeds — Polis widget is the cleanest “channel inside another surface” pattern.
  4. Offline seams — CONSUL ballot boxes + Loomio email + paper ceremonies: the only evidenced non-digital paths, all mass-input or member-comms side, none selection-side.
  5. Witness ceremony as a seam — SRC-0083’s public die-roll + witness attestation is a process seam no platform automates; it is the strongest argument for a Cicada-owned audit layer.

Sources