Post-freeze update, October 1 after 20:00 Mountain: Howard has selected all three headline themes below as October 15 campaigns. The table remains a historical comparison of earlier source versions. Use the current three-route index for Map v0006, Product v0004, Nobody v0002, their corrected clean Event bodies, and the unified BOFU field packet. The old “no route selected” statement below means no specific whole composition had been chosen for prospect traffic at the time of that comparison; it does not undo Howard's three-anchor decision.
October 1, 2026. Internal editorial comparison for Howard, Bernoulli3, Prigenix, Ari, and Tess. No route is selected for prospect traffic. There is one LinkedIn Event and no editable native invitation message. Howard alone will paste its eventual title/description and operate invitations. Additive public candidate sites can be reviewed first. The packet index links all current and historical copy.
| Steadier Map v0005 | One Product / Many Views v0003 | Nobody Decided v0001 | |
|---|---|---|---|
| First headline | “When the tools move fast, your team needs a steadier map.” | “Everyone saw the same AI demo. Did they see the same product?” | “The most expensive AI decision may be the one nobody decided to make.” |
| First felt stake | The team's bearings and capacity as tools and expectations move. | Different roles leave one demonstration with different ideas of what it proved. | A consequential choice may have been made, but whether, what, and who or what decided remain uncertain. |
| Immediate emotional promise | More capability and agility together, with a credible guide. | A shared picture across builders, managers, product, and the people who inherit the result. | Recognition of costly uncertainty without premature resolution; human agency remains visible. |
| Owned design | Human shared room, warm editorial clarity or carefully integrated dark treatment. | The published product site's strong warm human/system composition is the control. | Black across every root and leaf, Designery grammar, black-fading image edges, people present. |
| Deeper modules | Product's many views; the paired system-fit cost question; Howard's work; team ability/agility. | Prototype proof; one product/many roles; Howard; team ability/agility. | What may have been decided; who lives with it; Howard. Its team-benefit leaf still needs integration. |
| Candidate Event-description count | 4,479 characters | 4,729 characters | 4,400 characters |
Counts are wc -m on the fenced text only, excluding Markdown fences and operator notes, before any optional owned-site URL line. Product has only about 271 characters of headroom under the working 5,000-character cap, so bind its owned link concisely and re-count before Howard pastes. Titles/covers and the actual LinkedIn field must be inspected for truncation. No agentic LinkedIn access.
Howard's stronger AIGENEXUS editorial reference supplies the wider human-augmentation framing; its logotype/slogan is not to be redefined by these campaign drafts. The published product page is a serious control, not a generic wireframe. The dark-edge event PNG demonstrates image edges fading into black; its baked “faster code cost” wording does not nominate it as the main funnel cover. The shared-room PNG remains a floor for showing people and layered work. Bernoulli3's current composition must be judged at desktop and phone width, against headline, image, below-fold rhythm, proof, and seat action together. Reader-visible captions must not decode or deflate the image's uncertainty.
The Decision Economics question retains a strong place inside the Map/system-fit module when head and subhead are immediately adjacent: “What does faster code cost?” / “When the hard part is deciding whether it belongs in the real system.” Never strand the shorter question in a crop, thumbnail, title, or mobile break. Decision Economics v0002 is comparative history, not the selected whole-funnel lead. Its v0001 contains Howard's vetoed “best return” line and is rejected history only.
Two purchase paths, with one secondary upsell
For each candidate, a ready buyer follows the Event registration field directly to that route's matched TicketSpice page. The first buyer-facing heading echoes the route's full hook, October 15 / $250 facts appear near the seat selector, and the proof is concise enough to support rather than obstruct purchase. One person or several colleagues can buy ordinary public tickets.
A curious visitor follows a second Event link to that route's owned root, explores the leaf relevant to their work, and can reach the same matched checkout from root or leaf. Banking, telecom, enterprise IT, hardware-plus-software product development, and independent practice are inclusive examples, not rigid segmentation. Each leaf offers depth while maintaining a clear ticket action and return path. The native Event cannot deliver different descriptions to different invitees; these are whole-experience alternatives for editorial comparison, not a claim of per-invite A/B assignment.
A company-private exclusive is a secondary branch, not a substitute for the public $250 action. The repetition-refined team-benefit copy starts with Howard-endorsed “More ability. More agility. What could AI4DEV make possible for your team?” It carries exact John Schur excerpts and his whole published recommendation lower on the page, while reducing redundant attribution wrappers. The complete quoted block matches Howard's canonical supplied text byte-for-byte (SHA-256 ad16d61c9eb832317730555ee6721a4078cc0c5eb9f3961c8e19d11ec64ada8a). Keep the public ticket CTA visible on the team page, bind each route's exact live purchaser URL, and replace the localhost placeholder with an owned-domain inquiry link before publication. Private commercial floors belong only in internal planning, never public page, image, or metadata.
Current candidate-to-public bindings
- Steadier Map: full source exists; Bernoulli3 art, owned root/leaves, and a matched new TicketSpice page are not yet jointly published/read back.
MAP_*keys remain author-only. - One Product / Many Views: an earlier product page is live with strong visual composition, but its existing checkout link and some phrasing are older. The new full v0003 journey needs additive matched owned/checkout publication;
PRODUCT_*keys remain author-only. - Nobody Decided: a Compass edition is public as a previous expression; it must not be mistaken for the new full-hook black-canvas candidate. Current route-B TicketSpice paraphrases bury or misinterpret the hook. The full candidate remains a copy/art/publication task, not an approved live journey.
- Team/private branch: Bernoulli3 and Ari report an additive Studio edition publicly exact with the endorsed ability/agility headline and full testimonial. Its public ticket and private inquiry links still need review against the eventual chosen main route and Howard's owned-domain traffic preference.
TicketSpice's operational Page Title, first visible H1, ticket name, issued-ticket Event Name, social/SEO, image, URL slug, and card descriptor are separate controls. Ari's provider-side readback is required for the matched purchaser pages. None of the candidate copy may be described as a paid-order test, receipt test, or prospect launch merely because a public draft URL exists. Howard's selection follows review of the whole copy/image/layout experience.