The audience call changes the register, not the product. Same stages, same order, same components — a different voice, and one line that is a legal fix rather than a preference. Nothing here proposes a new flow or moves a step. Sections 3 and 4 of the brief document are unapproved flow proposals; I did not read past their headings and have designed nothing from them.
The reader we are writing for. Three to five years in, already reads filings, already holds positions, has usually been burned once and knows what it cost. Every sentence that explains something they know, or offers to improve their judgment, tells them we have mistaken them for someone else. That is the whole test applied below.
Checked live on the deployed build before writing any replacement copy
The refusal is not fine print — it is gone. RuleBar in
packages/sana-ui/src/index.tsx:53 is now
export function RuleBar() { return null; }, while still being imported and
rendered on four routes — screener, progress, settings and assessments. Anyone reading
the source sees <RuleBar /> on every page and would reasonably assume the
refusal is shown. It renders nothing. So item 3 is restore and promote, not
demote-to-promote — and the sharpest differentiator we have is currently making no claim at
all.
The promise line is already out of the app. The Masthead's
<span class="tag"> has been deleted, and the string appears on no route I
could reach signed in or signed out. /launch/deep states that public content is
served by a different renderer — so if the line is still live, it is live there, and
that is where the edit lands. I could not reach the public renderer to confirm, and
moatbrain.com currently sits behind the staging password gate.
The moat definition is gone, and its replacement kept the problem. "A moat is what keeps a good business good" no longer ships. What sits in its place is "…refine your Moatbrain — the judgment you build through practice" — which is the exact frame item 1 exists to remove, relocated from the promise line into first run. Item 5 is done; item 2 is the reason it did not help.
Highest leverage · use Bindi's wording verbatim
Build the judgment to invest like an owner.
Two failures in one line. It tells a five-year investor they lack judgment, and "build the judgment" is the construction the name-clearance screen flagged under ASIC framing.
Build your own research and decision process.
Bindi's alternative, unchanged. It has been through clearance, so I am not rewording it for rhythm — a line that has been legally reviewed should reach production with the same characters it was reviewed with.
Where: the public renderer (see the finding above), and
Masthead in packages/sana-ui/src/index.tsx if the tag slot is
restored.
Same stages, same order, same content
Choose company — Search the SEC universe or start with a vague idea.
Build thesis — Capture evidence, assumptions, and counter-work.
Decision memo — Export a user-owned record when gates pass.
"Start with a vague idea" is written for someone who does not yet have one. "Capture" is a research-assistant verb.
Choose company — Search the SEC universe by ticker or name.
Build thesis — Record the evidence, the assumptions, and the counter-case.
Decision memo — Export a record you own, once your own gates pass.
Same three steps, same order. The verbs move from assisting to recording, and "your own gates" says the standard is theirs — which is also true of the product.
Research funnel · 1 of 5
A funnel is something a company does to a user.
Your process · 1 of 5
The single word that carries the whole register shift, and it costs one find-and-replace.
Where: OrientationStrip in
packages/sana-ui/src/index.tsx; the .eyebrow string on each stage
route.
Restore it, then set it as a statement
—
The band that used to carry "Moatbrain structures your thinking. It does not
give a verdict." now returns null. Its former wording was also a description
of the product rather than a promise to the reader.
We will never tell you what to buy.
Every verdict on this page is yours. We bring the filings, the quotes and the structure.
Set as a statement, not a notice: cream rather than muted, upright rather than italic, no warning colour and no left-border "advisory" styling. The second line is what stops it reading as a limitation — it says what we do supply, in the same breath as what we refuse.
Why this one is worth the most. Every competitor scanned returns a verdict — one scores thesis pillars, another answers Supported or Challenged. A tool that will not do that is the only claim they cannot copy, and it lands hardest on someone who has been burned by a confident one. It should not be styled like something a lawyer made us print.
Where: RuleBar, packages/sana-ui/src/index.tsx:53
— already rendered on four routes, so restoring the component ships it everywhere with no
structural change.
Reordering two existing lines · no new components
Your coach: Nadia Halim
steady guide
The first thing this reader meets is a personality. They judge credibility by sources inside a minute, and the corpus — verbatim spans, filing dates, working links — is further down the panel than the assistant's name.
Evidence & sources
Every claim here carries
its filing, its date, and a verbatim span you can open.
Nadia Halim · steady guide
Identity is kept, demoted. Same two lines, swapped — the panel still belongs to the same agent, but the first sentence is a claim about the corpus that a sceptical reader can immediately test.
Where: the drawer header in
apps/web-start/src/components/ReviewLanePanel.tsx. Drawn in situ on
the shell page.
The definition is already gone — the register it sat in is not
Your coach stays with you as you research, question assumptions, and refine your Moatbrain — the judgment you build through practice.
Choose the style that will help you think clearly.
"The judgment you build through practice" is the promise line's problem relocated. "Help you think clearly" implies they currently do not.
Your coach stays with you across every assessment — pressing assumptions, holding you to your own standard, and keeping drafts out of your record until you accept them.
Choose how you want to be challenged. You can change later without losing your journal.
From "help you think" to "how you want to be challenged". The second version also states the draft-separation guarantee, which is a real mechanic and the kind of thing this reader actually wants to know on first contact.
Where: apps/web-start/src/components/CoachExperience.tsx:149.
Drawn in full on the
first-run page.
Item 6 was flagged for awareness, not for this pass, so:
The legacy public renderer still carries the old product name:
apps/web/components/MemoWorkspaceApp.tsx lines 1681 and 1753 read
"OwnerMind structures your thinking. It does not give a verdict." That is the pre-rename
brand on the renderer that serves public content. Not mine to edit, and not part of the
positioning brief — flagging it because it is the same sentence as item 3 and whoever restores
the refusal will be standing next to it.
staging.ownermind.co, sourceSha 7cd604b, signed in on
an isolated QA account and again signed out. Brief sections 0 and 1 only.
Copy and framing proposals for a pick — no code, no deploy, not routed to Scott's build.