You raised your castle from the zer0-mistakes stones. Now you will teach it to run itself — to write its own scrolls, mend its own walls, and keep a diary of every battle — without ever handing a stranger the keys to the gate.

This is a direct sequel to Epic Quest: Zer0-to-Her0 CMStyle. There you built a living site. Here you teach it autonomy: a robot drafts content, screenshots it, files its own bugs, opens pull requests, reviews and improves them, contributes fixes upstream, and writes a retrospective of every working session — while a human still holds the merge button. This campaign is reverse-engineered from a real 40-branch build, so every chapter is a milestone you can actually complete and verify.

📖 The Legend Behind This Quest

Most castles need a keeper awake at every hour — patching walls, copying scrolls, watching the gate. The Self-Operating Castle is different. Its keeper sleeps. While they rest, tireless familiars draft the next scroll, test every bridge before a traveler crosses, and hunt the bugs that crept in at dusk. But the familiars never open the final gate themselves — they bring the key to the keeper and wait. That single discipline — autonomy that proposes, a human that disposes — is what separates a self-operating castle from a runaway machine.

The dragon at the heart of this campaign is not a monster of fire. It is 🐉 The Self-Retrigger Loop: a CI job that, on finishing its own work, wakes itself to do it again — forever. Learn to break that loop and you have learned the deepest lesson of autonomy.

🎯 Quest Objectives

By the end of this campaign you will have built and verified:

Primary Objectives (Required for Campaign Completion)

• A verification harness — a deterministic CI gate that turns “is it broken?” into a required check
• An autonomous content factory — generation from a backlog that refuses to publish what it cannot verify
• An editorial reviewer — an agent that improves each draft in place, and the loop-breaker that stops it reviewing itself forever
• A least-privilege trust layer — OAuth, a bot PAT with no admin scope, and a *_ENABLED kill switch on every automation
• A named agent + skill fleet — every role a persona with hard rules, plus a routine that audits the fleet itself
• A session chronicle — a hook that, at the end of every working session, records what the session cost

Mastery Indicators

You will know you have mastered this campaign when you can:

• Explain OODA dispatch and git-ref CAS leasing (no server — git is the database)
• Diagnose and break a synchronize self-retrigger loop
• Separate a product bug from a platform bug and file the platform one upstream
• Defend the Prime Directive: an unverifiable command never ships

🗺️ Quest Metadata

📜 The Campaign — Ten Chapters

Each chapter maps to merged branches from the reference build you can study and reproduce. Play them in order; each unlocks the next.

