Files
channel-delivery-skic/SIMPLIFICATION.md

10 KiB
Raw Permalink Blame History

Bounded Delivery simplification — 2026-10-23

Authority and boundary

GUILD-IMP-20261023-delivery-existing-owners. Piotras (501954115690168321), verified Board member, approved “implement delivery skills proposal” in Guild message 1563054836508008539, as supplied by the commissioning parent. This record does not claim an independent Discord re-audit.

Implements only the published recommendation / smallest useful change, read from delivery-proposal-refresh-20261023/engineering/skills-delivery-channel.mdx, with 2026-10-23 source/finding evidence. Baseline: 225ae3b068d97748af69597353479eb9c26579fc, version 1.14.1; candidate 1.14.2.

Central package only; no helper, dependency change, file removal, migration, policy choice, dependency-repository edit or documentation-project edit. This manifest is an audit artifact, not an operational loaded reference. Parent owns publication, runtime refresh and separately authorized semantic project adoption.

Responsibility manifest

Each row states the old rule/location, retained or single owner, and the new load point. Unlisted operational paragraphs remain unchanged.

Rule / before After: owner and decision point Retained outcome / limit
Login origin and authorized purpose — entry + runtime repeated Board policy Board Corp v1 System SSO Credential Use; entry says load before login, runtime follows that binding Origin/purpose verification remains mandatory; unavailable owner stops login
Login secret names/runtime-only use — same two copies Board; same pre-login load Exact names retained in entry; no secret values introduced
No inspect/print/hash/serialize/paste/log/screenshot/persist or unsafe transport — same copies Board full policy, not a selected subset Board rules 2–3 and 7–8 retain all restrictions and session safety
Missing secret names only; never ask for values — same copies Board rules 2–4, pre-login load Injection only, no fallback secret
Login is not account/credential/MFA/permissions/billing/destructive authority Board plus short Delivery boundary No recovery or additional authority granted
Canonical lifecycle vocabulary repeated entry + status reference Existing status reference owns full vocabulary; entry loads it before status action Exact Task admission/claim, separate BLOCKED, TO_BE_RELEASED vs DONE retained in entry; full statuses unchanged in reference
Ways of Working five sections repeated entry + failure reference Existing failure reference owns domain coverage; entry loads it before edits All ten domain sections remain; verified practice only, not aspirations
Documentation platform mechanics Global Docusaurus + project overlay; failure reference before authoring/validating Source identity must match, not unrelated same-name VSSA installation; no domain/Diátaxis conflation
Canonical reusable definitions Existing global Glossary; failure reference before defining terms Final top-level Glossary and domain links, not copied explanations
Nested pnpm/Corepack bootstrap recipe — planning step 5 Retained unchanged locally pending resolution of global Docusaurus runtime identity Published owner has the procedure, but the installed name currently resolves to an unrelated source; no extraction to an unverified runtime owner
Current checkpoint/report claims — planning steps 8/12 Integrity evidence-first sequence; explicit before-report load in planning/status Fresh source/merge distinction, revalidation on drift/merge/close, final equality and duplicate suppression retained locally
Report shape and lifecycle meaning Delivery status reference remains owner Requested wave header, every Task, real owner, linked PR, gate codes, failure classification and no automatic DONE unchanged
pnpm/script implementation routing — runtime Coding Existing pnpm and scripts owners with source-table link and action triggers Approved Feature/Task, structure/namespace, traceability, no unrelated refactor/fabrication remain
Unit mechanics — runtime Unit testing Explicit TTD action load added; existing generic owner already routed in entry Existing bullets and Task stage left intact; no choice on discard/forward repair
Failure diagnosis/forward-repair procedure repeated entry + failure reference Existing failure reference; entry loads at observed failure Complete reference repair and escalation text unchanged, including no premature stop/help-policy rewrite
Build/CI failure classes repeated runtime + entry Entry owns classes; runtime loads it and Integrity before reporting Task CI job inventory and exact-head requirements untouched
Base-image policy repeated entry + runtime Existing runtime reference owns complete contract; entry loads before create/publish/consume Digest, version/platform/non-root/tools, candidate secret isolation, immutable publication/readback, fail-closed tests, lockfile parity, separate layers, forward repair/last-good all retained
Pitfalls duplicated entry + reference Existing pitfalls reference, loaded on failed/resumed work and before status Full reference unchanged; no safeguarding rule deleted

