This hub gathers observations of Scarlet's plain-language style across founder-facing documents. The dominant thread is an accessibility standard stated as an [absolute imperative] (StyleObs_TamarackReview_PlainLanguage) on 2026-03-13: no jargon unless defined first. Two mechanisms recur. One is outright [jargon exclusion] (StyleObs_PlainLanguagePolicy) — no git, no MCP, no RDF — describing the pipeline in two sentences. The other is gloss-in-place: [inline parentheticals] (StyleObs_ParentheticalClarification) like '(that's scope)', the organic [branch-and-trunk analogy] (StyleObs_BranchTrunkAnalogy) for version control, and [plain explanation] (StyleObs_ExtractionPlainLanguage) of backend extraction. Voice traits reinforce it: [first-person, active, alternating] (StyleObs_9) long sentences with short verdicts ('Cents, not dollars.'), [triadic momentum and high-stakes declaration] (StyleObs_7), [colloquial catch-alls] (StyleObs_DirectVoice) ('All of that'), and a [quantified value prop] (StyleObs_RatioValueProp) using a ratio with no dollar anchor. Note the counter-current: the same observer flags deliberate retention of precise terms — 'navigates' vs 'queries', 'FOUNDATION' all-caps as semantic weight — so plainness coexists with chosen technical precision rather than erasing it.
Witness phrases
verbatim F&F document shouldn't use any jargon unless it defines it first and attempts to plain language regardless
verbatim New hires operate at ~50% productivity for 3-6 months
verbatim This is my life's work.
verbatim no git, no MCP, no RDF, no GitHub Actions, no narrative architecture
verbatim 'navigates' vs 'queries' — deliberate verb choice to distinguish LLM associativity from formal query paradigm
verbatim Plain language as absolute standard (no jargon unless defined) sits against deliberate retention of precise/formal terms — 'navigates' vs 'queries', 'FOUNDATION' all-caps carrying semantic weight.
verbatim Two opposed mechanisms for the same goal: total jargon exclusion vs translate-in-place via parentheticals and analogy.
verbatim Most children are general voice/rhetoric observations; only a collaborator's review states plainness as a governing policy with a date — the rest are descriptive, not prescriptive.
verbatim Quantification framed as a plain-language device — ratio with no dollar anchor, 'Cents, not dollars.' — rather than financial precision.
In this area
StyleObservationStyleObs_7 you can connect that to anything that you could automate with Zapier
StyleObservationStyleObs_9 The past 20-25 years optimized for human-readable documentation; AI-native paradigm optimizes for machine-queryable worldview
StyleObservationStyleObs_BranchTrunkAnalogy Scarlet uses the organic 'branch and trunk' analogy to make GitHub's version control model accessible to a non-technical user.
StyleObservationStyleObs_DirectVoice Colloquial resolution after technical enumeration. 'All of that' as a deliberate plain-language catch-all after precise technical list.
StyleObservationStyleObs_ExtractionPlainLanguage Scarlet uses plain, accessible language to explain a technical backend process to a non-technical user; avoids jargon in favour of 'breaks down and understands'.
StyleObservationStyleObs_ParentheticalClarification Inline parentheticals used to immediately gloss technical terms: '(that's scope)', '(or arbitrary change description — a TX is really just...)'
StyleObservationStyleObs_PlainLanguagePolicy Explicit jargon exclusion: no git, no MCP, no RDF, no GitHub Actions, no narrative architecture. The extraction pipeline and PR review workflow described in two sentences with zero infrastructure jargon.
StyleObservationStyleObs_RatioValueProp New hires operate at ~50% productivity for 3-6 months
StyleObservationStyleObs_TamarackReview_PlainLanguage plain-language-imperative: Scarlet frames accessibility as an absolute standard, not a preference