aswritten.ai · public perspective

Perspective › Narrative UserFacingVsInternalLanguageSplit

Narrative UserFacingVsInternalLanguageSplit

5 nodes in this area of the perspective

This hub holds the deliberate two-layer language split: human words on the user-facing surface, engineering metaphor underneath. The surface thesis is that the [full tool surface reads as plain speech] (Claim_FullToolSurfaceHumanWords) — perspective, cite, remember, forget, review, introspect, share — and that [the naming IS the GitHub abstraction completing] (Claim_GitHubAbstractionComplete): Free/Expert users never see 'compile from repo' or 'load from share bundle'. Yet the split is principled, not erasure: on the code side [the 'compile' term is retained] (Claim_InternalCompileTermCorrect) because the n8n workflow literally compiles memories plus transactions into a worldview snapshot. The same surface-vs-internal logic drives two later refinements (Mar 2026): with 'consult' no longer a tool name, [the word was freed] (Claim_ConsultTermFreed) and dropped from glossary guidance, and [the user-facing parameter was renamed] (Claim_IDParamRename) from perspective='share-id' to a generic id='share-id', while the proxy still strips it before forwarding. The framing was set Jul 2025 and has been firming through Mar 2026 as naming decisions land against it.

Witness phrases

verbatim
Every tool name is a word a non-technical person would use in conversation.
verbatim
The abstraction is complete when the language doesn't leak implementation.
verbatim
The engineering metaphor is correct for the engineering layer.
verbatim
The word is no longer reserved terminology.
verbatim
perspective(id='acupuncture-an early prospect-gotham-an engineering manager at the customer-f50e')
verbatim
The split is not 'hide all implementation' — 'compile' is deliberately kept on the code side where the engineering metaphor is literally accurate, against the surface rule that language must not leak implementation.
verbatim
The Jul 2025 framing is principle; the Mar 2026 children are downstream applications (consult freed, id param rename) — read them as consequences, not restatements, of the split.
verbatim
The id-param rename goes further than hiding implementation: it drops the domain word 'perspective' as the parameter name in favor of a generic 'id', a tension with making every surface term a meaningful human word.

In this area

Claim Claim_ConsultTermFreed
With 'consult' no longer a tool name, it was freed as a general word. The 'avoid: Consult' note was removed from the Leaders/executives audience guidance in the glossary. The word is no longer reserved terminology.
Claim Claim_FullToolSurfaceHumanWords
Full tool surface: perspective, cite, remember, forget, review, introspect, share. Every tool name is a word a non-technical person would use in conversation.
Claim Claim_GitHubAbstractionComplete
The tool naming IS the GitHub abstraction completing. Free/Expert users don't see 'compile from repo' or 'load from share bundle.' They see 'perspective'. The abstraction is complete when the language doesn't leak implementation.
Claim Claim_InternalCompileTermCorrect
On the code side, 'compile' is retained. The n8n workflow literally compiles memories + transactions into a worldview snapshot. The engineering metaphor is correct for the engineering layer.

1 further node is not published in the public projection. Each node links from the entity index.