Files
2026-09-22 19:23:17 +02:00
..
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00
2026-09-22 19:23:17 +02:00

Current documentation index

AIM 3.3.0rc8. These files supersede previous release-specific handoffs/checklists. Do not copy an old validation status into a new release. Archive history externally; keep the reverse-chronological CHANGELOG in the distribution.

Topic Authoritative document
Release changes RELEASE_NOTES.md
Current evidence and limits VALIDATION.md
Operator acceptance procedure SANITY.md
Fresh installation INSTALLATION.md
Update and recovery deploy/README.md
Core development AGENTS.md
Add-on implementation responsibilities ADDON_AGENTS.md
API request/response lifecycle ADDON_API.md
Purposeful data and schema authoring OPERATION_RESULTS.md
Safe execution progress DETAILED_PROGRESS.md
Native target outcomes TARGET_OUTCOMES.md
Inventory tree INVENTORY_HIERARCHY.md
Hardened execution environment EXECUTOR_STAGING.md
Implemented/deferred boundary ADDON_SUPPORT.md
Current handoff checklist RELEASE_HANDOFF.md
Playbook options and reports PLAYBOOKS.md
Checkmk-specific operational settings CHECKMK.md

addon-support-v1.json is a snapshot of default capabilities, not a release manifest or runtime acceptance certificate. aimctl capabilities reports the installed state. The nine files in playbooks/schemas/ are normative data shapes; schema definitions are also resolved into catalog metadata so add-ons need not access the filesystem.

  • CHANGELOG.md — retained release history.
  • roles/*/README.md — role-specific reference documentation stays beside each role.
  • deploy/README.md — deployer/update/rollback mechanics stay beside the deployer.