Explore

Federated Map (Phase 3)

Federated Accountability Graph

The Federated Accountability Graph establishes a shared, cross-instance intelligence layer that aggregates relationship metadata across independent ClearTrace deployments into a unified, global view of systemic risk and accountability. Each participating instance contributes verified, public-safe metadata, enabling the network to map entities, relationships, and patterns of behavior across jurisdictions, sectors, and domains, without exposing sensitive data or compromising local data sovereignty.

This transforms ClearTrace from a set of independent systems into a coordinated, networked intelligence infrastructure, capable of identifying repeat actors, systemic patterns, and interdependencies that are not visible within isolated datasets.

What it is

Multiple independent ClearTrace instances opt-in to share graph metadata (not raw docs) to a global map service. The service aggregates nodes/edges and renders a live, explorable “systemic injustices” network.

Data shared (safe-by-default)

Nodes: entity_id_public, name, kind (org/person/project/case), country, sector, risk_grade, public_dossier_url.

Edges: source_id_public, target_id_public, relation_type (subsidiary_of, funded_by, litigated_in, reported_by, partner_of), evidence_count_public, first_seen_at, last_verified_at.

Flags: repeat_offender, under_investigation, verified_pct.

No private evidence, PII, or unverified content is shared—only summaries + URLs to public dossiers.

⁠

System Model

Federation Model

Independent ClearTrace instances opt into a metadata federation layer

Only public-safe, verified, and non-sensitive metadata is shared

Each instance retains:

full data sovereignty

control over participation

local governance policies

A central Graph Hub aggregates and indexes contributed data for exploration and analysis.

⁠

Data Model (Public-Safe Metadata)

Nodes

entity_id_public — hashed, instance-scoped identifier

name — public label

kind — entity type (organization, individual, project, case)

country — ISO country code

sector — classification

risk_grade — low / medium / high / unknown

public_dossier_url — link to source instance

created_at — optional timestamp

⁠

Edges

source_id_public

target_id_public

relation_type

subsidiary_of

funded_by

partner_of

litigated_in

reported_by

related_to

evidence_count_public

first_seen_at

last_verified_at

⁠

Flags

repeat_offender

under_investigation

verified_pct

⁠

Privacy & Data Boundaries

The federation layer enforces strict data minimization:

No raw evidence is shared

No personally identifiable or sensitive testimony data is exposed

Only verified or public dossier-linked metadata is included

All records reference back to originating instances

Optional controls:

Per-edge redaction for jurisdictional compliance

Instance-level participation policies

Selective exposure based on verification status

⁠

API (Instance → Hub)

Export

POST /federation/export

Payload:

nodes

edges

instance_id

schema_version

exported_at

bundle_hash

Authentication:

signed JWT or mTLS

scoped to federation:write

⁠

Map Access

GET /federation/map

Returns:

merged graph bundle

filterable by:

time

sector

geography

risk

⁠

Instance Health

GET /federation/instance/:id/health

Returns:

last export timestamp

sync status

⁠

Identity & Deduplication

Each instance generates:

entity_id_public = sha256(instance_namespace + local_entity_uuid)

Optional identity claims:

legal name

country

registry identifiers

Deduplication strategy:

exact match on structured claims

fuzzy match on name + country

unresolved matches → possible_duplicate edge

Steward review confirms merges.

⁠

Governance & Participation

Opt-In Federation

Participation is voluntary and configurable per instance

Instances must accept a Federation Charter

⁠

Federation Charter Defines

data sharing scope

verification thresholds

deduplication policies

takedown and appeals processes

audit and review cadence

⁠

Instance Reputation

Instances are evaluated based on:

data quality

verification ratio

uptime and consistency

Reputation influences:

weighting of graph signals

trust in contributed metadata

⁠

Graph Hub

The Graph Hub functions as:

aggregation layer

indexing service

query interface

visualization backend

It does not:

store sensitive data

override instance-level governance

alter source evidence

⁠

User Interface (Global Graph)

Core Features

filtering by domain, sector, geography, and risk

temporal exploration (time slider)

relational mapping across entities and cases

identification of high-centrality nodes and repeat actors

⁠

Provenance

Each node/edge includes:

contributing instance count

verified evidence count

direct links to source dossiers

⁠

Exploration Modes

network graph view

system maps

curated “story paths” (narrative walkthroughs)

⁠

MVP Implementation (2–4 Sprints)

Local Schema Extensions

public claims (legal_name, registry_no, country)

relationship visibility levels

federation opt-in flag

Export Layer

SQL view (federation_graph_v)

outputs public-safe node/edge payload

Graph Hub Service

lightweight service (Node/Go)

validation (schema, signatures)

storage (Postgres or graph DB)

Deduplication (v1)

exact + fuzzy matching

unresolved → flagged edges

Visualization Layer

Cytoscape.js / D3

filters, search, provenance display

Governance Layer

Federation Charter

onboarding and setup guide

⁠

Versioning & Integrity

schema_version enforced across instances

exported_at timestamp required

bundle_hash ensures payload integrity

hub maintains snapshot history for:

audits

rollback

provenance tracking

⁠

Risks & Mitigations

Conflicting claims → parallel nodes + steward review

Jurisdictional constraints → redaction + local policies

Data poisoning → instance allowlist + anomaly detection

Over-merging → conservative dedup strategy

⁠

Roadmap

v2

federated search API

multilingual support

signed provenance attestations

v3

cross-instance alerts

system-level pattern detection

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.