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
Invited accounts can choose Assisted in their own Cloudflare and GitHub accounts, or Managed on Run Edit Run hosting. The app shows availability before checkout. New accounts are by request: email us the project and plan you want. See plans.
- catalogue.json · entries
- 16
- seeds.json · releases
- 16
- agents/seeds/ · documents
- 167
- installable
- 16
Endpoints
Generated on every build from the pinned project releases, never copied by hand.
- /agents/catalogue.jsonEvery project: identity, category, version, licence, availability (
installableorin-development), its page and its documents. - /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. - /agents/seeds/<id>/seed.jsonA project’s manifest: capabilities mapped to requirements, outside services with reasons, extension points, limits, operating cost and deployment needs.
- /agents/seeds/<id>/CONTRACT.mdWhat the project does, clause by clause, with stable IDs. Coverage and unmet requirements are recorded separately.
- /agents/seeds/<id>/AGENTS.mdInstructions for the agent that maintains an installation: its source, requirements and checks.
- /llms.txtA short plain-text index of the site, the projects and the plans.
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.4.31",
"availability": "installable",
"clauseCount": 26,
"url": "/projects/happytohelp",
"manifest": "/agents/seeds/happytohelp/seed.json",
"contract": "/agents/seeds/happytohelp/CONTRACT.md"
}
ten of its keys; the full entry also carries releaseProvenance, publisherManifest, sitePresentation, spine, replaces, oneLiner, repository, releasePin, releaseSignature
Commands that work today
- Public source
- HappyToHelp, Lamp, Pencil, Dial, Slate, Cradle, Uptime, Penny, Oncall, Spool, Orbit, Nook, Mango, Vector, coffer and Pantry publish source for self-hosting. Follow each project's tagged documents for setup; source availability does not promise Run Edit Run installation or hosting.
- Run one
- Each available project runs on your own computer with one line from its page or /llms.txt:
npx -y @runeditrun/rer dev just-every/run-<project>clones its public source, installs it, sets up a local owner and starts it; nothing is deployed. HappyToHelp’s Standalone quickstart lists the prerequisites. - In a checkout
rer describe --jsonlists the project’s commands and their effects,rer doctorchecks the local setup andrer verifyruns its checks. ItsAGENTS.md,README.mdandOPERATIONS.mdare the reference for changing, verifying and deploying it.- Apps in Run Edit Run
- The app offers HappyToHelp, Lamp, Cradle, Dial, Mango, Nook, Oncall, Orbit, Pencil, Penny, Slate, Spool, Uptime and Vector. Invited accounts can choose Assisted or Managed; the app confirms availability before checkout. Other published projects can be imported from their public GitHub repositories, subject to the app’s setup checks.
- 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.mdrequires 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.