Skip to content

Defensible architecture: repository-specific vertical-slice QA v1 - #2

Merged
qt314wink merged 5 commits into
mainfrom
architecture/defensible-vertical-slice-v1
Jul 20, 2026
Merged

qt314wink merged 5 commits into
mainfrom
architecture/defensible-vertical-slice-v1

Conversation

@qt314wink

Copy link
Copy Markdown
Contributor

Purpose

Extends the merged control plane with a defensible vertical-slice verification contract that remains centralized in meaning but repository-specific in execution.

Architecture

  • schemas/repository-verification-profile.schema.json defines the shared language for repository archetype, maturity, criticality, runtime, commands, QA surfaces, promotion gates, evidence, and known omissions.
  • .github/workflows/reusable-defensible-vertical-slice.yml performs frozen installation, declared checks, repository-specific QA, deterministic artifact hashing, and retained verification receipts.
  • Missing tests are reported as absent rather than passed.
  • A successful receipt proves only declared automated surfaces; it does not erase known omissions or substitute for human visual/accessibility judgment.

Why this boundary

The organization owns verification semantics and evidence format. Each repository owns its commands, specialized risks, and promotion requirements. This avoids both duplicated workflows and a monolithic control plane that pretends every repo has the same failure modes.

Initial canaries

Separate draft PRs adopt this contract in:

  1. MelodicBloom/aether — WebGL application and reproducibility canary
  2. MelodicBloom/chromaflora-prime — motion/accessibility application canary
  3. qt314wink/svg-filter-lab — reusable visual-library/Storybook canary
  4. qt314wink/seed-loom — compiler, schema, provenance, visual regression, and deployment-truth canary

Safety

Verification only. No deployment, source mutation, secret access, cross-repository write authority, or branch-protection changes. Keep draft until canary runs expose and resolve contract defects.

Copy link
Copy Markdown
Contributor Author

Canary execution update

All four repository callers are now pinned to corrected control-plane commit 597d76aa36c833f8374b1756e4db46244e012323, replacing the mutable branch reference.

The new runs confirm the central sequencing fix works: checkout, setup-node, profile presence, and repository-identity validation now complete successfully before repository-local dependency gates run.

Observed results:

  • MelodicBloom/aether: fails at Require frozen dependency contract — package-lock.json is absent.
  • MelodicBloom/chromaflora-prime: passes the lockfile-presence gate, then fails at Install frozen dependencies — the committed lockfile is present but not a valid frozen representation of the declared dependency graph.
  • qt314wink/svg-filter-lab: fails at Require frozen dependency contract — no npm lockfile on the canary base.
  • qt314wink/seed-loom: fails at Require frozen dependency contract — no npm lockfile on the canary base.

This is the intended behavior of the control plane: infrastructure faults are now separated from reproducibility defects, and no lint/type/test/build surface is claimed after a failed dependency gate.

Before this PR is ready for review, recommended central follow-ups are:

  1. improve the lockfile gate error message to print the expected filename and repository profile runtime;
  2. emit a minimal failure receipt even when verification stops before build, so failed gates also produce durable evidence;
  3. retain the immutable SHA pin as the canary reference until this PR is merged and tagged.

Copy link
Copy Markdown
Contributor Author

Execution update — durable early-failure evidence

Implemented the briefing's highest-priority control-plane change on this PR branch.

Changes

  • Added step-success markers for runtime setup, profile validation, lockfile presence, frozen install, lint, typecheck, tests, build, specialized QA, and artifact digest.
  • Added an if: always() verification receipt containing source/workflow identity, job status, profile hash when available, completed/not-completed checks, and known omissions.
  • Added an if: always() artifact-retention step.
  • Improved the missing-lockfile error to name the repository, package manager, and expected lockfile.
  • Fixed hidden evidence upload by setting include-hidden-files: true for .automation-evidence/.

Canary finding

The first receipt canary successfully generated its failure receipt but initially failed to upload it because hidden paths are excluded by default. That defect is fixed at commit 214f41c65517d3158f50e99a54141566c45ee6a6.

AETHER is now pinned to that commit as the final retained-failure receipt canary. Do not merge until the resulting failed lockfile run shows a successfully retained defensible-verification-* artifact.

Tracked follow-up work

@qt314wink
qt314wink marked this pull request as ready for review July 20, 2026 06:35
@qt314wink
qt314wink merged commit 9281c31 into main Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant