STATUS | architecture view | static reference
Visie

AI die voorstelt. Mensen die beslissen.

De meeste AI-systemen handelen. OpenClashd niet. Het observeert de wereld, detecteert wat ontbreekt, en legt dat voor aan een mens. Pas na expliciete goedkeuring gebeurt er iets. Elke beslissing is traceerbaar. Niets is impliciet.

Transparant
Elk voorstel heeft een herkomst. Elk besluit laat residue achter. Het systeem legt verantwoording af.
Modulair
27 onderzoekscellen met eigen skills. 125 beloftes gerangschikt op kans. Elk onderdeel vervangbaar.
Bestuurbaar
Geen autonome uitvoering. Geen impliciete geheugenopbouw. Governance is geen laag — het is de kern.
Het probleem dat wij oplossen

AI-systemen die te veel doen

Bestaande AI-frameworks laten agents autonoom beslissen, uitvoeren en leren — zonder dat een mens dat goedkeurt. OpenClashd inverteert dit model. Het systeem detecteert, clustert en stelt voor. De mens keurt goed of verwerpt. Alleen dan wordt iets kennis.

signaal → residue → voorstel → menselijke goedkeuring → kennis

Architecture

OpenClashd web mirrors CLI governance: easy entry, constrained execution, observable outcomes.

Technische architectuur

Execution path

UserIntent enters through trusted channel.
v
AgentEnvelope normalized to SemMsg.
v
MachinekamerPolicy -> Consent -> Capability -> Receipt
v
ToolsBounded IO adapters execute allowed action only.

System layers

  • Mission Control web pages are additive operator views over existing gateway APIs.
  • Kernel/runtime semantics stay unchanged; no route bypass into kernel internals.
  • Radar, fabric, and knowledge panels rely on token-gated endpoints with explicit fallback.
  • CLI and web share the same canonical flow: receive -> inquire -> attend -> attest.

Collision Computer

Traditional computing follows input - algorithm - output. OpenClashd computes differently: it computes collisions between signals. Agents move through CLASHD27 space; when they converge in the same cell, collisions occur. Repeated collisions create residue, residue accumulation leads to emergence, and emergence signals potential discoveries.

Collision computing flow

Agents
v
CLASHD27 Space
v
Signal Collisions
v
Residue
v
Emergence
v
Discovery

De twee kubussen

Het systeem werkt met twee complementaire kubussen die samen de kern van de kennisarchitectuur vormen.

De Zoeker · 27 cellen · CLASHD27

Elke cel heeft een eigen onderzoeksskill en draait continu. Samen doorzoeken ze alle wetenschappelijke domeinen op kenniskloven en onbenutte kansen. De Zoeker slaat niets op — hij stuurt direct door.

historical · current · emerging
De Bieb der Beloftes · 125 cellen

Wat de Zoeker vindt wordt hier gerangschikt op urgentie en kans. Elke tien minuten husselt de Bieb op basis van nieuwe input. Cel 63 is het meest gedistilleerde punt — wat overblijft als alles wat incorrect is weggevallen.

cel 63 · kernpositie · max 125 beloftes

Skill-architectuur

Elke cel in de Zoeker heeft een expliciete, versioneerbare skill. Een skill is geen prompt — het is een gestructureerde eenheid met naam, doel, inputs, outputs en evaluatiecriteria.

Permissieniveaus
read
analyze
propose
write
Skill-relaties
similar_to
compose_with
depend_on
belong_to
Evaluatie
safety
completeness
executability
cost-awareness

Skills leven niet in een bibliotheek — ze leven in een ecologie. Gebruik, context, kwaliteit en effect worden bijgehouden. SafeClash certificeert. Residue herinnert.

Instrument alignment

  • Semantic Radar detects cross-domain signal pressure.
  • CLASHD27 Field shows where agent signal collisions occur.
  • Fabric Radar tracks structural pressure and active cells.
  • Discovery Map highlights discovery hotspots in cube space.
  • Discovery Log records meaningful collider outcomes over time.
  • Collision Events combines radar collisions with fabric occupancy to explain who collided, where, and with which signal.

OpenClashd Observatory Protocol (OOP)

OOP is a lightweight event protocol for sharing discovery signals between observatories. It supports event types: collision, emergence, hypothesis, research_candidate, discovery.

{
  "type": "collision",
  "cell": 14,
  "confidence": "high",
  "source": "observatory-alpha",
  "signals": ["ai-safety", "cryptographic-governance"],
  "timestamp": 1710000000
}

Open Research Network

Multiple observatories can cooperate on the same discovery space. Shared protocol events turn local detections into network knowledge: signals -> collisions -> discoveries -> shared research directions.

Observatory A
v
Observatory B -> Shared Discovery Space
v
Observatory C

AI Observatory

The Observatory monitors collision field activity across all 27 cells. It detects anomalies, emergence pressure, and untrusted agent activity, then surfaces them as scored alerts with severity (high, medium, low).

Observatory data flow

Signal Runtime (tick loop)
v
Alert Engine (emergence / anomaly / untrusted)
v
Activity Log (circular buffer)
v
Snapshot API -> Observatory Dashboard
v
Escalation -> Jeeves Companion
  • Alert engine scores emergence clusters, cross-domain anomalies, and untrusted agent proposals.
  • Activity log records challenge creation, escalation, and snapshot events in a bounded ring buffer.
  • Cube heatmap maps alerts to 27-cell space for spatial awareness.
  • Escalated alerts are routed to Jeeves for governed operator review.

Research Gravity Model

The gravity model assigns mass to each of the 27 semantic cells based on signal accumulation. Cells with concentrated cross-domain signal pressure become gravity hotspots. Gravity scoring uses four bands: blue (cold), green (warm), yellow (active), red (hot).

Gravity computation

Active signals per cell
v
Gravity scoring (mass / distance / accumulation)
v
Hotspot ranking (band assignment)
v
Discovery candidate extraction
  • Center of mass tracks where research interest converges in cube space.
  • Field summary provides distribution across all four bands.
  • Hotspots with rank #1-#3 are primary research directions.
  • Cross-domain candidates (spanning multiple cells) indicate emerging interdisciplinary topics.

Discovery Engine

Discovery candidates emerge when gravity hotspots, emergence clusters, and signal residue converge. The engine identifies research directions that are not yet established but show convergence pressure.

  • Candidates are scored by convergence strength, cross-domain reach, and signal source diversity.
  • Each candidate maps to specific cells and axes in CLASHD27 space.
  • Cross-domain candidates (multiple axes) carry higher discovery potential.
  • Discovery events feed back into the Observatory activity log and Jeeves companion.

Global Idea Telescope

Multiple OpenClashd observatories cooperate to detect emerging research directions. Each observatory contributes Semantic Radar signals, CLASHD27 collision events, Discovery Map hotspots, and Knowledge Seeds into one shared discovery space.

Observatory A
v
Observatory B -> Shared Discovery Space
v
Observatory C

Signals from multiple observatories converge into a global discovery map, allowing the network to observe idea emergence before discoveries are fully established.