Chapter 3 of 7  ·  Infrastructure, Architecture & Context

🌍 Setting & World-Building

Infrastructure (Setting), software architecture (World-Building), and the root context repository (Author's Atlas).

📚 Setting is where the story lives. World-Building is the rules that govern it. The Author's Atlas is the one map that holds it all together — without it, the story breaks at scale.

Overview

Every great story lives in two craft layers. The Setting is the physical world — the city's geography, the castle's layout. The World-Building is the system of rules and interconnections that make that world coherent — the trade routes, the laws of physics, the political structures. Authors who build complex worlds create an Author's Atlas: a single comprehensive map of the entire world that they consult before writing any chapter.

For the Snap AI Author, the Setting is your infrastructure — your cloud topology, managed services, deployment strategy, and Infrastructure-as-Code. The World-Building is your software architecture — microservices boundaries, communication contracts, data ownership, cross-cutting patterns. Both must be planned and peer-reviewed before services are built.

The most critical concept in this chapter is the Context Repository. AI tools like Claude Code and GitHub Copilot can only help coherently when they can see the entire system. A developer who opens a single microservice file and asks the AI for a change is asking it to write Chapter 12 without having read Books 1 and 2. The solution: a root repository with git submodules for every microservice, architecture docs at the root level, and shared contracts accessible everywhere. When the AI opens this repository, it sees the whole world — and every snap fires with full story-level context.

Core Concepts

  • The Setting — Infrastructure: Cloud topology, managed services, deployment strategy, and Infrastructure-as-Code — planned before any service is built into it.
  • The World-Building — Architecture: Microservices map, communication patterns, data ownership, and cross-cutting laws — reviewed with peers before implementation.
  • The Author's Atlas — Context Repo: A root repository with git submodules for every microservice. The AI sees the full system on every edit.
  • Shared Contracts at the Root: Architecture docs, schemas, and contracts stored at root level — so no service invents its own rules.

Key Principle

Context is the Snap AI Author's most valuable asset. An AI with partial context produces locally correct but globally incoherent output — the equivalent of a chapter that makes sense alone but breaks the rest of the story.

← Chapter 2
All Chapters
Chapter 4 →