chore: merge dev to main

.bestpractices.json

@@ -0,0 +1,70 @@
+{
+  "name": "Reproducible Agentic Environments System",
+  "description": "RAES describes and validates authored agentic-environment scenarios, with published contracts, examples, conformance checks, and a Python reference implementation.",
+  "homepage_url": "https://raesystem.github.io/rae/",
+  "repo_url": "https://github.com/RAESystem/rae",
+  "license": "MIT",
+  "implementation_languages": "Python",
+  "description_good_status": "Met",
+  "description_good_justification": "The README states the purpose, scope, first successful task, and current limits: https://github.com/RAESystem/rae#readme.",
+  "interact_status": "Met",
+  "interact_justification": "Public GitHub issues and pull requests support URL-addressable discussion: https://github.com/RAESystem/rae/issues.",
+  "contribution_status": "Met",
+  "contribution_justification": "Contribution setup and pull-request steps are in https://github.com/RAESystem/rae/blob/main/CONTRIBUTING.md.",
+  "contribution_requirements_status": "Met",
+  "contribution_requirements_justification": "CONTRIBUTING.md documents the dev branch, tests, docs rules, and Conventional Commit pull-request titles.",
+  "floss_license_status": "Met",
+  "floss_license_justification": "RAES uses the MIT License.",
+  "floss_license_osi_status": "Met",
+  "floss_license_osi_justification": "MIT is an OSI-approved open source license.",
+  "license_location_status": "Met",
+  "license_location_justification": "The license is at https://github.com/RAESystem/rae/blob/main/LICENSE.",
+  "documentation_basics_status": "Met",
+  "documentation_basics_justification": "The README and docs/public provide installation, a tested quickstart, concepts, task guides, research context, and limits.",
+  "documentation_interface_status": "Met",
+  "documentation_interface_justification": "The public Python, CLI, SDL, backend, and generated API pages document the current external interfaces.",
+  "sites_https_status": "Met",
+  "sites_https_justification": "The repository and package page use HTTPS.",
+  "discussion_status": "Met",
+  "discussion_justification": "GitHub issues and pull requests provide public, searchable, URL-addressable discussion.",
+  "english_status": "Met",
+  "english_justification": "Project documentation, issue templates, and contribution routes accept English.",
+  "maintained_status": "Met",
+  "maintained_justification": "The public repository has current commits, releases, issues, and pull requests.",
+  "repo_public_status": "Met",
+  "repo_public_justification": "The source repository is public at https://github.com/RAESystem/rae.",
+  "repo_track_status": "Met",
+  "repo_track_justification": "The project uses Git and preserves public history on GitHub.",
+  "repo_interim_status": "Met",
+  "repo_interim_justification": "Development work is visible on the public dev branch between releases.",
+  "version_unique_status": "Met",
+  "version_unique_justification": "Each published package release has a unique PEP 440 version.",
+  "version_semver_status": "Met",
+  "version_semver_justification": "Release Please manages semantic versions from Conventional Commit titles.",
+  "version_tags_status": "Met",
+  "version_tags_justification": "Release Please creates a matching Git tag and GitHub release.",
+  "release_notes_status": "Met",
+  "release_notes_justification": "Release Please publishes human-readable GitHub release notes and maintains CHANGELOG.md.",
+  "report_tracker_status": "Met",
+  "report_tracker_justification": "GitHub Issues is the public defect tracker.",
+  "report_archive_status": "Met",
+  "report_archive_justification": "GitHub archives and indexes issue reports and their discussion.",
+  "vulnerability_report_process_status": "Met",
+  "vulnerability_report_process_justification": "SECURITY.md explains how to report a suspected vulnerability.",
+  "vulnerability_report_private_status": "Met",
+  "vulnerability_report_private_justification": "SECURITY.md directs reporters to GitHub private vulnerability reporting or a private maintainer contact.",
+  "test_status": "Met",
+  "test_justification": "CONTRIBUTING.md documents the canonical nox verification command.",
+  "test_invocation_status": "Met",
+  "test_invocation_justification": "The same locked nox command runs locally and in CI.",
+  "continuous_integration_status": "Met",
+  "continuous_integration_justification": "GitHub Actions runs repository policy, tests, docs, security, and conformance checks.",
+  "code_of_conduct_status": "Met",
+  "code_of_conduct_justification": "The project policy is at https://github.com/RAESystem/rae/blob/main/CODE_OF_CONDUCT.md.",
+  "governance_status": "Met",
+  "governance_justification": "The maintainer-led decision and release model is at https://github.com/RAESystem/rae/blob/main/GOVERNANCE.md.",
+  "bus_factor_status": "Unmet",
+  "bus_factor_justification": "RAES currently has one maintainer, so its bus factor is below two.",
+  "two_person_review_status": "Unmet",
+  "two_person_review_justification": "The single-maintainer project does not require independent two-person review for every change."
+}

