code-anchored-context 0.1.1 → 0.2.1

package/{Development → context}/README.md

@@ -1,39 +1,35 @@
-# Development
+# context/
 
-This folder is the working memory for active and historical development
-context in this repository.
+This folder is the working memory for active and historical context in this
+repository.
 
 Use it for specs, interface notes, architecture notes, testing notes, delivery
 notes, infrastructure notes, actionable operations notes, ADRs, backlog items,
 implementation plans, and release-documentation notes. Do not use
-`Documentation/` for in-progress development planning.
+`docs/` for in-progress development planning.
 
 ## Start Here
 
-- `code-anchored-context.html` is a human-friendly visual brief for this
-  opinionated context practice.
-- `giving-ai-agents-context-around-code.md` is an article-form explanation of
-  Code-Anchored Context for human-agent collaboration.
 - `terminology.md` defines the shared vocabulary.
 - `current.md` points to the active release context.
-- `programs/` contains durable multi-release development context.
+- `programs/` contains durable multi-release working context.
 - `backlog/` contains deferred isolated work cut from initiatives.
-- `releases/` contains release-scoped development context.
+- `releases/` contains release-scoped working context.
 - `_templates/initiative/` contains the standard initiative shape.
 - `_templates/planned-initiative/` contains the standard future initiative
   shape for scoped program work outside the current release.
 - `_templates/release-context/` contains the standard release folder shell.
 
-## Relationship To Documentation
+## Relationship To docs/
 
-`Development/` and `Documentation/` serve different jobs:
+`context/` and `docs/` serve different jobs:
 
 | Folder | Meaning | Updated when |
 | --- | --- | --- |
-| `Development/` | What we are planning, building, deciding, or validating. | During normal development. |
-| `Documentation/` | What the product does as of a release or tag. | Only during explicit documentation refresh work. |
+| `context/` | What we are planning, building, deciding, or validating. | During normal development. |
+| `docs/` | What the product does as of a release or tag. | Only during explicit documentation refresh work. |
 
-Development notes can feed release documentation, but they are not product
+Working context can feed release documentation, but it is not product
 documentation. Capture that bridge in each initiative's
 `release-doc-notes.md`.
 
@@ -50,16 +46,16 @@ Some context needs to outlive a single release initiative:
 
 | Place | Use for |
 | --- | --- |
-| `Development/programs/` | Long-lived multi-release efforts, phase history, roadmaps, and durable decisions. |
-| `Development/programs/<program>/planned-initiatives/` | Scoped future delivery slices that belong to a program but are not in the current release yet. |
-| `Development/backlog/items/` | Deferred isolated work cut from an initiative but worth preserving. |
-| `Development/releases/<version>/initiatives/` | Release-scoped delivery slices and historical implementation context. |
+| `context/programs/` | Long-lived multi-release efforts, phase history, roadmaps, and durable decisions. |
+| `context/programs/<program>/planned-initiatives/` | Scoped future delivery slices that belong to a program but are not in the current release yet. |
+| `context/backlog/items/` | Deferred isolated work cut from an initiative but worth preserving. |
+| `context/releases/<version>/initiatives/` | Release-scoped delivery slices and historical implementation context. |
 
 The rule is:
 
 > Active work belongs in a release initiative. Multi-release context belongs in
 > a program. Scoped future program work belongs in a planned initiative.
-> Deferred isolated work belongs in the development backlog.
+> Deferred isolated work belongs in the context backlog.
 
 The delivery-surface rule is:
 
