code-anchored-context 0.1.1 → 0.2.0

package/{Documentation → docs}/_authoring/workflow.md

@@ -1,4 +1,4 @@
-# Documentation Workflow
+# Docs Workflow
 
 This file defines how documentation is versioned, refreshed, and structured
 across the repo. It applies to all documented areas; area-specific guidance
@@ -7,7 +7,7 @@ lives in [`areas/`](areas/).
 ## When Docs Get Edited
 
 Doc refresh is an explicit, on-request activity, not a side effect of code
-work. Humans or agents touch `Documentation/` only when:
+work. Humans or agents touch `docs/` only when:
 
 - A human explicitly asks for a release-time refresh, typically after the
   release tag is cut and QA has signed off.
@@ -27,11 +27,11 @@ outdated, leave it alone. Flag the staleness in your summary or add it to the
 initiative's `release-doc-notes.md`, but do not edit the doc as part of the
 current change unless explicitly asked.
 
-## Documentation Modes
+## Docs Modes
 
-There are two valid ways to introduce or maintain `Documentation/`.
+There are two valid ways to introduce or maintain `docs/`.
 
-### Baseline Documentation
+### Baseline Docs
 
 Use this mode only when a human explicitly asks to document the current system
 as a starting point. This is common when adopting the template in an existing
@@ -42,23 +42,23 @@ When creating a baseline:
 1. Confirm the scope: whole repo, one product area, one feature family, or one
    operational surface.
 2. Create or update the matching area guide under
-   `Documentation/_authoring/areas/` before writing product-facing pages.
+   `docs/_authoring/areas/` before writing product-facing pages.
 3. Document stable, currently accepted behavior from the current branch,
    current tag, or explicit reference point named by the human.
 4. Prefer broad, accurate coverage over exhaustive implementation detail.
-5. Record the baseline reference in `Documentation/releases/index.md`. If
+5. Record the baseline reference in `docs/releases/index.md`. If
    there is no release tag yet, use the commit, branch, date, or human-named
    baseline label that was used as the source.
-6. Leave uncertain or future behavior out of `Documentation/`. Capture open
-   questions in `Development/` or in the area authoring guide.
+6. Leave uncertain or future behavior out of `docs/`. Capture open
+   questions in `context/` or in the area authoring guide.
 
 Baseline docs are a snapshot of the system as adopted; they are not a promise
 that every undocumented behavior is unimportant.
 
-### Release-Forward Documentation
+### Release-Forward Docs
 
 Use this mode when the team chooses not to create a full baseline. In this
-mode, `Documentation/` may start sparse. Agents capture documentation impact
+mode, `docs/` may start sparse. Agents capture documentation impact
 in initiative `release-doc-notes.md` during development, then update product
 docs only at explicit release-refresh time.
 
@@ -67,7 +67,7 @@ becomes complete incrementally around behavior the team changes and releases.
 
 ## Cadence And Versioning
 
-Docs live under `Documentation/`. After any explicit baseline pass, they are
+Docs live under `docs/`. After any explicit baseline pass, they are
 refreshed once per release, at git-tag time, after release acceptance. Release
 docs are anchored to the release tag; the docs at tag `release/v1_2_3`
 describe the behavior of that release.
@@ -76,7 +76,7 @@ Default tag names follow the convention `release/vMAJOR_MINOR_PATCH` and match
 the release branch name. If a project uses a different release convention,
 document it here before the first refresh. If the first documentation pass is
 a baseline without a tag, record the baseline reference in
-`Documentation/releases/index.md`.
+`docs/releases/index.md`.
 
 ## Audience
 
@@ -100,9 +100,9 @@ or business process can observe. Add technical detail only when it affects
 released behavior, configuration, permissions, data, integrations, errors,
 support, operations, or auditability.
 
-Documentation should be product-readable first and technically anchored
-second. It can feed release notes, but it is more durable than release notes:
-release notes summarize what changed, while `Documentation/` describes what
+Docs should be product-readable first and technically anchored
+second. They can feed release notes, but they are more durable than release notes:
+release notes summarize what changed, while `docs/` describes what
 the accepted system does as of a release or baseline.
 
 Use progressive depth:
@@ -127,7 +127,7 @@ Every documented area has two layers:
 Standard per-area layout:
 
 ```text
-Documentation/<Area>/
+docs/<Area>/
   README.md
   features/
     <feature>.md
@@ -173,14 +173,14 @@ When invoked to refresh docs for a release:
 
 1. Work from the diff `<previous-release-tag>..HEAD`, scoped to one area at a
    time.
-2. Read the matching area guide in `Documentation/_authoring/areas/`.
+2. Read the matching area guide in `docs/_authoring/areas/`.
 3. Read relevant initiative `release-doc-notes.md` files under
-   `Development/releases/<release>/initiatives/`.
+   `context/releases/<release>/initiatives/`.
 4. Update the area's `README.md` if the high-level picture changed.
 5. Update feature pages for behavior that changed.
 6. Ignore pure refactors, internal renames, test-only changes, formatting,
    lint fixes, and dependency bumps with no behavior change.
-7. Append one row to `Documentation/releases/index.md`.
+7. Append one row to `docs/releases/index.md`.
 
 ## Source Order
 
@@ -189,7 +189,7 @@ source inspection:
 
 1. Previous release tag to current release diff.
 2. Relevant initiative `release-doc-notes.md` files.
-3. Matching area guide under `Documentation/_authoring/areas/`.
+3. Matching area guide under `docs/_authoring/areas/`.
 4. Existing product documentation.
 5. Source code, tests, config, CI/CD, infrastructure, and generated artifacts
    only as needed to verify shipped behavior.
@@ -207,4 +207,4 @@ working tree and say so in the release index row.
 - Transient migration scaffolding that will be removed before or soon after
   the release.
 - Draft plans, undecided architecture, or open implementation questions. Those
-  belong in `Development/`.
+  belong in `context/`.

package/{Documentation → docs}/releases/index.md

@@ -1,4 +1,4 @@
-# Release Documentation Index
+# Release Docs Index
 
 One row per tagged release. Tag names default to `release/vMAJOR_MINOR_PATCH`
 unless the project documents a different convention.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "code-anchored-context",
-  "version": "0.1.1",
-  "description": "Install repo-local agent context, development initiatives, and release-anchored documentation scaffolding into an existing project.",
+  "version": "0.2.0",
+  "description": "Install repo-local agent context, release initiatives, and release-anchored docs scaffolding into an existing project.",
   "license": "MIT",
   "type": "module",
   "bin": {
@@ -10,21 +10,21 @@
   "files": [
     "AGENTS.md",
     ".agents/",
-    "Development/AGENTS.md",
-    "Development/README.md",
-    "Development/_templates/",
-    "Development/backlog/",
-    "Development/code-anchored-context-structure.md",
-    "Development/code-anchored-context-why.md",
-    "Development/code-anchored-context.html",
-    "Development/current.md",
-    "Development/giving-ai-agents-context-around-code.md",
-    "Development/programs/",
-    "Development/releases/v0_1_0/README.md",
-    "Development/releases/v0_1_0/backlog.md",
-    "Development/releases/v0_1_0/initiatives/.gitkeep",
-    "Development/terminology.md",
-    "Documentation/",
+    "context/AGENTS.md",
+    "context/README.md",
+    "context/_templates/",
+    "context/backlog/",
+    "context/code-anchored-context-structure.md",
+    "context/code-anchored-context-why.md",
+    "context/code-anchored-context.html",
+    "context/current.md",
+    "context/giving-ai-agents-context-around-code.md",
+    "context/programs/",
+    "context/releases/v0_1_0/README.md",
+    "context/releases/v0_1_0/backlog.md",
+    "context/releases/v0_1_0/initiatives/.gitkeep",
+    "context/terminology.md",
+    "docs/",
     "bin/",
     "README.md",
     "LICENSE"
@@ -40,6 +40,7 @@
     "codex",
     "ai",
     "documentation",
-    "development-context"
+    "working-context",
+    "docs"
   ]
 }