.claude/agents/completion-verifier.md

@@ -1,14 +1,14 @@
 ---
 name: completion-verifier
-description: Verifies ACES SDL repo-policy, requirement-governance, changelog, and ADR-index completion before Claude stops.
+description: Verifies RAES SDL repo-policy, requirement-governance, changelog, and ADR-index completion before Claude stops.
 tools: Read, Grep, Glob, Bash
 model: sonnet
 maxTurns: 20
 ---
 
 # Completion Verifier
 
-You verify that implementation work is complete for ACES SDL. Prefer the
+You verify that implementation work is complete for RAES SDL. Prefer the
 repo-owned policy scripts over ad hoc reasoning.
 
 Run these checks and return your verdict:
@@ -18,7 +18,7 @@ Run these checks and return your verdict:
 - Run `git diff --name-only HEAD` to see what files changed.
 - Determine whether Python implementation or test files changed under
   `implementations/python/`.
-- Determine the active requirement UID from `ACES_REQUIREMENT_UID` or the branch
+- Determine the active requirement UID from `RAES_REQUIREMENT_UID` or the branch
   name.
 
 ## 2. Run repo policy checks

.claude/hooks/verify-extra.sh

@@ -12,13 +12,13 @@ if [[ ! -x "$PY" ]]; then
   exit 0
 fi
 
-if ! "$PY" "$ROOT/tools/check_repo_policy.py" >/tmp/aces-sdl-policy.out 2>&1; then
-  tr '\n' ' ' </tmp/aces-sdl-policy.out
+if ! "$PY" "$ROOT/tools/check_repo_policy.py" >/tmp/raes-sdl-policy.out 2>&1; then
+  tr '\n' ' ' </tmp/raes-sdl-policy.out
   exit 0
 fi
 
-if ! "$PY" "$ROOT/tools/check_requirement_governance.py" >/tmp/aces-sdl-gc.out 2>&1; then
-  tr '\n' ' ' </tmp/aces-sdl-gc.out
+if ! "$PY" "$ROOT/tools/check_requirement_governance.py" >/tmp/raes-sdl-gc.out 2>&1; then
+  tr '\n' ' ' </tmp/raes-sdl-gc.out
   exit 0
 fi
 

.claude/skills/raes-asset-inventory-capture/SKILL.md

@@ -1,18 +1,18 @@
 ---
 name: raes-asset-inventory-capture
-description: Run the ACES asset inventory methodology as an agent-runnable capture workflow from either Claude Code or Codex. Use when asked to inventory a target image, container, host, or asset into a methodology-conformant evidence bundle with mapping-ledger.yaml, explicit capture-limits.txt declinations, scanner/SBOM evidence, and ACES/APTL gap triage.
+description: Run the RAES asset inventory methodology as an agent-runnable capture workflow from either Claude Code or Codex. Use when asked to inventory a target image, container, host, or asset into a methodology-conformant evidence bundle with mapping-ledger.yaml, explicit capture-limits.txt declinations, scanner/SBOM evidence, and RAES/APTL gap triage.
 ---
 
-# ACES Asset Inventory Capture
+# RAES Asset Inventory Capture
 
 This skill runs from either Claude Code or Codex. Use it as the canonical
 agent entry point for the participant-discoverable asset inventory
-methodology: capture evidence first, map facts to ACES only when the mapping is
+methodology: capture evidence first, map facts to RAES only when the mapping is
 semantically correct, and leave every omission as durable evidence.
 
-The ACES methodology remains the authority. Read
-`docs/raes/inventory/asset-inventory-methodology.md` from the ACES repo before
-capture; when working in a downstream checkout, use that ACES document as the
+The RAES methodology remains the authority. Read
+`docs/raes/inventory/asset-inventory-methodology.md` from the RAES repo before
+capture; when working in a downstream checkout, use that RAES document as the
 canonical source. This skill operationalizes that prose; it does not define a
 second ledger schema or a second secret taxonomy.
 
