aswritten.ai · public perspective

Perspective › ModulesCapabilities

ModulesCapabilities

18 nodes in this area of the perspective

This hub gathers the product's tool surface and capability decisions, mostly dated March–May 2026. The dominant arc is aggressive consolidation: a March–April sweep settled the [five user-facing MCP tools] (Position_FiveCoreMCPTools) — perspective, cite, introspect, remember, review — confirmed also in the [narrative-level tool surface record] (Narrative_MCPToolSurface_FiveTools) where scope absorbed into introspect and refract/lens moved to the product repo only. Removed in the same sweep: [refract and its registry] (Position_RefractRegistryRemovedFromProduct), the [memories/source tool] (Position_MemoriesSourceToolRemoved), [discoveries] (Position_RemoveDiscoveries), the [notifications system] (Position_RemoveNotificationsSystem), and [auto-generated TX summaries] (Position_TXSummariesAutoGenRemoved). Against that removal current, the [Feedback/Help tool] (Position_FeedbackHelpAboveLine) was pulled *above* the line as primary churn prevention. The [review tool was widened to three cases] (Position_ReviewToolThreeCases). Capability framing runs alongside: [compilation layers] (Obs_CompilationLayers) from 4K bootstrap to 100K expansion, [perspective layering] (Obs_ChineseHerbalismLayeringExample) across multiple expertise voices, [transcript bootstrapping] (Position_TranscriptBootstrapOnramp) as a lighter onramp, and a [public perspective module] (Narrative_PublicPerspectiveModule) as a sibling repo with a hard 40-memory cap. Early usage (May) showed [two organic loop patterns] (Position_FourToolLoopEngagedUserPattern) across the enterprise customer's first nine days. A [four-column tool matrix] (StyleObs_FiveToolTable) serves as canonical architecture definition.

Witness phrases

verbatim
The five user-facing MCP tools are: perspective, cite, introspect, remember, and review. Scope, refract, and lens are removed from the user-facing surface.
verbatim
Feedback/help tool is above the line for launch. MCP tool that sends user a confirmation message (phone or email) and forwards request text to Scarlet. Front stays active to support this — only use of Front going forward. Prompt user to add phone to Outseta.
verbatim
Refract tool and registry removed from product. Registry is just the docs folder. Refract becomes a local Claude Code skill. Eliminates need to separate tools between org and everyone else — now one tool set for everyone.
verbatim
Memories/source tool removed from product. Memories are just files in the repo — anyone with a coding agent can read them directly. Org-only skill at most.
verbatim
The public perspective is a separate sibling repo (aswritten-public), hand-written in external voice, with a hard size cap of ~40 memories and no content above decision-level conviction.
verbatim
Call transcript bootstrapping (Fireflies/Gemini/Zoom) is a lighter onramp that allows for an immediate working perspective without a live interview.
verbatim
Two distinct usage patterns emerged organically across the enterprise customer's first nine days without prompting
verbatim
Notifications system removed; synchronous remember eliminates primary use case.
verbatim
Memories/source tool removed on the grounds that memories are just repo files any coding agent can read — but this leaves an open question about whether org-only access patterns are adequately served.
verbatim
Review tool cases 2 and 3 (named transaction vs. arbitrary content) are explicitly flagged as possibly the same — the boundary remains unresolved.
verbatim
The two organic usage loops are a promising signal but explicitly held open — 'worth confirming on subsequent customer engagements before treating as a settled finding.'
verbatim
TX summaries removed as auto-generated but the PR comment mechanism is explicitly kept — a partial removal that leaves residual infrastructure in place.

In this area

Narrative Narrative_MCPToolSurface_FiveTools
The five user-facing MCP tools are perspective, cite, introspect, remember, and review
Narrative Narrative_PublicPerspectiveModule
Public Perspective as First Module
Observation Obs_ChineseHerbalismLayeringExample
Concrete example of layering: three distinct expertise perspectives compiled together in a single chat session.
Observation Obs_CompilationLayers
Compilation layers serve right depth of context: 4K-token worldview bootstrap to full 100K-token domain expansion
Observation Obs_ModulesCapabilities
Three extraction moments: onboarding mode, decision-point extraction during work, consolidation and cross-referencing during review
Observation Obs_ReviewToolQuote
Review tool extended to three cases
StyleObservation StyleObs_FiveToolTable
Markdown table used as canonical architecture definition: Tool | Question | Input | Output — four-column single-responsibility matrix

11 further nodes are not published in the public projection. Each node links from the entity index.