diff --git a/decisions/wayfinder/texas-rr-engagement.md b/decisions/wayfinder/texas-rr-engagement.md new file mode 100644 index 0000000..ea4f8bc --- /dev/null +++ b/decisions/wayfinder/texas-rr-engagement.md @@ -0,0 +1,108 @@ +--- +type: wayfinder-map +slug: texas-rr-engagement +northstar: l2-ojfbot +tracker_issue: "#344" +status: charting +--- + +# Wayfinder — texas-rr-engagement + +## Destination + +The Texas R&R engagement — the first self-funded FDE client engagement — has traversed the full +arc **lead → research → discovery → scoped delivery → sustainment** on the fleet's own SE engine: +an engagement northstar + delivery roadmap carry the work (slices ride day-run/movement-contract +machinery, `/gated-slice` discipline where gates appear), value is measured **in the customer's +numbers** (hours/week, cycle time, retained builders — never tokens), the proof-of-work dossier is +genre-complete against the 6-genre ruler (`decisions/research/2026-08-01-fde-deliverables-audit.md`), +and a **playbook shadow** has filled per completed stage — pattern capture from evidence, never +ahead of it. The boundary "absorb workflows, never the role" holds throughout (the departed +~$100K/yr admin colleague makes role-backfill the standing scope-creep threat). Serves +`ns:l2-ojfbot#P2` (every app's daily work traces to a measurable property — the engagement runs on +the same machinery) and `ns:l3-shared#P1` (a stranger can be shown the cluster doing real work +end-to-end — this is the cluster doing real *external* work). + +## Notes + +- Charted 2026-08-01. Mode: full (registry resolves, 19 entries). Anchors verified resolve-or-fail + at charting. +- **Boundary with `fde-operating-presence` (#319):** that map owns the public-presence/flywheel + half (venues, identity, distribution). This map produces sanitized artifacts; that map publishes + them. The seam itself is this map's ticket "Dossier→presence seam" — the seam decision lives + here, the surfaces live there. +- Vault reads (design-time, one-way, `adr:bonded-pair-division-of-labor` draft): + `wiki/synthesis/texas-rr-engagement-brief` (pains, candidates C1–C3, proof plan, scale + hypothesis, boundary rules), `wiki/entities/texas-rr` (verified-vs-marketing ledger; operator + intel: departed admin colleague ~$100K/yr, duties unknown), `wiki/concepts/fde-operating-presence` + (G1–G6), `wiki/concepts/construction-restoration-ai` (segment stack + economics). +- Research ground truth (2026-08-01 vault pass): portal promise "Coming Soon" ×2 confirmed + verbatim; "BBB Accredited" badge unsupported (no BBB profile); verified footprint = 4 + HomeAdvisor reviews / Carrollton address vs enterprise marketing; buy-vs-build → thin + builder-side roll-up + eval layer over commodity SaaS (Buildertrend $399+/mo, Encircle $250/mo, + CompanyCam $79/mo), never a bespoke portal build. +- Constraints standing for every ticket: research-only until the operator opens contact (agents + never perform outreach); client material private until the sanitization gate clears it; + sequential-research rule (ONE deep-research cycle at a time). + +## Decisions so far + +Pre-map rulings (grilled at charting, recorded here — not closed tickets): + +- Map identity: engagement-first — this map charts the Texas R&R traversal; the generalized + pipeline is a shadow artifact + fog, never charted ahead of evidence — Yuri, 2026-08-01 +- SE engine binding: full fleet machinery (new l1 northstar + roadmap, `/gated-slice` where gates + appear); literal ISO-15288/Vee framing ruled out — Yuri, 2026-08-01 +- Dossier home: new private engagement repo (creation is a ticket, named by the northstar ruling) + — Yuri, 2026-08-01 +- Carried from the vault brief (operator-confirmed): portal = standing first-engagement candidate, + but pain-0 (decompose the departed admin role) may outrank it; over-delivery is the strategy, + unmeasured over-delivery is the failure mode — Yuri, 2026-08-01 + +Closed tickets: + +(none — charting session) + +## Tickets + +| Ticket (title, refer-by-name) | Type | Blocked by | Status | +|-------------------------------|------|------------|--------| +| Engagement northstar: naming, properties, movement contract (#345) | grilling | — | open | +| Discovery instrument for conversation #1 (#346) | grilling | — | open | +| Dossier→presence seam: sanitization gate + permission protocol (#347) | grilling | — | open | +| DFW restoration competitor + segment teardown (#348) | research | — | open | +| Engagement repo bootstrap (private; proof-plan skeleton; fleet-onboard) (#349) | task | Engagement northstar | open | +| Engagement stage-gates + TPM discipline (#350) | grilling | Engagement northstar | open | +| Playbook shadow: format, home, capture points (#351) | grilling | Engagement stage-gates | open | +| Sustainment + exit boundary (#352) | grilling | Engagement stage-gates | open | + +Frontier at charting: Engagement northstar, Discovery instrument, Dossier→presence seam, +Competitor teardown. Recommended first work session: **Engagement northstar** (unblocks two) or +**Discovery instrument** (gates the first real-world conversation). + +## Not yet specified + +- **Generalized pipeline map / customer #2** — statable only after C1/C2 metrics exist; the scale + hypothesis's falsifiable predicates (segment, ≥60% playbook reuse, ≤2 weeks to first demo) are + written in the vault brief and parked there. +- **Commercial model beyond the documentation-rights trade** — whether engagement #2 (or a later + phase of #1) is paid, and how that changes the boundary rules. Statable after the first + engagement produces measured value. +- **seh-study / SE-competency tie-in** — whether the engagement doubles as the SE learning + vehicle; deliberately not chosen at charting (fleet machinery ruled in, literal SE framing + ruled out). Revisit only if the operator elevates it. +- **Sub-network + builder-side data access shape** — what data the 100+ subs and the pilot + builder can actually provide; statable after discovery conversation #1. +- **Engagement northstar re-anchor** — once the northstar ticket closes, whether this map + re-anchors from `l2-ojfbot` to the new `l1-*` entry; statable at that close. + +## Out of scope + +- Publication surfaces, venues, identity, flywheel — owned by `fde-operating-presence` (#319); + boundary noted at charting 2026-08-01, not a new ruling. +- Outreach/contact execution, account creation, credential handling — user-performed; safety + rule, standing; noted at charting 2026-08-01. +- Delivery slices (portal roll-up, eval checklist, intake copilot builds) — deliveries live in + the engagement roadmap once it exists; two-ledgers rule; noted at charting 2026-08-01. +- Literal ISO-15288/NASA-Vee stage framing — ruled out by operator at charting 2026-08-01 + (fleet-native gate discipline instead).