@@ -82,7 +78,7 @@ not copy specs, plans, or ADRs into area-local documents.
 ## Standard Layout
 
 ```text
-Development/
+context/
   current.md
   programs/
     <program-slug>/
@@ -140,11 +136,11 @@ Release initiatives should link to their program when one exists. Programs
 should link back to the release initiatives that delivered each slice.
 
 Do not use a program for a small leftover task. Use
-`Development/backlog/items/` for deferred isolated work.
+`context/backlog/items/` for deferred isolated work.
 
-## Development Backlog
+## Context Backlog
 
-Use `Development/backlog/items/` for isolated work that was taken out of an
+Use `context/backlog/items/` for isolated work that was taken out of an
 initiative's scope but should be kept for later. Each backlog item records its
 origin initiative and release.
 
@@ -214,23 +210,23 @@ Use when relevant:
 When an initiative produces context that needs to survive after the release:
 
 - Move multi-release strategy, roadmap, and durable decisions into
-  `Development/programs/<program-slug>/`.
+  `context/programs/<program-slug>/`.
 - Move scoped future delivery slices into
-  `Development/programs/<program-slug>/planned-initiatives/<initiative-slug>/`.
+  `context/programs/<program-slug>/planned-initiatives/<initiative-slug>/`.
 - Move isolated deferred work into
-  `Development/backlog/items/<originating-initiative-slug>--<item-slug>.md`.
+  `context/backlog/items/<originating-initiative-slug>--<item-slug>.md`.
 - Keep release-scoped plans, implementation history, and final release notes
   inside the original initiative.
 
 ## Changing The Current Release
 
-Changing `Development/current.md` is a release transition, not just a line
-edit. Use `Development/_templates/release-transition.md` as the checklist.
-Create missing release folders from `Development/_templates/release-context/`.
+Changing `context/current.md` is a release transition, not just a line
+edit. Use `context/_templates/release-transition.md` as the checklist.
+Create missing release folders from `context/_templates/release-context/`.
 
 When setting a release as current, agents should scan all program planned
 initiatives for matching `Target release:` metadata and promote matching items
-into `Development/releases/<version>/initiatives/`.
+into `context/releases/<version>/initiatives/`.
 
 The promotion rule is:
 
@@ -241,7 +237,7 @@ The promotion rule is:
 When changing behavior, agents should:
 
 1. Read the local `AGENTS.md`.
-2. Open `Development/current.md`.
+2. Open `context/current.md`.
 3. Check the current release's initiatives for matching context.
 4. Use `plan.md` for live alignment, open questions, and rough thinking.
    Promote settled conclusions into the stable initiative files.
@@ -251,7 +247,7 @@ When changing behavior, agents should:
 7. Create or update a program planned initiative when future scoped work is
    clear but belongs outside the current release.
 8. Record future product-doc impact in `release-doc-notes.md`, not in
-   `Documentation/`, unless a human explicitly asks for documentation refresh.
+   `docs/`, unless a human explicitly asks for documentation refresh.
 
 The key rule for planning is:
 

package/{Development → context}/_templates/backlog-item.md

@@ -1,7 +1,7 @@
 # Backlog Item Title
 
 Status: Candidate
-Originating initiative: `Development/releases/v0_1_0/initiatives/<initiative-slug>/`
+Originating initiative: `context/releases/v0_1_0/initiatives/<initiative-slug>/`
 Originating release: `v0_1_0`
 Area: TBD
 Reason deferred: TBD
@@ -35,6 +35,6 @@ section and leave the item as a historical record.
 
 ```md
 Status: Promoted
-Promoted to: `Development/releases/<version>/initiatives/<initiative-slug>/`
+Promoted to: `context/releases/<version>/initiatives/<initiative-slug>/`
 ```
 

package/{Development → context}/_templates/initiative/README.md

@@ -17,7 +17,7 @@ produce.
 - Tests or verification: `path/to/...`
 - Delivery, CI/CD, build, or artifacts: `path/to/...`
 - Infrastructure, IaC, or environment config: `path/to/...`
-- Documentation or release notes: `path/to/...`
+- Docs or release notes: `path/to/...`
 
 Remove entries that do not apply and add the real paths. Prefer naming the
 delivery concern over assuming a specific folder layout.
@@ -59,5 +59,5 @@ support, observability, rollback, or repair context.
   Promote settled conclusions into the stable initiative files.
 - Update `release-doc-notes.md` when shipped behavior or product-facing
   behavior changes.
-- Do not update `Documentation/` from this initiative unless a human
+- Do not update `docs/` from this initiative unless a human
   explicitly asks for release documentation work.

package/{Development → context}/_templates/initiative/backlog.md

@@ -19,10 +19,10 @@
 Use this section only for work deferred within the active initiative.
 
 If a deferred item should outlive this initiative as future isolated work,
-create a backlog item from `Development/_templates/backlog-item.md` under:
+create a backlog item from `context/_templates/backlog-item.md` under:
 
 ```text