@@ -67,9 +67,9 @@ it.
 Run these before returning:
 
 ```shell
-aptl aces-inventory schema
-aptl aces-inventory validate <asset-dir>
-aptl aces-inventory gaps <asset-dir>
+aptl raes-inventory schema
+aptl raes-inventory validate <asset-dir>
+aptl raes-inventory gaps <asset-dir>
 ```
 
 No `needs_gap_triage` row may remain at review time.
@@ -144,8 +144,8 @@ No `needs_gap_triage` row may remain at review time.
 
 6. Build the ledger fact-by-fact.
 
-   Each captured fact needs evidence and an ACES/APTL mapping disposition:
-   `encoded`, `encoded_with_caveat`, `blocked_by_aces_gap`,
+   Each captured fact needs evidence and an RAES/APTL mapping disposition:
+   `encoded`, `encoded_with_caveat`, `blocked_by_raes_gap`,
    `blocked_by_aptl_gap`, or temporary `needs_gap_triage`. Before review,
    replace every `needs_gap_triage` with an encoded mapping or a linked gap.
 
@@ -176,7 +176,7 @@ CLI commands as fake URL paths, collapse flags into
 schema-passing representation. A fact that requires reinterpretation of the
 surface is a gap.
 
-**Lineage-before-gap gate.** Before reporting an ACES expressivity gap, read
+**Lineage-before-gap gate.** Before reporting an RAES expressivity gap, read
 `docs/explain/sdl/lineage.md`, `docs/explain/sdl/precedents.md`, relevant
 ADRs, and primary literature for the affected semantic family. The gap report
 must state the captured fact, checked surfaces, lineage/prior-art treatment,
@@ -189,18 +189,18 @@ explicitly asks for upstream design work.
 
 ## Gap Handling
 
-When current ACES cannot express a participant-discoverable fact:
+When current RAES cannot express a participant-discoverable fact:
 
-1. Search existing ACES and APTL issues.
+1. Search existing RAES and APTL issues.
 2. If a matching issue exists, link it in `mapping-ledger.yaml`.
 3. If none exists, file or draft a gap with evidence path, discovery vantage,
-   checked ACES surfaces, lineage/prior-art notes, and why the surfaces are
+   checked RAES surfaces, lineage/prior-art notes, and why the surfaces are
    insufficient.
 4. Stop for discussion before continuing through additional gaps when the
    methodology or issue asks for that pause.
 
-Do not use APTL backend consumption gaps as a substitute for ACES SDL
-expression. Do not use ACES schema shape as the authority for what was
+Do not use APTL backend consumption gaps as a substitute for RAES SDL
+expression. Do not use RAES schema shape as the authority for what was
 discovered.
 
 ## Completion Checklist
@@ -219,8 +219,8 @@ Before returning:
   limits;
 - scenario-target secrets are preserved as source capture facts, while
   operator/out-of-scenario material is excluded or recorded as a capture limit;
-- `aptl aces-inventory validate <asset-dir>` passes;
-- `aptl aces-inventory gaps <asset-dir>` has no unresolved
+- `aptl raes-inventory validate <asset-dir>` passes;
+- `aptl raes-inventory gaps <asset-dir>` has no unresolved
   `needs_gap_triage`;
 - any methodology document in the target checkout references this skill as the
   canonical agent entry point;

.claude/skills/raes-asset-inventory-capture/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "ACES Asset Inventory Capture"
-  short_description: "Run the ACES asset inventory methodology."
-  default_prompt: "Use $raes-asset-inventory-capture to capture a methodology-conformant ACES asset inventory bundle for a target image or container."
+  display_name: "RAES Asset Inventory Capture"
+  short_description: "Run the RAES asset inventory methodology."
+  default_prompt: "Use $raes-asset-inventory-capture to capture a methodology-conformant RAES asset inventory bundle for a target image or container."

.claude/skills/raes-asset-inventory-capture/scripts/normalize-syft-cyclonedx.jq

