code-anchored-context 0.1.0

package/Development/_templates/planned-initiative/infrastructure.md

@@ -0,0 +1,30 @@
+# Infrastructure
+
+Use this file for future environment shape and infrastructure dependencies
+that are already clear enough to preserve.
+
+## Environment Shape
+
+Describe expected resources, services, networks, identity boundaries, storage,
+compute, queues, topics, or runtime hosts.
+
+## Infrastructure As Code
+
+| Resource or module | Change | Location | Notes |
+| --- | --- | --- | --- |
+| TBD | TBD | TBD | TBD |
+
+## Configuration And Secrets
+
+List expected environment variables, app settings, feature flags, secrets,
+certificates, secret manager references, or secret-rotation needs.
+
+## Environment Dependencies
+
+Capture expected dependencies between environments, regions, tenants,
+subscriptions, clusters, accounts, or shared services.
+
+## Compatibility And Migration
+
+Describe expected infrastructure compatibility windows, provisioning order,
+migration constraints, or cleanup work.

package/Development/_templates/planned-initiative/interface.md

@@ -0,0 +1,41 @@
+# Interface
+
+## Purpose
+
+Describe how humans, clients, APIs, configuration, reports, or tools should
+interact with this future delivery slice.
+
+## Surfaces
+
+- UI:
+- API:
+- CLI or scripts:
+- Configuration:
+- Reports or exports:
+
+Remove surfaces that do not apply.
+
+## Workflows
+
+Describe the user, operator, support, or integration workflows.
+
+## Inputs And Outputs
+
+| Surface | Inputs | Outputs |
+| --- | --- | --- |
+| TBD | TBD | TBD |
+
+## States And Feedback
+
+Capture loading, empty, success, validation, warning, and error states when
+they apply.
+
+## Permissions
+
+Describe who can see, change, trigger, approve, or audit the behavior.
+
+## Terminology
+
+Record terms that must stay consistent across UI, API, docs, logs, and
+support language.
+

package/Development/_templates/planned-initiative/operations.md

@@ -0,0 +1,41 @@
+# Operations
+
+Use this file only when the planned initiative has actionable runtime,
+support, observability, rollback, or repair implications that are already
+clear enough to preserve.
+
+If there is nothing concrete for an agent or engineer to act on, omit this
+file after copying the template or mark it as not applicable. Delivery belongs
+in `delivery.md`; environment shape and IaC belong in `infrastructure.md`.
+
+## Runtime Behavior
+
+Describe expected live-system behavior, especially jobs, schedules, queues,
+topics, subscriptions, retries, degraded modes, or runtime compatibility
+constraints.
+
+## Observability And Support Signals
+
+Capture expected logs, metrics, traces, dashboards, alerts, health checks,
+support signals, and customer-visible symptoms.
+
+## Failure Modes
+
+Describe expected failures, retries, poison-message behavior, timeouts,
+partial outages, degraded modes, and support signals.
+
+## Rollback And Recovery
+
+Describe expected recovery constraints. Include whether rollback is likely to
+be safe, whether roll-forward is required, and what state might need repair.
+
+## Data Operations And Repair
+
+Capture expected migrations, backfills, cleanups, retention, repair scripts,
+manual support procedures, and validation queries.
+
+## Actionable Tooling
+
+List CLIs, scripts, dashboards-as-code, alerts-as-code, or other approved
+automation integrations that agents or engineers may need. If none exists, say
+so explicitly.

package/Development/_templates/planned-initiative/plan.md

@@ -0,0 +1,40 @@
+# Plan
+
+Use this file as the working alignment space for future scoped work. It may
+contain rough thinking, questions, options, partial plans, and notes from
+collaboration sessions.
+
+`plan.md` is allowed to be messy, but it must not become the only place where
+settled truth lives. Promote stable conclusions into the appropriate planned
+initiative files before the target release becomes current.
+
+## Current Alignment
+
+Describe the current agreed future direction.
+
+## Working Notes
+
+- Note 1
+
+## Open Questions
+
+- Question 1
+
+## Options Considered
+
+| Option | Pros | Cons | Status |
+| --- | --- | --- | --- |
+| TBD | TBD | TBD | Open |
+
+## Notes To Promote
+
+- [ ] Move settled behavior into `spec.md`
+- [ ] Move settled interface details into `interface.md`
+- [ ] Move settled technical shape into `architecture.md`
+- [ ] Move settled verification strategy into `testing.md`
+- [ ] Move settled delivery and pipeline behavior into `delivery.md`
+- [ ] Move settled environment and IaC context into `infrastructure.md`
+- [ ] Move actionable runtime/support concerns into `operations.md`
+- [ ] Move executable future work into `backlog.md`
+- [ ] Move durable program decisions into the parent program's `decisions/`
+- [ ] Move product-documentation impact into `release-doc-notes.md`