-Development/backlog/items/<originating-initiative-slug>--<item-slug>.md
+context/backlog/items/<originating-initiative-slug>--<item-slug>.md
 ```
 
 - None yet.

package/{Development → context}/_templates/initiative/plan.md

@@ -51,7 +51,7 @@ the canonical initiative files.
 - [ ] Move settled environment and IaC context into `infrastructure.md`
 - [ ] Move actionable runtime/support concerns into `operations.md`
 - [ ] Move executable work into `backlog.md`
-- [ ] Move multi-release context into `Development/programs/`
-- [ ] Move isolated deferred work into `Development/backlog/items/`
+- [ ] Move multi-release context into `context/programs/`
+- [ ] Move isolated deferred work into `context/backlog/items/`
 - [ ] Move durable decisions into `decisions/`
 - [ ] Move product-documentation impact into `release-doc-notes.md`

package/{Development → context}/_templates/initiative/release-doc-notes.md

@@ -1,20 +1,20 @@
-# Release Documentation Notes
+# Release Doc Notes
 
 Use this file to capture product-documentation impact while development is
-in progress. At release time, these notes help refresh `Documentation/`
+in progress. At release time, these notes help refresh `docs/`
 against the final shipped behavior.
 
-Do not edit `Documentation/` from normal development work unless a human
+Do not edit `docs/` from normal development work unless a human
 explicitly asks for a documentation refresh or a specific documentation fix.
 
 ## Product Behavior Changes
 
 - None yet.
 
-## Candidate Documentation Areas
+## Candidate Docs Areas
 
-- `Documentation/<Area>/README.md`
-- `Documentation/<Area>/features/<feature>.md`
+- `docs/<Area>/README.md`
+- `docs/<Area>/features/<feature>.md`
 
 ## QA Or Support Notes
 

package/{Development → context}/_templates/planned-initiative/README.md

@@ -2,8 +2,8 @@
 
 Status: Planned
 Target release: vNEXT
-Program: `Development/programs/<program-slug>/`
-Promotion target: `Development/releases/vNEXT/initiatives/<initiative-slug>/`
+Program: `context/programs/<program-slug>/`
+Promotion target: `context/releases/vNEXT/initiatives/<initiative-slug>/`
 Promoted to: None
 Promoted on: None
 
@@ -19,7 +19,7 @@ and what outcome it should produce.
 - Tests or verification: `path/to/...`
 - Delivery, CI/CD, build, or artifacts: `path/to/...`
 - Infrastructure, IaC, or environment config: `path/to/...`
-- Documentation or release notes: `path/to/...`
+- Docs or release notes: `path/to/...`
 
 Remove entries that do not apply and add the real paths. Prefer naming the
 delivery concern over assuming a specific folder layout.

package/{Development → context}/_templates/planned-initiative/release-doc-notes.md

@@ -1,20 +1,20 @@
-# Release Documentation Notes
+# Release Doc Notes
 
 Use this file to capture expected product-documentation impact while future
 work is being planned. When the planned initiative is promoted and later
 implemented, compare these notes against the final shipped behavior.
 
-Do not edit `Documentation/` from normal development work unless a human
+Do not edit `docs/` from normal development work unless a human
 explicitly asks for a documentation refresh or a specific documentation fix.
 
 ## Expected Product Behavior Changes
 
 - None yet.
 
-## Candidate Documentation Areas
+## Candidate Docs Areas
 
-- `Documentation/<Area>/README.md`
-- `Documentation/<Area>/features/<feature>.md`
+- `docs/<Area>/README.md`
+- `docs/<Area>/features/<feature>.md`
 
 ## QA Or Support Notes
 

package/{Development → context}/_templates/program/README.md

@@ -59,5 +59,5 @@ this program but are not in the current release yet.
   a scoped delivery slice before the target release becomes current.
 - Keep release-scoped implementation history in the relevant release
   initiative.
-- Use `Development/backlog/items/` for isolated deferred items that do not
+- Use `context/backlog/items/` for isolated deferred items that do not
   need a program.

package/{Development → context}/_templates/program/backlog.md

@@ -3,7 +3,7 @@
 This backlog holds future work that belongs to the program as a durable
 multi-release effort.
 
-Use `Development/backlog/items/` instead for isolated deferred work that does
+Use `context/backlog/items/` instead for isolated deferred work that does
 not need program-level context.
 
 Use `planned-initiatives/` instead when future work is already clear enough

package/{Development → context}/_templates/program/releases/v0_1_0.md

@@ -5,7 +5,7 @@
 Link to the release-scoped initiative when one exists:
 
 ```text
