Agents.

This site has a machine face.

Your agent reads this site too. The catalogue is published as JSON, and every project’s manifest, requirements and agent instructions are copied here unmodified from its release.

curl -s https://runeditrun.com/agents/catalogue.json

the whole catalogue, one request

catalogue.json · entries: 14
seeds.json · releases: 14
agents/seeds/ · documents: 114
installable: 1

Endpoints

Generated on every build from the pinned project releases, never copied by hand.

/agents/catalogue.jsonEvery project: identity, category, version, licence, availability (installable or in-development), its page and its documents.json · 14 entries
/data/seeds.jsonThe full feed the pages are built from, with each release’s requirements and provenance. For the project the plans offer, its stage (maturity) is the plans’ current status; its release’s own wording stays in its manifest.json · 14 releases
/agents/seeds/<id>/seed.jsonA project’s manifest: capabilities mapped to requirements, outside services with reasons, extension points, limits, operating cost and deployment needs.json · per project
/agents/seeds/<id>/CONTRACT.mdWhat the project does, clause by clause, with stable IDs. Coverage and unmet requirements are recorded separately.markdown · per project
/agents/seeds/<id>/AGENTS.mdInstructions for the agent that maintains an installation: its source, requirements and checks.markdown · per project
/llms.txtA short plain-text index of the site, the projects and the plans.text

Each project page, under /projects/, lists every document its release publishes, such as its README, baseline, handover and operating description.

One entry, as your agent reads it

/agents/catalogue.json
happytohelp

{
  "id": "happytohelp",
  "name": "HappyToHelp",
  "category": "support",
  "licence": "MIT",
  "version": "0.2.1",
  "availability": "installable",
  "clauseCount": 14,
  "url": "/projects/happytohelp",
  "manifest": "/agents/seeds/happytohelp/seed.json",
  "contract": "/agents/seeds/happytohelp/CONTRACT.md"
}

ten of its keys; the full entry also carries authoring, releaseProvenance, spine, replaces, oneLiner, license, repository, install

Commands that work today

HappyToHelp: HappyToHelp is the one project with public source. Its Standalone quickstart gives the prerequisites and the commands that clone and install it, including --agent for setup that your agent runs. After that, its README.md, OPERATIONS.md and AGENTS.md are the reference for developing, verifying and deploying it.
In development: The projects in development publish documents but no source yet, so there is nothing of theirs to clone or run.

Written for your agent

Any source can change: Use a project’s guidance and requirements to change anything, including UI, core logic, schema and infrastructure. Extension points are conveniences, not limits.
Evidence, not assertions: Run the project’s own checks and read its coverage gaps. A passing suite or a clean merge alone does not prove that the owner’s intent and existing data survive a change.
Nothing calls home: A project that publishes a BASELINE.md requires that an installation makes no request to Run Edit Run or its author. Read the release’s evidence for what is verified; catalogue metadata alone does not establish it.