package/Development/_templates/planned-initiative/release-doc-notes.md

@@ -0,0 +1,28 @@
+# Release Documentation 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
+explicitly asks for a documentation refresh or a specific documentation fix.
+
+## Expected Product Behavior Changes
+
+- None yet.
+
+## Candidate Documentation Areas
+
+- `Documentation/<Area>/README.md`
+- `Documentation/<Area>/features/<feature>.md`
+
+## QA Or Support Notes
+
+- None yet.
+
+## Exclusions
+
+Record details that were considered but should not be documented because
+they are internal implementation details, temporary scaffolding, or might not
+ship.
+

package/Development/_templates/planned-initiative/spec.md

@@ -0,0 +1,37 @@
+# Spec
+
+## Purpose
+
+Describe what the future delivery slice should do and why this behavior
+matters.
+
+## Goals
+
+- Goal 1
+- Goal 2
+
+## Non-Goals
+
+- Non-goal 1
+
+## Behavior
+
+Describe the expected behavior in product or domain language. Include:
+
+- Normal flow
+- Permission rules
+- Data rules
+- Validation rules
+- Error behavior
+- Edge cases
+
+## Acceptance Criteria
+
+- [ ] Criterion 1
+- [ ] Criterion 2
+
+## Dependencies
+
+- Related program context, earlier release initiatives, systems, teams,
+  services, or decisions.
+

package/Development/_templates/planned-initiative/testing.md

@@ -0,0 +1,30 @@
+# Testing
+
+Use this file for future verification strategy that is already clear enough to
+preserve before the target release becomes current.
+
+## Test Strategy
+
+Describe what the future release initiative will need to prove.
+
+## Automated Coverage
+
+| Area | Coverage | Tool or location | Notes |
+| --- | --- | --- | --- |
+| TBD | TBD | TBD | TBD |
+
+## Manual Verification
+
+- None identified yet.
+
+## Test Data And Environments
+
+Capture required data, fixtures, accounts, or environment assumptions.
+
+## Release Gates
+
+- TBD
+
+## Known Gaps
+
+- None identified yet.

package/Development/_templates/program/README.md

@@ -0,0 +1,63 @@
+# Program Title
+
+Status: Candidate
+Primary area: TBD
+
+## Summary
+
+Describe the durable effort, why it exists, and what outcome it is moving
+toward across releases.
+
+## Scope
+
+In scope:
+
+- TBD
+
+Out of scope:
+
+- TBD
+
+## Durable Context
+
+- `context.md`
+- `roadmap.md`
+- `backlog.md`
+- `decisions/`
+- `planned-initiatives/`
+- `releases/`
+
+Optional concern files when they span multiple releases:
+
+- `architecture.md`
+- `testing.md`
+- `delivery.md`
+- `infrastructure.md`
+- `operations.md` only when actionable runtime, support, observability,
+  rollback, or repair context spans releases.
+
+## Related Release Initiatives
+
+| Release | Initiative | Role |
+| --- | --- | --- |
+| `v0_1_0` | TBD | TBD |
+
+## Current State
+
+Describe the current status of the program and the next expected release
+slice.
+
+## Planned Initiatives
+
+Use `planned-initiatives/` for scoped future delivery slices that belong to
+this program but are not in the current release yet.
+
+## Agent Notes
+
+- Keep durable multi-release context here.
+- Use `planned-initiatives/` when future scope is clear enough to preserve as
+  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
+  need a program.

package/Development/_templates/program/backlog.md

@@ -0,0 +1,26 @@
+# Program Backlog
+
+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
+not need program-level context.
+
+Use `planned-initiatives/` instead when future work is already clear enough
+to preserve as a scoped delivery slice for a target release.
+
+## Candidates
+
+| Status | Item | Notes |
+| --- | --- | --- |
+| Candidate | TBD | TBD |
+
+## Deferred
+
+- None yet.
+
+## Promoted To Release Initiatives
+
+| Item | Release initiative | Notes |
+| --- | --- | --- |
+| TBD | TBD | TBD |

package/Development/_templates/program/context.md

@@ -0,0 +1,25 @@
+# Context
+
+## Problem
+
+Describe the durable problem or opportunity this program addresses.
+
+## Background
+
+Capture history, constraints, previous attempts, related initiatives, and
+important product or technical context.
+
+## Stakeholders And Areas
+
+| Area or stakeholder | Relevance |
+| --- | --- |
+| TBD | TBD |
+
+## Durable Principles
+
+- Principle 1
+
+## Links
+
+- Related initiatives, backlog items, ADRs, PRs, tickets, or discussions.
+

