Hugging Face's logo

Datasets:
KingKlown
/
koa-ecosystem

Dataset card Files
xet
 Community
Dataset Viewer

The dataset viewer is not available because its heuristics could not detect any supported data files. You can try uploading some data files, or configuring the data files location manually.

YAML Metadata Warning:empty or missing yaml metadata in repo card

Check out the documentation for more information.

---
license: apache-2.0
language:
  - en
  - fr
tags:
  - koa
  - okido
  - civic-tech
  - governance
  - public-good
  - offline-first
  - deterministic-systems
  - knowledge-infrastructure
  - semantic-sovereignty
  - non-domination
  - knowledge-graph
  - wikidata
  - multilingual
  - auditability
  - fail-closed
---

# OKIDO / kOA Ecosystem  
## Offline, Governable Knowledge-to-Action Infrastructure (Deterministic by Design)

This repository is the **public documentation hub** for an initiative that aims to build a **civilizational-grade** knowledge infrastructure:  
**auditable, offline-capable, governable**, and **stable over time**.

This is **not** “AI that decides”.  
It is **deterministic infrastructure** where AI can later be added as a bounded plugin — never the authority.

---

## One-line pitch

**OKIDO / kOA is a deterministic Knowledge-to-Action ecosystem:**  
it turns *verified knowledge → deliberation → decision → execution*, while preserving **semantic sovereignty**, **non-domination**, and **offline resilience**.

---

## Core philosophy

### “I build with AI, but I don’t build AI”
- The spine is **good old code**: deterministic, reproducible, testable.
- Output must be **stable** (no hallucinations, no drift, no silent shifts).
- AI may be used later as a **tool** (extraction/planning assistance), but always:
  - constrained by typed contracts
  - validated and auditable
  - rejectable (fail-closed)
  - lockable (once accepted, it stays)

### Determinism is a safety feature
Determinism is what enables:
- verification
- governance
- accountability
- reproducibility
- long-term stability

---

# High-level architecture

## Two separate systems (by design)

### 1) Konnaxion (Public Platform / Agora)
Konnaxion is the civic participation platform:
- learn → debate → decide → initiate action
- public-facing participation and collective intelligence modules

Links:
- https://www.okido.wiki/platforms/konnaxion
- https://github.com/Rejean-McCormick/Konnaxion/wiki

### 2) Orgo (Operational Engine / Bunker)
Orgo is the operational continuity engine:
- offline-first coordination
- routing tasks/cases/signals
- structured execution pipelines and resilience

Links:
- https://www.okido.wiki/platforms/orgo
- https://github.com/Rejean-McCormick/Orgo/wiki

✅ **Important:** Konnaxion and Orgo are **two different things**.  
They interoperate through controlled interfaces and shared formats (Kristals).

---

# The shared spine (input → truth → output)

## Kristals (Verifiable Knowledge Units)
Kristals are structured, validated, portable knowledge artifacts used when relevant across the ecosystem.

Repo:
- https://github.com/Rejean-McCormick/kristal-framework

## SenTient (Input: text → structured meaning)
SenTient is the ingestion layer that turns messy text into structured, usable meaning:
- entity extraction
- linking and reconciliation
- claim/tuple production for knowledge structures

Links:
- https://www.okido.wiki/technology/sentient
- https://github.com/Rejean-McCormick/SenTient

## Architect (Output: structured meaning → multilingual text)
Architect produces **multilingual text deterministically** from structured inputs (frames / functions).
It is designed to avoid hallucination by **not inventing facts**.

Links:
- https://www.okido.wiki/technology/architect
- https://github.com/Rejean-McCormick/abstract-wiki-architect/wiki
- https://meta.wikimedia.org/w/index.php?title=Abstract_Wikipedia/Tools/abstract-wiki-architect

---

# Ariane (Universal UI / Navigation Layer)
Ariane models UI flows and execution states as explicit structures, enabling:
- consistent UX in complex systems
- future agent-friendly navigation (without losing governance)

Link:
- https://www.okido.wiki/technology/ariane

---

# SwarmCraft (Orchestration Layer)

SwarmCraft is a strict orchestration engine based on a loop:

**SCAN → PLAN → EXECUTE**

It treats long outputs as **many small parts**, each with:
- explicit lifecycle state (`planned / drafted / locked`)
- caching by contract hash (idempotent rebuilds)
- validation gates between steps
- stable publishing behavior

Links:
- https://www.okido.wiki/technology/swarmcraft
- https://github.com/Rejean-McCormick/SwarmCraft
- https://github.com/Rejean-McCormick/SwarmCraft/wiki

⚠️ License note  
SwarmCraft is derived from *Swarmussy* (mojomast).  
**License lineage must be validated before redistribution of derived code.**  
Documentation and architectural proposals are fine; redistribution will follow proper verification.

---

# How SwarmCraft adds to Architect (document-level planning)

**Architect already does the hard part:** sentence realization.  
Given a structured input (frames / functions), it produces correct surface text (multilingual-ready).

What’s missing for full pages is **document-level planning**:
- selecting facts
- ordering them into lead + sections
- assembling many small sentences into coherent paragraphs/articles

## Proposal: SwarmCraft as an article-orchestration layer above Architect

Pipeline:

**Wikidata QID → fact set → article plan → part contracts → frame calls → Architect → paragraphs → validation → locked article**

```mermaid
flowchart TD
  Q[Wikidata QID / Fact Set] --> P[SwarmCraft Planner]
  P --> C[Contracts: Parts + Constraints]
  C --> A[Architect: deterministic realization]
  A --> T[Sentences]
  T --> D[Paragraphs / Sections]
  D --> V[Validation gates]
  V --> L[Lock & publish]

What “SwarmCraft” contributes

SwarmCraft makes long-form generation build-system-like:

  • deterministic task graph
  • typed contracts per part (inputs/outputs/constraints)
  • caching by contract hash
  • validation gates
  • locking accepted results (no regeneration drift)

Determinism comes from the build system, not the model. The generator can be probabilistic, but the process is constrained and reproducible.

Where “article knowledge” lives (not in the core)

SwarmCraft remains domain-agnostic. Article logic is injected through:

  • Scaffolds (entity-type templates: human/city/org)
  • Recipes (facts → frames/functions mapping)
  • Planner (facts + scaffold → contract tree)

Minimal vertical slice (first deliverable)

Human lead paragraph

  • Input: Wikidata QID
  • Output: 2–4 sentence lead (one language)
  • Uses existing frames / templates
  • Evidence mapping stored per sentence

This proves end-to-end flow: facts → plan → frames → Architect → paragraph.

End-to-end Knowledge-to-Action loop 

flowchart LR
  IN[Documents / signals / reports] --> S[SenTient]
  S --> K[Kristal validation & compilation]
  K --> EX[Kristal exchange: verifiable source of truth]
  K --> RP[Runtime pack: offline bundle]
  EX --> KON[Konnaxion: public deliberation]
  RP --> ORG[Orgo: offline ops & routing]
  KON --> DEC[Decision modules: Smart Vote / EkoH]
  DEC --> ORG
  ORG --> ACT[Execution: projects, response, tasks]
  ACT --> EX

Social modules (governance & collective intelligence)

This ecosystem is also a social project:

  • legitimacy through transparent rules
  • participation without manipulation
  • resilience without central capture

Examples:

  • Smart Vote (auditable voting modalities)
  • EkoH (bounded expertise weighting, transparent and reversible)

(Expanded documentation will be hosted under /docs/ in this repository.)

Repository structure (recommended)

  • README.md → this page (“Start here”)
  • docs/00_EXECUTIVE_SUMMARY.md → institutional pitch
  • docs/10_MODULES_MAP.md → separation of concerns and interfaces
  • docs/20_SWARMCRAFT_ABOVE_ARCHITECT.md → orchestration proposal
  • docs/UPDATES.md → ongoing changelog / weekly logs

Quick links index (do not remove)

OKIDO Wiki

GitHub

Wikimedia reference

Citation (for referencing in papers / institutions) 

@software{McCormick_OKIDO_KOA_2026,
  author  = {McCormick, R{\'e}jean},
  title   = {OKIDO / kOA Ecosystem: Offline, Governable Knowledge-to-Action Infrastructure},
  year    = {2026},
  url     = {https://huggingface.co/<YOUR_USERNAME_OR_ORG>/<YOUR_REPO_NAME>},
  note    = {Deterministic technosocial architecture: Kristals, SenTient, Architect, Konnaxion, Orgo, Ariane, SwarmCraft}
}

Contact / collaboration

Use GitHub issues and module repositories for technical tracking. For institutional contact, publish one stable contact point here (email or official channel) and mirror it on OKIDO Wiki.


If you want, I can also generate the matching files for your repo (`docs/00_EXECUTIVE_SUMMARY.md`, `docs/UPDATES.md`, etc.) so you can create them one by one in Hugging Face’s “Add file → Create new file” UI.
::contentReference[oaicite:0]{index=0}
Downloads last month
2
Total file size:
19.4 kB