refactor: migrate Markdown to AsciiDoc

.claude/PROJECT.adoc

@@ -0,0 +1,33 @@
+== Infrastructure-Automation - Claude Code Instructions
+
+This repository contains the Infrastructure-Automation project.
+
+=== Project Structure
+
+....
+infrastructure-automation/
+├── .claude/         # AI assistant instructions
+├── .git/           # Version control
+├── .gitignore      # Git ignore rules
+├── .editorconfig   # Editor configuration
+└── ...             # Project files
+....
+
+=== Build Commands
+
+Refer to project-specific documentation.
+
+=== Coding Conventions
+
+* Follow hyperpolymath standards
+* All code must have SPDX license headers
+* Use approved languages only (see CLAUDE.md)
+* Document all non-obvious decisions
+
+=== Security
+
+* No hardcoded secrets
+* All secrets through environment variables or secret management
+* SHA-pinned dependencies where applicable
+* HTTPS only, no HTTP URLs
+* No MD5/SHA1 for security purposes

CHANGELOG.adoc

@@ -0,0 +1,64 @@
+== Changelog
+
+All notable changes to `+infrastructure-automation+` will be documented
+in this file.
+
+This file is generated from conventional commits by the
+https://github.com/hyperpolymath/standards/blob/main/.github/workflows/changelog-reusable.yml[`+changelog-reusable.yml+`]
+workflow (`+hyperpolymath/standards#206+`). Adopt the workflow in this
+repo’s CI to keep this file in sync automatically — see
+https://github.com/hyperpolymath/standards/blob/main/templates/cliff.toml[`+templates/cliff.toml+`]
+for the canonical config.
+
+The format follows https://keepachangelog.com/en/1.1.0/[Keep a
+Changelog]; this project aims to follow
+https://semver.org/spec/v2.0.0.html[Semantic Versioning].
+
+=== [Unreleased]
+
+==== Added
+
+* feat(crg): add crg-grade and crg-badge justfile recipes
+* feat: add stapeln.toml container definition
+* feat: deploy UX Manifesto infrastructure
+* feat: add CLADE.a2ml — clade taxonomy declaration
+* feat: add mirror.yml workflow for GitLab/Bitbucket mirroring
+* feat: complete SaltStack to Ansible + Terraform migration
+
+==== Fixed
+
+* fix(scorecard): enforce granular permissions and add fuzzing
+placeholder
+* fix(ci): Resolve workflow-linter self-matching and metadata issues
+* fix: correct email jonathan.jewell → j.d.a.jewell
+* fix: SPDX headers (AGPL→PMPL), email, author name
+* fix: suppress deprecation warnings for ansible-core 2.24
+* fix: resolve Silverblue compatibility issues across all roles
+* fix: use $((x + 1)) instead of ((x++)) in self-check
+
+==== Changed
+
+* refactor: migrate 6SCM → 6A2 (.scm → .a2ml format)
+
+==== Documentation
+
+* docs: substantive CRG C annotation (EXPLAINME.adoc)
+* docs: add EXPLAINME.adoc — prove-it file backing README claims
+* docs: add design change rationale for Salt to Ansible migration
+
+==== CI
+
+* ci: deploy dogfood-gate, add Groove manifest and CRG tests
+* ci: migrate CodeQL Action v3 → v4
+* ci: update SHA pins for codeql-action and trufflehog
+* ci: deploy missing standard workflows (10 added)
+
+=== Pre-history
+
+Prior commits to this file’s introduction are recorded in git history
+but not formally classified into Keep-a-Changelog sections. To backfill,
+run `+git cliff -o CHANGELOG.md+` locally using the canonical
+https://github.com/hyperpolymath/standards/blob/main/templates/cliff.toml[`+cliff.toml+`]
+— this is one-shot mechanical work.
+
+'''''

CODE_OF_CONDUCT.adoc

@@ -0,0 +1,14 @@
+== Code of Conduct
+
+This project follows the
+https://www.contributor-covenant.org/[Contributor Covenant] v2.1.
+
+=== Summary
+
+* Be respectful and inclusive
+* Accept constructive criticism gracefully
+* Focus on what is best for the community
+
+=== Contact
+
+j.d.a.jewell@open.ac.uk

CONTRIBUTING.adoc

@@ -0,0 +1,30 @@
+== Contributing
+
+=== Development Workflow
+
+[arabic]
+. Read `+0-AI-MANIFEST.a2ml+` for project conventions
+. Read `+.machine_readable/STATE.scm+` for current status
+. Make changes following existing patterns
+. Test with `+just check+` (dry run)
+. Validate with `+just lint+`
+. Run `+just self-check+` to verify
+
+=== Role Development
+
+When adding a new Ansible role:
+
+[arabic]
+. Create directory structure: `+tasks/+`, `+defaults/+`, `+meta/+`
+. Add `+meta/main.yml+` with role metadata (homoiconic self-description)
+. Add `+defaults/main.yml+` with documented default variables
+. Ensure all tasks are idempotent
+. Add the role to the appropriate playbook
+. Update `+TOPOLOGY.md+`
+
+=== Code Standards
+
+* All files must have `+# SPDX-License-Identifier: CC-BY-SA-4.0+`
+* Ansible tasks must have descriptive `+name+` fields
+* Variables must be documented with comments in `+defaults/main.yml+`
+* Use `+ansible.builtin.*+` fully qualified collection names

GOVERNANCE.adoc

@@ -0,0 +1,60 @@
+== Governance
+
+=== Overview
+
+This project is governed by the following principles and structures to
+ensure transparent, inclusive, and effective decision-making.
+
+=== Roles and Responsibilities
+
+==== Maintainers
+
+Maintainers are responsible for: - Reviewing and merging pull requests -
+Managing releases and versioning - Ensuring code quality and standards -
+Triaging issues and bug reports - Community engagement and support
+
+==== Contributors
+
+Contributors are expected to: - Follow the code of conduct - Submit
+well-documented pull requests - Write tests for new functionality -
+Maintain existing tests - Update documentation as needed
+
+=== Decision Making
+
+==== Minor Changes
+
+* Can be made by any maintainer
+* Include bug fixes, documentation updates, dependency updates
+
+==== Major Changes
+
+* Require discussion in issues or pull requests
+* Include new features, architectural changes, API changes
+* Need approval from at least 2 maintainers
+
+==== Breaking Changes
+
+* Require RFC (Request for Comments) process
+* Need approval from majority of maintainers
+* Must include migration guide
+
+=== Code of Conduct
+
+All participants are expected to follow our Code of Conduct. Violations
+can be reported to the maintainers.
+
+=== Communication
+
+* *Issues*: For bug reports and feature requests
+* *Discussions*: For questions and general discussion
+* *Pull Requests*: For code contributions
+
+=== Licensing
+
+All contributions are made under the terms of the repository’s LICENSE
+file. By submitting a pull request, you agree to license your
+contributions accordingly.
+
+'''''
+
+_Last updated: 2026-07-18_