-Development/releases/v0_1_0/initiatives/<initiative-slug>/
+context/releases/v0_1_0/initiatives/<initiative-slug>/
 ```
 
 ## Scope

package/{Development → context}/_templates/release-context/README.md

@@ -1,6 +1,6 @@
-# vNEXT Development Context
+# vNEXT Context
 
-This folder contains development context for the `vNEXT` release.
+This folder contains working context for the `vNEXT` release.
 
 ## Navigation
 
@@ -14,20 +14,20 @@ Create an initiative when work is non-trivial, behavior-changing,
 cross-project, release-significant, or likely to need future product
 documentation.
 
-Use `Development/_templates/initiative/` as the starting point.
+Use `context/_templates/initiative/` as the starting point.
 
 ## Carry-Forward Rule
 
 If an initiative is part of a larger phased effort, link it to a program
-under `Development/programs/`.
+under `context/programs/`.
 
 If isolated work is cut from scope but should be kept for later, create a
-backlog item under `Development/backlog/items/` and link it back to the
+backlog item under `context/backlog/items/` and link it back to the
 originating initiative.
 
 ## Planned Initiative Promotion
 
 When this release becomes current, promote matching planned initiatives from
-`Development/programs/*/planned-initiatives/` into this release's
+`context/programs/*/planned-initiatives/` into this release's
 `initiatives/` folder. Leave the planned initiative in place as historical
 planning context and update its status to `Promoted`.

package/{Development → context}/_templates/release-context/backlog.md

@@ -1,6 +1,6 @@
 # vNEXT Backlog
 
-This file tracks release-level development context that is not yet captured
+This file tracks release-level working context that is not yet captured
 by an initiative, plus a short summary of initiative progress once
 initiatives exist.
 
@@ -11,4 +11,3 @@ No backlog items recorded yet.
 ## Initiative Summary
 
 No initiatives registered yet.
-

package/{Development → context}/_templates/release-transition.md

@@ -1,23 +1,23 @@
 # Release Transition Checklist
 
-Use this checklist when changing `Development/current.md` to a new current
+Use this checklist when changing `context/current.md` to a new current
 release.
 
 Target release: vNEXT
 
 ## Steps
 
-- [ ] Update `Development/current.md` to the target release.
-- [ ] Create `Development/releases/<target-release>/` from
-      `Development/_templates/release-context/` if it does not exist.
+- [ ] Update `context/current.md` to the target release.
+- [ ] Create `context/releases/<target-release>/` from
+      `context/_templates/release-context/` if it does not exist.
 - [ ] Create `README.md`, `backlog.md`, and `initiatives/` for the target
       release if missing.
-- [ ] Scan `Development/programs/*/planned-initiatives/*/README.md` for
+- [ ] Scan `context/programs/*/planned-initiatives/*/README.md` for
       `Target release: <target-release>`.
 - [ ] For each matching planned initiative, materialize it into:
 
 ```text
