Skip to main content

Delivery skills

Use this reference to distinguish the accepted full program, evidence of implementation, unresolved decisions, deferred helpers and the original historical audit. Piotras authorized the full program: “implement full program”. The previous implemented minimum does not redefine the full scope. Approval establishes the work to perform; it is not evidence that every migration, policy resolution or runtime update has happened.

Full-program completion is not claimed. The program remains partial: Central and AeroSim A02/A04 are implemented and runtime-verified; app/package helpers are routed only as drafts. The current scheduler decision is PAUSED, public ownership is intentionally retained, and other-project rollout is separate from the Central/AeroSim scope; contributor approval remains pending. The historical acceptance ledger remains a dated record, not the current dependency inventory. Historical immutable publications remain evidence of their bounded earlier work only. All section headings are collapsed by default; select a heading or use the contents outline.

Accepted full program and acceptance ledger​

The full program includes all A01–A18 dispositions, dependency reconciliation, complete-package provenance, selected GitOps loadability, one procedure owner, proposal-scoped naming and organization migrations, every helper assessment, semantic project rollout, tests/review/publication, runtime readback and documentation/diagram acceptance. It is neither the earlier minimum nor a requirement to manufacture seven helpers.

Authority boundary: Home remains distinct. Existing project overrides prevail; applicable project authorization remains required for adoption. No application deployments, scheduler changes, credential/security changes or project policy waivers are implied. Delivery retains project authority, lifecycle, workspace, worker and handoff bindings. Resolve only the exact missing decision; continue independent simplification.

Status and evidence contract​

  • in_progress: work is underway; acceptance has not been demonstrated.
  • IMPLEMENTED: reviewed safe source/package clauses are merged and runtime-verified; unresolved decisions and live application acceptance are separate.
  • pending_readback: documentation awaits parent publication and deployed verification.
  • partial: bounded owner/migration/runtime receipts exist, but the complete acceptance requirement is not yet met.
  • blocked: a specific policy choice or authority evidence is still missing.
  • assessed: candidate evaluation is recorded, not extraction or rollout.
  • pending: the integrating session has not attached verified acceptance evidence for this run. This does not deny earlier bounded fixes such as A10/A18 or prove no parallel implementation exists.
  • An approved program, an assessment, a local test pass and a published/runtime-verified implementation are different records. None substitutes for another.

The full-program partial implementation evidence contains exact merged-package receipts, complete runtime per-file SHA-256 maps, 18 verified migration records and the candidate/loader/scheduler reports. Receipt source hashes pin this snapshot; later parent publications require a new readback. Migration is not source implementation, owner publication is not Delivery adoption, and local tests are not remote CI. Full-package acceptance includes scripts/tests and adoption records; private overlays and personal access inventories are not published here.

Current verified disposition snapshot​

Verified 2026-10-26 for Delivery maintainers selecting owners and identifying the decisions still pending. AeroSim v1.29.0 declares 27 direct dependencies: 18 retained + 5 concrete helper owners + 2 generic bases + 2 draft review aids; Central v1.18.0 declares 19. This count is not approval of the draft conventions or full-program closure. Both body-only fallback routes (gitops-manifest-engineering and gondor-v1-nodes) remain intact.

Central PR #17 corrected A02/A04, then AeroSim PR #44 refreshed its Central source pin. Both require independent review before substantive push and any target-base commit change invalidates merge readiness. Frozen local candidate → independent read-only review → exact reviewed push → required exact-head CI → unchanged-base merge → separate integration verification. Empty kickoff visibility has no file/tree changes and is not substantive publication. AeroSim PR #42 policy is preserved, not reimplemented or weakened. Central alignment debt is resolved; sole implementation worker, human domain ownership, lifecycle and release gates remain unchanged.

Published sourceDefault / exact integrationDisposition
glossary-skictest / 6cdd1c2601a5655b3a156102cef8081b9d1a564epublished and runtime-verified
documentation-docusaurustest / 47b94dc780bae7ab92f5dd6557127f29ec13c5c0published and runtime-verified
self-hosted-service-account-recoverytest / 577a7a4fec09f91d78026ed86f29c37b1fdcb4c6published and runtime-verified
channel-delivery-skictest / e5d00989e73e9c6a2eb9126c94469a5a569b3d2bpublished and runtime-verified
channel-delivery-skic-aerosimtest / 5d09c3c7a3ff38c3f951388fe7ca9bf2d831dea5published and runtime-verified
documentation-docusaurusmain / a58a3c22f50726310792c40867043697f7a4a7e7published and runtime-verified
develop-monorepo-pnpm-app-skictest / 22c05d002ded48dd23aa7022924e655417a0ff12v0.1.0 draft review aid; not an approved convention
develop-monorepo-pnpm-package-skictest / f4e40c41193d088d43dd3be30ea103b15a640ce1v0.1.0 draft review aid; not an approved convention

Completed source fixes: Glossary README now labels glossary-skic canonical and corp-v1-glossary compatibility. Generic documentation-docusaurus-global and independent documentation-docusaurus-vssa both load; legacy documentation-docusaurus retains VSSA entry and direct-reference compatibility. The generic source remains private; no other-project consumers were silently rerouted. Recovery has a new reviewed publication of the unchanged installed procedure, not recovered historical remote lineage. Historical authorship/revision remains unverified; no recovery operation occurred.

Draft routing, not policy adoption: develop-monorepo-pnpm-app-skic covers application lifecycle/integration; develop-monorepo-pnpm-package-skic covers package API/export/consumer compatibility. Both remain v0.1.0 drafts, installed and invoked by Central and AeroSim as review aids only. Contributors were invited; access discussion is not substantive input or approval. Existing monorepo procedures and project authority prevail.

Evidence: the A02/A04 correction receipt records exact source revisions, independent pre-push reviews and complete source/runtime hashes. 22 Central tests and 35 AeroSim tests pass in source and installed packages. All 9 packages / 135 runtime files were compared with immutable remote source bytes; no mismatches. Neither changed skill repository configures remote CI; these are local tests, not a remote CI claim. Documentation candidate and integration CI/publication are separately gated in PR #515.

Historical publication preserved: PR #514, integration 49879912dd914961d610e3d6cd38ed8c64613a2f, and its unchanged earlier reconciliation receipt describe the preceding 134-file snapshot and then-outstanding Central gap. The new receipt's source_verified_at applies to the correction, not that historical verification. Earlier VSSA CI and loader counts remain historical, not rerun claims.

Current human decisions (2026-10-26): Piotras’s explicit instruction is “1 - pause, 2- keep as is, 3 follow you recomendation”. The operator supplied the parent-session pause receipt: reconciler 6777dc7d3d82 is PAUSED, enabled=false, at 2026-10-26T10:50:48.924087+00:00. This worker records that receipt; it did not call the scheduler. Do not resume or recreate the job. The historical post-stop restart-consent gap remains historical, not an outstanding current choice.

Central Delivery and Glossary intentionally retain their current public ownership in home-v1-skills-code-agent; no transfer or visibility change is authorized or required. Finish Central/AeroSim as the bounded scope; 3DArch/E-Shop v1/Maze Next Gen rollouts stay separate, require their own channel approvals, and do not block this scope. Contributor helper drafts remain drafts, not approved conventions. Independent final QA follows this documentation publication. No application deployment is part of this work, and bounded completion does not assert unrelated project rollout or contributor acceptance.

The current reference and skill-link tables below describe the published paths. Both AeroSim-only references remain project-owned: gitea-actions-policy.md is byte-unchanged; single-subagent-task-delivery.md was updated in PR #42 for A02/A04 policy alignment. The four removed reports (ADOPTION.md, FULL-PROGRAM.md, naming-delivery-review.md, SIMPLIFICATION.md) stay absent from skill roots. Domain, lifecycle, sole-implementer, DEV/UAT/Releases and recovery interlocks remain in force.

