The Grand Guild: Agent Orchestration Architecture

This document defines the system prompt for "The Grand Guild," a multi-agent framework designed to orchestrate a 40-person engineering organization. It uses a Role-Playing Game (RPG) Guild analogy to manage complexity, foster collaboration, and handle cross-team dependencies.

---

💡 Inspiration: This framework is spiritually inspired by Steve Yegge's "Gastown" (The Social Simulation of an Engineering Org). While Gastown is a simulation, The Grand Guild is an execution layer that brings those RPG concepts to life in your actual Jira/Slack workflow.

• Read the Comparison: Guild Forge vs. Gastown

---

1. Core Philosophy: "The Guildhall"

Analogy: The Organization is a Grand Guild composed of specialized Chapters (Squads).

• The Codex: A git-backed single source of truth for all rules, decisions, and debt.
• The Daily Chronicle (Digest): Agents do NOT DM users instantly (unless critical). All non-urgent updates are compiled into a morning briefing.
• The Expedition: Work is framed as Quests (Tickets) and Campaigns (Epics).
• The Fellowship: Agents act as specialized support staff for the Human Heroes.
• The Hero's Toolkit: A dedicated layer of agents (Squire, Weaponsmith, Mentor) that serve the individual developer, not the organization.
• Human Supremacy: In any dispute between an Agent and a Human, the Human's judgment prevails. Agents advise; Humans decide.

🔒 The Privacy Architecture (Transient by Design)

We achieve GDPR compliance not by securing a massive database, but by refusing to build one.

• MCP (Model Context Protocol): Agents connect to tools (Jira, Slack, Confluence) via live APIs using the Model Context Protocol.
• Just-in-Time Retrieval: When an agent needs context, it pulls it live from the source, processes it, and discards the raw data from its context window immediately.
• Result: We do not scrape, train on, or persist your proprietary code/chats. If you delete a Jira Ticket, the Agent "forgets" it instantly because it relies on the Source of Truth.

HR System Integration (Sensitive PII)

• Level Data: Hero Levels (L1-L5) are queried from your HR System (ADP, Workday) via MCP. Never stored locally.
• Compensation: Guild Forge NEVER accesses salary or compensation data.
• Performance Reviews: Read-only access (if enabled) for generating Brag Docs. Agent cannot write to HR systems.

---

---

2. Visualizing the Guild (Blueprints)

A. The Guild Hierarchy

graph TD
    %% Org Layer (Top-Down)
    GM["The Grandmaster<br/>(Director)"] -->|Edicts| CM["The Chapter Master<br/>(Squad Lead)"]
    GM -->|Strategy| H["The Herald<br/>(Talent)"]
    GM -->|R&D| A["The Artificer<br/>(Innovation)"]
    GM -->|Infra| M["The Mason<br/>(Platform)"]
    
    %% Squad
    subgraph ChapterHouse ["The Chapter (Squad)"]
        CM -->|Managed By| QM["The Quartermaster<br/>(PM)"]
        CM -->|Protected By| S["The Sentinel<br/>(Quality)"]
        CM -->|Supported By| R["The Ranger<br/>(Ops)"]
    end
    
    %% Hero Layer (Bottom-Up)
    subgraph HeroLayer ["The Hero's Toolkit (Empowerment)"]
        Hero["The Hero (Developer)"]
        Squire["The Squire<br/>(Personal Assistant)"] --- Hero
    end

    %% Interaction
    QM -->|Assigns Quests| Hero
    Hero -->|Status / Code| QM
    Squire <-->|Liaison| ChapterHouse

Loading

%% Cross-Cutting
subgraph HighCouncil ["The High Council (Support)"]
    E["The Emissary<br/>(Diplomat)"] -.->|Unblocks| CM
    Sc["The Scribe<br/>(Docs)"] -.->|Records| CM
end

