@sabaiway/agent-workflow-memory 8.2.0 → 8.2.1

package/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to the memory substrate. Versions are this **package's** npm
 they are distinct from the **deployment-lineage** stamp written into a project's
 `docs/ai/.memory-version` (which tracks the shared `agent-workflow` lineage, head `4.0.0`).
 
+## 8.2.1 — the architecture template points to the layout rules instead of a fixed set of layers (AD-191)
+
+`references/templates/architecture.md`: the lead line drops "Layers", and the Layers and Module Boundaries sections
+give way to one section, **Layout rules**: modules nest by meaning, and in a kit deployment the rules live in
+`docs/ai/rules/effective/project-layout.md`. The File Tree and the rest of the template are unchanged; a deployed
+`docs/ai/architecture.md` is never rewritten. PATCH: template text only.
+
 ## 8.2.0 — the docs navigator stamps a cap it honours past 80 lines (AD-182)
 
 **`references/scripts/check-docs-size.mjs` now writes a `docs/ai/index.md` that its own default run and `--check-index`

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-memory
 description: Deploy or upgrade a portable AI-agent memory substrate in any project — an entry-point `AGENTS.md` (+ `CLAUDE.md` alias) and a structured `docs/ai/` context store with cap/archive/index enforcement. Use when the user wants to bootstrap `docs/ai/`, set up the Memory Map and session protocols, install the docs-rotation pre-commit hook, or run `/agent-workflow-memory` / `/agent-workflow-memory upgrade`. Triggers on "set up the memory system", "deploy the AI memory here", "bootstrap docs/ai", "upgrade the memory substrate". This is the substrate only — the workflow methodology (plan→execute→review, queue, Cleanup) is owned elsewhere and injected into AGENTS.md by the family composition root.
 disable-model-invocation: true
 metadata:
-  version: '8.2.0'
+  version: '8.2.1'
 ---
 
 # agent-workflow-memory

package/capability.json

@@ -3,7 +3,7 @@
   "schema": 1,
   "name": "agent-workflow-memory",
   "kind": "memory-substrate",
-  "version": "8.2.0",
+  "version": "8.2.1",
   "provides": ["context"],
   "roles": {},
   "detect": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-memory",
-  "version": "8.2.0",
+  "version": "8.2.1",
   "description": "Portable, cross-agent memory substrate for AI coding agents — an AGENTS.md entry point + docs/ai context with cap/archive/index enforcement, deployable standalone or as part of the agent-workflow family. The memory layer of the agent-workflow family.",
   "keywords": [
     "ai-agents",

package/references/templates/architecture.md

@@ -9,28 +9,13 @@ maxLines: 350
 
 # Architecture
 
-> How the code is organized. Layers, boundaries, where new code goes.
+> How the code is organized: where each module lives and where new code goes.
 
-## Layers
+## Layout rules
 
-```
-UI Components       ← {{src/components/}}
-    ↓
-Hooks / Composition ← {{src/hooks/}}
-    ↓
-Services (pure)     ← {{src/services/}}
-    ↓
-State / Storage     ← {{src/store/ or src/data/}}
-    ↓
-Types / Schemas     ← {{src/types/}}
-```
-
-## Module Boundaries
-
-- **Components** — render only. No fetching, no business logic.
-- **Hooks** — orchestration; combine services + state.
-- **Services** — pure functions. Easy to test.
-- **State** — single source of truth per domain.
+The code is laid out by the project-layout rules: modules nest by meaning, and a name says where
+code, tests and specs live. In a kit deployment those rules live in
+`docs/ai/rules/effective/project-layout.md`, laid down by the kit's upgrade.
 
 ## File Tree (top level)