Eight named functions on /about, with the biographies moved to meet the site's claims

Decision. /about now carries a "Leadership & functions" section listing the eight working functions of the division, each with a name and a remit, directly beneath the four signing offices. Where a supplied biography asserted more than the rest of the site asserts, the biography was edited and the site was left alone — three such edits, listed below.

The names, and why they were held for one round. The section was specified with eight names to publish as written. I shipped one and held seven pending a confirmation, then published all eight once the owner confirmed each is a real person who has agreed to appear. The hold is recorded here rather than quietly dropped, because the rule that produced it still governs this file: LeadershipRole.name has always carried "Empty until a real, consenting individual is published. Never invent one," and the first entry on /corrections — shipped the same day — is the withdrawal of five case studies that named contractors as customers when none of them were. Publishing unconfirmed colleagues one click from that page would have made the corrections record read as theatre. Confirmation is the whole difference between the two situations, and it is cheap to ask for.

Three biographies moved to meet published claims. The instruction was that where a biography and the site disagree, the biography moves. All three cases:

1. 1.Head of Product Engineering read "SOC 2-compliant SaaS infrastructure." SOC 2 Type II is an audit in flight here, not a report we hold, and lib/legal-documents.ts commits that it "is not represented as achieved anywhere on this site or in any document we issue." A published biography is a document we issue. It now reads "built to the SOC 2 Type II control set now under audit," which is true today and stays true when the report lands.
2. 2.Customer Success Manager read "long-term retention across active contractor accounts." /corrections C-001 states in terms that the named contractors were not customers, and docs/directory-listings.md records that the division has none yet. The remit now states what the function owns, which is true on the first account and on the hundredth.
3. 3.Engineering Lead read "to ensure zero margin variance." What the product does, and what /platform/cpq, the pricing plans and the contact engine all say it does, is enforce a margin floor at the line as the quote is built. A floor is a guarantee we hold; zero variance is a guarantee about the buyer's business that we cannot make. It now uses the same wording as every other surface.

Why the roles carry their own weight. A role title and a remit stay true through any staffing change, which is why they are modelled separately from the name that currently holds them. LEADERSHIP above answers "who signs" for a procurement reviewer; this answers "what is staffed here" for a reader working out whether there is an organisation behind the product.

What would make this wrong. If any of the eight stops being accurate — a person leaves, or a remit is overtaken by how the work is actually divided — the entry is wrong from that day, and a stale org chart on a page that also hosts a corrections record is worse than no org chart. The maintenance burden is real and it is accepted deliberately: this file is read on every /about build, so the review point is any change to headcount.