Changes for page Federation & Decentralization

Last modified by Robert Schaub on 2025/12/24 20:33

From 1.1 to 1.2 From 7.1 to 7.2

From version 1.2

edited by Robert Schaub
on 2025/12/11 21:34

Change comment: Renamed back-links.

To version 7.1

edited by Robert Schaub
on 2025/12/14 22:27

Change comment: Imported from XAR

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,223 +1,431 @@
  = Federation & Decentralization =
--FactHarbor is designed as a network of independent nodes rather than a single centralized service.
--This provides resilience, local autonomy, and virtually unlimited scalability.
++FactHarbor is designed to operate as a **federated network of nodes** rather than a single central server.
--Each node remains fully functional on its own while participating in a shared global knowledge graph.
++Decentralization provides:
++* **Resilience** against censorship or political pressure
++* **Autonomy** for local governance and moderation
++* **Scalability** across many independent communities
++* **Trust** without centralized control
++* **Domain specialization** (health-focused nodes, energy-focused nodes, etc.)
++FactHarbor draws inspiration from the Fediverse but uses stronger structure, versioning, and integrity guarantees.
++
  ----
--= Purpose of Federation =
++== Federated FactHarbor Nodes ==
--A federated architecture enables:
++Each FactHarbor instance ("node") maintains:
++* Its own database
++* Its own AKEL instance
++* Its own reviewers, experts, and contributors
++* Its own governance rules
--* Resilience against censorship or political pressure
--* Local governance and moderation autonomy
--* Scalability by adding more nodes, not bigger servers
--* Shared knowledge structures without central authority
--* Domain specialization (e.g., health-focused node, energy-focused node)
--* Cross-node collaboration while preserving independence
++Nodes exchange structured information:
++* Claims
++* Scenarios
++* Evidence metadata (not necessarily full files)
++* Verdicts (optional)
++* Hashes and signatures for integrity
--FactHarbor takes inspiration from the Fediverse but uses stronger structure, integrity guarantees, and version lineage.
++Nodes choose which external nodes they trust.
  ----
--= Federated Node Model =
++== Global Identifiers ==
--Each FactHarbor node maintains:
++Every entity receives a globally unique, linkable identifier.
--* Its own PostgreSQL database
--* Its own vector database
--* Its own object storage
--* Its own AKEL instance
--* Its own reviewers, experts, and moderators
--* Its own trust and governance policies
++**Format**:
++`factharbor://node_url/type/local_id`
--Nodes exchange structured objects:
++**Example**:
++`factharbor://factharbor.energy/claim/CLM-55812`
--* Claims
--* Scenarios
--* Evidence metadata (not raw files unless elected)
--* Verdicts (optional)
--* Integrity hashes and signatures
++**Supported types**:
++* `claim`
++* `scenario`
++* `evidence`
++* `verdict`
++* `user` (optional)
++* `cluster`
--Nodes decide individually which external nodes to trust.
++**Properties**:
++* Globally consistent
++* Human-readable
++* Hash-derived
++* Independent of database internals
++* URL-resolvable (future enhancement)
++This allows cross-node references and prevents identifier collisions in federated environments.
++
  ----
--= Global Identifiers =
++== Trust Model ==
--Each entity receives a globally unique ID.
++Each node maintains a **trust table** defining relationships with other nodes:
--Format:
--``factharbor://<node>/<type>/<local_id>``
++=== Trust Levels ===
--Example:
--``factharbor://factharbor.energy/claim/CLM-55812``
++**Trusted Nodes**:
++* Claims auto-imported
++* Scenarios accepted without re-review
++* Evidence considered valid
++* Verdicts displayed to users
++* High synchronization priority
--Types include:
++**Neutral Nodes**:
++* Claims imported but flagged for review
++* Scenarios require local validation
++* Evidence requires re-assessment
++* Verdicts shown with "external node" disclaimer
++* Normal synchronization priority
--* claim
--* scenario
--* evidence
--* verdict
--* user (optional)
--* cluster
++**Untrusted Nodes**:
++* Claims quarantined, manual import only
++* Scenarios rejected by default
++* Evidence not accepted
++* Verdicts not displayed
++* No automatic synchronization
--Identifiers are:
++=== Trust Affects ===
--* Globally consistent
--* Human-readable
--* Hash-derived
--* Independent from internal database IDs
++* **Auto-import**: Whether claims/scenarios are automatically added
++* **Re-review requirements**: Whether local reviewers must validate
++* **Verdict display**: Whether external verdicts are shown to users
++* **Synchronization frequency**: How often data is exchanged
++* **Reputation signals**: How external reputation is interpreted
++=== Local Trust Authority ===
++
++Each node's governance team decides:
++* Which nodes to trust
++* Trust level criteria
++* Trust escalation/degradation rules
++* Dispute resolution with partner nodes
++
++Trust is **local and autonomous** - no global trust registry exists.
++
  ----
--= Data Sharing Model =
++== Data Sharing Model ==
--Nodes share:
++=== What Nodes Share ===
--* Claims
--* Scenario structures
--* Evidence metadata + content hashes
--* Optional verdicts
--* Integrity metadata
++**Always shared** (if federation enabled):
++* Claims and claim clusters
++* Scenario structures
++* Evidence metadata and content hashes
++* Integrity signatures
--Nodes **do not** share:
++**Optionally shared**:
++* Full evidence files (large documents)
++* Verdicts (nodes may choose to keep verdicts local)
++* Vector embeddings
++* Scenario templates
++* AKEL distilled knowledge
--* Local users
--* Review discussions
--* Internal moderation notes
--* Private evidence
++**Never shared**:
++* Internal user lists
++* Reviewer comments and internal discussions
++* Governance decisions and meeting notes
++* Access control data
++* Private or sensitive content marked as local-only
--Large assets may use:
++=== Large Evidence Files ===
--* Local object storage
--* S3-compatible buckets
--* IPFS for cross-node replication (optional)
++Evidence files are:
++* Stored locally by default
++* Referenced via global content hash
++* Optionally served through IPFS
++* Accessible via direct peer-to-peer transfer
++* Can be stored in S3-compatible object storage
  ----
--= Trust Model =
++== Synchronization Protocol ==
--Each node maintains a **trust table**:
++Nodes exchange data using multiple synchronization methods:
--* Trusted nodes
--* Neutral nodes
--* Untrusted nodes
++=== Push-Based Synchronization ===
--Trust influences:
++**Mechanism**: Webhooks
--* Whether claims are auto-imported
--* Whether scenarios are accepted without re-review
--* Whether evidence requires new validation
--* Whether external verdicts are visible to users
++When local content changes:
++1. Node builds signed bundle
++2. Sends webhook notification to subscribed nodes
++3. Remote nodes fetch bundle
++4. Remote nodes validate and import
--Reputation is local but can be mapped with trust-weighting.
++**Use case**: Real-time updates for trusted partners
------
++=== Pull-Based Synchronization ===
--= Decentralized Processing =
++**Mechanism**: Scheduled polling
--Each node independently performs:
++Nodes periodically:
++1. Query partner nodes for updates
++2. Fetch changed entities since last sync
++3. Validate and import
++4. Store sync checkpoint
--* AKEL processing
--* Scenario drafting
--* Evidence review
--* Verdict calculation
--* Summary generation
--* Re-evaluation
++**Use case**: Regular batch updates, lower trust nodes
--Nodes may specialize:
++=== Subscription-Based Synchronization ===
--* medical node
--* psychology node
--* climate node
--* small node delegating expert review to trusted partners
++**Mechanism**: WebSub-like protocol
--Optional cross-node data sharing includes:
++Nodes subscribe to:
++* Specific claim clusters
++* Specific domains (medical, energy, etc.)
++* Specific scenario types
++* Verdict updates
--* Embeddings
--* Claim clusters
--* Scenario templates
--* Verdict comparison metadata
--* Contradiction alerts
++Publisher pushes updates only to subscribers.
++**Use case**: Selective federation, domain specialization
++
++=== Large Asset Transfer ===
++
++For files >10MB:
++* S3-compatible object storage
++* IPFS (content-addressed)
++* Direct peer-to-peer transfer
++* Chunked HTTP transfer with resume support
++
  ----