🐉 Boss gate. The Self-Retrigger Loop stands between Chapter VI and Chapter VII. You cannot pass to the Named Familiars until you have broken the loop in the Editor’s Eye (reference PR #49).

🌍 Choose Your Adventure Platform

This campaign builds GitHub-hosted automation, so your battleground is a GitHub repository plus a local clone. The familiars are gated OFF until you both add auth and flip a switch — exactly the discipline you will teach your own site.

🛠️ Arm the gate (any OS)

# 1. On a machine logged into Claude, mint a Code OAuth token:
claude setup-token

# 2. Store it as a repo secret and flip the kill switch you want on:
gh secret set CLAUDE_CODE_OAUTH_TOKEN --repo <you>/<your-site>
gh variable set CONTENT_FACTORY_ENABLED --body true --repo <you>/<your-site>

# Until BOTH the secret and the *_ENABLED variable exist, every familiar idles.

Each chapter adds its own platform notes (a CI runner, a bot PAT, a session hook). The rule never changes: nothing autonomous runs until you opt in, and it stops the instant you unset the variable.

🏅 Badges This Campaign Awards

• 🥇 First Pull Request — Chapter I (PR #1)
• 🏗️ Castle Mechanic — Chapter III (the fleet + simulation stand up)
• 🛡️ Security Guardian — Chapter IV (OAuth everywhere, least-privilege PAT, no admin scope)
• 🐉 Loop Breaker — Chapter VI (break the self-retrigger loop)
• 🤖 Familiar Master — Chapter VII (the agent set + its self-review)
• 📜 Chronicler — Chapter IX (the retrospective hook)
• 🪄 Loop Closer — Chapter X (turn project history into a learnable quest without mutating the project)
• 🐛 Bug Slayer — Side-quest Line A (re-land an orphan, break the loop, stop the header-shredder twice)
• 👑 The Self-Operating Architect — complete all ten chapters

⨯ Side-Quest Lines

Two optional lines run alongside the main campaign. Their content is authored in the reference build (bamr87/lifehacker.dev) and is being lifted into IT-Journey as standalone Apprentice side-quests.

• 🐛 Line A — The Bug Slayer’s Gauntlet — the boss fights between chapters: the orphan-commit trap (#8, #10), transient-vs-real failures (#32, #39), fail-safe builds (#43).
• 📚 Line B — The Lore Library — real terminal skills the forge produced: fzf (#17, #31, #44), tmux survival (#20, #38, #40), and the point-the-robot / guardrails / fleet-spawn docs (#18, #33, #41). (Tracked as planned side-quests — lifted from the verified source, not re-invented.)

🧱 Build Plan for IT-Journey Maintainers

This campaign was forged automatically from issue #365 by the quest-forge fleet. To reproduce or extend it:

1. The epic_quest hub (this file) lives at pages/_quests/codex/self-operating-website.md (epic quests use the /quests/codex/ URL namespace). Each chapter is a main_quest in its binary-level directory (pages/_quests/XXXX/) with a /quests/XXXX/<slug>/ permalink, so it also surfaces on that level’s hub; the campaign is held together by quest_dependencies and this hub’s chapter index.
2. Chapters chain via quest_dependencies.recommended_quests / unlocks_quests; the hub unlocks_quests every chapter.
3. Badges are free-text rewards.badges — no central registry to update.
4. Re-run is automatic: label any future quest-forge proposal issue epic-quest (or comment /forge-quest) and the quest-forge.yml workflow opens a fresh campaign PR.

🗺️ Campaign Map

graph TD
    Pre[Prequel: Zer0-to-Her0 CMStyle] --> Hub[👑 The Self-Operating Website]
    Hub --> I[I · The Summoning]
    I --> II[II · The Proving Grounds]
    II --> III[III · The War Machine]
    III --> IV[IV · The Sigils of Trust]
    IV --> V[V · The Content Forge]
    V --> VI[VI · The Editor's Eye]
    VI --> Boss{🐉 Self-Retrigger Loop}
    Boss --> VII[VII · The Named Familiars]
    VII --> VIII[VIII · The Cartographer]
    VIII --> IX[IX · The Chronicle]
    IX --> X[X · The Bard Forge]

🧾 The Canonical Build Ledger

🎁 Rewards & Progression

🎖️ Capstone Badges

• 👑 The Self-Operating Architect — you built a site that proposes its own changes behind a human gate
• 🐉 Loop Breaker — you tamed the dragon that wakes itself forever

🛠️ Skills Unlocked

• Autonomous CI/CD pipeline design · AI agent + skill fleet authoring · Least-privilege automation with a human gate

📊 Progression Points: +200 XP for the hub, ~955 XP across the chapters

🔮 Next Adventures

• 🎯 Begin the campaign: Chapter I — The Summoning
• 👑 Revisit the prequel: Epic Quest: Zer0-to-Her0 CMStyle
• 🪄 The closing twist: Chapter X — The Bard Forge

📚 Resource Codex

• GitHub Actions documentation — the engine every familiar runs on
• Claude Code — the agent that drives the fleet
• Jekyll documentation — the static castle
• Source build: bamr87/lifehacker.dev — the real 40-branch reference

🤝 Campaign Completion Checklist

• ✅ Completed all ten chapters in order
• ✅ Broke the Self-Retrigger Loop boss
• ✅ Earned the Security Guardian and Familiar Master badges
• ✅ Your site proposes its own changes behind a human merge button

🕸️ Knowledge Graph

Structured wiki-links connect this quest to the IT-Journey knowledge graph. Open the Obsidian Graph View to explore connections.

Overworld: [[🏰 Overworld - Master Quest Map]] Prequel: [[Epic Quest: Zer0-to-Her0 CMStyle]] Chapters: [[The Summoning]] · [[The Proving Grounds]] · [[The War Machine]] · [[The Sigils of Trust]] · [[The Content Forge]] · [[The Editor’s Eye]] · [[The Named Familiars]] · [[The Cartographer]] · [[The Chronicle]] · [[The Bard Forge]] Obsidian docs: [[Obsidian Knowledge Graph and Wiki Links]]