-Development/releases/<target-release>/initiatives/<initiative-slug>/
+context/releases/<target-release>/initiatives/<initiative-slug>/
 ```
 
 - [ ] Update the promoted release initiative so it links back to the parent
@@ -26,7 +26,7 @@ Development/releases/<target-release>/initiatives/<initiative-slug>/
 
 ```md
 Status: Promoted
-Promoted to: `Development/releases/<target-release>/initiatives/<initiative-slug>/`
+Promoted to: `context/releases/<target-release>/initiatives/<initiative-slug>/`
 Promoted on: YYYY-MM-DD
 ```
 

package/{Development → context}/backlog/README.md

@@ -1,4 +1,4 @@
-# Development Backlog
+# Context Backlog
 
 This folder stores isolated deferred work that was cut from a release
 initiative but should remain discoverable.
@@ -10,8 +10,8 @@ Use a backlog item when:
 - it does not need durable program-level context
 - it is not active in the current release
 
-Create items from `Development/_templates/backlog-item.md` and place them in
-`Development/backlog/items/`.
+Create items from `context/_templates/backlog-item.md` and place them in
+`context/backlog/items/`.
 
 When a backlog item is picked up later, do not move or rewrite the original
 item. Mark it as `Promoted` and link to the new release initiative.

package/{Development → context}/current.md

@@ -1,4 +1,4 @@
-# Current Development Context
+# Current Context
 
 Current release: `v0_1_0`
 
@@ -26,7 +26,7 @@ Registered initiatives:
 - `releases/v0_1_0/initiatives/npm-installer-cli/` - npm initializer for
   installing this context template into existing projects.
 
-To start an initiative, copy `Development/_templates/initiative/` into
-`Development/releases/v0_1_0/initiatives/<initiative-slug>/`, then update the
+To start an initiative, copy `context/_templates/initiative/` into
+`context/releases/v0_1_0/initiatives/<initiative-slug>/`, then update the
 copied `README.md` first so agents have a clear entry point before editing the
 supporting files.

package/{Development → context}/programs/README.md

@@ -10,7 +10,7 @@ Use a program when an effort has:
 - planned future work that should remain visible
 - context that would be lost if it lived only in one release initiative
 
-Create programs from `Development/_templates/program/`.
+Create programs from `context/_templates/program/`.
 
 ## Planned Initiatives
 
@@ -19,7 +19,7 @@ to scope, split, or preserve implementation intent, but the target release is
 not current yet.
 
 When a planned initiative's target release becomes current, promote it into
-`Development/releases/<version>/initiatives/` and leave the planned initiative
+`context/releases/<version>/initiatives/` and leave the planned initiative
 behind as historical planning context.
 
 ## Current Programs

package/{Development → context}/releases/v0_1_0/README.md

@@ -1,6 +1,6 @@
-# v0.1.0 Development Context
+# v0.1.0 Context
 
-This folder contains development context for the `v0_1_0` release.
+This folder contains working context for the `v0_1_0` release.
 
 ## Navigation
 
@@ -14,20 +14,20 @@ Create an initiative when work is non-trivial, behavior-changing,
 cross-project, release-significant, or likely to need future product
 documentation.
 
-Use `Development/_templates/initiative/` as the starting point.
+Use `context/_templates/initiative/` as the starting point.
 
 ## Carry-Forward Rule
 
 If an initiative is part of a larger phased effort, link it to a program
-under `Development/programs/`.
+under `context/programs/`.
 
 If isolated work is cut from scope but should be kept for later, create a
-backlog item under `Development/backlog/items/` and link it back to the
+backlog item under `context/backlog/items/` and link it back to the
 originating initiative.
 
 ## Planned Initiative Promotion
 
 When this release becomes current, promote matching planned initiatives from
-`Development/programs/*/planned-initiatives/` into this release's
+`context/programs/*/planned-initiatives/` into this release's
 `initiatives/` folder. Leave the planned initiative in place as historical
 planning context and update its status to `Promoted`.

package/{Development → context}/releases/v0_1_0/backlog.md

@@ -1,6 +1,6 @@
 # v0.1.0 Backlog
 
-This file tracks release-level development context that is not yet captured
+This file tracks release-level working context that is not yet captured
 by an initiative, plus a short summary of initiative progress once
 initiatives exist.
 

package/{Development → context}/terminology.md

@@ -1,29 +1,29 @@
-# Development Terminology
+# Context Terminology
 
 This glossary defines the terms used by the Code-Anchored Context practice in
-`Development/`. Use these terms consistently in programs, initiatives,
+`context/`. Use these terms consistently in programs, initiatives,
 backlog items, ADRs, agent summaries, and release-transition work.
 
 ## Core Folders
 
 | Term | Meaning |
 | --- | --- |
-| `Development/` | Working development context: plans, specs, ADRs, implementation notes, delivery-surface context, future scope, and release-documentation notes. |
-| `Documentation/` | Released product documentation. It describes shipped behavior for a release/tag and is not edited during normal development work. |
-| `Development/current.md` | Pointer to the current active release context. Updating this is a release transition. |
-| `Development/releases/<version>/` | Release-scoped development context for one version. |
-| `Development/programs/` | Durable multi-release development context. |
-| `Development/backlog/items/` | Deferred isolated work cut from initiatives but worth preserving. |
+| `context/` | Working context: plans, specs, ADRs, implementation notes, delivery-surface context, future scope, and release-documentation notes. |
+| `docs/` | Released product documentation. It describes shipped behavior for a release/tag and is not edited during normal development work. |
+| `context/current.md` | Pointer to the current active release context. Updating this is a release transition. |
+| `context/releases/<version>/` | Release-scoped working context for one version. |
+| `context/programs/` | Durable multi-release working context. |
+| `context/backlog/items/` | Deferred isolated work cut from initiatives but worth preserving. |
 
 ## Work Containers
 
 | Term | Meaning | Lives in |
 | --- | --- | --- |
-| Program | A cross-release parent effort with durable context, roadmap, phase history, and program-level decisions. | `Development/programs/<program-slug>/` |
-| Planned initiative | A scoped future delivery slice that belongs to a program but is not in the current release yet. | `Development/programs/<program-slug>/planned-initiatives/<initiative-slug>/` |
-| Release initiative | An active or historical delivery slice for a specific release. | `Development/releases/<version>/initiatives/<initiative-slug>/` |
-| Development backlog item | Isolated deferred work that was cut from an initiative and may be picked up later. | `Development/backlog/items/<originating-initiative>--<item>.md` |
-| Program release slice | A program-level summary of what a release is expected to do or did for the program. | `Development/programs/<program-slug>/releases/<version>.md` |
+| Program | A cross-release parent effort with durable context, roadmap, phase history, and program-level decisions. | `context/programs/<program-slug>/` |
+| Planned initiative | A scoped future delivery slice that belongs to a program but is not in the current release yet. | `context/programs/<program-slug>/planned-initiatives/<initiative-slug>/` |
+| Release initiative | An active or historical delivery slice for a specific release. | `context/releases/<version>/initiatives/<initiative-slug>/` |
+| Context backlog item | Isolated deferred work that was cut from an initiative and may be picked up later. | `context/backlog/items/<originating-initiative>--<item>.md` |
+| Program release slice | A program-level summary of what a release is expected to do or did for the program. | `context/programs/<program-slug>/releases/<version>.md` |
 
 ## Choosing The Right Container
 
@@ -36,7 +36,7 @@ or needs a roadmap beyond one release.
 Use a planned initiative when future program work is clear enough to plan,
 specify, or split, but the target release is not current yet.
 
-Use a development backlog item when an isolated piece of work was cut from
+Use a context backlog item when an isolated piece of work was cut from
 scope and should be preserved, but it does not need program-level context.
 
 ## Files
@@ -45,7 +45,7 @@ The structure follows delivery concerns, not technologies. Use concern names
 such as `testing.md`, `delivery.md`, and `infrastructure.md`; name specific
 tools inside those files only when the tools matter.
 
-Mermaid is the preferred diagram syntax for development context because it is
+Mermaid is the preferred diagram syntax for working context because it is
 both readable Markdown for agents and renderable visual context for humans.
 
 | Term | Meaning |
@@ -60,7 +60,7 @@ both readable Markdown for agents and renderable visual context for humans.
 | `infrastructure.md` | Stable description of environment shape, IaC, resources, networking, identity, storage, secrets, and environment dependencies. |
 | `operations.md` | Optional actionable runtime support context: observability, failure modes, rollback, repair, support procedures, and tooling. |
 | `backlog.md` | Trackable work items for the containing initiative or program. |
-| `release-doc-notes.md` | Notes for future product documentation refresh work. This is the bridge to `Documentation/`. |
+| `release-doc-notes.md` | Notes for future product documentation refresh work. This is the bridge to `docs/`. |
 | ADR | Architecture Decision Record. Use for durable decisions and tradeoffs. |
 | `brief.html` | Optional human-friendly presentation layer. |
 
@@ -88,15 +88,15 @@ Planned initiatives are promoted when their target release becomes current or
 when release planning explicitly begins:
 
 ```text
