Components

This site

A consumer of the contract, never a source of it. It explains the framework; it does not define it.

The page you are reading is a component, and it is declared in the same contract as every other part. That is less strange than it sounds, and it fixes something specific.

The dependency runs one way

This site reads ecosystem.yaml from the public repository. The framework does not know the site exists, has no reference to it, and would be unaffected if it were deleted tomorrow.

Inverting that would make the framework depend on a website. A version number defined by whatever a page happened to render, component descriptions that only existed as marketing copy, a check that passed because the site agreed with itself. The direction is not a preference; it is what keeps the contract worth trusting.

Which is why this page can say what it is missing

Eight of the nine components have no page of their own yet. The build knows that — it reads the contract, compares it against what has been written, and says so rather than rendering a convincing subset.

A manual that only shows what it has finished is a manual you cannot tell is incomplete.

What is rendered and what is written

Everything factual on a component page — what it reads, what it writes, what it depends on, which repository documents it — comes from the contract at build time. The prose around it is written here, because the contract carries what a component is and not what a reader needs in order to understand it.

If the two ever disagree, the contract is right and this page is a bug.

This part is public

The site is public. Its source is not — which is worth stating rather than leaving to be discovered.

From ecosystem.yaml, contract 41 · core-skills 1.89.4 · read at build 2026-10-08