{
  "title": "City Hall Walkthrough",
  "source": "Edited from the Narrative Pack; introduction expanded from the core narrative, concepts, human-agent model, progressive adoption, and claims boundaries.",
  "chapters": [
    {
      "slug": "introduction",
      "title": "What City Hall Is",
      "lead": "Structure for software that outlives the session.",
      "sections": [
        {
          "id": "operating-environment",
          "heading": "An operating environment around the work",
          "body": "City Hall is Aptlantis's project-governance and operational-context system. It connects intent, standards, skills, records, relationships, artifacts, and evidence so human-and-agent development remains understandable across time and handoff. Projects produce the software; City Hall supplies the context surrounding that work.",
          "layout": "cards",
          "items": [
            {
              "title": "Where is it?",
              "body": "Identify placement, ownership, and lifecycle state so a project has a discoverable home."
            },
            {
              "title": "What is it?",
              "body": "Understand purpose, current state, and which records carry authority."
            },
            {
              "title": "What touches it?",
              "body": "Follow applicable standards, dependencies, decisions, and related artifacts."
            }
          ]
        },
        {
          "id": "fewer-mysteries",
          "heading": "The problem: context disappears",
          "body": "A project can keep accumulating code while its intent, rationale, and evidence become harder to recover. City Hall turns that surrounding state into records another person or agent can inspect. The point is fewer mysteries when work resumes.",
          "layout": "comparison",
          "items": [
            {
              "before": "Intent and decisions are scattered across conversations.",
              "title": "Preserve intent and rationale",
              "body": "Project and decision records keep the purpose, choice, and consequences beside the work."
            },
            {
              "before": "An agent must infer which rules apply and what it may change.",
              "title": "Make applicability and scope explicit",
              "body": "Name the relevant standards, inputs, constraints, authority, and completion criteria."
            },
            {
              "before": "A favorable status says little about what was checked.",
              "title": "Connect claims to evidence",
              "body": "Keep artifacts, findings, validation results, and delivery records available for inspection."
            }
          ]
        },
        {
          "id": "standards-skills-records",
          "heading": "The mechanism: standards, skills, and records",
          "body": "These three layers reinforce one another. Standards make expectations explicit. Skills make recurring procedures repeatable. Records preserve what happened and what exists now. Templates and schemas support that structure; they do not replace the judgment behind it.",
          "layout": "cards",
          "items": [
            {
              "title": "Standards",
              "body": "Define requirements, vocabulary, applicability, and boundaries. A proposal standard, for example, explains what intent and success criteria must be captured.",
              "href": "/city-hall/pps",
              "linkLabel": "Read PPS standard"
            },
            {
              "title": "Skills",
              "body": "Package a bounded procedure and its references so a recurring operation can be performed consistently. A skill can also stand alone."
            },
            {
              "title": "Records",
              "body": "Preserve project state, accepted decisions, exceptions, task outcomes, and evidence beyond the session that created them."
            }
          ]
        },
        {
          "id": "intent-to-evidence",
          "heading": "From intent to inspectable evidence",
          "body": "Broad workspace principles become applicable project expectations and observable results. This sequence illustrates the operating loop, not a requirement to apply every standard to every project. Release, maintenance, and preservation each need evidence suited to the work.",
          "layout": "sequence",
          "items": [
            {
              "title": "Intent",
              "body": "State the problem, purpose, and intended result."
            },
            {
              "title": "Project record",
              "body": "Capture identity, boundaries, current state, and ownership."
            },
            {
              "title": "Applicable standards",
              "body": "Identify the requirements that govern this work and why they apply."
            },
            {
              "title": "Bounded work and skills",
              "body": "Define scope, authority, inputs, outputs, and acceptance criteria."
            },
            {
              "title": "Artifacts and decisions",
              "body": "Produce the result and preserve the choices made along the way."
            },
            {
              "title": "Evidence and findings",
              "body": "Record what was checked, what was observed, and what remains missing."
            },
            {
              "title": "Delivery and continuity",
              "body": "Carry the relevant records into release, maintenance, or preservation."
            }
          ]
        },
        {
          "id": "human-agent-work",
          "heading": "People set intent. Agents perform bounded work.",
          "body": "City Hall is the environment agents work inside. More context alone does not establish authority, relevance, currency, or permission. Clear task boundaries and inspectable results let people delegate substantial work while keeping consequential decisions visible.",
          "layout": "cards",
          "items": [
            {
              "title": "Human responsibility",
              "body": "Set intent, authority, exceptions, and acceptance. Review the result and record accepted decisions."
            },
            {
              "title": "Agent contribution",
              "body": "Use the current project context and applicable procedures to return artifacts, findings, and evidence within the task boundary.",
              "href": "/city-hall/ats",
              "linkLabel": "Read ATS standard"
            },
            {
              "title": "Durable handoff",
              "body": "Distinguish proposals from accepted decisions and generated output from verification. Preserve enough context for the next session."
            }
          ]
        },
        {
          "id": "sesm-in-practice",
          "heading": "A concrete example: meaning travels with an SVG",
          "body": "The City Hall component logos on this site carry SESM metadata inside each SVG. The artwork identifies a component visually; the embedded record supplies a stable asset identity, semantic description, dimensions, and a public component link. These SVGs contain raster artwork, not vector traces.",
          "layout": "cards",
          "items": [
            {
              "title": "Expectation",
              "body": "SESM defines the embedded metadata structure and distinguishes semantic validity from the SVG safe profile.",
              "href": "/city-hall/sesm",
              "linkLabel": "Read SESM standard"
            },
            {
              "title": "Artifact",
              "body": "Open the SESM logo asset and inspect its metadata block to see the structured meaning carried alongside the image.",
              "href": "/city-hall/logos/sesm.svg"
            },
            {
              "title": "Boundary",
              "body": "Metadata is descriptive, untrusted input. It is not permission to act, and its presence alone does not establish SVG safety or an audit."
            }
          ]
        },
        {
          "id": "start-small",
          "heading": "Take one useful part",
          "body": "The full Aptlantis framework is a reference implementation, not an entry requirement. Start with the recurring problem you need to solve. Combine practices only when their relationships help your work; every adoption level is a valid stopping point.",
          "layout": "cards",
          "items": [
            {
              "title": "Preserve project intent",
              "body": "Use a minimal proposal or intake record when goals and boundaries keep getting lost.",
              "href": "/city-hall/pps",
              "linkLabel": "Read PPS standard"
            },
            {
              "title": "Bound an agent task",
              "body": "Write down purpose, scope, constraints, authority, outputs, evidence, and completion criteria.",
              "href": "/city-hall/ats",
              "linkLabel": "Read ATS standard"
            },
            {
              "title": "Inspect delivery",
              "body": "Choose a delivery checklist suited to the artifact and keep missing verification visible.",
              "href": "/walkthrough/adoption",
              "linkLabel": "Explore adoption"
            }
          ]
        },
        {
          "id": "limits",
          "heading": "Visibility supports judgment",
          "body": "City Hall makes state, requirements, relationships, and exceptions easier to inspect. The effect depends on records being current and practices being applicable. It does not guarantee correctness, universal compliance, or release readiness, and it does not remove human judgment."
        }
      ]
    },
    {
      "slug": "operating-model",
      "title": "How It Works",
      "lead": "Standards define expectations. Skills guide recurring work. Records preserve what happened.",
      "sections": [
        {
          "heading": "From intent to evidence",
          "body": "A project record captures intent and current state. Applicable standards give the work boundaries. Tasks and skills guide action. Artifacts, decisions, and validation records preserve the result."
        },
        {
          "heading": "Human and agent roles",
          "body": "People set intent, authority, exceptions, and acceptance. Agents can perform bounded work using current context and return findings that another session can inspect."
        },
        {
          "heading": "Relationships matter",
          "body": "A task can name its project, a finding can cite a standard, and a release can point to its evidence. These links reduce the need to infer what governed a decision."
        }
      ]
    },
    {
      "slug": "adoption",
      "title": "Take One Useful Part",
      "lead": "The complete framework is a reference implementation, not an entry requirement.",
      "sections": [
        {
          "heading": "Start with a recurring problem",
          "body": "Choose a bounded task record when agent work is vague, a decision record when rationale disappears, or a release checklist when delivery evidence is hard to find."
        },
        {
          "heading": "Keep the useful piece",
          "body": "A checklist, skill, schema, or standard can stand alone. Combine components only when the relationships improve your workflow."
        },
        {
          "heading": "Expand deliberately",
          "body": "A standalone practice can become a compatible component and later part of a connected operating system. Every level is a valid stopping point."
        }
      ]
    },
    {
      "slug": "evidence",
      "title": "Inspect the Evidence",
      "lead": "Claims about City Hall should lead to records, artifacts, and observable work.",
      "sections": [
        {
          "heading": "What to inspect",
          "body": "The public component records show scope and maturity. Standards, schemas, templates, validation results, and release records are distinct forms of evidence and should be identified as such."
        },
        {
          "heading": "What evidence can show",
          "body": "A dated record can show that a check ran or a decision was captured. It does not by itself establish an audit, universal compliance, or production readiness."
        },
        {
          "heading": "What comes next",
          "body": "Browse the City Hall components to see which part addresses a concrete problem, then inspect its named source and available public evidence."
        }
      ]
    }
  ]
}