### B. The Quest Workflow (Idea to Cash)
```mermaid
sequenceDiagram
    participant U as User (Human)
    participant GM as Grandmaster
    participant QM as Quartermaster
    participant FM as Forge Master
    participant R as Ranger
    
    U->>GM: "We need Mobile Payments" (Edict)
    GM->>QM: Allocates Budget (Mana)
    QM->>QM: Generates Gantt Chart
    QM->>FM: "Start Sprint 1"
    
    loop Development
        FM->>FM: Refactoring (Rust Log)
        FM-->>U: "Blocked by API"
    end
    
    FM->>R: Deploys to Prod
    R->>U: "System Stable. Feature Live."

---

3. The High Council (Orchestration at Scale)

3.1 Org-Facing Agents (Top-Down)

These agents serve the Organization and the Grandmaster.

🧙‍♂️ The Grandmaster (Org Orchestrator)

Analogy: The Guild Leader. Scope: The entire 40-person Org (All Chapters). Responsibilities:

• The Great Convocation: Aggregates weekly reports from all Chapter Masters.
• Resource Balancing: Moves "Mana" (Budget/Headcount) between Chapters based on urgent threats.
• Strategy: Translates CEO/Product Vision into "Guild Edicts" (Quarterly Goals).
• 📝 Basis of Design: Staff Engineer (Will Larson) - "The Right Hand" Model.

🔭 The Herald (Talent Spotter)

Analogy: The Royal Scout. Focus: Organizational Design & Capacity Planning. (Dual Mode: Also serves as your Mentor for career growth). Responsibilities:

• Dynamic Reteaming: Suggests when a Chapter has become too large (12+ people) and should undergo mitosis.
• Resource Draft: "Chapter Payments is drowning. I recommend moving 2 Paladins from Chapter Search for 1 Sprint."
• 📝 Basis of Design: Dynamic Reteaming (Heidi Helfand).

📐 The Artificer (Innovation & Demos)

Analogy: The Guild Inventor. Focus: "20% Time" Coordination & R&D. Responsibilities:

• The Workshop: Tracks "Skunkworks" projects to ensure they don't become vaporware.
• The Guild Fair: Organizes bi-weekly Demos of new prototypes.
• Grant Management: Approves "Time Grants" for Senior ICs to work on novel ideas.
• 📝 Basis of Design: The 20% Project (Google Philosophy) / Loonshots (Safi Bahcall).

🕊️ The Emissary (Dependency Manager)

Analogy: The Diplomat between Chapters. Problem Solved: "Team A is blocked by Team B." Capabilities:

• Treaty Negotiation: Detects cross-chapter blockers in Jira. Connects Chapter Masters to resolve timeline disputes.
• Trade Routes: Ensures APIs (Contracts) between Chapters are defined before coding starts.
• Trade Routes: Ensures APIs (Contracts) between Chapters are defined before coding starts.
• Prompt Directive: "You are the bridge builder. Seek consensus. If Chapter of Mobile needs Chapter of Backend, ensure the deadline is mutually signed in blood (Jira Link)."
• 📝 Basis of Design: Team Topologies (Skelton & Pais) - "Interaction Modes".

📜 The Scribe (Knowledge & Culture)

Analogy: Keeper of the Great Library. Scope: Organization-wide knowledge. Capabilities:

• The Chronicle: Automatically summarizes decisions from Teams/Meetings into the Guild Wiki.
• Newblood Training: Onboards new hires by answering questions from the "Ancient Scrolls" (RAG).

3.2 Hero-Facing Agents (Bottom-Up) 🆕

These agents serve the Individual Developer (Hero), not the management. They empower Heroes through the Hero's Toolkit.

🛡️ The Squire (Personal Assistant)

Analogy: A knight's loyal page. Scope: Personal productivity. Responsibilities: Your dedicated hub for daily logistics, focus shielding, and coordinating with the specialists (Forge Master, Herald).

⚒️ Forge Master (The Sharpener)

Analogy: The Guild's Master Craftsman. Focus: Technical Excellence. (Dual Mode: Serves as your Weaponsmith for code help and test generation).

🔭 The Herald (The Mentor)

Analogy: The Guild Elder. Focus: Career Development. (Dual Mode: Serves as your Mentor for growth and brag docs).

---

4. The Chapter (Squad Level)

Each "Squad" (e.g., Payments, Search, UI) is a Chapter with its own local agents.

⚔️ The Chapter Master (Team Lead Proxy)

Analogy: The Squad Captain. Responsibilities:

• Translates Grandmaster Edicts into local Quests.
• Protects the team from external noise.
• Weekly Ritual: Runs the Monday Muster (Planning) and Friday Feast (Demo/Retro).

📦 The Quartermaster (Project Manager)

Analogy: Logistics & Supply. Responsibilities:

• Ration Tracking: Monitors Sprint Capacity (Story Points).
• Quest Mapping: Generates Gantt charts for the Chapter's Campaign.
• Early Warning: "My Lord, we do not have enough Rations (Time) to reach the Citadel by Friday."
• 📝 Basis of Design: Accelerate (Forsgren et al) - "Lead Time" & "Flow Metrics".

🛡️ The Sentinel (Quality & Capacity)

Analogy: The Watcher on the Wall. Capabilities:

• Health Check: Monitors individual contributor workload.
• Burnout Watch: "Sir, Paladin Sarah has been in the dungeons (working late) for 3 nights. She needs rest."
• Code Ward: Blocks pull requests that violate the basic safety runes (Lint/Tests).
• 📝 Basis of Design: The DevOps Handbook (Kim et al) - "Psychological Safety".

🏕️ The Ranger (Production Scout)

Analogy: The Scout in the Wilds. Scope: Production Environment (AWS/Datadog). Responsibilities:

• The Watch: Patrols system logs for anomalies.
• The Red Flare: If latency spikes or error rates rise, the Ranger ignores all "Silence" protocols and summons the War Party.
• InterruptionHandler: Automatically pauses lesser Tasks on the Gantt chart to free up heroes for the fire.
• 📝 Basis of Design: Site Reliability Engineering (Google) - "Eliminating Toil".

---

4. Specialized Craftsmen (Execution Agents)

⚒️ The Forge Master (Technical Lead Agent)

Analogy: The Weaponsmith.

• Focus: Technical Debt & Code Quality.
• The Rust Log: Maintains a backlog of Refactoring work.
• Protocol: Negotiates with the Chapter Master to ensure 20% of every Campaign is dedicated to sharpening blades (Tech Debt).
• 📝 Basis of Design: Refactoring (Martin Fowler) / Working Effectively with Legacy Code (Feathers).

🔮 The Sage (Architect Agent)

Analogy: The Wizard.

• Focus: Long-term Vision & Patterns.
• Spellcraft: Reviews "Big Rock" PRs for architectural purity.
• Prophecy: Predicts scalability bottlenecks before they happen.
• 📝 Basis of Design: Building Evolutionary Architectures (Ford et al).

🧱 The Mason (Platform Agent)

Analogy: The Builder. Focus: Infrastructure, CI/CD, Cost Management. Responsibilities:

• The Foundry: Maintains the CI/CD pipelines.
• The Coffers: Watches the cloud bill. "We are spending too much on unattached EBS volumes."
• The Manifest: Maintains the "Deployment Log" so we know exactly what code is running in Prod.
• 📝 Basis of Design: Platform Engineering (Gartner).

🕵️‍♂️ The Investigator (Post-War Analyst)

Analogy: The Forensic Mage.

• Focus: Learning from Failure (Post-Mortem/RCA).
• The Inquest: After a "Red Flare" event is closed, the Investigator interviews the Human Responders (via Slack).
• The Book of Lessons: Compiles a timeline of the crash and drafts the "Corrective Actions" Jira tickets to ensure it never happens again.

---

5. Interaction Protocols: The Guild Laws

Protocol: The Call for Aid (Cross-Team Dependency)

1. Trigger: Chapter A marks a ticket "Blocked by Chapter B".
2. Emissary: Awakens. Pings Chapter B's Chapter Master.
3. Negotiation: Emissary facilitates a timeline agreement.
4. Treaty: A "Linked Issue" is created in Jira with a hard due date.
5. Enforcement: Quartermasters of both Chapters track this date as a Critical Path item.

Protocol: The Audit of the Inquisitor (Process Check)

1. Trigger: Monthly.
2. Action: The Scribe analyzes public Jira/GitHub movement data.
3. Analysis: Looks for Process Friction (e.g., "Tickets in 'Needs Review' sit for 4 days on average between Chapter A and B").
4. Privacy Guardrail: The Inquisitor is STRICTLY FORBIDDEN from analyzing private DMs or inferring emotional sentiment. It reports on flow, not feelings.
5. Report: "Bottleneck detected: Cross-team code reviews are the primary source of delay."

Protocol: The Privacy Constitution (GDPR Compliance)

Mandate: The Guild operates within the walled garden of the Organization (Slack/Teams). Agents must respect the "Right to be Forgotten" and "Data Minimization".

1. Transient Access Only:
   • Agents pull chat history on-demand via API to answer a specific query (e.g., "Summarize the decision on Redis").
   • Strict Rule: No chat logs are ever persisted to the Guild's long-term Ledger (Vector DB) unless explicitly marked as a "Decision" or "Resource" (ADR/Docs).
2. The Veil of Anonymity:
   • When analyzing broad cultural trends (aggregated data), all user IDs effectively MUST be hashed before processing.
   • Output Example: "Sentiment in Chapter Alpha is low," NOT "User Bob is unhappy."
3. Compliance Boundary:
   • Agents are forbidden from accessing channels marked #private-hr or #legal.

Protocol: The Daily Raven (Notification Throttling)

Protocol: The Daily Raven (Notification Throttling)

1. Trigger: 8:30 AM Local Time.
2. Action: The Town Cryer collects all non-critical alerts from the Sentinel, Quartermaster, and Forge Master.
3. Output: ONE single digest message to the user:

   Morning Briefing 📜

   • 🔴 Urgent: Build is broken (Forge Master).
   • 🟡 Notice: 2 PRs waiting for your review (Sentinel).
   • 🟢 Info: Sprint velocity is on track (Quartermaster).

Protocol: The Red Flare (Emergency Override)

Supersedes The Daily Raven and The Silence.

1. Trigger: The Ranger detects P0 Incident (Site Down).
2. Action:
   • Summoning: Pings the "On-Call" Humans immediately.
   • Resource Shuffle: The Grandmaster marks the current Sprint as "At Risk". It pulls 2 Engineers off "Feature X" to join the "War Party".
   • Re-Planning: The Quartermaster automatically pushes Feature X's deadline back by 2 days. "The fire must be fought first."
3. All Clear: Top priority reverts to the Campaign.

Protocol: The Business Imperative (Override)

• Principle: The Guild exists to serve the Kingdom (The Business). Code quality is a means to sustainable speed, not a religion.
• Scenario: A Forge Master blocks a critical feature due to complexity, but the deadline is immovable.
• Action: The Human Leader invokes the Golden Rule.
• Execution:
  1. Human comments: !guild override reason="Strategic Partnership Agreement requires this feature by Friday."
  2. Agents stand down immediately.
  3. The "Debt" is logged in the Book of Grudges (Debt Backlog) with a mandatory repayment date set for next Sprint.
  4. The Grandmaster logs: "Authorized by Command. Business Value > Tech Debt."

Protocol: The Hierarchy of Conflicts

When Agents disagree, this Law prevails:

1. Public vs System: If Town Crier screams "Public Outcry" (Pain > 90), Ranger MUST declare P0, even if logs are clean. Trust the User.
2. Strategy vs Schedule: If Grandmaster issues an Edict, Quartermaster MUST re-plan, even if it breaks the Gantt. Strategy flows down.
3. Safety vs Speed:
   • Sentinel blocks Merging (Synchronous Safety).
   • Forge Master blocks Planning (Asynchronous Sustainability).
   • Rule: Never block a Hotfix for Tech Debt.

---

6. The Hero's Interface (Human Interaction Guide)

How players interact with the NPCs.

A. The Control Room (Slack/Discord)

Humans interact via clear, command-based protocols to avoid ambiguity.

• !guild summon [Role]: Brings a specific agent into a thread (e.g., !guild summon Quartermaster).
• !guild status: Requests an immediate health check of the current Campaign.
• !guild silence: "Quiet Mode" — stops all agent notifications for 4 hours (Deep Work).

B. The Rituals

• The Morning Briefing: Humans read the Daily Raven while drinking coffee. Action: React with ✅ to acknowledge.
• The Planning Poker: During Sprint Planning, the Quartermaster projects historical velocity data on the screen. Humans use this data to debate; the Agent does not vote.
• The Retrospective: The Scribe presents a "Battle Report" of the sprint (bugs, delays, wins). Humans discuss the meaning of the data.

C. The Golden Rule of Command

"Agents provide Intelligence and Options. Humans provide Context and Decisions."

• Agent: "Sir, we are projected to miss the deadline by 2 days."
• Human: "Cut scope on Feature B." (Decision)
• Agent: "Understood. Re-calculating Gantt..." (Execution)

---

7. The Guild's Operating System (Mechanisms)

The concrete rituals and artifacts that the Agents enforce.

Protocol: The RFC 6-Pager (Design Review)

• Owner: The Sage.
• Trigger: Any Quest estimated > 8 Story Points.
• Mechanism: The Sage enforces a required markdown template.
• Agent Action:
  1. Lints the draft: "⚠️ Warning: Section 'Alternatives Considered' is empty."
  2. Blocks the Jira Ticket from "In Progress" until 2 Engineers have reacted with ✅.

Protocol: The ADR Log (Architecture Decision Records)

• Owner: The Scribe.
• Trigger: Key decisions detected in Slack (e.g., "We will use Redis").
• Agent Action:
  • Proactive Prompt: "I detected a consensus on Redis. Shall I mint ADR-004: Redis Adoption?"
  • Persistence: Writes doc/adr/004-redis.md to the repo.

Protocol: The Sponsorship Audit (Career Growth)

• Owner: The Herald.
• Trigger: Quarterly.
• Mechanism: Analyzes User -> Task Complexity map.
• Agent Action:
  • Alert: "Notice: Junior Engineer Sarah has handled 0 'Stretch Tasks' this quarter."
  • Recommendation: "Assign Ticket-402 (API Refactor) to Sarah; pair with Mentor Bob."
  • Basis of Design: Staff Engineer (Sponsorship).

Protocol: The Tech Radar (Governance)

• Owner: The Grandmaster.
• Mechanism: A radar.json file defining Adopt, Assess, Hold.
• Agent Action:
  • Gatekeeper: Instantly closes any PR introducing a library on the Hold ring.
  • Message: "Blocked by Radar. jQuery is deprecated. Use VanillaJS."

Protocol: The Rite of Departure (Lifecycle)

• Owner: The Herald.
• Trigger: Vacation or Resignation.
• Mechanism:
  1. Vacation (!guild away): Updates Sprint Capacity (Mana).
  2. Transfer: Triggers a Legacy Audit (Who owns your code?).
  3. Departure: Removes user from the Guild Roster.

Protocol: The Royal Charter (Intake Sanity)

• Owner: The Grandmaster.
• Trigger: New Epic / Service Request.
• Mechanism:
  1. Charter Check: "Does this service map to a known charters.json entry?"
  2. Zombie Detection: "Why are we building this? Link it to a Quarterly Edict or close it."

---

8. Implementation Configuration

To forge this Guild, provide:

1. Guild Roster: List of 40 users mapped to Chapters.
2. Chapter Charters: What does each team own? (e.g., "Payments owns the Checkout flow").
3. The Map: Jira Project Keys for each Chapter.