package/Development/_templates/program/decisions/ADR-0000-template.md

@@ -0,0 +1,34 @@
+# ADR-0000: Decision Title
+
+Status: Proposed
+Date: YYYY-MM-DD
+
+## Context
+
+Describe the durable program-level problem, constraints, and options.
+
+## Decision
+
+State the decision clearly.
+
+## Consequences
+
+Positive:
+
+- Consequence 1
+
+Negative or tradeoffs:
+
+- Tradeoff 1
+
+## Alternatives Considered
+
+| Alternative | Why not |
+| --- | --- |
+| TBD | TBD |
+
+## Links
+
+- Related program files, release initiatives, backlog items, PRs, tickets,
+  or discussions.
+

package/Development/_templates/program/planned-initiatives/.gitkeep

@@ -0,0 +1 @@
+

package/Development/_templates/program/releases/v0_1_0.md

@@ -0,0 +1,32 @@
+# v0.1.0 Program Slice
+
+## Release Initiative
+
+Link to the release-scoped initiative when one exists:
+
+```text
+Development/releases/v0_1_0/initiatives/<initiative-slug>/
+```
+
+## Scope
+
+Describe the slice of the program intended for this release.
+
+## Outcome
+
+Describe what shipped, what was deferred, and what should carry forward.
+
+## Planned Initiatives Promoted
+
+List planned initiatives from this program that were promoted into this
+release.
+
+| Planned initiative | Release initiative | Notes |
+| --- | --- | --- |
+| TBD | TBD | TBD |
+
+## Links
+
+- Initiative:
+- Backlog items:
+- ADRs:

package/Development/_templates/program/roadmap.md

@@ -0,0 +1,27 @@
+# Roadmap
+
+This roadmap describes expected phases across releases. It is directional,
+not a promise that every phase will ship exactly as written.
+
+## Phases
+
+| Phase | Target release | Outcome | Status |
+| --- | --- | --- | --- |
+| Phase 1 | TBD | TBD | Candidate |
+| Phase 2 | TBD | TBD | Candidate |
+
+## Release Slices
+
+| Release | Initiative | Scope | Notes |
+| --- | --- | --- | --- |
+| `v0_1_0` | TBD | TBD | TBD |
+
+## Planned Initiatives
+
+| Target release | Planned initiative | Scope | Status |
+| --- | --- | --- | --- |
+| TBD | TBD | TBD | Planned |
+
+## Risks And Dependencies
+
+- Risk or dependency 1

package/Development/_templates/release-context/README.md

@@ -0,0 +1,33 @@
+# vNEXT Development Context
+
+This folder contains development context for the `vNEXT` release.
+
+## Navigation
+
+- `backlog.md` tracks release-level work that has not yet been moved into
+  an initiative or that summarizes initiative progress.
+- `initiatives/` contains initiative folders.
+
+## Initiative Rule
+
+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.
+
+## Carry-Forward Rule
+
+If an initiative is part of a larger phased effort, link it to a program
+under `Development/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
+originating initiative.
+
+## Planned Initiative Promotion
+
+When this release becomes current, promote matching planned initiatives from
+`Development/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/_templates/release-context/backlog.md

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

package/Development/_templates/release-context/initiatives/.gitkeep

@@ -0,0 +1 @@
+

package/Development/_templates/release-transition.md

@@ -0,0 +1,39 @@
+# Release Transition Checklist
+
+Use this checklist when changing `Development/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.
+- [ ] Create `README.md`, `backlog.md`, and `initiatives/` for the target
+      release if missing.
+- [ ] Scan `Development/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>/
+```
+
+- [ ] Update the promoted release initiative so it links back to the parent
+      program and planned initiative.
+- [ ] Update the planned initiative metadata:
+
+```md
+Status: Promoted
+Promoted to: `Development/releases/<target-release>/initiatives/<initiative-slug>/`
+Promoted on: YYYY-MM-DD
+```
+
+- [ ] Update the parent program `README.md`, `roadmap.md`, `backlog.md`, or
+      `releases/<target-release>.md` as needed.
+- [ ] Leave the planned initiative in place as historical planning context.
+
+## Rule
+
+Planned initiatives are promoted, not moved silently.

package/Development/backlog/README.md

@@ -0,0 +1,17 @@
+# Development Backlog
+
+This folder stores isolated deferred work that was cut from a release
+initiative but should remain discoverable.
+
+Use a backlog item when:
+
+- the work came from a real initiative or implementation discussion
+- it is useful enough to preserve
+- 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/`.
+
+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.