This hub gathers the project's naming and positioning conventions, which cohere around two devices. First, a consistent lowercase brand stylization: the [system handle] (Obs_SystemHandle) \"aswritten\" as a centralized constant and the [domain-style brand name] (StyleObs_BrandName) with its .ai TLD. Second, an extended code metaphor running through the positioning — [intellectual property as code] (Observation_IPAsCode) as the core phrase, the [compiled-target framing] (Observation_CompiledTarget) applied in parallel to both content and the application, and a proposed extension to [organizational change as code] (StyleObs_OrgChangeAsCode) aimed at quantifying how the org changes. Against this settled stylistic vocabulary sits one genuinely open thread: the [product name itself] (Question_ProductNaming) is uncommitted, with stated dissatisfaction toward 'collective memory' and 'collaborative AI' recurring as an alternative. So the region reads as a firm convention layer (lowercase + code-as-X metaphor) wrapped around an unresolved product-naming decision.
Witness phrases
verbatim intellectual property as code
verbatim content is a compiled target. The application is a compiled target
verbatim I'd also like to add something about organizational change as code, ie being able to quantify the way the org is changing
verbatim Product name is explicitly unresolved: dissatisfaction with 'collective memory', 'collaborative AI' surfaces repeatedly, direction TBD — the one uncommitted decision amid settled conventions.
verbatim The 'as code' metaphor is still being stretched — 'organizational change as code' is a proposed addition, not yet an established convention like 'IP as code'.
verbatim Attachment is mostly skos:related (loose style observations) except the product-naming question, which attaches as skos:broader — structurally the odd one out.
StyleObservationStyleObs_BrandName I just started this new company,
StyleObservationStyleObs_OrgChangeAsCode I'd also like to add something about organizational change as code, ie being able to quantify the way the org is changing