aswritten.ai · public perspective

Perspective › TerminologyControl

TerminologyControl

15 nodes in this area of the perspective

This hub maintains the project's controlled vocabulary, establishing a canonical lexicon for [narrative architecture] (StyleObs_KeyPhrase_NarrArch) and [collective memory] (StyleObs_CollectiveMemoryTerm). The terminology is anchored by core positioning phrases like [IP-as-code] (Observation_IPAsCode) and [Collaborative Worldview] (StyleObs_TerminologyControl_IPasCode), which enforce a [terminology-control rule] (StyleObs_TerminologyControl) prioritizing specific metaphors over generic industry labels. The vocabulary extends into coined metaphors that define the system's stance on data management, specifically [context squishing] (Observation_ContextSquishing) versus [intentional memory] (Observation_IntentionalMemory), and the [cultivation trap] (Observation_CultivationTrap) of lock-in. Technical abstractions are formalized through the [git-native triad] (Observation_GitNativeTriad) and precise definitions for [Memory] (Obs_MemoryDefinition) and [Transaction] (Obs_TransactionDefinition). The span includes operational shorthand like [SSoT] (StyleObs_7) and [product market fit] (StyleObs_KeyPhrase_PMF), alongside structural terms like [compiled target] (Observation_CompiledTarget) and [tool signatures] (StyleObs_TechTerms), which together frame the project's technical and strategic identity.

Witness phrases

verbatim
intellectual property as code
verbatim
context squishing
verbatim
git native, i.e. versionable, branchable, reviewable
verbatim
**Memory**: Ephemeral user content (chat message, Discourse post, uploaded doc)
verbatim
**Transaction**: Graph changes (insert/delete operations)
verbatim
Tension exists between automated summarization and the project's insistence on 'intentional' manual curation.
verbatim
The use of 'SSoT' (Single Source of Truth) sits in potential friction with the 'git-native' paradigm of branching and multiple versions.

In this area

StyleObservation Obs_MemoryDefinition
**Memory**: Ephemeral user content (chat message, Discourse post, uploaded doc)
StyleObservation Obs_TransactionDefinition
**Transaction**: Graph changes (insert/delete operations)
StyleObservation Observation_CompiledTarget
content is a compiled target. The application is a compiled target
StyleObservation Observation_ContextSquishing
you are going to get behind the scenes,
StyleObservation Observation_CultivationTrap
Current state incentivizes **cultivating long-running personal AI instances**
StyleObservation Observation_GitNativeTriad
git native, i.e. versionable, branchable, reviewable
StyleObservation Observation_IntentionalMemory
One is to make memory intentional. So instead of this context squishing autosummarization, we have an agent or context that chooses to remember stuff, offers that to the user, and then saves that to the git repo intentionally
StyleObservation Observation_IPAsCode
intellectual property as code
StyleObservation StyleObs_7
you can connect that to anything that you could automate with Zapier
StyleObservation StyleObs_CollectiveMemoryTerm
building collective memory as a
StyleObservation StyleObs_KeyPhrase_NarrArch
narrative architecture
StyleObservation StyleObs_KeyPhrase_PMF
Standard startup terminology; signals stage and traction.
StyleObservation StyleObs_TechTerms
Simplifies tool signatures (one parameter instead of two)
StyleObservation StyleObs_TerminologyControl
Consistent use of 'worldview' (not 'context' or 'knowledge base') and 'collective memory' (not 'semantic memory').
StyleObservation StyleObs_TerminologyControl_IPasCode
IP-as-code / Collaborative Worldview

Each node links from the entity index.