Living City

A lightweight city metaphor for understanding Artemis City agents, memory, routing, and governance roles.

The city metaphor

Artemis City uses a city metaphor to make the system’s operational roles easier to reason about. Agents are citizens, memory is civic infrastructure, ATP messages are official notices, and governance agents act as oversight offices.

System concept	City metaphor	Primary owner
Memory operations	Mail delivery	Pack Rat / Postal Service
Obsidian vault	City archives	City Librarian
Trust scores	Citizen clearances	Trust Office
Agents	Citizens	Agent registry
MCP server	Post office	Central hub
Context loading	Archive research	Reading Room
ATP messages	Official notices	City Hall

Core citizens

Artemis

• Role: Governance and oversight
• Clearance: Full
• Duties: Policy, dispute resolution, city planning
• Office: City Hall

Pack Rat

• Role: External data handling and message transport
• Clearance: High
• Duties: Route external messages and objects into a central interaction layer
• Office: Post Office

Compsuite

• Role: Signal monitor and sentinel
• Clearance: Process-specific
• Duties: Monitor outputs, detect problem areas, and distinguish noise from optimization
• Office: City Hall Watchtower

AgentZero

• Role: System monitoring and operations
• Clearance: High
• Duties: Monitor city health, manage configuration, and produce status reports
• Office: Operations Center

Agent311

• Role: User assistance and information
• Clearance: High
• Duties: Answer questions, provide context, and route requests to the right civic service
• Office: Information Desk

Trust and routing

Trust behaves like a clearance system. Successful operations can raise trust, failed operations can lower it, and inactive paths decay over time so stale routes lose influence. Minimum thresholds prevent the system from treating a decayed route as authoritative without fresh validation.

Example exchange

post_office = get_post_office()

for citizen in ["pack_rat", "planner", "AgentZero"]:
    post_office.send_mail(
        sender="artemis",
        recipient=citizen,
        subject="Daily Briefing",
        content=f"Good morning, {citizen}. Today's priorities are ready."
    )

The same pattern applies to archive research:

history = post_office.request_from_archives(
    requester="planner",
    query="ATP protocol decisions",
    section="Reflections"
)

synthesis = f"Based on {len(history)} archived documents..."
post_office.send_to_archives(
    sender="planner",
    archive_section="Reports",
    title="ATP_Research_Summary",
    content=synthesis
)

Archive organization

City Archives/
├── Postal/
├── Agents/
│   ├── artemis/
│   ├── pack_rat/
│   └── planner/
├── Archives/
│   ├── Reflections/
│   ├── Reports/
│   ├── Policies/
│   └── Projects/
├── History/
└── Delivery_Logs/

Why this metaphor helps

• Relatable: Mail, archives, offices, and clearances make distributed systems easier to discuss.
• Visual: Agent interactions map cleanly to routes, offices, and records.
• Extensible: New agents can be introduced as new civic roles without changing the metaphor.
• Operational: The metaphor stays tied to routing, memory, provenance, and trust instead of becoming decorative copy.

See the routing modes, hybrid memory bus, and trust scoring references for the underlying mechanics.