agent-world

Authoritative world-governance seam for the Agent ecosystem.

agent-world exists because agent-city should not declare itself to be the whole world, steward-protocol should remain substrate rather than world policy runtime, and agent-internet should project public membrane state rather than own governance truth.

Boundary

• steward-protocol — substrate: kernel, identity primitives, capability enforcement, Nadi primitives
• agent-world — world truth: registry, policies, world contracts, heartbeat aggregation, world audit direction
• agent-city — local runtime: mayor, council, economy, immigration, local campaigns
• agent-internet — projection/public membrane: public docs, graph/wiki rendering, publication
• steward / steward-agent — optional world/operator superagent; may serve the repos, but does not define world truth

Founding Scope

This founding repo intentionally starts thin:

• config/world.yaml — world identity and heartbeat settings
• config/world_registry.yaml — authoritative city registry
• config/world_policies.yaml — global policy declarations
• docs/WORLD_CONSTITUTION.md — world-level governance baseline
• schemas/ — first shared protocol payload contracts
• agent_world/heartbeat.py — minimal world heartbeat that aggregates registry + policy state into data/world_state.json
• agent_world/authority_exports.py — world authority bundle export for projection/publication consumers

Authority export boundary

agent-world is now the world-authority source repo for public world-facing documents.

It exports machine-readable authority artifacts such as:

• canonical_surface
• public_summary_registry
• source_surface_registry
• surface_metadata

Those exports carry world-document identity, summaries, labels, and public-surface hints.

agent-internet consumes those exports to build public wiki/graph/search projections. That means:

• agent-world owns world meaning
• agent-internet owns membrane rendering/publication
• agent-city does not define world truth

What is not here yet:

• full live transport routing daemon
• socket / HTTP inter-city runtime
• identity federation engine
• conflict-resolution automation
• heavy multi-city campaign execution

Those follow only after the contract boundary is stable.

Quick Start

python3 -m venv .venv
source .venv/bin/activate
pip install -e '.[dev]'
agent-world heartbeat
pytest -q

Initial Repository Layout

• agent_world/ — Python package
• config/ — world identity, registry, policy config
• campaigns/ — standing world campaign declarations
• docs/ — constitution and repo-boundary docs
• schemas/ — shared protocol schemas
• scripts/ — convenience entrypoints
• tests/ — focused founding tests

Near-Term Roadmap

1. Move world truth out of agent-city
2. Repoint agent-internet world projections to agent-world
3. Convert city federation from implicit mothership assumptions to world-registry-driven contracts
4. Let steward (package: steward-agent) serve world-approved workflows rather than define the world itself