Files
the-nexus/mempalace/rooms.yaml
Alexander Whitestone 5dfcf0e660
Some checks failed
CI / test (pull_request) Failing after 8s
CI / validate (pull_request) Failing after 14s
Review Approval Gate / verify-review (pull_request) Failing after 2s
Add sovereign room to MemPalace fleet taxonomy
Refs #1116. Adds 'sovereign' room for cataloging Alexander Whitestone's
requests and responses as dated, retrievable artifacts.

Room config:
- key: sovereign, available to all wizards
- Naming convention: YYYY-MM-DD_HHMMSS_<topic>.md
- Running INDEX.md for chronological catalog
- Fleet-wide tunnel for cross-wizard search
2026-04-12 12:40:06 -04:00

126 lines
3.9 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# MemPalace Fleet Taxonomy Standard
# Refs: #1082, #1075 (MemPalace × Evennia — Fleet Memory milestone)
#
# Every wizard palace MUST contain the 5 core rooms listed under `core_rooms`.
# Optional domain-specific rooms are listed under `optional_rooms` for reference.
# Wizards may add additional rooms beyond this taxonomy.
#
# Room schema fields:
# key — machine-readable slug (used for tunnel routing and fleet search)
# label — human-readable display name
# purpose — one-line description of what belongs here
# examples — sample artifact types filed in this room
version: "1"
core_rooms:
- key: forge
label: Forge
purpose: CI pipelines, builds, infra configuration, deployment artefacts
examples:
- build logs
- CI run summaries
- Dockerfile changes
- cron job definitions
- server provisioning notes
- key: hermes
label: Hermes
purpose: Agent platform, Hermes gateway, harness CLI, inter-agent messaging
examples:
- harness config snapshots
- agent boot reports
- MCP tool definitions
- Hermes gateway events
- worker health logs
- key: nexus
label: Nexus
purpose: Project reports, documentation, knowledge transfer, field reports
examples:
- SITREP documents
- architecture decision records
- field reports
- onboarding docs
- milestone summaries
- key: issues
label: Issues
purpose: Tickets, backlog items, PR summaries, bug reports
examples:
- Gitea issue summaries
- PR merge notes
- bug reproduction steps
- acceptance criteria
- key: experiments
label: Experiments
purpose: Prototypes, spikes, sandbox work, exploratory research
examples:
- spike results
- A/B test notes
- proof-of-concept code snippets
- benchmark data
optional_rooms:
- key: evennia
label: Evennia
purpose: MUD world state, room descriptions, NPC dialogue, game events
wizards: [bezalel, timmy]
- key: game-portals
label: Game Portals
purpose: Portal registry, zone configs, dungeon layouts, loot tables
wizards: [timmy]
- key: lazarus-pit
label: Lazarus Pit
purpose: Dead/parked work, archived experiments, deprecated configs
wizards: [timmy, allegro, bezalel]
- key: satflow
label: SatFlow
purpose: Economy visualizations, satoshi flow tracking, L402 audit trails
wizards: [timmy, allegro]
- key: workspace
label: Workspace
purpose: General scratch notes, daily logs, personal coordination
wizards: ["*"]
- key: home
label: Home
purpose: Personal identity, agent persona, preferences, capability docs
wizards: ["*"]
- key: general
label: General
purpose: Catch-all for artefacts not yet assigned to a named room
wizards: ["*"]
- key: sovereign
label: Sovereign
purpose: Artifacts of Alexander Whitestone's requests, directives, and conversation history
wizards: ["*"]
conventions:
naming: "YYYY-MM-DD_HHMMSS_<topic>.md"
index: "INDEX.md"
description: "Each artifact is a dated record of a request from Alexander and the wizard's response. The running INDEX.md provides a chronological catalog."
# Tunnel routing table
# Defines which room pairs are connected across wizard wings.
# A tunnel lets `recall <query> --fleet` search both wings at once.
tunnels:
- rooms: [forge, forge]
description: Build and infra knowledge shared across all wizards
- rooms: [hermes, hermes]
description: Harness platform knowledge shared across all wizards
- rooms: [nexus, nexus]
description: Cross-wizard documentation and field reports
- rooms: [issues, issues]
description: Fleet-wide issue and PR knowledge
- rooms: [experiments, experiments]
description: Cross-wizard spike and prototype results
- rooms: [sovereign, sovereign]
description: Alexander's requests and responses shared across all wizards