dotmem 0.0.9 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -50,8 +50,8 @@ The canonical profile (`core/profile/`) defines:
50
50
  - **Language conventions** (`language.md`) — communication style
51
51
 
52
52
  When activated via `Joy` or `Jo`, dotmem loads this canonical profile as part of the deterministic
53
- discovery order. The profile is optional for basic memory operations but required for
54
- identity-gated features (carrier handshake, authority binding).
53
+ discovery order. The profile is mandatory for every Dotmem installation and execution mode and
54
+ is required for identity, profiles, memory and continuity.
55
55
 
56
56
  ### Activation Behavior
57
57
 
@@ -69,7 +69,7 @@ carrier and, when required, a trusted binding. If it returns the handshake gate,
69
69
  dotmem storage is user-anchored and resolved at runtime, never assumed from a hardcoded path.
70
70
  The canonical storage root is whatever `dotmem.paths.resolveDotMemStorageRoot()` resolves for the
71
71
  current OS user. By default that is the user anchor, written here in its platform-neutral canonical
72
- form `<user-home>/.mem`. It can be relocated through `DOTMEM_STORAGE_ROOT` or the user locator;
72
+ form `<user-home>/.dotmem`. It can be relocated through `DOTMEM_STORAGE_ROOT` or the user locator;
73
73
  report the active location with `npx dotmem storage`.
74
74
  After the CLI gate has passed, discovery order is mandatory:
75
75