code-anchored-context 0.1.1 → 0.2.0

package/{Development → context}/README.md

@@ -1,12 +1,12 @@
-# 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
 
@@ -16,24 +16,24 @@ implementation plans, and release-documentation notes. Do not use
   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 +50,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 +82,7 @@ not copy specs, plans, or ADRs into area-local documents.
 ## Standard Layout
 
 ```text
-Development/
+context/
   current.md
   programs/
     <program-slug>/
@@ -140,11 +140,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 +214,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 +241,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 +251,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}/code-anchored-context-structure.md

@@ -1,7 +1,7 @@
 # Code-Anchored Context: The Structure
 
 This is the companion to the
-[reasoning article](code-anchored-context-why.md). It covers how development
+[reasoning article](code-anchored-context-why.md). It covers how working
 context is laid out so both humans and agents can navigate it.
 
 ## Denormalize Navigation, Not Knowledge
@@ -15,24 +15,24 @@ keeps its own plans, cross-project work fragments.
 
 Local `AGENTS.md` files point agents toward the right place. But plans, specs,
 ADRs, release context, testing strategy, delivery notes, and infrastructure
-context live centrally under `Development/`.
+context live centrally under `context/`.
 
 ## The Core Model
 
-Vocabulary is captured in `Development/terminology.md`. The main containers:
+Vocabulary is captured in `context/terminology.md`. The main containers:
 
 ```text
 Program                  Long-lived multi-release effort.
 Planned initiative       A scoped future slice inside a program.
 Release initiative       Active or historical work for a specific release.
-Development backlog item Isolated work cut from scope but worth preserving.
+Context backlog item     Isolated work cut from scope but worth preserving.
 Program release slice    What a release contributes to a program.
 ```
 
 Each kind of context gets a home:
 
 ```text
-Development/
+context/
   terminology.md
   current.md
   programs/
@@ -49,7 +49,7 @@ knowledge it preserves, not the tool that produced it.
 The main unit of active delivery:
 
 ```text
-Development/releases/<version>/initiatives/<initiative>/
+context/releases/<version>/initiatives/<initiative>/
   README.md   plan.md   spec.md   interface.md   architecture.md
   testing.md  delivery.md  infrastructure.md  operations.md
   backlog.md  decisions/  release-doc-notes.md
@@ -85,7 +85,7 @@ Some work is bigger than one release. A program holds durable multi-release
 context:
 
 ```text
-Development/programs/<program>/
+context/programs/<program>/
   README.md  context.md  roadmap.md  backlog.md
   decisions/  planned-initiatives/  releases/
 ```
@@ -94,20 +94,20 @@ Future work that is clear enough to plan — but whose target release is not
 current yet — becomes a planned initiative:
 
 ```text
-Development/programs/<program>/planned-initiatives/<initiative>/
+context/programs/<program>/planned-initiatives/<initiative>/
 ```
 
 When the target release becomes current, it is promoted into
-`Development/releases/<version>/initiatives/<initiative>/`. Promotion is
+`context/releases/<version>/initiatives/<initiative>/`. Promotion is
 explicit; the original planned initiative stays as historical context.
 
-## Development Backlog
+## Context Backlog
 
 Work cut from scope but worth preserving — when it doesn't justify a program or
 planned initiative — lives in:
 
 ```text
-Development/backlog/items/<originating-initiative>--<item>.md
+context/backlog/items/<originating-initiative>--<item>.md
 ```
 
 Each item records where it came from, why it was deferred, future value, and
@@ -117,7 +117,7 @@ silently rewritten.
 ## Release Transitions
 
 Changing the current release is more than editing a pointer. When
-`Development/current.md` moves to a new release, agents should scan program
+`context/current.md` moves to a new release, agents should scan program
 planned initiatives, promote items targeting the new release into the release
 folder, update links both ways, and preserve the originals as history.
 

package/{Development → context}/code-anchored-context-why.md

@@ -13,19 +13,19 @@ That context usually exists — in chats, tickets, pull request comments,
 planning notes, and people's heads — but agents need it in a structured,
 discoverable form.
 
-## Documentation vs Development
+## Docs vs Working Context
 
-This is why I separate **released product documentation** from **development
+This is why I separate **released product documentation** from **working
 context**:
 
 ```text
-Documentation/   What shipped.
-Development/      What we are planning, building, deciding, testing,
+docs/   What shipped.
+context/      What we are planning, building, deciding, testing,
                   shipping, hosting, deferring, and learning.
 ```
 
 Product documentation stays stable and release-accurate: it describes a known
-release, not an unfinished branch. Development context is allowed to evolve —
+release, not an unfinished branch. Working context is allowed to evolve —
 it is where humans and agents work through ambiguity.
 
 ## The Principle
@@ -52,8 +52,8 @@ instead of reconstructing it from memory.
 ```mermaid
 flowchart LR
   Code["Codebase<br/>What exists"]
-  Dev["Development/<br/>What is being planned, built, decided, tested, shipped, deferred"]
-  Docs["Documentation/<br/>What shipped in a known release"]
+  Dev["context/<br/>What is being planned, built, decided, tested, shipped, deferred"]
+  Docs["docs/<br/>What shipped in a known release"]
   Agents["Agents and humans"]
 
   Agents --> Code
@@ -73,7 +73,7 @@ Code-Anchored Context is context continuity. It helps agents and humans answer:
 - What should become product documentation later?
 - What reasoning needs to survive a change of IDE, agent, or session?
 
-Code tells an agent *what exists*. Development context tells it *why* it
+Code tells an agent *what exists*. Working context tells it *why* it
 exists, where it is going, what has been decided, and what was left for later.
 
 For the concrete folder layout, see the companion article,