Files
channel-kanban-skic/references/aerosim-lessons-review.md
T

36 lines
4.8 KiB
Markdown

# AeroSim lessons review — kanban
## Evidence boundary
Source repository: [corp-v1-aerosim-skills-code-agent/channel-kanban-skic-aerosim](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/channel-kanban-skic-aerosim)
Source commit: `526de6b6e4c331bd7e44794b6485d04d3e006eed` (branch `test`, pinned clone; not the earlier adoption-base SHA).
Central baseline: `e8507ad71813a7d9ba9e70f69f7e8a7bdf530a7b`. Reviewed the full source package: `SKILL.md`, `ADOPTION.md`, and `references/kanban-bootstrap-and-validation.md`, `references/recurring-refresh-and-publication.md`. All existing source reference files were byte-identical to central at baseline; changes below address omissions or contradictions, not wholesale copying.
The installed `channel-kanban-skic-aerosim/SKILL.md` was also compared read-only. Runtime SHA-256: `a942940d69fb4c165a1dc33bc301347d4b565e6d88ebe3915091d35515f5e950`. Runtime differs from the pinned repository and has no verified source commit for its local-only changes; it is observation, not remote or Board approval evidence. This delegated review did not change any installed package or AeroSim/other project copy. The coordinating session owns authorized central publication and central runtime refresh.
Review authority: Board-owner request message `1562171939961966693` authorizes central reference improvement and remote publication; the coordinating session also owns the authorized central runtime refresh. Central source publication must be verified before refreshing its installed package. No project adoption, project permission/authority expansion or naming migration is authorized.
## Adopted lessons
- `SKILL.md` → **Overview** (ownership paragraph): an acceptance/UAT verdict belongs to a frozen deployment, separate from Task state and release authority. Keep acceptance separate from flow; UAT topology comes from the already-approved central operating model, not project permission inheritance.
- `references/recurring-refresh-and-publication.md` → **Live deployment evidence without a governed item mapping**, plus `SKILL.md` → **State Reconciliation**: operational health does not retroactively establish scope, admission or release readiness. Expose source/template divergence and exact evidence, preserving unrelated valid Focus work instead of globally clearing the queue.
- `SKILL.md` → **Human Approval Gate**, **Board**, **Focus**, and `ADOPTION.md` → **Semantic synchronization — READY_FOR_DELIVERY pickup gate**: align the older bootstrap/refresh references with the existing exact-task admission gate. Correct four-versus-five columns, restore ReadyForDelivery to bootstrap sections, and remove the stale human-approval requirement for mere InBacklog visibility. Admission is distinct from Scope's canonical delivery vocabulary.
## Exclusions
The existing structural/evidence-readiness, publication-lag and concurrent-writer references already contain the reusable detail; do not duplicate them. No named approver, standing merge delegation, runtime-only blocker execution mandate, board URL or broader channel access is imported. Runtime-only **Hermes owns blocker resolution** and **Standing AeroSim PR merge authority** differ from the pinned repository and are not central authority. The prohibition on direct or delegated implementation from Kanban remains unchanged.
## Central topology authority
The coordinating review record `GUILD-IMP-20261020-aerosim-reference-lessons` confirms central-only maintenance. `channel-board-skic` v4.5.0, **Board Authority** / **Naming Model** / **Hermes access and Corp project automation policy**, records Board message `1552966246591365123` approving eight lifecycle channels, with UAT between Delivery and Releases. Align ordinary synchronization and references to that existing policy. Historical seven-channel bootstrap overrides are not widened; only separately reauthorized overrides may add UAT. Runtime seven-channel wording is stale, not promoted authority.
## Remaining authority issue
`channel-board-skic` v4.5.0 **Documentation Repository** and **Kickoff Definition of Done** still describe four columns and human admission into `InBacklog`, conflicting with the existing central Kanban **Human Approval Gate** / **Focus** exact-task `READY_FOR_DELIVERY` contract and the pinned AeroSim `ADOPTION.md` pickup-gate decision. This review removes that stale wording only inside the owned Kanban package. It does not modify or declare a new approval for `channel-board-skic`; its maintainer must reconcile the cross-skill inconsistency through the Board workflow.
## Verification
Run `python3 -B -m unittest discover -s tests -v` from this repository and `git diff --check`. Tests validate normative documentation contracts and linked files offline; they do not claim live workflow, CI, deployment or remote publication verification.