docs(bryn): bucket the hero flow into two stage groups [BRYN-1086] - #899
Open
kevinhcolgan wants to merge 10 commits into
Open
docs(bryn): bucket the hero flow into two stage groups [BRYN-1086]#899kevinhcolgan wants to merge 10 commits into
kevinhcolgan wants to merge 10 commits into
Conversation
Per GTM feedback, the pipeline reads as two bigger groups rather than a chain of steps: 'Noise to signal' (sources, identity, signals, score) and 'Play agent engine' (Plays and the actions they run). The suggested 'Noise to Signal Intelligence' label was adjusted: 'intelligence' is on the brand book's banned list. Adds subgraph title margins and cluster theming to the shared mermaid configs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The raw events entering identity resolution are now named (page views ⬩ clicks, product events, your events) so the 'noise' reads as noise, and the cross-bucket edge says what crosses it: a scored signal triggers a Play. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…BRYN-1086] Outputs read as effect categories with real connectors as examples: Alerts (Slack ⬩ Teams ⬩ Discord) and Tool updates (CRM ⬩ sequences ⬩ webhooks), matching the engine's verbs-name-the-effect model. Jira and the suggested ellipsis were dropped: no Jira connector exists today and three real examples imply extensibility without over-promising. The hand-off label becomes 'scored signals trigger Plays'. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
dagre centers a parent over its middle child, not the cluster; widening the on-page node balances the outer children so the middle child (and Plays above it) lands on the cluster midline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…RYN-1086] Moving the pixel to the middle of the source row centres the chain the same way the engine bucket was fixed, and it earns its place: the visitor-to-pixel edge now forms a single straight spine from Website visitor down to Plays, with product analytics and the webhook balanced either side. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A dotted return edge from the Play agent engine to the website visitor, labelled 'personalized content and outreach': on-page personalization reaches them directly, sequences and rep follow-up reach them through the Plays. Drawn from the whole engine block deliberately; that is the mental-model altitude for the hero, with the per-verb detail living in the Play anatomy diagram. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…N-1086] The loop-back version put the engine's return arrow at the top of the diagram, starting the story at its own ending. Unrolled instead: one arrow, 'personalized content and outreach', drops from the engine to a terminal Website visitor node, so the read is strictly top to bottom and the diagram is bookended by the same visitor. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…1086] Per review: the return leg now leaves the engine's output row and loops up the right margin to the original visitor, replacing the terminal bookend node. Anchored at the on-page personalization box so the edge exits the bottom of the engine rather than its top boundary. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…-1086] The return line previously emerged from the top region of the engine block, which read as the engine sitting first in the flow. An invisible elbow node ranked below the outputs forces the dotted loop to leave the engine's underside, sweep below the block, and climb the right margin to the original visitor. Shipped SVGs verified for cluster order this time. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Restores the terminal-node version (14ca431) after trying the loop-back variants: one arrow, 'personalized content and outreach', from the engine to a second Website visitor node. Strict top-to-bottom read, no long margin edge. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #896, from GTM feedback: rather than reading as a chain of diminishing steps, the hero diagram now groups the pipeline into two bigger buckets:
The website visitor stays outside as the story's start. One wording note for reviewers: the suggested label was "Noise to Signal Intelligence", but "intelligence" is on the Brand Book v0.6 anti-vocabulary list, so the bucket is labelled "Noise to signal". Shout if the original wording should win anyway.
Also adds cluster border/title theming and subgraph title margins to the shared mermaid configs (
static/images/bryn/src/theme-*.json) so bucket titles don't collide with nodes.Affects the Overview and How Bryn works pages (same SVG filenames, no MDX changes). Verified: light + dark renders reviewed, single purple accent preserved, no banned characters in labels.
🤖 Generated with Claude Code