aswritten.ai · public perspective

Perspective › JargonPolicy

JargonPolicy

23 nodes in this area of the perspective

This hub tracks the evolution of jargon policy, oscillating between [internal-audience density] (StyleObs_DomainJargon) and [explicit terminology control] (StyleObs_JargonPolicy). The corpus exhibits a persistent tension: while many artifacts assume [insider fluency] (StyleObs_EngagementShape_JargonPolicy) through un-defined technical acronyms like [MCP] (StyleObs_MCP) or [SOW] (StyleObs_EnterpriseCustomerPattern_Jargon), there is a parallel, rigorous effort to [codify canonical vocabulary] (StyleObs_8). This control manifests as [hard verb constraints] (StyleObs_TranscriptBootstrap_VerbConstraint), [intentional jargon splits] (StyleObs_JargonSplit) between user-facing and engineering registers, and [plain-language exclusion policies] (StyleObs_PlainLanguagePolicy). A recurring idiolect, notably in [Scarlet's contributions] (StyleObs_ScarletConversationalWhy), uses jargon to name mechanisms while appending plain-language clauses to explain their strategic 'why.' Recent entries highlight the emergence of [idiomatic AI-era terms] (StyleObs_VibeCoding) and [strategic reframing jargon] (StyleObs_RelationshipCadenceArtifact) that signal in-group status while simultaneously attempting to standardize the lexicon for broader organizational use.

Witness phrases

verbatim
Do NOT say "train" — say "create a perspective"
verbatim
so when the agent is making a new decision in that space, it can reason from the intent rather than cargo-culting the last value
verbatim
Preserve verbatim quotes as verbatim claims, not as paraphrasable evidence.
verbatim
Especially for the free and expert tier, you shouldn't need to know anything about GitHub or that the product even runs on GitHub.
verbatim
tx_summary — plain-language summary of what shifted in the worldview
verbatim
Explicit prohibition of infrastructure jargon in favor of pure process description.
verbatim
Use of RDF namespace notation (narr:*) as a primary, code-like prose register.
verbatim
Strategic selection of tier names (e.g., 'Professional') to avoid organizational-size bias.

In this area

StyleObservation StyleObs_8
Documentation describes; worldview generates. Documentation goes stale; worldview evolves
StyleObservation StyleObs_Cargoculting
'Cargo-culting' used as a single compound verb to describe the failure mode of copying a value without understanding its intent. This is idiomatic engineering jargon deployed precisely — it signals the author's technical fluency and frames
StyleObservation StyleObs_DomainJargon
Controlled jargon: 'TX' (transaction), 'PR' (pull request), 'zone', 'lens', 'centrist', 'introspect'. Used without definition — assumes insider audience.
StyleObservation StyleObs_EngagementShape_JargonPolicy
Product-specific jargon (webhook, repo, branch routing, backfill diagnostic, SOW) used without definition, implying internal audience. General business terms (calibration, cadence, engagement) used in product-specific senses that differ fro
StyleObservation StyleObs_EnterpriseCustomerPattern_Jargon
Feltron-style PDF
StyleObservation StyleObs_GitHubTier_JargonPolicy
technical-jargon-contrasted-with-plain-user-language
StyleObservation StyleObs_Jargon_EnterpriseCustomer
marginal cost of adding a second channel is near-zero because Front's unified inbox model
StyleObservation StyleObs_Jargon_MCP
subgraph (filtered TriG)
StyleObservation StyleObs_JargonDensityHealthcare
Healthcare-specific jargon (pelvic floor, HIPAA, intake, handoff criteria, referring physician, concierge medicine, IPS documents) used without definition, implying internal audience. Product jargon (CPC, goal URL, perspective, escalation,
StyleObservation StyleObs_JargonPolicy
Vibe coding, vibe reading, vibe writing.
StyleObservation StyleObs_JargonSplit
Intentional split between user-facing human words and internal engineering metaphors.
StyleObservation StyleObs_MCP
Acronym used without expansion; assumes domain knowledge
StyleObservation StyleObs_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.
StyleObservation StyleObs_RecursiveDogfooding
Recursive dogfooding
StyleObservation StyleObs_RegisterTechnical
Predominantly technical engineering register (SPARQL, webhook, additionalParameters, base64) with deliberate informal asides ('zombie', 'all of that'). Signals expert-to-expert communication.
StyleObservation StyleObs_RelationshipCadenceArtifact
Coined term 'relationship-cadence artifact' to reframe a metrics report as a customer relationship tool — jargon that encodes strategic intent
StyleObservation StyleObs_ScarletConversationalWhy
Scarlet's idiolect: technical terms ('RAG', 'LLM', 'link relations') used without definition but immediately followed by a plain-language 'why' clause. The jargon names the mechanism; the conversational clause explains why it matters. Patte
StyleObservation StyleObs_TechnicalJargon_DesignSession
Product-specific jargon (tx_summary, zones, review_instructions, warm-start, cold-start, PR, MCP) is used without definition throughout, signaling an internal audience. The jargon is consistent and controlled — these are canonical terms bei
StyleObservation StyleObs_TechnicalJargonNarrPrefix
Technical jargon uses narr: prefix notation inline (narr:Actor_*, narr:Actor_TonyMaley, prov:generated) as if writing code documentation. This is a distinctive idiolect — mixing RDF namespace notation into prose design notes.
StyleObservation StyleObs_TierNamingJargonPolicy
Deliberate jargon policy: 'Professional' chosen over 'Enterprise' to avoid org-size connotations. 'SOW' (Statement of Work) used without definition, implying internal audience. 'BYOK', 'ZDR', 'MSA' used as known acronyms. Tier names are pla
StyleObservation StyleObs_TranscriptBootstrap_VerbConstraint
Explicit verb prohibition pattern: 'Do NOT say X — say Y.' Scarlet uses this construction to encode terminology control as a hard rule. 'train' is prohibited; 'create a perspective' is mandated. Consistent with prior naming constraint memos
StyleObservation StyleObs_VerbatimPreservation
Preserve verbatim quotes as verbatim claims, not as paraphrasable evidence.
StyleObservation StyleObs_VibeCoding
Section header 'Vibe Coding' — emerging jargon for AI-assisted development

Each node links from the entity index.