Skip to content

How this site is derived

The website is a projection of the repository, built the way the tool asks projects to build their own instructions.

Ownership

layerownslives in
product truthpolicy schema, profiles, worker instructions, the CLIshare/skeleton/**, bin/, lib/
public narrativewhat it is, why, how, what it refusesREADME.md, docs/**
claimsevery capability, with status, source, implementation, testdocs/CLAIMS.yaml
marketing copyheadline, leads, button labels; no claims, no numbers, a line budgetsite/data/marketing.toml
hand-written settingsthe manifesto, the homepage's order and budgets, the navigation, the challenge page, the proof tiles, how each kind is published; words, order and settings, never a countsite/data/*.toml
hand-written pageslong-form articles and pages like this one; a number they state is cited from site/data/figures.toml, and scripts/site-check refuses one typed beside a counted nounsite/content-src/**
cited figureseach number hand-written prose may state: its name, the generated file it is read from at build, and what it countssite/data/figures.toml
derived datastable JSON the templates readsite/data/generated/** (committed, checked)
derived contentcanonical Markdown with generated front mattersite/content/docs/** (gitignored, rebuilt)
presentationZola templates, Flowbite components, Tailwind utilities, Alpine enhancementssite/templates/**, site/tailwind.css
outputthe static sitesite/public/**

Pipeline

The pipeline is drawn at the foot of this page rather than typed here. It is rendered from site/data/generated/diagrams.json, which the generator writes from the inputs it actually read, so a canonical file added to the derivation appears in the picture without anyone redrawing it. The block that used to sit here was a second, hand-maintained copy of that same diagram, and the two already named different things.

Sync guarantee

scripts/generate-site-data --check regenerates into a temporary directory and diffs it against the committed site/data/generated/. A difference fails the build. The input hash in source.json covers every canonical file the generator reads; it appears in the footer of every page. A regression test changes one canonical value in a scratch copy and asserts the derived data changes with it, so the derivation is proven rather than assumed.

What is never edited by hand

site/data/generated/**, site/content/docs/**, site/static/app.css, site/static/js/**, site/public/**. Change the canonical file; rebuild.

How this site is derivedfrom generate-site-data inputs
flowchart LR
    subgraph canonical
        A[share/skeleton]
        B[docs + README]
        C[docs/CLAIMS.yaml]
    end
    G[scripts/generate-site-data]
    D[(site/data/generated)]
    Z[Zola]
    F[Tailwind + Flowbite + Alpine]
    P[GitHub Pages]
    A --> G
    B --> G
    C --> G
    G --> D --> Z --> F --> P
Policy to instruction filesfrom share/skeleton/policy.yaml projections
flowchart TD
    P[.ai/repo/policy.yaml]
    U[majordomus update]
    P --> U
    U --> T0["AGENTS.md<br/><small>agents</small>"]
    U --> T1["CLAUDE.md<br/><small>claude-code</small>"]
    U --> T2["GEMINI.md<br/><small>gemini</small>"]
    T0 -.->|stamp| D[majordomus doctor]
Linked from this diagram (2)

This page is about the website. For the program the website is about — every module of the CLI and every file it reads and writes, scanned out of the shell sources on each build — see the program map.

Searches the titles and descriptions of every page this site publishes.