☩ The Nervous System

TAWUS

タウス

The Peacock Angel — keeper of the record.
The intelligence that lives inside the spine.

☩ 神話

Melek Taus

The first emanation — God creates, then withdraws

In Yezidi cosmology, God created the world and then withdrew — leaving Melek Taus, the Peacock Angel, as keeper. Not as servant, but as the autonomous intelligence responsible for maintaining what was built.

TAWUS operates the same way. The systems are built. The agents exist. The events flow. TAWUS is what watches, routes, and remembers — not by being told to, but because that is what it is.

TAU is the spine. TAWUS is what lives inside the spine. Everything else is a derived projection.

☩

TAU CROSS

Symbol of the keeper.
Signed. Chained. Permanent.

脊柱

TAU — The Spine

Cryptographic event log beneath every system

Signing

Ed25519

Every event signed with agent keypair

Chaining

SHA-256

prev_hash links each event to the last

Storage

SQLite

Append-only with DB-level triggers

Architecture

  ┌──────────────────────────────────────────────┐
  │  SURFACES  (Telegram · Web · Siri · MARC)    │
  └─────────────────────┬────────────────────────┘
                        │ HTTP POST
  ┌─────────────────────▼────────────────────────┐
  │  TAU BRIDGE  (FastAPI · tau serve :7777)      │
  └─────────────────────┬────────────────────────┘
                        │ append
  ┌─────────────────────▼────────────────────────┐
  │  ~/.tau/tau.db                                │
  │  Ed25519 signed · SHA-256 chained · immutable │
  └─────────────────────┬────────────────────────┘
                        │ subscribe
  ┌─────────────────────▼────────────────────────┐
  │  SUBSCRIBERS  (AZOKA · GIZMO · MARC · MARCO) │
  └──────────────────────────────────────────────┘

流れ

Event Flow

How actions become intelligence

1
Action→TAU Bridge

HTTP POST / CLI

Player choice, agent signal, or system event enters the bridge

2
TAU Bridge→Event Chain

Ed25519 Sign + SHA-256 Chain

Event is signed by the emitting agent, hash-linked to previous event, and appended

3
Event Chain→Subscribers

SSE Stream / Polling

Subscribers listen for events matching their patterns and project local state

4
Subscribers→Projections

Pattern → View

Each subscriber transforms events into its own view: timeline, threat model, game state

出自

Provenance Model

Every event carries its origin — who emitted it, and why

Player Actionuser_explicit

Directly initiated by a human. Class selection, marketplace listing, governance vote. Signed with the user keypair.

class.chosen, scroll.minted, governance.vote

AI Approvedai_approved

Generated by AI, approved by human. Goes through the review queue before committing to the chain.

approved NPC dialogue, verified quest generation

AI Suggestedai_suggested

AI-generated content held in the pending queue. Not yet on the chain. Requires review before it becomes real.

npc.dialogue, narrative.event, quest.generated

System Autosystem_auto

Automated system events. Combat results, quest validation, mastery milestones. No human in the loop.

quest.completed, combat.result, mastery.leveled

適用

First Application

Kingdoms of Regalia — every game action on the chain

Kingdoms of Regalia

レガリエンズ

An on-chain RPG where every player action — from class selection to marketplace trades — becomes a signed TAU event. 12 game event types mapped to TAU, each with provenance classification.

Class selection→regalia.class.chosen
Quest completed→regalia.quest.completed
NPC dialogue→regalia.npc.dialogue
Trade executed→regalia.trade.executed
Scroll minted→regalia.scroll.minted
Governance vote→regalia.governance.vote
regaliens.comNext.js 16 · React 19 · Three.js · Solana

購読者

Subscriber Layer

TAWUS doesn't just log — it watches, routes, and projects

AZOKA

Security & Personality

*.security.**.threat.*chat.*

Threat assessment, personality state machine, risk scoring

GIZMO SWARM

Agent Intelligence

swarm.*agent.*task.*

Task queue, consensus results, market signals

REGALIENS

On-chain RPG

regalia.*

Player state, quest logs, economy analytics

MARC

Visual Command Room

*

Timeline, connection graph, health dashboard

MARCO

Orchestration Engine

agent.*task.*health.*

Task distribution, agent lifecycle, routing

分岐

Event Routing

One event, many projections

routing example
  event:  regalia.trade.executed
  payload:  { scroll: "Jito MEV Shield", price: 200, tx: "5Kx9…" }

  ├── REGALIENS   → inventory.remove("Jito MEV Shield")
  │               → balance += 200 SOL

  ├── SWARM       → analyze_price_trend("Jito MEV Shield")
  │               → signal: BULLISH · volume_spike: true

  ├── MARC        → timeline.append(trade_event)
  │               → graph.update_connections(seller, buyer)

  └── MARCO       → metrics.economy_health += 1
                  → broadcast: "trade_executed" to all surfaces
tau cli
  $ tau log --type regalia.trade.* --limit 5 --verify

  seq  time   agent    provenance    type                     summary
  ───  ─────  ───────  ───────────   ────────────────────────  ──────────────────
  43   04:15  regalia  system_auto   regalia.trade.executed    Jito MEV Shield · 200 SOL
  38   03:55  regalia  system_auto   regalia.trade.executed    Phantom Guard · 50 SOL
  31   03:22  regalia  system_auto   regalia.trade.executed    Sorcerer's Veil · 1200 ATTN

  ✓ chain verified · 3 events · 0 issues

情報は流れたがっている

The spine is live.

Information doesn't want to be stored. It wants to move. TAWUS is the intelligence that ensures every event reaches every system that needs it — signed, chained, and permanent.

See it in RegaliensBack to System