Skip to content

docs: five builds — pick what you are building, and a gate that keeps public links public - #1

Merged
rpedersen3 merged 2 commits into
mainfrom
docs/operating-ladder
Oct 12, 2026
Merged

rpedersen3 merged 2 commits into
mainfrom
docs/operating-ladder

Conversation

@rpedersen3

@rpedersen3 rpedersen3 commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

A developer arriving at this kit could not tell which of five very different things they were building, and three of the five had no guide at all.

docs/builds.md names them — an app · a behaviour · a service agent · an estate · a town — says how to tell which one you are doing, and sends you to exactly one guide.

New guides for the ones that had none:

  • docs/build-a-service-agent.md — the two shapes (hosted: no app at all; self-hosted: the Service Host embedded), the four birthrights a charter must finish or stop, how another person's agent reaches it under her grant, and a verification whose fifth row is the one that fails in practice. Honest about service-host being early and create-app --kind service not yet shipped.
  • docs/authoring-skills.md — the execution contract in a playbook's frontmatter, field by field, so a capability is defined once and the agent surfaces and UX behaviour are projections of it.
  • docs/estate-anatomy.md — the parts of an estate in substrate terms, public for the first time.
  • docs/operating.md — the ladder for builds 4 and 5.

scripts/check-public-links.mjs is the mechanism, wired into pnpm check. This kit is the public face of private source repositories, and the easy mistake is a link into one: it renders for us and 404s for everyone else. The gate found nine already here — the skills corpus, the source monorepo and the findings ledger were all linked into private repositories from the public README.

Companion changes, already on their repos' default branches: ap-town (new-town runbook, publish-an-estate, its own link gate), the site (/build/paths, /architecture/operating), and the skills site's landing page. Those link here, so merging this is what makes them resolve.

🤖 Generated with Claude Code

rpedersen3 and others added 2 commits October 11, 2026 17:45
…te or a town

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…s public

A developer arriving here could not tell which of five very different things they were building, and three of
the five had no guide at all. docs/builds.md names them (an app · a behaviour · a service agent · an estate · a
town), says how to tell which one you are doing, and sends you to exactly one guide.

New guides for the two that had none:
  - build-a-service-agent.md — the two shapes (hosted: no app at all; self-hosted: the Service Host embedded),
    the four birthrights a charter must finish or stop, how another person's agent reaches it under HER grant,
    and the verification whose fifth row is the one that fails in practice.
  - authoring-skills.md — the execution contract in a playbook's frontmatter, field by field, so a capability is
    defined once and the agent surfaces and UX behaviour are projections of it.
  - estate-anatomy.md — the parts of an estate in substrate terms, public for the first time.

check:public-links is the mechanism, not the intention. This kit is the public face of private source
repositories, and the easy mistake is a link into one: it renders for us and 404s for everyone else. The gate
found nine already here — the skills corpus, the source monorepo and the findings ledger were all linked into
private repositories from the public README. They now point at the live corpus, the site and the audits page.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@rpedersen3 rpedersen3 changed the title docs: the operator's ladder docs: five builds — pick what you are building, and a gate that keeps public links public Oct 12, 2026
@rpedersen3
rpedersen3 merged commit 64c8118 into main Oct 12, 2026
3 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant