Historical snapshot, 25 October 2026. The body below is preserved as received. The completed SMS CRM chapters subsequently retained at
9986480dare now available through the current customer guide. Its chapter-specific receipts and limits supersede this earlier no-chapters inventory.
SMS CRM evidence-status index
Every row below states what evidence actually exists for an SMS CRM area, what kind it is (source-inspection / rendered observation / closed-unqualified / none), and where the record lives. This index is the complete and honest inventory behind the SMS CRM guides front door. It was assembled on 25 October 2026 from the retained ledgers and evidence maps of this repository; no journey was rerun to produce it.
Status vocabulary
- SOURCE-INSPECTION — a retained record proving what code/files exist. It is not journey evidence and supports no customer-behavior claim.
- RENDERED OBSERVATION — a screenshot of the surface captured during a qualified journey for a different product area. It proves the surface rendered; it proves no SMS CRM capability.
- CLOSED-UNQUALIFIED — an attempt or captured-frame ambition that was closed because the surface did not exist or the run did not qualify. These get no working-capability claims and are listed as documented-pending-evidence.
- NONE — no retained record at all.
The rows
1. SMS CRM overview and activation — SOURCE-INSPECTION only
- Record: the Detailed52 (D52) lane's source checks (2026-10-24,
ledger
C:/CT-ZCODE3244/zcode-full-plan24-3244/lane-3310-d52-ledger.json,sourceChecks.D16.F02) state thatsms-crm-contacts"surface mounts viasms-crm-overview.tsxbehindsmsCrmActivation.ts" and that the whole family is gated behind/v1/identity/businessessms-product resolution. - What this proves: the components exist in the source tree and how they gate. What it does not prove: any customer journey through them.
2. SMS CRM contacts management — one RENDERED OBSERVATION
- Record: the BATCH3456 journeys lane's final passing run
(2026-10-24T12:29Z,
codex/zcode-3456-journeys @ 9d2136cb, 3 journeys, one chromium run, exit 0) rendered the tenant's contacts-management surface in leg B4 of journey B — "reached through the product hub for this dual-product tenant" — listing the imported test contacts. The screenshot is retained byte-exact in this repository:docs/user-guides/convotide/contacts/assets/contacts-import/04-sms-crm-contacts-management.png(shown as step 4 of the contacts import chapter, whose evidence standing — local candidate, Chief acceptance open — applies). - What this proves: the surface rendered with imported contacts in one synthetic dual-product tenant. What it does not prove: search, editing, tagging, deletion, consent handling or any other behavior of that surface.
3. Contacts import-validation summary (D52 row D16.F02) — CLOSED-UNQUALIFIED, surface absent
- Record: the same D52 ledger's finding, verbatim in substance: the
captured frame's controls — "Ready For Use badge, Total/Valid/Invalid
summary cards, First/Last/Contact table headers, back nav" — "do NOT
exist in this repo's surfaces (grep-verified absent)";
apps/workspace/components/sms-crm-contacts.tsx:68-76is "search + count + capped-notice only", and "sms-crm-contacts is a different surface gated behind /v1/identity/businesses sms-product resolution. NOT a ready row without a Chief surface decision." The lane'shonestNotRunrecords the attempt as NOT attempted for exactly this reason; the row was routed as "the repo can build the API+UI once Chief names the surface" (owner note in the same record). - Standing: documented-pending-evidence. The ambition is recorded; the surface does not exist; no SMS CRM import-validation behavior is claimed anywhere in these guides.
4. SMS CRM visual approval, 2026-10-13 — layout only, explicitly not guidable
- Record: the older guide evidence map (docs/user-guide/evidence-map.md) lists: "SMS CRM visual approval (2026-10-13, layout only) — No chapter: functional acceptance remains required; instructions are not invented from a visual-only approval."
- Standing: a layout approval is not functional evidence. No chapter, here or in the older trees, was ever written from it.
5. Everything else in SMS CRM — NONE
- Campaigns, bots, analytics, billing, settings, numbers, seats and any other surface inside the SMS CRM product: no executed, qualified journey evidence is retained in the FULL3747 lane ledgers, the 3244 lane ledgers, the older evidence maps, or the sibling guide branches (searched 2026-10-25; the retained ledgers' SMS CRM mentions are exhausted by rows 1–4 above).
- Notably, the O14 evidence matrix's 62 rows — 61 executed green by the FULL3747-O14EV lane, 1 (O03.22) carried open to the browser lane — were executed against the WhatsApp product family surfaces, not the SMS CRM family; they are cited throughout the ConvoTide tree and never as SMS CRM evidence.
The documented-pending-evidence list (journeys a chapter needs)
- Activating/reaching the SMS CRM area as a customer (the gate journey).
- Contacts management behaviors beyond rendering: search, edit, tag, delete, consent view.
- The import-validation summary surface — blocked on a Chief surface decision and build (row 3); until the surface exists there is nothing to journey.
- Every other SMS CRM surface's core journeys (campaigns, analytics, billing, settings) — none attempted, none qualified.
A chapter for any row above will be written only from that row's own qualified receipts — never from the records on this page.