Verified existing sources

Source audit used the published capture, not version-label equality. No owner content was copied into a new helper or changed in this task.

  • Board login owner: published/installed equal in evidence; loaded for comparison.
  • Integrity reporting owner: published/installed equal; loaded for comparison.
  • Global Docusaurus: full captured remote_text read from delivery-refresh-evidence/documentation-source.json, including nested-pnpm remedy. Direct unauthenticated fetch returned 404; no false live-readback claim. Skill loader resolves a different VSSA owner; operational loads now explicitly require correct provenance.
  • Glossary: retained existing route; no glossary procedure extracted.
  • TTD: retained strict existing route, no discard-policy rewrite.
  • Ordinary Git, pnpm and scripts source links remain in the unchanged Development Skill Routing table. No Git procedure is extracted because exact Task/branch/readback requirements are tightly coupled to unresolved gates.

Deferred findings and untouched boundaries

A01: no gate algorithm extraction; published development-gates lacks installed complete-job-inventory protections. A02/A04: substantive push/review order and harmless-base-drift wording untouched. A03: main-session review/worker restrictions unchanged. A05: strict TTD route retained, weaker wording/local-discard versus valid-work forward repair not reconciled. A06: whole-wave claim mapping not chosen. A08: no help-threshold/worker-role decision. A09: project CI source/runtime drift not changed. A10: no obsolete Helm fix needed; current static artifact versus functional UAT boundary retained. A11: exact branch/title/attempt/early-PR identity untouched. A12: no recovery skill or authorization change. A13: GitOps loadability/storage source issues not solved; all runtime/storage safeguards retained. A14: exact-context preflight remains byte-identical. A15: domain/platform distinction retained. A16: base-image safeguard remains local, not delegated to an incomplete external owner. A17: no scheduler authority conclusion or job mutation. A18: central eight-channel boundary unchanged; no project cleanup here.

The four complete files task-delivery-gates.md, repository-entry-and-visibility.md, common-pitfalls.md, aerosim-lessons-review.md are byte-identical. Runtime workspace, exact-context preflight/base-image/runtime-resource tail, failure-repair procedure and entry Authority/Escalation are hash-locked in tests. All 12 metadata dependencies and all 8 references remain.

Validation and operational footprint

Test-first: initial unittest run had 12 tests, with expected failures for missing load points and size reduction (2 failures). Final suite includes unittest classes and the three existing function-style routing tests through unittest.FunctionTestCase; plain discovery alone would miss those three. No network required by tests.

Final local validation: uv run --with pytest python -B -m pytest tests -q — 16 tests passed. git diff --check passed. No remote CI workflow is configured. Publication/installation is separately verified by the parent.

Measured operational footprint

Includes entry and every reference; excludes this audit manifest, tests, adoption record and caches. No removed procedure was moved into an operationally loaded new file.

File Before bytes After bytes Reduction
SKILL.md 27413 23017 4396
references/aerosim-lessons-review.md 3400 3400 0
references/common-pitfalls.md 2276 2276 0
references/failure-and-documentation.md 4428 5136 -708
references/planning-artifact-reconciliation.md 6624 6621 3
references/repository-entry-and-visibility.md 6514 6514 0
references/runtime-and-ci.md 11078 10654 424
references/status-and-reporting.md 5135 5385 -250
references/task-delivery-gates.md 17921 17921 0
Total 84789 80924 3865 (4.56%)