@@ -1,4 +1,4 @@
-# Deterministic ACES inventory Syft CycloneDX normalization.
+# Deterministic RAES inventory Syft CycloneDX normalization.
 # Allowed transform: remove Syft file-location component properties only.
 def strip_syft_location_properties:
   walk(

.claude/skills/raes-gap-remediation-implement/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: raes-gap-remediation-implement
-description: Architecture-first overlay for remediating ACES/APTL gaps, especially gaps found by the ACES asset inventory capture methodology. Use before normal Ground Control /implement work when a gap may require new or changed SDL/runtime semantics, schemas, validators, ADRs, docs, capture mappings, or cross-repo ACES/APTL behavior. Forces whole-surface review, lineage and primary-literature grounding, peer-review-grade justification, and then delegates to the repo's standard Ground Control implement workflow.
+description: Architecture-first overlay for remediating RAES/APTL gaps, especially gaps found by the RAES asset inventory capture methodology. Use before normal Ground Control /implement work when a gap may require new or changed SDL/runtime semantics, schemas, validators, ADRs, docs, capture mappings, or cross-repo RAES/APTL behavior. Forces whole-surface review, lineage and primary-literature grounding, peer-review-grade justification, and then delegates to the repo's standard Ground Control implement workflow.
 ---
 
-# ACES Gap Remediation Implement
+# RAES Gap Remediation Implement
 
 Use this skill as an overlay before the normal Ground Control implementation
 lane. It does not replace `/implement`; it supplies the architecture and
@@ -12,7 +12,7 @@ documentation obligations that must be carried into `/implement`.
 The expected review bar is academic peer review for tier-1 publication: a
 reviewer must be able to reconstruct why the remediation exists, why existing
 surfaces were insufficient, why the chosen design is not duplicative, and how
-the implementation follows established ACES lineage and relevant external
+the implementation follows established RAES lineage and relevant external
 practice.
 
 ## Operating Rule
@@ -35,11 +35,11 @@ Before invoking `/implement`, produce or add to the issue a brief with these
 sections:
 
 1. **Gap Claim**: captured fact, discovery vantage, evidence paths, affected
-   scenario/asset, and the assurance claim that current ACES/APTL cannot make.
+   scenario/asset, and the assurance claim that current RAES/APTL cannot make.
 2. **Existing Surface Audit**: SDL sections, runtime subdomains, schemas,
    validators, parser aliases, module refs, docs, examples, and related issues
    checked. State why each near match is insufficient.
-3. **Lineage and Precedent**: relevant ACES lineage, precedents, ADRs, prior
+3. **Lineage and Precedent**: relevant RAES lineage, precedents, ADRs, prior
    issues/PRs, and downstream APTL usage. Explain whether the gap extends an
    existing family or requires a new one.
 4. **Literature and Practice**: primary literature and core/adjacent practice
@@ -67,7 +67,7 @@ Run this gate before choosing a design.
   service, sensor, manager, content, evidence, and source/provenance families as
   applicable.
 - Check whether the fact is scenario state, delivery infrastructure, evidence,
-  control-plane machinery, downstream APTL consumption, or an ACES SDL
+  control-plane machinery, downstream APTL consumption, or an RAES SDL
   expression gap.
 - Treat duplicate parallel surfaces as a design failure. Extend the established
   family when the semantics belong there; create a new family only when the
@@ -81,7 +81,7 @@ Reject an implementation plan if any gate fails.
   generic relationships, or arbitrary key/value fields.
 - **No shallow schema pass**: do not choose the representation that validates
   while changing the meaning of the captured fact.
-- **No downstream-only fix**: do not patch APTL consumption when ACES lacks the
+- **No downstream-only fix**: do not patch APTL consumption when RAES lacks the
   needed expression surface.
 - **No docs-free surface**: every new or changed semantic surface needs public
   rationale in ADR/docs, not just tests.

.claude/skills/raes-gap-remediation-implement/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "ACES Gap Remediation"
+  display_name: "RAES Gap Remediation"
   short_description: "Architecture-first gap remediation overlay"
-  default_prompt: "Use $raes-gap-remediation-implement to remediate an ACES/APTL gap through the Ground Control implement workflow."
+  default_prompt: "Use $raes-gap-remediation-implement to remediate an RAES/APTL gap through the Ground Control implement workflow."

.codex

@@ -8,7 +8,7 @@ Use the repo policy tooling before and after implementation work.
 - `implementations/python/.venv/bin/python tools/check_requirement_governance.py`
 - `implementations/python/.venv/bin/python tools/verify_all.py`
 
-Set `ACES_REQUIREMENT_UID` when the branch name does not already contain a UID
+Set `RAES_REQUIREMENT_UID` when the branch name does not already contain a UID
 such as `GOV-918`.
 
 ## Hard rules
@@ -17,7 +17,7 @@ such as `GOV-918`.
   `docs/`, and `implementations/`.
 - Do not edit `contracts/schemas/` directly; change generator inputs and
   regenerate.
-- Do not recreate the retired `implementations/python/src/aces/` namespace.
+- Do not recreate retired compatibility namespaces.
 - Import only the owning `raes` or `raes_*` packages under
   `implementations/python/packages/`.
 - Keep concept-authority artifacts in the approved concept-authority surfaces.