• 1:
• 2:
• 3:

bazel_agent bazel run //tools/openspec -- list --specs
OPENSPEC_PROJECT=projects/agents bazel_agent bazel run //tools/openspec -- list
OPENSPEC_PROJECT=infra/vault bazel_agent bazel run //tools/openspec -- list --specs

bazel_agent bazel test //infra/src/openspec/validation:validate_test //infra/src/openspec/validation:archive_test

1 -

Goal migration to OpenSpec

On 2026-09-08, all nine tracked maintained project goal records at source commit 550d7e79b1f5fdbc2b6017b75178471d6914082f were migrated into native OpenSpec changes. Each change now lives in its owning project’s openspec/ workspace. Eight completed records are imported as archived history. The Reimu Fumo change remains open with blocked execution and no accepted candidate.

The machine-readable inventory maps all 222 tracked source files (834,320 bytes) to byte-identical provenance snapshots. Test fixtures and ignored task scratch are outside the maintained-record inventory.

Record mapping

Mapping and acceptance

• Objective and scope map to proposal.md; accepted plans, decisions, rejected approaches, and constraints map to design.md.
• The latest acceptance criteria map to tasks.md and meaningful capability delta requirements. Each YAML criterion keeps its stable ID and revision in migration.json; original revisions, attempts, review verdicts, and evidence remain in provenance.
• Completed task checkboxes reproduce explicit historical acceptance reviews. They do not revalidate today’s source. The Markdown Cordis record declares Complete and no failing criteria; its absent execution field stays unavailable rather than being guessed.
• Reimu acceptance and continuation tasks remain unchecked. A supported authorized unblock can change execution while the outcome remains open until every required criterion passes.
• Completed records were placed directly in their owner’s openspec/changes/archive/2026-09-08-<id>/. No archive or spec-sync command applied their historical deltas. Current baseline specifications were derived separately from maintained owner source. Do not reapply historical deltas.
• Historical Phase 5 acceptance includes an explicit fixture-gap inventory. Its accepted review and still-pending prose are both retained; migration does not claim the missing infrastructure fixtures were implemented.

Provenance and navigation

Each change has migration.json, a checksum inventory at provenance/manifest.json, original record bytes at provenance/source/, and a provenance navigation guide. The old agent goal landing and BUILD file are also retained under the repository-agent-system archive. The historical BUILD snapshot uses .original to preserve bytes without creating a new Bazel package.

Among preserved Markdown links, 47 links depend on the former location; companion navigation tables resolve them where the referenced artifact exists. 46 historical targets are unavailable in the checkout. Original bytes and historical Git identities are not rewritten to disguise unavailable scratch or superseded paths.

The former maintained goal directories are removed, and the legacy goal tool and its store were later removed as well; native OpenSpec work is the continuation surface. Provenance files are excluded from generic formatting so their source digests remain stable. The migration inventory is import evidence, not an alternate work scheduler or mutable status catalog. The removal change is remove-deprecated-goal-component.

2 -

go-mod-version Specification

Purpose

Keep tracked go.mod files on the Go version configured for tools/go_mod.

Sources: tool README, tool BUILD, and archive.

Requirements

Requirement: Configured go.mod version

The repository SHALL provide a tools/go_mod command that discovers every tracked go.mod file and sets its go directive to the version configured in the tool’s BUILD file. The command MUST offer an update mode and a check mode.

Scenario: Update module files

• WHEN a user runs the update target
• THEN every tracked go.mod file whose go directive differs from the configured version is rewritten to that version
• AND files already on the configured version remain unchanged

Scenario: Check module files

• WHEN the check test runs
• THEN it fails if any tracked go.mod file has a go directive different from the configured version
• AND it passes when every tracked go.mod file matches

Requirement: Repository quality integration

The go.mod version check MUST run as part of //:repo_quality_test so a version mismatch fails repository quality.

Scenario: Quality suite covers the check

• WHEN a go.mod file’s go directive differs from the configured version
• THEN //:repo_quality_test fails

3 -

Repository Evolution Specification

Purpose

Define how the alwaldend/src monorepo evolves its shared structure, build system and development workflows. Component behavior is specified in each owner’s local OpenSpec workspace. This baseline was inspected at source revision 550d7e79b1f5fdbc2b6017b75178471d6914082f on 2026-09-08 and incorporates the OpenSpec migration delivered with this specification. Changes in infra/src record repository evolution; they do not collect unrelated component work or claim runtime health or deployed infrastructure.

Sources: repository map, agent policy, root build, project boundary, infrastructure boundary, tool boundary, and OpenSpec workflow.

Requirements

Requirement: Component ownership and source boundaries

The repository MUST keep component purpose and publication boundaries in the nearest owner README, executable and dependency structure in BUILD and MODULE files, and agent policy in the applicable AGENTS.md chain. Specifications SHALL describe component requirements with links to these owners.

Scenario: Select an implementation owner

• WHEN a change affects a project, tool or infrastructure component
• THEN its owning documents and Bazel workspace determine the affected paths and supported consumers
• AND a repository-wide catalog or specification does not grant broader publication or execution authority

Requirement: Reproducible Bazel development

Repository agent build and test operations MUST use bazel_agent bazel in the owning workspace with pinned dependencies and the repository’s shared agent configuration. Generated dependency and catalog files MUST be updated through their owning generator.

Every nested module that declares MODULE.bazel MUST declare only dependencies its own sources use, with a resolvable version or an override that applies when that module is the root. Every nested module directory MUST appear in the root .bazelignore so root target expansion does not cross the workspace boundary. Each nested workspace MUST build and test standalone.

Scenario: Change a shared dependency