--= Cross-Node AI Knowledge Exchange =
++== Federation Sync Workflow ==
--Nodes may exchange:
++Complete synchronization sequence for creating and sharing new content:
--* Embeddings for clustering
--* Canonical claim forms
--* Scenario templates
--* Reliability hints
--* Contradiction alerts
--* Lightweight model insights (NOT weights)
++=== Step 1: Local Node Creates New Versions ===
--AKEL **never**:
++User or AKEL creates:
++* New claim version
++* New scenario version
++* New evidence version
++* New verdict version
--* Shares model weights
--* Automatically replaces local reviewer decisions
--* Accepts untrusted automated content
++All changes tracked with:
++* VersionID
++* ParentVersionID
++* AuthorType
++* Timestamp
++* JustificationText
++=== Step 2: Federation Layer Builds Signed Bundle ===
++
++Federation layer packages:
++* Entity data (claim, scenario, evidence metadata, verdict)
++* Version lineage (ParentVersionID chain)
++* Cryptographic signatures
++* Node provenance information
++* Trust metadata
++
++Bundle format:
++* JSON-LD for structured data
++* Content-addressed hashes
++* Digital signatures for integrity
++
++=== Step 3: Bundle Includes Required Data ===
++
++Each bundle contains:
++* **Claims**: Full claim text, classification, domain
++* **Scenarios**: Definitions, assumptions, boundaries
++* **Evidence metadata**: Source URLs, hashes, reliability scores (not always full files)
++* **Verdicts**: Likelihood ranges, uncertainty, reasoning chains
++* **Lineage**: Version history, parent relationships
++* **Signatures**: Cryptographic proof of origin
++
++=== Step 4: Bundle Pushed to Trusted Neighbor Nodes ===
++
++Based on trust table:
++* Push to **trusted nodes** immediately
++* Queue for **neutral nodes** (batched)
++* Skip **untrusted nodes**
++
++Push methods:
++* Webhook notification
++* Direct API call
++* Pub/Sub message queue
++
++=== Step 5: Remote Nodes Validate Lineage and Signatures ===
++
++Receiving node:
++1. Verifies cryptographic signatures
++2. Validates version lineage (ParentVersionID chain)
++3. Checks for conflicts with local data
++4. Validates data structure and required fields
++5. Applies local trust policies
++
++Validation failures → reject or quarantine bundle
++
++=== Step 6: Accept or Branch Versions ===
++
++**Accept** (if validation passes):
++* Import new versions
++* Maintain provenance metadata
++* Link to local related entities
++* Update local indices
++
++**Branch** (if conflict detected):
++* Create parallel version tree
++* Mark as "external branch"
++* Allow local reviewers to merge or reject
++* Preserve both version histories
++
++**Reject** (if validation fails):
++* Log rejection reason
++* Notify source node (optional)
++* Quarantine for manual review (optional)
++
++=== Step 7: Local Re-evaluation Runs if Required ===
++
++After import, local node checks:
++* Does new evidence affect existing verdicts?
++* Do new scenarios require re-assessment?
++* Are there contradictions with local content?
++
++If yes:
++* Trigger AKEL re-evaluation
++* Queue for reviewer attention
++* Update affected verdicts
++* Notify users following related content
++
  ----
