Five wires between organs that already exist and the Slack mouth that cannot see them — so Alie’s Cement Creek question gets an Arby-grade answer from Neo. All three calls ruled: one flip, no ceiling, team scope confirmed.
Today, if Alie asks “Did Robert send Cement Creek the checkout link?” Neo answers with a shrug — politely, honestly (the never-overclaim and always-carry contracts are live), but a shrug. He cannot see who Robert is, what’s in the work queue, any signed client, or any payment status. Every one of those organs already exists — in his own body or in DE Brain’s.
After this ships, the same question gets an Arby-grade answer from Neo: the account pulled live from DE Brain, the missing-Stripe-link gap named, the honest uncertainty stated, and a next step offered. Same brain as Arby for company truth; Neo’s own memory for Robert’s world. That was your Call 3, already ruled — this spec makes it real.
Step-back, answered: the two deeper plans under this one (what Neo is next to Arby; whether this is really “general tool use”) were caught and settled — Call 3 ruled the first; the toolset stays small, listed, and read-only for the second. And the memory precondition is met: the diary bound landed, so Neo can take in more of the world without the old memory deaths.
person:slack:U0D3K48GZ → canonical Robert. Lane path resolves event.personRef through canonicalPersonRef (person-basis.ts:263) before personFileRows (call site: eve-slack-lane-live.ts:434). Gates [M]: Plato backward-reach shows the lane imports person-basis.js; seed-presence check; fixture proves canonical rows differ from raw rows.workQueueSnapshot injected at the existing seam-wiring site (worker.ts lane block beside readEntityFile/activeEntries); read-only snapshot of the cycle’s built queue (buildWorkQueue, imported worker.ts:142). Gates [M]: “tell me about my work queue” fixture composes queue rows; queue questions stop routing exclusively into the ask ledger; byte-identical with the flag off.de-brain-consult.ts on the salesforce.ts transport boundary (salesforce.ts:15-24 pattern): injected fetcher, read-only allowlist (account_360, search_account_cases, read-only query_salesforce), new secret DE_BRAIN_TOKEN, hard timeout, degrade-but-label (status “down” + detail, never fabricated rows), trust tiers per field. Read-through invariant [M]: Plato forward-reach from the consult module excludes every store seam. Courts [J]: Cement-Creek fixture (mocked rows → must cite source, name the gap, end at a pickup; contradicted fixture = the live “no known entity address” reply MUST fail) and degrade fixture (timeout → honest “couldn’t check”; invented account facts MUST fail).billing_payment_status declared at eve-slack-lane.ts:52, zero producing return sites today (all emit entity_status). Producer maps consult result → typed lookup result with per-field trust tiers. Gates [M]: producer-count grep flips 0→≥1; regression fixture: closed-won account, Stripe link missing → billing_payment_status with the gap named.REACH_TOOLS = RUNG2_TOOLS (eve-slack-lane.ts:304) + the four reach tools; enumerated const, no dynamic registry. Budgets extend RUNG2 constants (:38-40) — max ~8 calls, walk phase per Q2 ruling. Tool-call receipts enter the compose input; the Phase-0 [M] regression extends: claim naming a source with no matching receipt → red. Flag EVE_SLACK_REACH (“1” enables W1–W5); NOTE the existing unrelated REACH secret gates the reach-detector (worker.ts:557) — name collision deliberately avoided, do not touch it. OFF → byte-identical.All three answered on the v1 surface. Recorded here; nothing open on this spec.
All five wires land behind ONE flag and flip together. Your words: “One flip… I agree with your recommendation.”
An honest “digging into this — give me a minute” interim message whenever the walk runs long; never a truncated answer at an arbitrary cutoff.
Consult-backed answers may reach team channels, per the audience-table rulings. Your words: “also agreed.”
Real, bounded by Q2’s design. The knock’s instant ack is what keeps a 40-second dig from feeling like the old 11-minute silence.
The consult degrades honestly — “I couldn’t check the company system just now” — never a fabricated answer. Same degrade-but-label discipline as every existing source.
More tools, more things to falsely claim. The twin contracts get sharper teeth: every claim naming a source must carry the receipt of the actual call — checked mechanically, not by vibes.
The consult is read-through by construction — a structural gate asserts the consult path cannot write to any store. The diary-bound lesson applies to every byte.
Reference strip — identity seed + join · queue seam · consult transport + courts · payment producer · REACH_TOOLS + flag. Builds start only after the engine bay is cleared; verdict legs run as ruled (pair on the consult transport — new external call carrying a service token). Canonical source: docs/ai/design/slack-reach-2026-07-17.md.