This hub tracks the document's reliance on [triadic rhetorical structures] (StyleObs_rule_of_three) to anchor complex value propositions. The pattern manifests as a tool for cognitive efficiency, appearing in [product pillar definitions] (StyleObs_RuleOfThree_UseCases) and [technical feature sets] (Observation_GitNativeTriad) that leverage parallel suffixes for memorability. Beyond simple lists, the device is used to [frame developer-centric workflows] (StyleObs_10) at critical decision points. While the rule of three serves as a primary cadence, the document occasionally [stretches the rhythm] (StyleObs_6) to accommodate more complex, five-item taxonomies, suggesting that the triadic form is a baseline rather than a rigid constraint. The most aggressive application of the pattern remains the [escalating-severity triad] (StyleObs_RuleOfThree), which uses the structure to contrast the utility of AI across different seniority levels.
Witness phrases
verbatim git native, i.e. versionable, branchable, reviewable
verbatim explicit, reviewable, and testable
verbatim Senior people have supercharged AIs. Junior people have dumb AIs. New hires have useless AIs.
verbatim positioning, offering, product, teams, and process
verbatim The pattern is not strictly limited to three items, as seen in the expansion to five-item lists.
verbatim The rhetorical intent shifts from balanced categorization to escalating, comparative critique.
In this area
StyleObservationObservation_GitNativeTriad git native, i.e. versionable, branchable, reviewable
StyleObservationStyleObs_10 explicit, reviewable, and testable
StyleObservationStyleObs_6 where we have an organization