-Development/programs/<program>/planned-initiatives/<initiative>/
-  -> Development/releases/<version>/initiatives/<initiative>/
+context/programs/<program>/planned-initiatives/<initiative>/
+  -> context/releases/<version>/initiatives/<initiative>/
 ```
 
 Backlog items are promoted when someone decides to pick them up:
 
 ```text
-Development/backlog/items/<originating-initiative>--<item>.md
-  -> Development/releases/<version>/initiatives/<initiative>/
+context/backlog/items/<originating-initiative>--<item>.md
+  -> context/releases/<version>/initiatives/<initiative>/
 ```
 
 Promotion does not silently move or delete the original context. Leave the
@@ -105,7 +105,7 @@ original planned initiative or backlog item in place, update its status to
 
 ## Release Transition
 
-A release transition is the act of changing `Development/current.md` to a new
+A release transition is the act of changing `context/current.md` to a new
 release. This is not just a line edit.
 
 During a release transition, agents should:
@@ -117,4 +117,4 @@ During a release transition, agents should:
 - update links both ways
 - leave planned initiatives as historical planning context
 
-Use `Development/_templates/release-transition.md` as the checklist.
+Use `context/_templates/release-transition.md` as the checklist.

package/{Documentation → docs}/Welcome.md

@@ -1,15 +1,15 @@
-# PROJECT_NAME Documentation
+# PROJECT_NAME Docs
 
 Welcome to the release-anchored documentation for PROJECT_NAME.
 
 This folder describes shipped behavior for a known release or tag. It is not
 the place for in-progress feature planning, implementation notes, or draft
-architecture decisions. Put that work in `Development/`.
+architecture decisions. Put that work in `context/`.
 
-## How This Documentation Is Organized
+## How These Docs Are Organized
 
 ```text
-Documentation/
+docs/
   .order
   Welcome.md
   releases/
@@ -30,7 +30,7 @@ Every documented area should have:
 
 - a high-level `README.md` that explains the area's purpose and architecture
 - one page per feature under `features/`
-- an authoring guide under `Documentation/_authoring/areas/`
+- an authoring guide under `docs/_authoring/areas/`
 
 ## Contributing
 
@@ -45,4 +45,4 @@ Every documented area should have:
 - Describe behavior, inputs, outputs, permissions, errors, business rules, and
   operational expectations in domain language.
 - Prefer Mermaid diagrams for flows, architecture, and relationships.
-- Add release refreshes to `Documentation/releases/index.md`.
+- Add release refreshes to `docs/releases/index.md`.