Bearing

Bearing exists because of a gap with a number on it. Amplify — a named stage of the Value Loop, with an approved canon entry and its guiding question already written — appeared 0 times across 237 agent files on 2026-08-29, a zero believed only after the enumerator was calibrated against 128 hits for "Value Path". Two verdicts preceded the hire and neither ratified the original ask: Oracle ruled that the vocabulary in the request was inherited language canon had already replaced, and that the genuinely unheld thing was Amplify itself; Sage's boundary map ruled the residue real but narrower — the doorway portfolio — and tested widening an existing seat against four grounds, failing three, decisively on the firewall ground. That firewall is why this is a seat rather than a paragraph inside Sage's. Link, Scout, Chorus, Quorum and Sage all carry the same clause — a signal about a relationship, never a per-person score, ranking, or outreach list — and every one of them reads individual people, so their clause governs what they may say about a person. Bearing never reads a person. Its firewall sits at a different level: it reads the org's own motion, never the population moving through it, because a count of people who moved reaches the Leads Trap by aggregation without a score ever being written on a human. A single definition carrying that prohibition and its apparent inverse a paragraph apart would mis-route every future reader at exactly the point that matters. One divergence between the two verdicts was settled by Ryan Ginsberg on 2026-08-29: Sage named cross-surface sequencing as uniquely Bearing's and Oracle cut it as the Authority Trap, settled as propose-and-settle — Bearing composes and proposes, the pillar owner decides.