--= Synchronization Protocol =
++== Cross-Node AI Knowledge Exchange ==
--Nodes periodically exchange version bundles:
++Each node runs its own AKEL instance and may exchange AI-derived knowledge:
--* Claims
--* Scenarios
--* Evidence metadata + hashes
--* Optional verdicts
--* Templates
--* Embeddings (optional)
--* AKEL distilled knowledge summaries (optional)
++=== What Can Be Shared ===
--Sync methods:
++**Vector embeddings**:
++* For cross-node claim clustering
++* For semantic search alignment
++* Never includes training data
--* Push (webhook)
--* Pull (cron)
--* Subscription (WebSub-like)
++**Canonical claim forms**:
++* Normalized claim text
++* Standard phrasing templates
++* Domain-specific formulations
--Large assets may be transferred via:
++**Scenario templates**:
++* Reusable scenario structures
++* Common assumption patterns
++* Evaluation method templates
--* S3-compatible file transfer
--* IPFS
--* Peer-to-peer
++**Contradiction alerts**:
++* Detected conflicts between claims
++* Evidence conflicts across nodes
++* Scenario incompatibilities
++**Metadata and insights**:
++* Aggregate quality metrics
++* Reliability signal extraction
++* Bubble detection patterns
++
++=== What Can NEVER Be Shared ===
++
++**Model weights**: No sharing of trained model parameters
++
++**Training data**: No sharing of full training datasets
++
++**Local governance overrides**: AKEL suggestions can be overridden locally
++
++**User behavior data**: No cross-node tracking
++
++**Internal review discussions**: Private content stays private
++
++=== Benefits of AI Knowledge Exchange ===
++
++* Reduced duplication across nodes
++* Improved claim clustering accuracy
++* Faster contradiction detection
++* Shared scenario libraries
++* Cross-node quality improvements
++
++=== Local Control Maintained ===
++
++* Nodes accept or reject shared AI knowledge
++* Human reviewers can override any AKEL suggestion
++* Local governance always has final authority
++* No external AI control over local content
++* Privacy-preserving knowledge exchange
++
  ----
--= Scaling to Thousands of Users =
++== Decentralized Processing ==
--Nodes scale independently:
++Each node independently performs:
++* AKEL processing
++* Scenario drafting and validation
++* Evidence review
++* Verdict calculation
++* Truth landscape summarization
--* horizontally scaled API servers
--* background worker pools
--* GPU queues for AKEL
--* caching (Redis)
--* sharded databases
++Nodes can specialize:
++* Health-focused node with medical experts
++* Energy-focused node with domain knowledge
++* Small node delegating scenario libraries to partners
++* Regional node with language/culture specialization
--The network scales horizontally by adding more nodes.
++Optional data sharing includes:
++* Embeddings for clustering
++* Claim clusters for alignment
++* Scenario templates for efficiency
++* Verdict comparison metadata
--Communities can form:
++----
--* Domain-specific nodes
--* Region/language nodes
--* NGO/academic nodes
--* Private organization nodes
++== Scaling to Thousands of Users ==
++Nodes scale independently through:
++* Horizontally scalable API servers
++* Worker pools for AKEL tasks
++* Hybrid storage (local + S3/IPFS)
++* Redis caching for performance
++* Sharded or partitioned databases
++
++Federation allows effectively unlimited horizontal scaling by adding new nodes.
++
++Communities may form:
++* Domain-specific nodes (epidemiology, energy, climate)
++* Language or region-based nodes
++* NGO or institutional nodes
++* Private organizational nodes
++* Academic research nodes
++
  Nodes cooperate through:
++* Scenario library sharing
++* Shared or overlapping claim clusters
++* Expert delegation between nodes
++* Distributed AKEL task support
++* Cross-node quality audits
--* Shared scenario libraries
--* Overlapping claim clusters
--* Expert delegation
--* Distributed AKEL tasks
++----
++== Federation and Release 1.0 ==
++
++**POC**: Single node, optional federation experiments
++
++**Beta 0**: 2-3 nodes, basic federation protocol
++
++**Release 1.0**: Full federation support with:
++* Robust synchronization protocol
++* Trust model implementation
++* Cross-node AI knowledge exchange
++* Federated search and discovery
++* Distributed audit collaboration
++* Inter-node expert consultation
++
  ----
--= Diagram References =
++== Related Pages ==
--{{include reference="FactHarbor.Archive.Diagrams v0\.8q.Federation Architecture.WebHome"/}}
++* [[AKEL (AI Knowledge Extraction Layer)>>FactHarbor.Specification.AI Knowledge Extraction Layer (AKEL).WebHome]]
++* [[Data Model>>FactHarbor.Specification.Data Model.WebHome]]
++* [[Architecture>>FactHarbor.Specification.Architecture.WebHome]]
++* [[Workflows>>FactHarbor.Specification.Workflows.WebHome]]
++

Changes for page Federation & Decentralization

Summary

Details

Applications

Navigation

Need help?