• WHEN an implementation adds an external build input
• THEN its owner records an immutable version and integrity information
• AND applicable generated locks and package checks validate the declared dependency through the pinned build workflow

Scenario: Build a nested module standalone

• WHEN a nested Bazel workspace is built or tested on its own
• THEN its module graph resolves without depending on root-only overrides
• AND the workspace builds and tests through its shared configuration

Scenario: Expand root targets across a nested boundary

• WHEN the root workspace expands targets beneath a nested module directory
• THEN the nested workspace is excluded by the root ignore list
• AND root expansion neither loads nor silently omits that module

Requirement: Isolated implementation and evidence

Repository modifications MUST use a dedicated feature branch and linked worktree. Task scratch MUST remain under ignored out/<task>/ in the applicable workspace. Acceptance SHALL identify the candidate and relevant checks and representative output before delivery.

Scenario: Finish a repository change

• WHEN an authorized implementation is ready for delivery
• THEN task-owned changes pass applicable formatting, quality and semantic checks and are committed and published through the repository procedure
• AND unrelated edits, scratch and protected data are excluded

Requirement: Declarative infrastructure authority

Persistent infrastructure configuration MUST be defined in checked-in owning infrastructure code. Infrastructure operations MUST require the user’s exact operation and scope authorization; an implementation validation request SHALL NOT authorize live deployment.

Scenario: Validate an infrastructure specification

• WHEN an agent adds or updates an infra component specification
• THEN it inspects source and runs applicable offline checks
• AND it does not infer deployed state or execute live apply or deployment from the existence of the specification

Requirement: OpenSpec coverage and work state

Each direct project in projects/ and infra/ SHALL keep its baseline specifications and maintained changes in its own openspec/ workspace. infra/src/openspec SHALL describe evolution of the repository itself, including shared structure, build system and development workflows. The repository root SHALL NOT collect component specifications or change records. Maintained work SHALL preserve outcome, decisions, tasks and requirement deltas. Existing task authority MUST survive workflow transitions.

Scenario: Change a component contract

• WHEN a change affects a project’s supported behavior
• THEN its specifications and change artifacts remain in that project’s openspec/ directory
• AND the pinned CLI and context routing select that owner workspace

Scenario: Evolve the repository itself

• WHEN a change affects the monorepo’s shared structure or development workflow
• THEN infra/src/openspec records its repository requirements and evolution
• AND component contracts remain with their respective owners

Scenario: Resume unfinished maintained work

• WHEN an agent resumes a named OpenSpec change
• THEN it reads that owner’s change artifacts, candidate, evidence and next action
• AND unfinished or blocked acceptance remains explicit until evidence supports completion

Scenario: Validate a standalone project

• WHEN a project has its own Bazel module
• THEN repository OpenSpec validation still checks its declared local workspace
• AND a successful repository check does not omit that project’s requirements

Requirement: Legacy goal migration and deprecation

The migration SHALL preserve all tracked maintained goal history and its recorded acceptance and execution states with source-to-change mappings and checksums. The goal skill MUST be disabled for discovery and the goal tool MUST identify itself as deprecated compatibility functionality.

Scenario: Inspect a migrated historical record

• WHEN a reader follows a legacy goal’s migration entry
• THEN its OpenSpec change exposes the original history and status
• AND historical completion does not establish acceptance for a different candidate or automatically apply old specification deltas

Requirement: Rule scripts and generated documentation

Bazel rules MUST NOT embed templated executable content in rule source. A rule that needs an executable MUST reference an ordinary checked-in script and supply its inputs as declared arguments or data files. Every public rule set MUST generate stardoc documentation for its public .bzl entry points, and the repository’s main documentation output MUST include that generated documentation.

Scenario: A rule needs to run scripted logic

• WHEN an implementation needs a rule to run a script
• THEN the script is checked in as a normal file with its own target and receives data through arguments or a declared data file
• AND generated shell or program text does not live in the .bzl source

Scenario: A rule set exposes public rules

• WHEN a project publishes a public Bazel rule or macro
• THEN it declares stardoc coverage for the declaring file
• AND the generated pages appear in the repository documentation build

Requirement: Bazel rule modules are tool components

First-party standalone Bazel rule modules SHALL live under tools/<module>/. Their relocation MUST preserve module names, supported public rule and macro interfaces, standalone workspace resolution, generated rule documentation, and owner-local specifications. Repository consumers and discovery mechanisms MUST resolve their new source locations through the owning declarations.

Scenario: Consume a relocated rule module

• WHEN a root or nested workspace loads a relocated rule module through its supported module name and public rule interface
• THEN the module resolves from its new tool-owned location
• AND its supported build behavior remains available without changing the public module identity

Scenario: Discover a relocated owner’s specifications and rules

• WHEN repository documentation, skill discovery, or OpenSpec validation traverses the relocated modules
• THEN it selects the modules’ new owner paths
• AND generated rule documentation and existing component specifications remain included in their declared outputs and checks

Requirement: Rule tools do not publish dedicated project landings

The relocated rule modules SHALL have no dedicated project landing-site configuration. After authorized retirement, their selected landing repository and DNS declarations MUST be absent from the owning infrastructure, and shared-catalog consumers MUST exclude those retired repositories. Retirement MUST preserve unrelated repositories, sites, access grants, and authentication resources.

Scenario: Build or import the remaining repository catalog

• WHEN the catalog is projected for GitHub or GitLab after rule-landing retirement
• THEN the retired landing repositories are absent
• AND remaining repositories retain their catalog identities, names, and configured access behavior

Scenario: Retire a selected landing site

• WHEN the owning declarative workflows execute the user’s explicitly authorized retirement scope
• THEN the selected Pages repository and matching DNS record are removed
• AND the reviewed plans and postconditions show no unrelated deletion or replacement