Historical disposition snapshot (PR #15 / #41, 2026-10-23)​

This dated record is superseded by the 2026-10-26 current snapshot. Its pending findings describe that earlier verification, not current implementation.

This reference is for Delivery maintainers checking which owner to load and which clauses still need a decision. The verified implementation has 25 direct dependencies: 18 retained + 5 concrete helper owners + 2 generic bases. It is not a completed 27-pointer rollout. Both body-only fallback routes (gitops-manifest-engineering and gondor-v1-nodes) remain intact. Compatibility aliases still load.

Central PR #15 was integrated before AeroSim PR #41. AeroSim now pins central db3115aa86062b46efb29cb0585d41be524a0c8b in its operational SKILL.md; the removed ADOPTION.md is not a current source. Eight changed packages use their discovered test defaults. Complete-package verification covers 72 tracked source/runtime files. Local source tests are not remote CI: these eight packages have no configured CI workflows or exact-head tasks.

Published ownerActual default / integrationState
ci-runtime-skictest / a31736f010e770257dca18ecb7813ab3ba33469dcomplete for bounded source/runtime disposition
delivery-docstest / 1470de113f03bac9100046dabe57d966a175dd0ccomplete for bounded source/runtime disposition
status-reporting-skictest / d77b8037dedfd07522333fe3a2a0429bc2339228complete for bounded source/runtime disposition
development-securitytest / bd205a6b2796f694e5e7d12fc8300eb117b77916complete for bounded source/runtime disposition
development-security-skictest / ea0cb5d030b103d52b1b3c59328703ce8e9a167ccomplete for bounded source/runtime disposition
channel-delivery-skictest / db3115aa86062b46efb29cb0585d41be524a0c8bcomplete for bounded source/runtime disposition
channel-delivery-skic-aerosimtest / 653f16fa1ccfa3feb1bb5b06df1ddbba26325528complete for bounded source/runtime disposition
glossary-skictest / e34795dec9f896dfab5252a0aac40811854fb2e7complete for bounded source/runtime disposition

The four removed reports (ADOPTION.md, FULL-PROGRAM.md, naming-delivery-review.md, SIMPLIFICATION.md) remain absent from AeroSim source/runtime. No replacement root audit reports were added. Evidence belongs in this documentation and its downloadable JSON, not distributed skill roots.

The reference disposition and skill-link disposition tables below describe actual published paths, not proposed-only allocation. The two AeroSim-only references remain byte-identical. Glossary now uses glossary-skic in the existing public organization; the former public name redirects. This is not a transfer to private SKIC ownership.

SKILL.md sectionCentral dispositionAeroSim disposition
Overviewempty heading removedempty heading removed
When to Useredundant triggers removed; unique exclusion moved before Authority and Escalationredundant triggers removed; unique exclusion moved before Authority and Escalation
Common Pitfallsentry duplicate removed; topic owners and residual exception reference loaded at decision pointnot present originally; not manufactured
Verification Checklistmoved to one explicitly invoked references/final-verification.mdnot present originally; not manufactured
Project-Adoption Delivery Lessonsduplicated lifecycle/PR/CI rules consolidated; unique Task/authority constraints retained in Decision-point referencesnot present originally; not manufactured
Proactive Iteration Requirementmerged into Synchronization Workflowmerged into Synchronization Workflow
Synchronization Workflowsingle retained workflow; useful activity and no-filler guard folded inconsolidated from Proactive Iteration and end-to-end dispatch reference; no duplicate dispatch algorithm
Shared Corp v1 System Loginmoved to security boundary owner loads; Board remains credential authoritynot present originally; not manufactured
Documentation Ownershipmoved to delivery-docs with concrete authoring/glossary bindingsnot present originally; not manufactured

One explicitly invoked references/final-verification.md replaces each repeated entry checklist. Security helpers bind shared login to Board policy; delivery-docs owns documentation outcomes and invokes concrete authoring/glossary bindings. Helpers coordinate existing procedure owners rather than duplicating their mechanics. Local authority, six stages, the sole implementer, DEV/UAT/Releases boundaries and exact recovery interlocks remain in force.

Independent verification reran source and runtime suites: 17 central, 29 AeroSim and 15 helper tests per location, including 50 safeguard-removal subtests per location. The real Hermes loader passed 41 skill names and 27 reference loads. One nonblocking defect remains: Glossary README line 5 still labels the old alias as the skill. Correct it to glossary-skic and label corp-v1-glossary as compatibility in a source follow-up; published SKILL.md and both loader names already work. This is not an unqualified implementation-complete verdict.

Partial / blocked / deferred: A02 and A04 need explicit human policy choices; gate-dependent thinning is partial. A17 needs exact post-stop resumption evidence; this work changes no scheduler. App/package helpers remain deferred for missing distinct sourced scope and removable procedure; no empty packages are counted. Recovery loads but remote provenance remains unverified. Global Docusaurus identity remains source-qualified and fail-closed. Public/private transfers and other-project adoption still require their own decisions.

Historical partial implementation snapshot (before PR #15 / #41)​

Historical receipts below establish 18 verified migrations, 15 merged source packages and 17 runtime package readbacks. All 18/18 direct dependencies load. Safe Delivery/owner clauses are IMPLEMENTED; full-program completion is not claimed. Candidate dispositions remain 5 existing-owner + 2 deferred; no seven-helper rollout is asserted.

Central Delivery v1.15.0, PR #14, a1741dc061f9d11f6871ada7cc4440f1ea9f8bb3 was published first. AeroSim v1.26.0, PR #39, 5094671b5f78026a51e9c3da0e891cf299a75076 explicitly pins that central revision in ADOPTION.md; central-first adoption and installed equality are verified. Final source review passed 27 central and 38 AeroSim checks; the adoption-delta review reran 38 AeroSim checks. These are offline package contracts, not application CI. Earlier pending statements in preparation reviews are historical and superseded by these receipts.

Migration receipts​

Repository IDSource → targetDefault branchTransfer status
131home-v1-skills-code-agent/development-monorepo-pnpm → global-skills/development-monorepo-pnpmtestverified
152corp-v1-aerosim-skills-code-agent/channel-releases-skic-aerosim → skic-aerosim-skills/channel-releases-skic-aerosimtestverified
118home-v1-skills-code-agent/development-branching-strategy → global-skills/development-branching-strategytestverified
123home-v1-skills-code-agent/development-scripts → global-skills/development-scriptstestverified
132home-v1-skills-code-agent/devsecops-ci-cd-gitea → global-skills/devsecops-ci-cd-giteatestverified
285home-v1-skills-code-agent/development-integrity → global-skills/development-integritymainverified
286home-v1-skills-code-agent/development-gates → global-skills/development-gatesmainverified
287home-v1-skills-code-agent/development-method-ttd → global-skills/development-method-ttdmainverified
294home-v1-skills-code-agent/development-durable-wave-execution → global-skills/development-durable-wave-executionmainverified
136corp-v1-aerosim-skills-code-agent/development-branching-strategy-aerosim → skic-aerosim-skills/development-branching-strategy-skic-aerosimtestverified
139corp-v1-aerosim-skills-code-agent/development-scripts-aerosim → skic-aerosim-skills/development-scripts-skic-aerosimtestverified
140corp-v1-aerosim-skills-code-agent/devsecops-ci-cd-gitea-aerosim → skic-aerosim-skills/devsecops-ci-cd-gitea-skic-aerosimtestverified
141corp-v1-aerosim-skills-code-agent/documentation-docusaurus-aerosim → skic-aerosim-skills/documentation-docusaurus-skic-aerosimtestverified
151corp-v1-aerosim-skills-code-agent/channel-delivery-skic-aerosim → skic-aerosim-skills/channel-delivery-skic-aerosimtestverified
133home-v1-skills-code-agent/development-gitops-argo-cd-gondor-v1 → home-gondor-v1-skills/development-gitops-argo-cd-home-gondor-v1testverified
144home-v1-skills-code-agent/home-v1-discord → global-skills/discordtestverified
189home-v1-skills-code-agent/home-v1--truenas → global-skills/truenastestverified
149corp-v1-aerosim-skills-code-agent/channel-general-skic-aerosim → skic-aerosim-skills/channel-general-skic-aerosimtestverified

Migration-time refs, protections and destination team IDs remain in the JSON receipt; these are not the later owner-publication heads.

Merged owners and runtime source hashes​

Owner repositoryMerged sourcePR / candidate CIRuntime source SHA
global-skills/development-gates02e716ddff053c71a921839419ed2bd2334f1e67PR #2 · not configured; local contract tests only02e716ddff053c71a921839419ed2bd2334f1e67
global-skills/development-integrity3ca0fbb284b5eb194ad5ff1f2756f1fde0077c6aPR #1 · not configured; local contract tests only3ca0fbb284b5eb194ad5ff1f2756f1fde0077c6a
global-skills/development-method-ttdd3d91be7bb2926b0f1bd16db60c0fe2250ed8d39PR #1 · not configured; local contract tests onlyd3d91be7bb2926b0f1bd16db60c0fe2250ed8d39
global-skills/development-durable-wave-executiona180018ef3bc337bb1fbabd095fa7a4e13471fc5PR #1 · not configured; local contract tests onlya180018ef3bc337bb1fbabd095fa7a4e13471fc5
home-gondor-v1-skills/development-gitops-argo-cd-home-gondor-v17ceb741c5fecbe34eb06e10a72e3ae26e3cc6f14PR #2 · not configured; local contract tests only7ceb741c5fecbe34eb06e10a72e3ae26e3cc6f14
global-skills/discord952c63ad28c27435e42d7ab7f3bd7ada0f629a4fPR #1 · not configured; local contract tests only952c63ad28c27435e42d7ab7f3bd7ada0f629a4f
global-skills/truenas91472bb7ed253bc3790be2968dfebcb4a0efa012PR #5 · success91472bb7ed253bc3790be2968dfebcb4a0efa012
global-skills/devsecops-ci-cd-gitea669e28eadfe79ac7cb3c10ccdea318dd5296d481PR #2 · not configured; local contract tests only669e28eadfe79ac7cb3c10ccdea318dd5296d481
skic-aerosim-skills/development-branching-strategy-skic-aerosim8cea0b52070d560da8cae26796d219963cf33560PR #1 · not configured; local contract tests only8cea0b52070d560da8cae26796d219963cf33560
skic-aerosim-skills/development-scripts-skic-aerosim80e9051fef0fc8be35f9da4b570068b8b83a0576PR #1 · not configured; local contract tests only80e9051fef0fc8be35f9da4b570068b8b83a0576
skic-aerosim-skills/devsecops-ci-cd-gitea-skic-aerosime2f20cb4de76e289d0883cf98fde9032c98ba372PR #2 · not configured; local contract tests onlye2f20cb4de76e289d0883cf98fde9032c98ba372
skic-aerosim-skills/documentation-docusaurus-skic-aerosim42b1227e2b04fa18ba29d489f4c4ebb9885209e1PR #3 · not configured; local contract tests only42b1227e2b04fa18ba29d489f4c4ebb9885209e1
global-skills/development-scripts0e36552938da94c0539e39b35256b8effe34c25dPR #2 · not configured; local contract tests only0e36552938da94c0539e39b35256b8effe34c25d
home-v1-skills-code-agent/channel-delivery-skica1741dc061f9d11f6871ada7cc4440f1ea9f8bb3PR #14 · not configured; local contract tests onlya1741dc061f9d11f6871ada7cc4440f1ea9f8bb3
skic-aerosim-skills/channel-delivery-skic-aerosim5094671b5f78026a51e9c3da0e891cf299a75076PR #39 · not configured; local contract tests only5094671b5f78026a51e9c3da0e891cf299a75076

Additional runtime readbacks (not new merge claims):

  • home-v1-skills-code-agent/development-gitops-argo-cd at 510b2bb590118362804d6036cbbf37db72dc21d0.
  • global-skills/development-branching-strategy at 636aba2b9e0957705fc874f07b310a4be9916f1c.

The JSON retains every published changed-file hash and complete runtime file-hash map. TrueNAS candidate task 11483 succeeded; integrated task 11484 also succeeded (run 7306); the other recorded packages explicitly report not configured; local contract tests only, not green remote CI. Loader acceptance covers canonical/historical Gondor GitOps, its generic base, Discord and TrueNAS; the TrueNAS external scan collision was resolved and the alias subsequently loaded successfully. This is not live application/API acceptance.

Other-project owning-channel handoffs​

GET-verified handoff messages request approval; they are not adoption receipts. All three source/runtime packages remain unchanged.

ProjectStatusOwning-channel handoff
3darchpending_project_approvalVerified handoff
eshopv1pending_project_approvalVerified handoff
mazengpending_project_approvalVerified handoff

Remaining gates​

  • A02: Unresolved substantive review/push order; empty kickoff visibility is not a policy choice.
  • A04: Unresolved base-advance invalidation and evidence requirements; full-program approval is not an exact choice.
  • A17: Creation context resolved; exact human post-stop resumption authority remains a bounded evidence gap, not a finding of unauthorized operation.
  • visibility: Central Delivery and Glossary are public; target skic-skills is private. Preserve effective visibility or obtain an explicit owning decision before transfer.
  • general_hotspot: General migration is COMPLETE (repository 149); existing PR #2 remains open/out-of-scope, not a naming blocker. Parent reports coordination comment 5412 and preserved PR head/base; no domain merge or source edit claimed.
  • rollout: Central-first AeroSim source adoption is IMPLEMENTED and runtime-verified; other-project own-channel adoption remains pending (CUGA not applicable).
  • global_docusaurus: Global Docusaurus source-qualified identity collision remains pending; no overwrite of the VSSA installation is authorized.
  • docs: PR #511 previous-snapshot publication and deployed readback are verified; the additional current diagram and revised evidence still await their own publication and deployed readback.

Historical A17 evidence includes original authorization and the later explicit stop (human stop instruction). The 2026-10-26 explicit pause supersedes the pending current-choice interpretation, not this historical record.

A17 chronology: the September 22 stop remains distinct from the September 26 TODO-task question 1553356862118690959, the bot’s direct creation reply 1553357667123331164, and execution 1553359083116036238 for job 6777dc7d3d82. The creation trigger is known; explicit post-stop resumption consent was not located in the bounded history. This neither proves unauthorized operation nor authorizes a scheduler change.

Full-program acceptance ledger (historical bounded implementation)​

IDThis runAcceptance requirementEvidence contract
A01IMPLEMENTEDDelegate exact-head review/CI/integration algorithms to one existing owner; retain project lifecycle exits.Clause-level before/after map, decision-point loads and exact-head gate regression tests.
A02blockedResolve substantive review/push order explicitly; distinguish empty kickoff visibility from candidate publication.Recorded exact policy resolution and published sequence tests; broad approval alone is not the choice.
A03IMPLEMENTEDPreserve executor review, main-session packet verification and the existing one-worker override.Protected override diff and role tests proving no invented independent reviewer or human gate.
A04blockedResolve base-advance invalidation and evidence requirements before thinning gate procedures.Recorded exact base-drift decision, old/new base evidence and regression tests.
A05IMPLEMENTEDRetain mandatory TTD and named exception authority; bound local discard without destroying valid shared work.RED/GREEN contract tests and clause mapping for isolated experiments versus shared forward repair.
A06IMPLEMENTEDMap durable whole-wave accountability to eligible per-Task claims without promoting blocked members.Persistent ledger contract, admission/recovery tests and verified documentation-lock serialization.
A07IMPLEMENTEDDelegate checkpoint evidence while retaining canonical states, requested wave formatting and destinations.Before/after reporting map, explicit integrity loads and tests preserving non-approval semantics.
A08IMPLEMENTEDMap escalation to advice without a second implementer; preserve same-gate repair and independent work.Help-trigger and role contract tests, owner routing and protected worker/repair continuity evidence.
A09IMPLEMENTEDReconcile CI owner source/runtime drift before replacing the duplicate three-case pipeline policy.Published complete CI package, candidate artifact/readback tests and runtime equality evidence.
A10IMPLEMENTEDPreserve the already corrected artifact-validation boundary; do not reopen the obsolete blanket Helm exclusion.Regression tests distinguishing static Delivery artifact checks from functional non-unit UAT verification.
A11IMPLEMENTEDPreserve Task release, unpadded attempt, early visibility and standing merge authority over generic Git mechanics.Protected project naming/delegation tests and reconciled branching owner publication.
A12IMPLEMENTEDKeep Board login policy and specialist recovery mechanics authoritative; retain exact project recovery interlocks.Qualified owner provenance/load tests and complete recovery script/test package continuity.
A13IMPLEMENTEDSeparate storage/GitOps mechanics from DEV-only authority; repair selected loadability without losing fallback routes.Selected-owner load proof plus fallback tests; retain actual environment mappings and UAT/Releases boundaries.
A14IMPLEMENTEDDelegate exact-context preflight and toolchain mechanics without changing Task containment or repository validation.Preflight/load tests preserving workspace bindings, repository-root execution and required all-app CI.
A15IMPLEMENTEDPreserve complementary domain coverage, Docusaurus authoring and glossary ownership.Coverage comparison demonstrating no duplicate documentation platform contract or missing domain outcomes.
A16IMPLEMENTEDThin repeated pitfalls only after retaining lock verification and the complete base-image safeguards.Moved-rule owner map and tests for every unmatched safeguard, not merely a shorter Delivery entry.
A17blockedBind scheduling clauses to authorization chronology, including stops and any later explicit resumption.Original authority/stop/resumption evidence and conditional contract tests; no scheduler mutation.
A18IMPLEMENTEDCarry forward the prior eight-channel correction without changing handoff ownership or release acceptance.Regression check of eight-channel topology and separately verified Releases/Discord responsibilities.
provenancepartialFreeze complete published and installed packages, source identities and dependency drift, not version labels alone.Host/org/repo/default branch/immutable SHA and per-file hashes including references, scripts, tests and adoption records; private overlays excluded.
loadabilitypartialVerify the selected Gondor GitOps owner and safe fallback continuity; resolve source-qualified name collisions.Installed loader and relative-reference checks; preserve gitops-manifest-engineering and gondor-v1-nodes until safe continuity is proved.
ownershipIMPLEMENTEDKeep one authoritative procedure owner while Delivery retains project authority, lifecycle, workspace, worker and handoff bindings.Every moved clause has an owner, decision-point load and protected local binding; package-wide duplication comparison.
namingpartialApply proposal-scoped naming and organization migrations with history, access and dependency continuity; Home remains distinct.Old-to-new identity map, collision/access/protection checks, history/default-branch continuity, aliases and all metadata/body/adoption links.
candidatesassessedEvaluate all seven helpers using distinct responsibility, two concrete consumers and actual content removal.Per-candidate disposition and consumer/extraction evidence; no empty routers or quota-driven helper creation.
rolloutpartialRoll out semantically under applicable project authorization, preserving each project override.Per-project authority, source/adoption pins, semantic differences and explicit pending or non-applicable dispositions.
runtimeIMPLEMENTEDRequire complete-package tests, exact-head review, source publication and installed runtime readback.Real local and configured remote CI results, PR/merge receipts, package equality and zero-drift convergence; no-CI is not green CI.
docspartialPublish the verified partial current snapshot diagram and evidence, then verify its deployed coverage.Native editable current topology, XML/coverage checks, visual review, validate/build and exact publication/deployed readback for this bounded snapshot.

Decisions and helper dispositions​

A02/A04 are implemented in AeroSim PR #42 / v1.28.0 and preserved in v1.29.0: independent review precedes substantive push; every target-base commit change invalidates merge readiness. A05/A06/A08 safe preservation, claim and escalation contracts are implemented and reviewed; they do not decide A02/A04. A03/A11 remain existing overrides, not fresh approval requests. For A17, Piotras’s later explicit pause instruction supersedes pending-choice wording: the operator-provided parent receipt records 6777dc7d3d82 PAUSED with enabled=false at 2026-10-26T10:50:48.924087+00:00. The original stop/restart chronology remains historical evidence, not a current decision blocker. Keep public Central Delivery and Glossary ownership as is. Other-project rollout is separate, approval-gated work; complete the Central/AeroSim scope without claiming those adoptions. This documentation worker changes no scheduler.

The earlier existing-owner-only assessment is historical. Five concrete nonempty owners are now published and consumed by both central and AeroSim Delivery; the two app/package candidates now have published v0.1.0 drafts and bounded review-aid routing, not approved conventions.

CandidateActual dispositionPublished source
ci-runtime-skiccomplete: concrete contract extracted and duplicate source removedSKILL.md
delivery-docscomplete: concrete contract extracted and duplicate source removedSKILL.md
status-reporting-skiccomplete: concrete contract extracted and duplicate source removedSKILL.md
development-securitycomplete: concrete contract extracted and duplicate source removedSKILL.md
development-security-skiccomplete: concrete contract extracted and duplicate source removedSKILL.md
develop-monorepo-pnpm-app-skicv0.1.0 draft: installed review aid; contributor approval pendingSKILL.md
develop-monorepo-pnpm-package-skicv0.1.0 draft: installed review aid; contributor approval pendingSKILL.md

A helper needs a distinct responsibility, two concrete consumers of that contract and actual content removal leaving the project bindings intact. Record a justified existing-owner or deferred disposition rather than creating an empty helper. Evaluation of all seven stays in scope even when creation does not pass these criteria.

Historical diagram comparison and publication gate​

VERIFIED PARTIAL CURRENT SNAPSHOT

This native editable current diagram shows independently checked published sources and installed readbacks: central PR #17 → AeroSim PR #44, 27 direct dependencies including two draft review aids, and separate Global / Home / SKIC boundaries. Its solid arrow means central-first semantic adoption, not inherited authority. The historical diagrams below remain unchanged.

loading...

Editable source: engineering/diagrams/delivery-current-implementation.drawio. The receipt tables and remaining-gates list above provide the accessible text equivalent. Native XML remains editable even though the embedded viewer is read-only.

Snapshot acceptance is not full-program acceptance. Accept this diagram against the verified current source/runtime snapshot and its explicit paused scheduler (A17), intentionally retained public ownership, draft contributor-review limits and separate other-project scope. Exact final current diagrams may evolve after owner decisions. Recovery now has a new reviewed publication in global-skills; historical remote lineage remains unverified. Home remains separate from Global and SKIC. Five concrete helper extractions are represented; no scheduler action or application acceptance is implied.

Verified previous-snapshot publication: PR #511 merged as 15f73a28f837151a7456dc428d8409edf22c7d55; integrated CI task 11487, run 7308, succeeded. The parent receipt records authorized deployed readback with page SHA-256 9e7af7bffda585e0cd31e0fc4428301e2cac355036655f4b2f206d181441ba7d and evidence SHA-256 9fc4d5b294a1776318430b9e7651d25b0564530ae599d13a833f40d93c88d341. These hashes identify the previous snapshot, not this revised evidence or new diagram; no self-referential publication SHA is asserted. The intervening snapshot is tracked separately in PR #513; its exact-head CI and deployed readback must not be inferred from the previous snapshot receipt.

The two existing source diagrams are preserved unchanged as historical baseline / conditional proposal comparisons, not the current topology. Their target labels are not migration receipts. Safe central/AeroSim source adoption and separate Global/VSSA Docusaurus identities are verified. Public ownership intentionally stays as is; other-project own-channel adoption is separate and not a blocker for the bounded Central/AeroSim scope. Historical reconciliation publication: PR #514. Gate-correction publication: PR #515. Caption-only forward-fix: PR #516. These are distinct change records, not a claim that any numbered PR remains the current publication. Each record carries its own exact review, CI and deployed-readback evidence; evidence must not be inferred from earlier snapshots. This documentation work does not change installed skills.

The earlier implementation manifest, the pre-implementation reassessment and the original 2026-10-05 audit below are separate dated records. Their older “not approved” wording describes the authority available at that time; the full-program authorization above supersedes that scope limit, not the evidence requirements, extraction criteria or project-policy boundaries.

Recorded implementation and baseline​

Implemented minimum​

Prior bounded implementation on 2026-10-23 — not full-program completion: the recommendation to simplify through existing owners, not the original full-split comparison. Board member and AeroSim team member Piotras approved it in Guild message 1563054836508008539. Improvement: GUILD-IMP-20261023-delivery-existing-owners.

PackageImmutable publicationRemote and runtime verification
channel-delivery-skicpublished source · PR13/13 tracked files equal
channel-delivery-skic-aerosimpublished source · PR21/21 tracked files equal
  • Central Delivery: consolidated repeated lifecycle vocabulary, failure workflow, documentation coverage, CI failure classes, base-image guidance and pitfalls into their existing owning references; login loads Board and checkpoint reporting loads development-integrity at the decision point. All eight references and twelve declared dependencies remain.
  • AeroSim: semantically adopted Board login and integrity routing, routed nested-pnpm recovery to the verified AeroSim documentation owner, removed repeated Focus guidance, and corrected “seven” to “eight” without changing the channel list (A18). All nine references, eighteen declared dependencies and both conditional GitOps fallback routes remain. ADOPTION.md records the published central source commit; project overrides and original adoption history are preserved.
  • No new helper skills, organization transfers, scheduler mutations, production changes or policy waivers. Review/CI gates, worker ownership, account recovery and DEV/UAT/release boundaries remain unchanged.

Verification: 16 central and 25 AeroSim tests passed, including byte-preservation checks for protected contracts, plus the runtime-compatible frontmatter validator. Neither skill repository has a CI workflow; these are local test results and authenticated exact-commit readbacks, not remote-CI claims. Complete tracked packages, including scripts/tests and AeroSim adoption metadata, were checked against runtime. Detailed rule disposition is in each package's SIMPLIFICATION.md; the implementation manifest records all file hashes, publication identities, coverage and measured reduction.

Operational bytes (entry plus every reference, excluding tests and audit/adoption records) fell from 84,789 to 80,924 centrally and 107,273 to 105,884 in AeroSim. These are bounded reductions, not a claimed dramatic token saving; actual context use depends on loaded references.

Project rollout: five project Delivery packages were discovered and assessed. AeroSim is updated; three adopted copies await their own-channel authorization. CUGA is a compact independent context package with no central-copy dependency, so this extraction is not applicable.

ProjectDispositionEvidence / next owner
3darchpending-project-approvalApproval handoff
aerosimupdatedVerified updated package above
eshopv1pending-project-approvalApproval handoff
mazengpending-project-approvalApproval handoff
cuganot-applicableIndependent compact context package; not a central-copy adoption

Remaining boundaries: A02/A04/A06/A08/A17 remain unresolved; A03/A11 remain project-specific overrides. The central nested-pnpm recipe is deliberately retained because the installed global Docusaurus name resolves to a different source; the qualified AeroSim owner was verified independently. Dependency drift and other unchanged findings remain as in the baseline. The seven helper candidates still need distinct responsibility, two concrete consumers and demonstrated deletion before extraction. The full-split diagrams below remain comparison views, not the implemented topology.

This pre-implementation baseline was refreshed on 2026-10-23 against published sources and the active installation. The current evidence below distinguishes repository identity, installed content and proposed destinations; none is inferred from a matching version label. The original October audit remains explicitly historical in Analysis.

The purple channel-delivery-skic-aerosim boundary contains SKILL.md and its nine internal reference files. Outside that boundary, the eighteen skills currently declared by metadata.hermes.related_skills are grouped by responsibility. At that pre-implementation baseline, the installed entry point declared version 1.25.0; its content and identity have changed since the October 5 snapshot, so version alone is not freshness evidence. Each pointer names its verified Gitea organization; the installed recovery skill has no verified repository mapping and is labelled unverified, not assigned an invented organization. Green skill cards are referenced by exact name in the SKILL.md body; blue skill cards are declared only in related_skills.

Verified sources and dependency drift​

Pre-implementation check, 2026-10-23. The then-current channel-delivery-skic and channel-delivery-skic-aerosim have canonical names, but their actual repositories remain under home-v1-skills-code-agent and corp-v1-aerosim-skills-code-agent. Their SKILL.md plus all reference files match the installed bytes: 9/9 central files and 10/10 AeroSim files, independently read back at the pinned commits. This closes the old Delivery-source mismatch; it does not establish complete-package equality for scripts, assets or adoption records.

  • Central Delivery now has 8 references: the original seven operational files plus aerosim-lessons-review.md, a provenance/review record—not an eighth extraction candidate. It declares 12 dependencies.
  • AeroSim Delivery retains 9 references and 18 declared dependencies. Two additional body-only conditional routes, gitops-manifest-engineering and gondor-v1-nodes, supply fallback mechanics when the selected Gondor GitOps skill cannot load. Preserve these routes as well as the 18 metadata links.
  • corp-v1-main remains a compatibility alias to channel-board-skic, not a separate policy owner. The canonical Board is actually published in skic-skills. The earlier proposed Board label is superseded; Proposal now uses channel-board-skic.
  • Discord and TrueNAS retain their old installed/source identities in this audit. Their authorized targets remain discord / truenas under global-skills; this refresh does not report those moves completed.

Comparison inventory. Links pin the inspected commit, not a mutable branch. “Unavailable locally” describes the inspected installation, not repository nonexistence. Counts cover entry points and enumerated references only; the shared Docusaurus comparison is entry-only. See the current source and finding manifest for commit identities, per-file hashes and all 18 finding records. The original evidence download remains a historical snapshot.

Skill / pinned entry pointActual source locationCompared files
channel-board-skicskic-skills/channel-board-skic · test5 equal / 0 different / 0 unavailable locally
channel-delivery-skichome-v1-skills-code-agent/channel-delivery-skic · test9 equal / 0 different / 0 unavailable locally
channel-delivery-skic-aerosimcorp-v1-aerosim-skills-code-agent/channel-delivery-skic-aerosim · test10 equal / 0 different / 0 unavailable locally
channel-general-skic-aerosimcorp-v1-aerosim-skills-code-agent/channel-general-skic-aerosim · test1 equal / 1 different / 0 unavailable locally
channel-releases-skic-aerosimcorp-v1-aerosim-skills-code-agent/channel-releases-skic-aerosim · test2 equal / 0 different / 0 unavailable locally
corp-v1-glossaryhome-v1-skills-code-agent/corp-v1-glossary · test1 equal / 0 different / 0 unavailable locally
corp-v1-mainCompatibility alias → channel-board-skicNot treated as a published/equal package
development-branching-strategyhome-v1-skills-code-agent/development-branching-strategy · test0 equal / 0 different / 1 unavailable locally
development-branching-strategy-aerosimcorp-v1-aerosim-skills-code-agent/development-branching-strategy-aerosim · test0 equal / 1 different / 0 unavailable locally
development-durable-wave-executionhome-v1-skills-code-agent/development-durable-wave-execution · main13 equal / 0 different / 0 unavailable locally
development-gateshome-v1-skills-code-agent/development-gates · main1 equal / 1 different / 0 unavailable locally
development-gitops-argo-cd-gondor-v1home-v1-skills-code-agent/development-gitops-argo-cd-gondor-v1 · test0 equal / 0 different / 3 unavailable locally
development-integrityhome-v1-skills-code-agent/development-integrity · main2 equal / 0 different / 0 unavailable locally
development-method-ttdhome-v1-skills-code-agent/development-method-ttd · main1 equal / 0 different / 0 unavailable locally
development-monorepo-pnpmhome-v1-skills-code-agent/development-monorepo-pnpm · test6 equal / 0 different / 0 unavailable locally
development-scriptshome-v1-skills-code-agent/development-scripts · test0 equal / 1 different / 6 unavailable locally
development-scripts-aerosimcorp-v1-aerosim-skills-code-agent/development-scripts-aerosim · test6 equal / 1 different / 0 unavailable locally
devsecops-ci-cd-giteahome-v1-skills-code-agent/devsecops-ci-cd-gitea · test5 equal / 0 different / 0 unavailable locally
devsecops-ci-cd-gitea-aerosimcorp-v1-aerosim-skills-code-agent/devsecops-ci-cd-gitea-aerosim · test1 equal / 3 different / 0 unavailable locally
documentation-docusaurushome-v1-skills-code-agent/documentation-docusaurus · test0 equal / 1 different / 0 unavailable locally
documentation-docusaurus-aerosimcorp-v1-aerosim-skills-code-agent/documentation-docusaurus-aerosim · test7 equal / 2 different / 0 unavailable locally
gitops-manifest-engineeringPublished source unverifiedNot treated as a published/equal package
gondor-v1-nodesPublished source unverifiedNot treated as a published/equal package
home-v1--truenashome-v1-skills-code-agent/home-v1--truenas · test2 equal / 0 different / 0 unavailable locally
home-v1-discordhome-v1-skills-code-agent/home-v1-discord · test0 equal / 1 different / 0 unavailable locally
self-hosted-service-account-recoveryPublished source unverifiedNot treated as a published/equal package

Do not mirror differences blindly. Published and installed dependency content still differs: development-gates lacks installed complete-job-inventory safeguards remotely; the AeroSim CI source declares 1.1.0 while the installation declares 1.2.0; branching, scripts and documentation overlays contain installed standing merge delegation. General includes an intentionally runtime-only private overlay, which is excluded from this document and its downloadable evidence. Preserve effective authority and private bindings while separately reconciling reusable source content. Matching Delivery files do not make all dependencies synchronized.

The selected development-gitops-argo-cd-gondor-v1 exists remotely but is still unavailable through the inspected skill loader. Its explicit fallback mitigates routing; it does not fix installation or authorize a variant substitution. Exact-name source searches did not verify publication for recovery or the two fallback skills; they remain installed capabilities with unverified publication, not proven nonexistent repositories.

Reference and skill map​

Historical baseline comparison — not full-program implemented topology.

loading...

The editable source is engineering/diagrams/skills-delivery-channel.drawio.

Analysis​

Historical pre-disposition analysis. Its “current” wording refers to the dated baseline, not PR #15 / #41. Use the current verified snapshot above for installed state.

Current reassessment​

This reassessment is the pre-implementation baseline retained for traceability. Implemented minimum records the later changes, including the A18 count correction; pending policy findings are not silently marked resolved.

2026-10-23 reassessment of A01–A18. This table supersedes the historical audit's present-tense status, not its recorded evidence. It reviews skill contracts, not runtime deployments or live scheduler authorization. A10 is resolved in current source; A16 is partly superseded; the remaining distinctions below still matter. Existing overrides are not new approval questions.

IDCurrent dispositionRefreshed finding and evidence
A01current — duplicateStages 3–5 still repeat exact-head equality, complete successful attempt and separate integration identity; external gates still owns the same evidence model. Retain project exit gates; thin the reusable algorithm. Source 1 · Source 2
A02current — unresolvedStage 3 steps 5–6 still push substantive changes then review the PR head; reusable gates orders review then exact-head push. Early empty kickoff visibility does not settle substantive publication order. Source 1 · Source 2
A03current — explicit overrideProject still explicitly wins on review ownership; active executor reviews, main verifies worker packet, and a second review worker/human dependency is forbidden. Do not manufacture an independent reviewer or call packet verification independent code review. Source 1 · Source 2 · Source 3
A04current — unresolvedStage 4 still says base drift is harmless; reusable gates still demands synchronization and repeat review whenever base advances. Define evidence for any retained exception; a rename resolves nothing. Source 1 · Source 2
A05current — weaker clauses and discard ambiguityMandatory TTD routing remains stricter than when-practical wording in stage 3 and runtime. TTD still says delete untested code/start over; forward repair still protects valid work. Preserve strict current routing, clarify local discard versus shared work before affected extraction. Source 1 · Source 2 · Source 3
A06current — claim mapping unresolvedOne worker per independently eligible Task and durable recovery remain explicit. Whole-wave skill still claims all members including blocked ones; project dispatch does not specify equivalent persisted whole-wave ownership. Keep worker allocation override and lock serialization; clarify mapping. Source 1 · Source 2
A07current — duplicate plus formatting overlayStatus and planning references retain fresh-head/checkpoint algorithms; integrity/gates own reusable evidence. Retain canonical states, requested wave header, gate codes, non-approval interpretation and destinations. Source 1 · Source 2 · Source 3
A08current — escalation mapping unresolvedSame-gate forward repair remains; integrity still calls for help after one attempt or one hour. General blocker ownership strengthens accountability, not an explicit reconciliation of helper role with one-worker boundary. Source 1 · Source 2 · Source 3
A09current — duplicate, new dependency driftDelivery policy still specifies the same three CI cases as the AeroSim CI skill. Installed CI 1.2.0 adds candidate image/chart packaging and explicit required aggregate inputs absent from published 1.1.0. Reconcile owner version before replacing local policy with pointer. Source 1 · Source 2 · Source 3
A10resolved — original obsolete Helm clause removedCurrent equal installed/published Delivery stage 3 expressly permits Dockerfile/image/container/publication/Helm artifact validations. Actions policy no longer sends every Helm-rendering test to E2E and explicitly requires candidate chart packaging. Functional non-unit suites remain UAT-owned. Residual wording about default-branch artifact ownership should not erase explicit candidate packaging. Source 1 · Source 2
A11current — explicit override and source driftProject entry still uses exact Task release and unpadded attempt; branching skill still derives version from tags and uses 001. Delivery precedence and standing merge delegation remain effective. Installed branching adds delegation absent remotely; ordinary Git mechanics can be delegated, exact project rules cannot. Source 1 · Source 2 · Source 3
A12current — duplicate; owner name supersededcorp-v1-main is now a local compatibility loader to channel-board-skic, whose actual source is skic-skills. Login policy and specialist recovery still have existing owners; exact own-account delegation stays project-local. Recovery repository remains unverified; do not invent global-skills ownership. Source 1 · Source 2
A13current — mechanics duplication; gap mitigated not fixedTrueNAS storage mechanics and GitOps environment mappings remain distinct from Delivery DEV-only authority. Selected Gondor GitOps skill is remotely present but skill_view still fails. AeroSim now explicitly supplies fallback mechanics through manifest engineering/nodes/repository inspection; not equivalent installation. No live StorageClass state checked. Source 1 · Source 2 · Source 3 · Source 4
A14current — complement and preflight duplicationTask containment, exact-context toolchain preflight, repository-root script execution and pnpm conventions remain separate layers with duplicated checks. Keep cache/task authority and authoritative repository validation; do not infer folder renames or replace all-app CI with narrow checks. Source 1 · Source 2 · Source 3
A15current — complement, no demonstrated contradictionDelivery domain sections still coexist with Docusaurus Diátaxis and glossary ownership. No new documentation helper is justified simply by similar subject matter. Source 1 · Source 2 · Source 3
A16partly superseded — central policy now shares safeguardPitfall duplication and project lock verification persist. Base-image policy is no longer exclusively an unmatched AeroSim rule: current central Delivery entry and runtime reference also contain it. This is not evidence CI specialist owns the entire policy; do not delete it during thinning. Source 1 · Source 2 · Source 3 · Source 4
A17current — authorization evidence unresolvedAeroSim still mandates hourly reconciliation; current Board still limits scheduler exception to approved General bootstrap. Dispatcher-only wording does not identify the required Board authorization. No live schedule or Discord decision audit performed; do not claim job unauthorized or resolved solely from these texts. Source 1 · Source 2
A18current — stale topology (extra finding already in proposal)Project entry enumerates eight channels but still says seven; the gate reference repeats seven. Board has the eight-channel topology. Retain this wording cleanup without changing the authorized boundary. Source 1 · Source 2 · Source 3

Remaining decisions

Affected workRequired resolution before that extraction
Review order and base drift — A02/A04Record substantive review/push order and exact evidence for retaining or invalidating review after a base advance. An early empty PR is not the substantive publication decision.
TTD and forward repair — A05Define permitted discard of local experiments versus preserving valid shared work; strict TTD and its named exception authority already apply.
Wave claims and escalation — A06/A08Map durable whole-wave ownership to eligible per-Task claims; define helper roles without a second implementer or pausing independent work.
Scheduling — A17Locate and bind the applicable authorization evidence before adopting scheduler clauses. This source audit does not conclude that a live job is unauthorized and creates or changes no job.
Safe replacement links — A09/A12/A13Reconcile relevant source/runtime differences and publication/loadability evidence before replacing a local safeguard with an owner pointer. Keep intentional private overlays private.

Recommended next implementation, still subject to the owning gates: thin duplicate procedures into existing owners, retain the project workflow, and do not create seven helper skills as a batch. Preserve the one-worker contract, standing merge authority, project branch rules, DEV-only deployment, functional non-unit UAT ownership, exact deployed tuple and separately verified Releases handoff. The updated central evidence-handoff guidance is a reusable lesson, not an automatic AeroSim rollout.

The scan also found illustrative cleanup debt: the worker reference still lists browser/database caches under Delivery beside prose assigning them to UAT; per-Task gate wording should not negate the explicit parallel-eligible-Task model. These are source-cleanup findings, not changes implemented by this proposal refresh. The seven helper candidates remain Unproven: the audit has not demonstrated all three agreed extraction criteria for any of them.

Skill names and Gitea organizations​

Historical inventory, checked 2026-10-07; not the target naming convention and not an approved migration. The later agreed naming direction supersedes this observed pattern for planned names, not for existing source identities. The organization identifies source ownership; the skill name identifies capability and sometimes project scope. A name is not a unique source identity or a grant of authority.

Shared: home-v1-skills-code-agent/<base-skill>
Adopted: corp-v1-<project>-skills-code-agent/<base-skill>-<project>

For example, home-v1-skills-code-agent/development-branching-strategy has an AeroSim adoption at corp-v1-aerosim-skills-code-agent/development-branching-strategy-aerosim. The same suffix pattern holds for the inspected 3DArch, EShopv1 and Mazeng skill repositories. Shared corp-v1-* skills can still belong to home-v1-skills-code-agent.

Exception or boundaryConsequence
cogarch-v1-channel-storm belongs to cognitive-architect-v1-skills-code-agentContext aliases prevent literal prefix-to-owner mapping.
eldorado-v1-skills owns eldorado-storm-v1Neither organization suffix nor channel-name form is universal.
home-v1-skills-code-agent/documentation-docusaurus and vssa-v1-skills-code-agent/documentation-docusaurus both existUnqualified names can collide; VSSA frontmatter also uses documentation-docusaurus.
corp-v1-aerosim hosts application/deployment repositories; corp-v1-aerosim-skills-code-agent hosts skillsA skill can govern work outside its source organization without changing ownership or permissions.

Recommendation: record host/organization/repository, skill path and immutable revision; record the adopted upstream revision separately. Discover the default branch rather than assuming main. Naming is only a search hint. Keep actual helper repositories unassigned and recovery-skill ownership unverified until supported by source evidence; distinguish them from the target naming destinations below; do not rename, replace or install anything from this pattern alone.

Naming evidence, examples and limits

Channel names commonly follow <context>-channel-<function>[-<project>]: corp-v1-channel-delivery-aerosim, vssa-v1-channel-storm, and cogarch-v1-channel-storm. Other verified project examples are corp-v1-channel-delivery-3darch, documentation-docusaurus-eshopv1, and development-scripts-mazeng in their respective Corp project skill organizations.

Authenticated, paginated repository listings covered the shared Home organization, four Corp project skill organizations, Cognitive Architect, VSSA, Eldorado and the AeroSim application organization. Every returned repository in the four Corp project skill organizations had its project suffix. This is a repository-name finding, not proof of synchronization or content equivalence.

Representative raw-file checks verified these names and default branches:

The installed AeroSim Delivery SKILL.md and ADOPTION.md additionally connect the shared Delivery source to its AeroSim destination. Local adoption evidence does not prove remote/runtime equality. These source links are mutable, not pinned snapshots; frontmatter was sampled, not audited for every repository. The investigation is not an exhaustive inventory of all organizations or installed copies.

Agreed naming direction​

Agreed direction; partial migration verified by the earlier refresh. The accepted full program now includes proposal-scoped migrations and candidate assessments; the earlier refresh alone did not approve them. The Discord and TrueNAS moves are specifically authorized below, but not performed by this documentation update. Organizations group skills by ownership and project; skill names group variants by capability when cloned side by side.

  • SKIC replaces Corp in canonical channel-skill names, not as a parallel scope. Historical repository organizations and environment bindings must still be verified separately.
  • Organization: <scope>[-<project>]-skills.
  • Skill: <capability>[-<scope>][-<project>].
  • Global skills have no suffix; omit both scope and project from their names.
  • Projects may own their own skills organization.
  • Repository name, installed skill folder and declared skill name must match.
Target organizationExample skill / repository name
global-skillsdevelopment-gates
home-skillsdevelopment-gates-home
skic-skillsdevelopment-gates-skic
skic-aerosim-skillsdevelopment-gates-skic-aerosim

Global → workstream → project expresses increasing specialization, not automatic copying or inherited approval. Create a scoped variant only when its rules or context differ. The organization list can grow; this decision sets no fixed total. Detailed maintenance and approval rules remain a separate decision.

Decision evidence: RootAtSkic specified Corp → SKIC, no global suffix, and scope-first organizations with capability-first project names. The request to apply that decision to this page authorizes this documentation adjustment, not repository migration or installation.

Scope clarification — RootAtSkic’s response: Home remains a separate scope, with home-skills distinct from global-skills. Global has Home and SKIC as parallel specializations; Gondor v1 remains a Home platform specialization and AeroSim a SKIC project specialization. Moving two reusable utilities does not remove Home or turn environment-specific bindings into global policy.

RootAtSkic authorizes Piotras and Hermes to move and rename the Discord and TrueNAS skills to global-skills, as discord and truenas. This supersedes the earlier alternative to remove Home if no response arrived. Authorization is recorded; migration and installation were not performed by this documentation update. Server addresses, channel IDs, permissions and platform-specific context remain environment bindings, not rules imposed on every consumer.

Reconciled sources: the original skills organization and naming decision Markdown establishes the naming convention and separate organizations. Its original “migration not yet authorized” status is historical; the RootAtSkic response relayed to Guild adds the narrow two-skill authorization. Neither earlier source alone authorized the full extraction plan; the later full-program authorization governs its execution under the retained criteria. Later channel-skill naming migration is separately recorded below; it does not authorize helper extraction.

How to read the rest of this page: the captured baseline and audit citations retain historical names, not the target naming convention. Proposal begins with an old-to-new mapping and then uses target names only; exact skill contents are omitted. Both proposal diagrams use the agreed target naming; the baseline diagram records the earlier 2026-10-23 installation, while the dated audit preserves its original historical evidence. The summary table maps the split candidates to target names. The Delivery identities channel-delivery-skic-aerosim and channel-delivery-skic now exist and are installed. Their actual source repositories are identified in the current evidence, not inferred from the target organizations skic-aerosim-skills and skic-skills. A completed name change is not proof of an organization transfer or the proposed thinning.

For the additional diagram pointers, capability-preserving target labels are derived from the naming convention, not separately approved repository creations: for example the platform-specific development-gitops-argo-cd-home-gondor-v1 in home-gondor-v1-skills. The separately authorized exceptions are discord and truenas, both targeting global-skills. A scoped organization is used only for an already specialized skill; global dependencies retain unsuffixed names. The migration review must verify each destination and owner before publication.

The channel-skill migration handoff records completed name changes with repository organizations preserved. This refresh verifies the Delivery-related subset, not the entire portfolio. Remaining organization transfers and helper creation require their applicable gates. No migration is executed by this page update. Any later migration must preserve authority overlays and dependency traceability rather than treating a rename as approval to change behavior.

Internal-reference versus external-skill audit​

Historical audit date: 2026-10-05. Status: findings and recommendations only—not adopted policy. Read the 2026-10-23 reassessment above for current applicability; the original excerpts and line numbers below are retained for traceability, not presented as today’s source. This audit checks whether the proposed split removes duplicate responsibility or merely moves it into another skill. It covers Delivery's SKILL.md, all nine AeroSim internal references, and the relevant sections of all 18 declared external skill entry points, with selected supporting references. It is not an exhaustive audit of every transitive dependency.

Evidence baseline and limits

The primary subject was the installed AeroSim Delivery v1.25.0 captured on 2026-10-05; this is a dated evidence baseline, not a fresh claim about every executor. The published Delivery repository at 0c0e68bde3189fd96415af6035200cf7fcb9c877 declares v1.24.0. Its SKILL.md and five reference files differ from the installed copies; four references match. Therefore, a published-source link alone does not prove the installed wording quoted below.

The source evidence manifest records inspected paths, installed SHA-256 fingerprints, line-numbered excerpts, resolved remote commits, and whether each compared file matches. References to D below mean corp-v1-channel-delivery-aerosim; internal filenames are under its references/. External names identify their own SKILL.md unless a reference filename is stated. Line numbers describe the captured installed files, not an assumed future branch head.

Two special cases matter:

  • home-v1--truenas loads from /opt/data/home-v1-skills-code-agent/home-v1--truenas, not the ordinary /opt/data/skills tree. Its specialist storage reference was read there.
  • development-gitops-argo-cd-gondor-v1 fails the installed skill lookup, but its repository exists. Its remote entry point was read at 3c3d495417993d5c15bb3379bdae5c85f04e1890. This is a loadability gap, not proof that the skill does not exist. The inspected remote text explicitly supports project-specific per-environment repository mappings. This audit neither installs it nor substitutes development-gitops-argo-cd-aerosim.

Classification: duplicate means the same procedure is maintained twice; complement means distinct responsibilities fit together; explicit override means an existing project rule resolves the difference; unresolved tension means the inspected text does not supply a sufficiently precise reconciliation. An override is not a new decision made by this audit.

Task gates and reusable development rules

The initial comparison was correct about duplication, but review ownership is already an explicit AeroSim override. It should not be presented as an entirely unresolved policy choice. Review order and base-drift acceptance still need precise reconciliation.

IDInternal versus external evidenceFinding and proposed ownership
A01task-delivery-gates.md, stages 3–5, binds local/remote/PR heads, one successful CI attempt and a separate integration revision. development-gates, Evidence model, Ordered gates and Attempt integrity, defines the same invariants.Duplicate. development-gates should own the immutable evidence algorithm. Delivery retains the numbered lifecycle gates, required project jobs, status transitions, deployment obligation and handoff destinations, invoking the external contract at stages 3–5.
A02Task stage 3 steps 5–6: “commit and push” followed by “reviews that exact PR head.” development-gates, ordered steps 2–3: “Obtain independent logic/security review” then “Push only the exact reviewed head.” Repository entry also requires an empty kickoff PR before edits.Unresolved ordering tension. Distinguish kickoff visibility from substantive candidate publication. Document one explicit review-before/after-push policy and its load point; do not silently choose a sequence during extraction. The existing override names visibility and review ownership, but does not explicitly spell out substantive review/push order.
A03Task stage 3: the active executor reviews the candidate; main session verifies the packet in worker mode. development-gates, Ordered gates, and development-integrity, Evidence-first status sequence, require independent review. D/SKILL.md, Development Skill Routing, says AeroSim wins on “review ownership.”Explicit override, plus terminology debt. Preserve current AeroSim executor review and main-session verification; do not mislabel packet verification as a second independent code review. Make the reusable contract's review-role input explicit before adoption. This audit does not introduce another worker or a human approval gate.
A04Task stage 4 step 2 permits confirming “base drift is harmless”; step 3 returns to review for a rebase or tree change. development-gates, Ordered gates, says “If the base advances … synchronize and repeat review.”Unresolved base-drift tension. Decide whether every base advance invalidates review, or whether a documented compatibility check can preserve it. Define the required base/tree evidence once in development-gates; retain any approved AeroSim exception explicitly. “Harmless” alone is not a testable contract.
A05Task stage 3 step 2 says a failing test for new behavior is required “when practical”; runtime-and-ci.md:90–94 uses similar wording. development-method-ttd, The Iron Law, says “NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST.” D/SKILL.md, Development Skill Routing, already requires TTD unless RootAtSkic approves an exception.Duplicate with stale weaker wording. Current routing supplies the stricter requirement; it is not an unapproved exemption. Keep RED–GREEN–REFACTOR in development-method-ttd; retain the unit-only boundary and exception authority in Delivery. Separately reconcile TTD's “Delete it. Start over” with Task stage 3's forward-repair/no-revert rule: the scope of permitted local discard versus preservation of valid shared work is not stated precisely.
A06single-subagent-task-delivery.md, Same-Wave Parallel Dispatch, selects independently eligible Tasks, one worker each, with durable recovery. development-durable-wave-execution, Atomic whole-wave claim, says “Claim the whole wave as one ownership unit” and includes claimed-and-blocked members.Partial duplication and claim-granularity tension. Project worker allocation already wins; one worker per Task is not itself a conflict with wave coordination. What remains unclear is how whole-wave ownership is persisted when only eligible Tasks are claimed. External skill owns durable recovery mechanics; Delivery must define the wave-to-Task claim mapping and retain documentation-merge serialization.
A07status-and-reporting.md:21–27,55–81 separates lifecycle from activity and requires verified evidence. development-integrity, Plain-language reporting / Completion test, separates implementation, remote checks and formal closure. planning-artifact-reconciliation.md:2–17 repeats fresh-head, exact-worktree, CI and post-merge readback.Duplicate with complementary formatting. development-integrity owns honest checkpoint claims; development-gates owns exact identities. Delivery retains canonical status names, requested wave-header format, gate codes and report destinations. Keep planning semantics—documentation merge is not Feature approval—but reference the shared verification algorithm.
A08Task Mandatory gate-failure recovery and failure-and-documentation.md:9–28 require repeated repair until the gate passes, with pauses only at genuine external/authority boundaries. development-integrity, Ask for help early, requires help after one focused attempt or one hour and suggests an independent repair/review worker.Unresolved escalation integration. Same-gate repair and asking for help can coexist, but the trigger, helper role and effect on the one-worker boundary are not mapped. General owns project escalation authority; Delivery should state how to request help without creating a second implementer or pausing independent Tasks. Do not turn the threshold into permission to abandon work.

CI, runtime, documentation and governance

IDInternal versus external evidenceFinding and proposed ownership
A09gitea-actions-policy.md:5–68 specifies manual branch readiness, credential-free PR builds, trusted test publication and immutable retries. devsecops-ci-cd-gitea-aerosim/references/pipeline-workflow.md:3–53 specifies the same three cases; generic devsecops-ci-cd-gitea/references/pipeline-workflow.md:9–48 supplies reusable mechanics. runtime-and-ci.md:124–132 repeats chart identity/readback.Duplicate. AeroSim CI skill owns exact workflow names, triggers, all-app validation and artifact contracts; generic CI skill owns reusable Gitea/Harbor mechanics. Delivery owns when evidence is required and what gets handed to GitOps/UAT. A new corp-v1-ci-runtime must coordinate these owners, not become a third pipeline specification.
A10gitea-actions-policy.md:66 sends every “Helm-rendering test” to E2E; Task stage 3 step 4 also excludes Helm-rendering suites. Current D/SKILL.md assigns “Helm chart linting/rendering/packaging” to Delivery and forbids E2E chart rendering; AeroSim CI Verification requires Helm artifact contracts.Stale internal clause, resolved by the explicit current boundary. Delivery owns static/build-time artifact validation; UAT owns functional non-unit behavior. Record and remove the obsolete blanket wording during an approved cleanup; no fresh testing-ownership decision is needed.
A11repository-entry-and-visibility.md:24–60 requires a visible PR before edits, Task-target release, unpadded attempt and title equal to branch. development-branching-strategy-aerosim, Rules / Workflow, derives version from “Git tags only,” uses 001, and retains older confirmation/user-merge wording. D/SKILL.md explicitly gives precedence to exact branch naming, visibility and merge authority.Explicit override plus repeated mechanics. Delivery owns Task identity and early visibility; branching skill owns ordinary Git mechanics. Standing AeroSim merge authority already supersedes older user-only merge clauses. Do not ask again or discard the project naming rule merely to deduplicate.
A12runtime-and-ci.md:35–44 repeats corp-v1-main, Corp v1 System SSO Credential Use. Internal :48–75 repeats recovery safeguards from self-hosted-service-account-recovery, Workflow, and references/gitea-on-truenas-reactivation.md.Duplicate with complementary authority. Shared login policy remains owned by corp-v1-main; specialist recovery mechanics remain in the recovery skill. Delivery retains its exact own-account delegation and stricter preconditions. The proposed security helpers must not become additional authorities for the same credential policy. Preserve helper interlocks if their implementation is later relocated.
A13runtime-and-ci.md:149–155 describes isolated development resources and retained TrueNAS storage. home-v1--truenas/references/gondor-retained-application-storage.md:5–12,22,60–107 owns dataset/NFS/static-PV safeguards and live verification. The pinned remote GitOps entry point, Repositories, expressly allows one rendered repository per environment.Duplicate storage mechanics; complementary environment authority. TrueNAS owns storage procedure, GitOps owns rendering/desired-state mechanics, Delivery owns development scope and UAT handoff, Releases owns production. Keep actual AeroSim repository substitutions. Verify the live StorageClass rather than treating copied Delete wording as timeless system state.
A14runtime-and-ci.md:24–33,112–120 defines Task containment and exact-context toolchain preflight. development-scripts-aerosim, Repository model / Standard runtime flow, defines repository-root script execution; development-monorepo-pnpm, Tooling baseline / Validation, owns versions/workspace mechanics. planning-artifact-reconciliation.md:11 repeats the Docusaurus nested-pnpm fallback.Complement with reusable preflight duplication. Task containment and repository-root execution fit together. Keep workspace authority in Delivery; script bootstrap in the scripts skill; pnpm mechanics in the monorepo skill; Docusaurus-specific validation in the docs skill. Narrow local tests do not override required all-app CI. Do not infer a mandate to rename AeroSim folders from the generic four-root example.
A15failure-and-documentation.md:30–50 defines Ways of Working and Engineering coverage. documentation-docusaurus-aerosim, My Philosophy / Structure, defines Diátaxis, frontmatter and build rules; corp-v1-glossary, Documentation Contract, owns canonical terms.Complement, not a demonstrated contradiction. Domain sections and Diátaxis page types answer different questions. Delivery owns verified domain content; Docusaurus owns authoring/build mechanics; Glossary owns shared definitions. Extract only a distinct reusable responsibility, not a second documentation platform contract.
A16common-pitfalls.md:20–29 repeats exact-head checks, toolchain preflight and authorization continuity from development-gates and Docusaurus guidance; :28 adds concrete documentation-lock-holder verification. runtime-and-ci.md:134–145 adds AeroSim's reusable base-image policy.Duplicate reminders plus unique project rules. Turn repeated pitfalls into pointers to their owners. Preserve lock verification and the base-image policy until an explicit destination retains them; the inspected external CI texts do not replace the complete base-image contract. Extraction is not a reason to delete unmatched safeguards.
A17D/SKILL.md, Hourly Worker Reconciliation, mandates a recurring Delivery dispatcher. development-durable-wave-execution, Interruption-safe scheduler contract, discusses job continuation. corp-v1-main, Hermes access and Corp project automation policy, permits only a Board-approved General bootstrap exception by default.Unresolved authorization tension. Delivery explicitly limits cron to dispatch/recovery rather than implementation, which narrows generic execution mechanics. But an hourly Delivery job is not the same as the Board's named General-bootstrap exception. The inspected Delivery text does not identify the corresponding Board authorization override. Reconcile authority evidence before adoption; this audit neither creates nor changes jobs.
A18Task gates repeatedly say “seven project channels,” while current D/SKILL.md lists eight including UAT. corp-v1-main records the approved eight-channel topology; corp-v1-channel-general-aerosim, Approved Information Boundary, lists eight. Releases Release Completion Gate owns TO_BE_RELEASED → DONE; home-v1-discord owns message/readback mechanics.Stale topology wording; complementary handoff ownership. Use the existing eight-channel decision, not a new invented boundary. Delivery owns its handoff destination and must not absorb release acceptance or Discord transport procedures. The target proposal must preserve that existing eight-channel decision; this review does not change source skills.

Coverage and implications for the split

Every internal reference is accounted for; an unlisted contradiction is not implied by a shared topic.

Internal referenceFindingsRetain locally / delegate
task-delivery-gates.mdA01–A05, A08, A10, A18Retain ordered project stages and exit outcomes; delegate reusable review/CI algorithms after reconciling A02/A04.
status-and-reporting.mdA07Retain project vocabulary and presentation; reference integrity evidence.
planning-artifact-reconciliation.mdA07, A14Retain approval/lifecycle interpretation; delegate generic remote/worktree/toolchain checks.
single-subagent-task-delivery.mdA03, A06, A08Retain worker/authority/readback boundary; map it explicitly to shared recovery and escalation.
gitea-actions-policy.mdA09, A10Retain a routing/ownership overlay, not a parallel pipeline specification.
repository-entry-and-visibility.mdA11Retain exact project identity and visibility rules; reference Git mechanics.
runtime-and-ci.mdA05, A09, A12–A14, A16Retain project authority, environment/cache bindings and unmatched base-image policy; delegate specialist procedures.
failure-and-documentation.mdA08, A15Retain repair continuity and documentation-domain ownership; delegate evidence/authoring mechanics.
common-pitfalls.mdA16Keep project-specific traps and pointers, not another full policy copy.

Recommended split principle: preserve the workflow, remove duplicate authority. Existing skills should remain the single owners of reusable procedures. Delivery should specify the project bindings, inputs, required outcomes and handoffs. A short reminder can remain; a second independently maintained algorithm should not.

The original disposition labels “kept whole / unchanged” are provisional, not evidence that those files are free of duplication. In particular, task-delivery-gates.md and planning-artifact-reconciliation.md need thinning, not wholesale deletion. The diagrams retain the original allocation option. The proposed responsibilities remain unapproved; exact skill texts are intentionally omitted from Proposal. No source skill or diagram allocation is changed.

Before adoption:

  1. Reconcile substantive review/push order, base drift, local-discard scope, whole-wave claim mapping, escalation integration and scheduler authority with the applicable owners.
  2. Preserve already-effective AeroSim overrides for reviewer role, branch naming, standing merge authority, testing/artifact boundaries and development-versus-production ownership.
  3. Resolve installed-versus-published drift and the GitOps loadability gap without silently replacing the selected skill.
  4. Replace duplicated procedures with exact owner links and decision-point loads. Preserve unmatched safeguards and all 18 current dependencies; this audit proposes zero link removals.
  5. Validate the approved split against these findings, the reference inventory and project bindings. Until then, all helper drafts remain proposals and no operational policy changes follow from this page.

Historical decision list — superseded by the 2026-10-23 reassessment

IssueRequired resolution before adoption
Review sequence and base drift (A02/A04)Agree on substantive review/push order and exactly when a changed base invalidates review. Kickoff visibility is a separate concern.
Local discard versus forward repair (A05)Define when local experimental work may be discarded without reverting valid shared work.
Wave ownership, help and scheduling (A06/A08/A17)Map wave claims to Task workers, define escalation without a second implementer, and verify scheduler authorization.
Provenance and availabilityReconcile installed/published differences and the selected GitOps skill's loadability; do not silently substitute another variant.

The detailed audit retains its dated findings. The draft corrections in this review are document-only; they do not claim those source skills have been repaired.

Proposal​

Historical full-split design, retained for comparison. The two disposition tables in this section are updated to actual implementation; draft target names and the conditional 27-pointer diagram elsewhere are not current inventory.

Old-to-new skill names​

Accepted program design; conditional allocation comparison. Read this retained proposal through the full-program ledger above. The earlier smallest-useful-change recommendation is historical sequencing, not a scope ceiling. Helper publication still depends on the extraction criteria; diagrams are not implementation evidence.

This is the only place in Proposal that uses old skill names. All following sections and diagram labels use the new names. Unchanged global names are included for traceability. These are naming targets with mixed implementation status; the current evidence identifies verified existing names separately from destinations still proposed. Actual source identities remain in the current evidence and editable diagram metadata.

Old nameNew name
corp-v1-channel-deliverychannel-delivery-skic
corp-v1-channel-delivery-aerosimchannel-delivery-skic-aerosim
corp-v1-channel-general-aerosimchannel-general-skic-aerosim
corp-v1-channel-releases-aerosimchannel-releases-skic-aerosim
corp-v1-ci-runtimeci-runtime-skic
corp-v1-develop-monorepo-pnpm-appdevelop-monorepo-pnpm-app-skic
corp-v1-develop-monorepo-pnpm-packagedevelop-monorepo-pnpm-package-skic
corp-v1-development-securitydevelopment-security-skic
corp-v1-glossaryglossary-skic
corp-v1-mainchannel-board-skic
corp-v1-status-reportingstatus-reporting-skic
delivery-docsdelivery-docs
development-branching-strategydevelopment-branching-strategy
development-branching-strategy-aerosimdevelopment-branching-strategy-skic-aerosim
development-durable-wave-executiondevelopment-durable-wave-execution
development-gatesdevelopment-gates
development-gitops-argo-cd-gondor-v1development-gitops-argo-cd-home-gondor-v1
development-integritydevelopment-integrity
development-method-ttddevelopment-method-ttd
development-monorepo-pnpmdevelopment-monorepo-pnpm
development-scriptsdevelopment-scripts
development-scripts-aerosimdevelopment-scripts-skic-aerosim
development-securitydevelopment-security
devsecops-ci-cd-giteadevsecops-ci-cd-gitea
devsecops-ci-cd-gitea-aerosimdevsecops-ci-cd-gitea-skic-aerosim
documentation-docusaurus-aerosimdocumentation-docusaurus-skic-aerosim
home-v1--truenastruenas
home-v1-discorddiscord
self-hosted-service-account-recoveryself-hosted-service-account-recovery

The Delivery core and its AeroSim adoption are separate targets. Naming does not replace or broaden any owner's authority. The target-name summary below covers the nine numbered candidates; this mapping also covers their retained dependencies. This presentation follows the request to consolidate naming and remove exact skill contents, which supersedes the earlier retention of full drafts.

Recommendation​

Scope and authorization. Home stays separate. The retained discord and truenas dependencies target global-skills under RootAtSkic’s specific authorization; their move is not reported as completed. Channel-skill renames have progressed independently; remaining organization moves and helper extractions remain separately gated. See the reconciled decision evidence.

Apply the agreed naming direction when describing target skills; use target names throughout this proposal; actual live bindings appear in Current state, historical evidence remains in Analysis, and proposed targets are not substituted into runtime bindings by this document. Naming agreement does not approve the extraction plan.

Simplify Delivery before splitting it. Do not create the seven helper skills as one batch. Keep project authority, Task lifecycle, workspace and handoffs in Delivery; link to existing owners for reusable review, CI, GitOps, documentation and security procedures. Extract a helper only when it has a distinct responsibility that an existing skill does not already own.

Smallest useful change — historical first increment, not full-program scope

Use the current reassessment, not the historical issue statuses, to sequence implementation. The old Delivery mismatch and obsolete Helm clause are no longer pending fixes; dependency drift and the remaining decisions still are.

  1. Thin duplicate procedures into links to their existing owners, preserving all current project dependencies and safeguards.
  2. Keep short documentation, reporting and login bindings in Delivery or its references unless reuse justifies a separate skill. Do not create a three-item checklist file solely to shorten a skill body.
  3. Resolve a policy conflict before the extraction that touches it; block only the affected extraction, not unrelated simplification. Preserve existing explicit project overrides. Existing project authority—including standing merge delegation—still applies.

Agreed extraction criteria

Keep the comparison diagrams and agreed decision criteria. Exact skill contents are intentionally omitted at this stage. A new helper is justified only by evidence of all three:

  • a distinct responsibility not already owned by an existing skill;
  • at least two concrete consumers needing the same guidance;
  • an explicit content move out of Delivery, leaving only its project-specific bindings.

Without that evidence, retain the guidance in Delivery or improve its existing owner. Mark the candidate Unproven — extraction criteria not yet demonstrated; this is neither rejection nor approval. App/package placeholders remain deferred.

Maintain one authoritative policy owner. Existing shared login policy stays authoritative unless a separately approved change explicitly transfers ownership. Helpers may provide non-duplicated handling procedures or bindings, not independently maintained copies of credential policy.

Acceptance evidence: require a before/after comparison showing one authoritative owner for each moved rule, no lost safeguards or dependencies, an explicit decision-point load for the owner, and less duplicated guidance across all affected skills—not merely fewer lines in Delivery. Content cleanup must not silently resolve review/push order, base drift, wave claims or scheduler authority; require the applicable recorded resolution before an affected extraction.

Decision evidence: preserve structure, extraction threshold, Unproven status, one policy owner, scoped conflict blocking, acceptance comparison, and request to update the proposal. Those earlier decisions authorized the proposal update, not publication. The later full-program approval now authorizes program execution under these criteria; publication, installation and migration still require their own evidence.

Proposed skill and reference map​

Historical conditional proposal, not current implementation. Unassigned/deferred labels below belong to this earlier comparison; the current diagram and tables record the later publications.

Both proposal diagrams use the agreed target naming for skill labels and organization labels. They retain the original split option for comparison, not the recommended minimum implementation. Read their numbered candidates through the target-name summary. Every displayed organization is a target, not a claim that a repository exists or migration occurred. Original names and verified repository URLs remain separately recorded as source metadata in the editable XML. The skill view combines the original seven-reference central baseline with mandatory preservation of all current AeroSim skill links. The reference-allocation view remains limited to the original seven central reference files; the two AeroSim-only references remain project-owned. The latest central source also contains aerosim-lessons-review.md recorded in Current state; this historical comparison is not its current file inventory. Neither view implements or approves the split. Skill numbers match the summary table; placeholders remain explicitly marked.

Proposed skills and retained references

The purple boundary contains the proposed AeroSim Delivery adoption's SKILL.md, four retained central reference files, and two unchanged AeroSim-only reference files. All 27 proposed direct skill pointers sit outside that boundary, grouped by responsibility and labelled with target names and Target org. Existing source-repository verification stays in separate XML metadata; draft repositories remain unassigned and the recovery source remains unverified. Target placement does not resolve those provenance gaps. Green label accents identify the 18 retained current links; blue label accents identify the nine additional candidate pointers. This legend shows retention status, not body-versus-metadata usage. The disposition table specifies each current link's retained responsibility and the extracted skills' concrete load bindings.

loading...

Reference content destinations

Destination cards use target skill names and target organizations, including channel-delivery-skic and ci-runtime-skic. This is a proposed allocation, not a renamed installation.

Allocation boundary: this seven-file central-source diagram does not allocate the AeroSim-specific login and account-recovery sections identified in audit A12. Its runtime-and-ci.md arrow covers CI/runtime topics only. Read it together with the supplementary topic allocation below; it is not a complete allocation of the audited AeroSim reference.

Arrows show the original option's content destinations. “Kept whole” labels indicate retained ownership, not an exemption from the thinning required by the audit. Repeated destination cards identify the same skill. Extracted content is not presented as a newly created reference file; the separately proposed final checklist is explicitly identified.

loading...

Supplementary AeroSim allocation — runtime-and-ci.md

Audited topicProposed destination and retained authority
Login and secret handlingSkills 5/6: development-security and development-security-skic. Generic handling belongs in skill 5; exact project bindings belong in skill 6. Existing channel-board-skic policy remains authoritative; extraction does not create a second credential authority.
Account recoveryci-runtime-skic coordinates the conditional load of self-hosted-service-account-recovery; the specialist owns recovery mechanics. Delivery retains the exact own-account delegation and recovery preconditions. Moving the load point grants no account, permission or platform authority.

These are proposed responsibility destinations, not installed changes. Preserve the existing safeguards until an approved extraction provides and verifies the corresponding bindings.

Editable source: engineering/diagrams/delivery-skill-split-proposal.drawio.

No current skill link is removed. The actual AeroSim metadata contains 27 direct pointers: all 18 retained links under canonical names, five concrete helper owners, two generic bases and two draft review aids. Body-only fallback loads and compatibility aliases are additional preserved routes, not metadata count inflation. Source links below pin actual repository identities and immutable defaults; recovery links to its new reviewed publication; historical remote lineage remains unverified.

Actual skillDispositionDecision-point load / responsibilityWhy retained or addedPublished source / loadability
channel-board-skiccomplete: retainedDelivery and security overlayRetains shared SKIC policy; extracting login rules does not replace project governance.SKILL.md
channel-general-skic-aerosimcomplete: retainedDelivery governanceRetains the authoritative project ownership and approval-routing record; a reusable helper cannot replace it.SKILL.md
channel-releases-skic-aerosimcomplete: retainedDelivery release handoffRetains the release owner and completion/handoff contract; a reporting helper does not grant release authority.SKILL.md
discordcomplete: retainedDelivery channel operationsRetains the existing Discord operations pointer; no evidence establishes that it is obsolete.SKILL.md
documentation-docusaurus-skic-aerosimcomplete: retaineddelivery-docs → AeroSim documentation bindingRetains the concrete documentation-platform skill required by the generic documentation helper.SKILL.md
glossary-skiccomplete: retaineddelivery-docs → SKIC glossary bindingRetains canonical term ownership; generic documentation guidance is not a substitute for the glossary.SKILL.md
self-hosted-service-account-recoverycomplete: retainedci-runtime-skic → recovery bindingRetains the specialist recovery procedure pointer; invocation remains subject to the exact project authorization and preconditions, with no broadened authority.new reviewed publication; runtime loads; historical lineage unverified
truenascomplete: retainedci-runtime-skic → platform-storage bindingRetains the concrete TrueNAS procedure pointer required by the runtime/storage policy; it is not replaced by generic CI guidance.SKILL.md
development-durable-wave-executioncomplete: retainedDelivery wave orchestrationRetains reusable dependency-wave claim, continuation, recovery and closure mechanics.SKILL.md
development-gatescomplete: retainedDelivery and ci-runtime-skicRetains immutable review, exact-head CI and integration gates; CI extraction does not reimplement them.SKILL.md
development-integritycomplete: retainedDelivery and status-reporting-skicRetains evidence and honest completion rules; reporting templates add an overlay rather than replacing integrity checks.SKILL.md
development-method-ttdcomplete: retainedDelivery coding and unit testingRetains RED–GREEN–REFACTOR and unit-test discipline for behavior changes and fixes.SKILL.md
development-branching-strategy-skic-aerosimcomplete: retainedDelivery → AeroSim branching overlayRetains project-specific branching and PR rules alongside the generic base; similar names are not proof of equivalence.SKILL.md
development-monorepo-pnpmcomplete: retainedDelivery and draft app/package review aidsRetains the existing global monorepo contract; draft folder helpers are narrower and do not impose conventions.SKILL.md
development-scripts-skic-aerosimcomplete: retainedDelivery → AeroSim script overlayRetains project-specific Taskfile and script conventions alongside the generic base, without flattening local rules.SKILL.md
devsecops-ci-cd-giteacomplete: retainedci-runtime-skic → reusable pipeline mechanicsRetains Gitea/Harbor workflow mechanics; the new CI/runtime skill coordinates them instead of duplicating them.SKILL.md
devsecops-ci-cd-gitea-skic-aerosimcomplete: retainedci-runtime-skic → AeroSim pipeline overlayRetains the exact AeroSim CI/CD contract as well as the reusable Gitea skill; neither substitutes for the other.SKILL.md
development-gitops-argo-cd-home-gondor-v1complete: retainedci-runtime-skic and Delivery GitOps workRetains the current selected GitOps implementation skill; this proposal does not authorize switching to another variant.SKILL.md
ci-runtime-skiccomplete: addedruntime-and-ci / failure-and-documentationCoordinates isolated runtime, immutable images and same-gate repair without replacing procedure owners.SKILL.md
delivery-docscomplete: addedfailure-and-documentation / documentation workOwns ten coverage outcomes and delegates authoring/glossary bindings.SKILL.md
status-reporting-skiccomplete: addedstatus-and-reporting / blocker communicationOwns report vocabulary and templates without acquiring release authority.SKILL.md
development-securitycomplete: addedruntime-and-ci / authentication preflightOwns operation and secret-exposure preparation; no new credential policy.SKILL.md
development-security-skiccomplete: addedruntime-and-ci / shared loginBinds Board policy and exact authorized recovery preconditions.SKILL.md
development-branching-strategycomplete: addedbranch and PR decision pointsGeneric Git mechanics complement, never replace, the AeroSim overlay.SKILL.md
development-scriptscomplete: addedtoolchain / script decision pointsGeneric exact-context preflight complements the project script overlay.SKILL.md
develop-monorepo-pnpm-app-skicdraft review aid: addedDelivery application lifecycle/integration reviewv0.1.0 draft, not approved conventions; existing monorepo owner remains authoritative.SKILL.md
develop-monorepo-pnpm-package-skicdraft review aid: addedDelivery package API/export/compatibility reviewv0.1.0 draft, not approved conventions; existing monorepo owner remains authoritative.SKILL.md

Mandatory AeroSim adoption overlay

Implemented bindings: delivery-docs invokes project Docusaurus and Glossary; ci-runtime-skic invokes generic/project CI, selected Gondor GitOps and conditionally authorized storage/recovery; status-reporting-skic invokes integrity and preserves Releases handoff. Security invokes Board policy, not an independent credential authority. Delivery keeps governance, both branching/script overlays and their generic bases. Preserve the Task entry distinction: new pickup requires current READY_FOR_DELIVERY; continuation requires current IN_PROGRESS, the existing claim and historical verified admission, not re-admission. A generic base skill does not replace its AeroSim overlay. Recovery loads only for an explicitly authorized recovery procedure; reporting does not own release approval or execution.

The two app/package helpers are installed v0.1.0 draft review aids, included in the 27 direct pointers. Routing is implemented; contributor approval and adoption as mandatory conventions are not claimed. Existing monorepo procedures remain authoritative.

Removal or replacement gate

Any later proposed removal must identify the exact current skill, reason, replacement or evidence that it is no longer needed, affected responsibilities and call sites, and the owner decision required by existing governance. A move to an extracted skill must name and link the new owner and prove the dependency remains reachable and is loaded at the right decision point. It is not a deletion rationale by itself. Similar names, genericization, or absence from the full-split option are not sufficient reasons. Until this evidence is reviewed, preserve the direct link and mark any questioned dependency retained pending review. This revision proposes zero removals.

The two AeroSim-only references absent from the original seven-reference central baseline remain project-owned: gitea-actions-policy.md is byte-unchanged; single-subagent-task-delivery.md was updated in PR #42 for A02/A04 policy alignment. The reference-allocation view above does not silently delete or relocate them.

Reference file disposition​

The seven central reference rows now map to published owners below. Split references retain only project bindings and decision-point loads; two additional AeroSim-only references remain project-owned. gitea-actions-policy.md is byte-unchanged; single-subagent-task-delivery.md was updated in PR #42 for A02/A04 policy alignment. A02/A04 gate policy is implemented for both Central and AeroSim; no source-alignment debt or new human decision remains. Each destination contains a substantive contract rather than an empty router.

Reference fileState and responsibility coverageActual destination / consumer sources
common-pitfalls.mdcomplete — Removed repeated lists; shared CI/repair, docs and reporting safeguards reside at owners. Delivery retains exact admission/visibility exception loads and AeroSim lock-holder check.Owners: channel-delivery-skic; ci-runtime-skic; delivery-docs; status-reporting-skic. Consumers: skic; skic-aerosim
failure-and-documentation.mdcomplete — Same-gate repair loop, blocker packet/routing and ten domain-coverage outcomes moved once; local authoring/glossary bindings and sole-executor help threshold preserved.Owners: ci-runtime-skic; status-reporting-skic; delivery-docs. Consumers: skic; skic-aerosim
runtime-and-ci.mdcomplete — Workspace/cache/preflight, base images, isolated resources and owner-adoption gate moved. Board policy bound via security helpers. AeroSim own-account authority/interlocks and local DEV/image/chart bindings retained.Owners: ci-runtime-skic; development-security; development-security-skic. Consumers: skic; skic-aerosim
status-and-reporting.mdcomplete — Complete vocabulary and wave/human-facing templates moved; current Scope remains authority, concrete AeroSim Board/RootAtSkic/Releases bindings stay local.Owners: status-reporting-skic. Consumers: skic; skic-aerosim
task-delivery-gates.mdcomplete: Central and AeroSim A02/A04 — Both require independent review before substantive push and invalidate merge readiness on any target-base commit change. Frozen exact candidates, required exact-head CI and separate integration evidence preserve the six stages and sole implementation worker.Owners: channel-delivery-skic; channel-delivery-skic-aerosim. Consumers: skic; skic-aerosim
repository-entry-and-visibility.mdcomplete — Project entry, naming and visible PR rules retained unchanged; existing ordinary Git owner loads retained.Owners: channel-delivery-skic; channel-delivery-skic-aerosim. Consumers: skic; skic-aerosim
planning-artifact-reconciliation.mdcomplete — Existing thinned semantic admission/lifecycle and duplicate-suppression contract retained; existing gate/integrity loads preserved, canonical URLs refreshed.Owners: channel-delivery-skic; channel-delivery-skic-aerosim. Consumers: skic; skic-aerosim

Project-owned sources: gitea-actions-policy.md (byte-unchanged); single-subagent-task-delivery.md (updated for A02/A04 in PR #42).

Summary table​

Historical candidate assessment (2026-10-23, before extraction and draft publication). The statuses below are retained for comparison only; use the current verified snapshot and helper dispositions above for implementation state.

These are candidates retained for comparison, not a rollout plan. Target names apply the agreed naming direction to the original split option; they do not approve creating its helpers. Target organization is a naming destination, not evidence that the organization or repository exists. The two empty structure helpers remain deferred.

#Target skill nameTarget organizationCandidate status
1channel-delivery-skicskic-skillsExisting canonical name verified; thinning remains proposed; target organization transfer not inferred
2ci-runtime-skicskic-skillsUnproven — extraction criteria not yet demonstrated
3delivery-docsglobal-skillsUnproven — extraction criteria not yet demonstrated
4status-reporting-skicskic-skillsUnproven — extraction criteria not yet demonstrated
5development-securityglobal-skillsUnproven — extraction criteria not yet demonstrated
6development-security-skicskic-skillsUnproven — extraction criteria not yet demonstrated
7development-monorepo-pnpmglobal-skillsExisting skill; name unchanged, organization migration not performed
8develop-monorepo-pnpm-app-skicskic-skillsUnproven — extraction criteria not yet demonstrated; Deferred — empty placeholder
9develop-monorepo-pnpm-package-skicskic-skillsUnproven — extraction criteria not yet demonstrated; Deferred — empty placeholder

Candidate evidence register

No candidate below currently demonstrates the complete agreed threshold. Role labels and possible consumers are not evidence of two concrete consumers. The comparison diagrams illustrate the full-split option; their “new” labels do not establish extraction readiness.

CandidateExisting owner or binding to avoid duplicatingConsumer evidenceContent move to prove before acceptance
ci-runtime-skicExisting CI, gates, GitOps and storage specialists; Delivery retains project authority and unmatched safeguardsTwo concrete consumers not demonstratedProposed CI/runtime, repair and preflight extraction; identify exact source/destination clauses and remove duplicate procedures without losing safeguards
delivery-docsDelivery domain content; Docusaurus authoring/build mechanics; Glossary terminologyTwo concrete consumers not demonstratedProposed documentation-domain guidance from failure-and-documentation.md; prove distinct value beyond existing owners
status-reporting-skicIntegrity evidence rules; Delivery status vocabulary/format; Releases completion authorityTwo concrete consumers not demonstratedProposed reporting and blocker wording from status-and-reporting.md and failure-and-documentation.md; retain project bindings and avoid duplicate integrity rules
development-securityExisting shared login policy and specialist recovery mechanicsTwo concrete consumers not demonstratedIdentify genuinely non-duplicated generic handling guidance; no second credential-policy owner
development-security-skicExisting shared login policy (channel-board-skic)Two concrete consumers not demonstratedProposed project-specific bindings only; any transfer of policy ownership requires separate approval
develop-monorepo-pnpm-app-skicExisting monorepo skillTwo concrete consumers not demonstratedNo distinct content demonstrated; empty placeholder remains deferred
develop-monorepo-pnpm-package-skicExisting monorepo skillTwo concrete consumers not demonstratedNo distinct content demonstrated; empty placeholder remains deferred

Candidates 1 and 7 are existing Delivery/monorepo responsibilities, not new helper extractions. The Delivery rename is verified separately; their target organization labels do not authorize transfers. The register is an evidence gap assessment, not a finding that reuse cannot exist.