# 03: The Sequence

Eight steps. Each names what it produces and the gate that says it is done. **Steps 1 to 3 are content and need no new machinery.**

---

## Step 1. The capability block

**Produces:** a new section on the report saying what connecting this provider grants an agent.

Verb by object class by reach, reversibility marked, in the estate's primitive form. Five rows at minimum: sending audio into the world, which is irreversible; reading a credential; spending against a plan; **creating a voice**, which is the row a reader will not expect; and reading audio supplied for transcription.

**Gate:** the block names at least one capability the vendor's own documentation does not frame as a capability. If it reads like a feature list, it is wrong.

## Step 2. The tier intersection

**Produces:** one short section on the patterns page saying that the credential pattern is a property of the provider and the capability tier is a property of the tool, with the small matrix from `02` and a line for each existing tool saying which cell it sits in.

**Gate:** every experiment on the site can be pointed at exactly one cell without argument.

## Step 3. Positioning, disclosure line, and the product rule

**Produces:** three small edits. One paragraph early saying the site is narrower rather than better. A one-line disclosure at the top of each page, not only on its own page. And a standing note wherever a credential rule appears saying that it holds for a named product rather than for the vendor.

**Gate:** a reader who lands mid-site on a deep link sees the disclosure without scrolling.

## Step 4. The video walkthrough

**Produces:** one page that takes a single short script from generation through alignment to captions to a timed render, using only the experiments that already exist, with the cost and the wall-clock recorded at each stage and every claim carrying a state.

**This is the highest-value new page on the site** and it needs no new capability, only assembly.

**Gate:** somebody with a key can follow it end to end and reach the same artefact. The cost is measured, not projected. What broke is written down.

## Step 5. What was tried and abandoned

**Produces:** a dated page listing experiments run and not pursued, each with the result and the reason.

Seed it from step 4, because a walkthrough always produces rejected attempts, and from the concurrency and text-handling experiments, which exist to find limits and therefore have negative results by design.

**Gate:** the page has at least three entries and none of them is a euphemism.

## Step 6. Tier three, resolved either way

**Produces:** either a working tier-three tool, or the `pattern-three` page carrying the specification state prominently with a sentence saying what would have to ship for it to become real.

**The second is acceptable and should be done first regardless**, because it is honest today and takes an hour.

**Gate:** no page implies that pattern three works here today.

## Step 7. Composition and the machine surface

**Produces:** cross-links pointing at pages rather than domains, one sentence saying which sense of provider this site means, and `llms-full.txt`.

**Gate:** every outbound link into the family lands on the page that answers the question the link text promises.

## Step 8. What we use it for

**Produces:** the thin section made real, naming actual workflows this provider is used for in this estate.

**Deliberately last**, because it cannot be written honestly until step 4 has produced a real workload.

**Gate:** every workflow named is one somebody has actually run.

---

## Order At A Glance

```
   1 capability block        content only, no machinery
   2 tier intersection       content only
   3 positioning + rules     content only
        |
        v
   4 video walkthrough       the demonstration, assembled from what exists
        |
        +---> 5 tried and abandoned      seeded by step 4
        |
   6 tier three resolved     honest label now, tool later
   7 composition + llms-full
        |
        v
   8 what we use it for      needs step 4 to have happened
```

## Two Things Held Outside This Plan

**The speech counterpart to the listen call** is a platform proposal rather than a site task. Raise it, do not build it here.

**The grant application** is the project lead's, and the disclosures page must record it as pending before it is made rather than after it is granted. That ordering is the whole value of having built the page early.

---

*Released under CC BY 4.0.*