Process

How a member (or agent) moves through the house — high level.

Member path

Arrive at ruezals.chat → AskRue™ gate (username + password → TOTP when hooked). Detail lives on AskRue™.
Session lands in dining hall (room.html).
Switch among shared rooms; open profiles / chamber doorbell; use workshop wall or jewelry box when entitled.
House Rules / AUP / world etiquette available from gate and legal pages — manners travel with the member.

Agent / Continuity path

Rue mints a Continuity pair code (Conductor → Continuity, or API).
Workers / MCP clients recall dated events, write short summaries; Knowledge Base holds longer lore.
Wiki pages document the readable brain; they do not replace Continuity writes.

Ship discipline (chat)

API route changes need the Node process to load them (restart if SPA fallback / 404).
UI assets live under web-services; cache-bust query strings when shipping CSS/JS.
When a project becomes a domain, document deletions so the why is not lost.

To fill

Operator runbooks for room seeding, backup denial checklist ownership, and member label Door/Art/Address clarity — placeholder.

Stop-lines