Skip to main content
No family pages are published yet. They are generated output, and the generator that emits them has not landed. This page is the frame: it says what each family page will carry and where it comes from, so that what appears here later is checkable against a stated contract rather than taken on trust.

​
One page per errand family

An errand family is a group of errands that share a shape — reading the terms of the debts you carry, getting the most out of an employer retirement plan, asking a counterparty to change something. Each family gets one page in this section. Every family page carries the same seven things, for every errand in it: The ceiling is the field to read first. It is the difference between “this will be done” and “this will be brought to the last step and handed to you”, and it is published before you delegate rather than discovered afterwards.

​
These pages are generated, and never hand-edited

The family pages are emitted from the capabilities manifest — the same generated record the connector serves to your assistant over MCP, produced by the same generator that emits the instructions the runtime follows. One fact, one source. That is what makes a published ceiling worth anything. If a page were written by hand it could say READY while the runtime allowed something else. Because the page, the manifest and the runtime’s instructions come out of one generator, a ceiling that moves moves everywhere at once — and shows up in the changelog.

​
The contract the generator emits into

Recorded here so that a page appearing in this section can be checked against it:
  • Source of truth — the capabilities manifest, built from the errand corpus at a pinned commit.
  • Output — one MDX file per family under capabilities/, with title and description front-matter and the seven fields above, in that order, for each errand.
  • Navigation — each generated page is added to the “What Hence can do” group in the site config.
  • Committed, not built here — generated pages are committed to the repository like any other source, and a regenerate-and-diff check is what keeps them honest.
  • Never hand-edited. A correction belongs in the corpus or the generator; an edit made here is overwritten and, worse, is invisible until it is.

​
Until then

The errands in the first wave, and their published ceilings, are listed on What Hence executes. Those are the ceilings the family pages will carry.