aswritten.ai · public perspective

Perspective › Behaviors

Behaviors

5 nodes in this area of the perspective

This hub gathers the system behaviors of a git-native memory product — both the low-level operations and the user-facing workflow. The canonical operation set is enumerated as [Compile/Extract/Diff/TX/Commit/Evolve] (Narrative_SIC_Behaviors_1), the semantic-compilation primitives. At the workflow layer these sequence into a [create-memory → posit → remember chain] (Obs_WorkflowBehaviors), where posit previews and remember commits. The framing throughout is [intentional rather than automatic memory] (Observation_IntentionalMemory): an agent chooses what to remember, offers it to the user, then saves it to git — explicitly opposed to context autosummarization. This sits inside the broader [git-native collaborative worldview] (Narrative_GitNativeMemory) that differentiates the product from model-held built-in memory (intentional memory, multiplayer AI, progressive compilation). the customer's chief architect also flagged a gap the behavior set does not yet cover: an [onboarding mode] (Feature_OnboardingMode) to bootstrap collective memory from knowledge in people's heads rather than from ongoing AI work.

Witness phrases

verbatim
Compile (replay transactions to snapshot), Extract (RDF from input), Diff (semantic comparison), TX (generate transaction), Commit (append to Git), Evolve (operation on snapshot).
verbatim
- `mcp/create-memory` → `mcp/posit` (preview) → `mcp/remember` (commit file)
verbatim
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
verbatim
Shift from model-held memory to git-native worldview; intentional memory; multiplayer AI; progressive compilation
verbatim
Onboarding Mode is named an unbuilt gap — the behaviors detect novelty in ongoing work but cannot bootstrap memory from knowledge that only lives in people's heads.
verbatim
Intentional, agent-chosen memory is positioned explicitly against automatic context autosummarization — a deliberate design stance, not a neutral default.
verbatim
Two altitudes coexist without being reconciled: low-level SIC operations (Compile/Extract/Diff/TX/Commit/Evolve) vs the user-facing mcp/ workflow verbs — same hub, different granularity.

In this area

Narrative Feature_OnboardingMode
Onboarding Mode: The Missing Feature
Narrative Narrative_GitNativeMemory
Git-Native Collaborative Worldview
Narrative Narrative_SIC_Behaviors_1
Compile (replay transactions to snapshot), Extract (RDF from input), Diff (semantic comparison), TX (generate transaction), Commit (append to Git), Evolve (operation on snapshot).
StyleObservation Obs_WorkflowBehaviors
- `mcp/create-memory` → `mcp/posit` (preview) → `mcp/remember` (commit file)
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

Each node links from the entity index.