Files
pikasTech-HWLAB/docs/dev-evidence-blocker-aggregator.md
T
2026-05-21 16:47:04 +00:00

2.9 KiB

DEV Evidence / Blocker Aggregator

This is the lightweight report-only entry point for pikasTech/HWLAB#41. It helps a commander decide whether the DEV acceptance path is green, blocked, or ready for another repair round across #33-#39, #7, and #31.

Run from the repository root:

node scripts/dev-evidence-blocker-aggregator.mjs --pretty

For a short validation response:

node scripts/dev-evidence-blocker-aggregator.mjs --check

Source Levels

The aggregator keeps evidence levels separate so fixture output cannot be promoted to live DEV evidence:

Level Meaning
SOURCE Repository contracts, schemas, docs, manifests, or examples.
LOCAL Localhost or in-process smoke results only.
DRY-RUN Fixture-backed or no-mutation dry-run readiness evidence.
DEV-LIVE Read-only evidence observed from the real DEV route.
BLOCKED Missing issue reads, missing DEV evidence, missing artifacts, or other open blockers.

Current Contract Map

Milestone Current visible level Contract entry
M0 SOURCE docs/m0-contract-audit.md, protocol schemas, evidence chain examples, M0 validator.
M1 LOCAL docs/m1-local-smoke.md, fixtures/mvp/runtime.json, scripts/m1-contract-smoke.mjs.
M2 DRY-RUN DEV deploy smoke fixture, artifact catalog, runtime boundary, and M2 dry-run validator.
M3 LOCAL Hardware trusted loop topology fixture and local patch-panel smoke.
M4 LOCAL Agent automation loop fixture, local runtime skeleton, skills commit, evidence, and cleanup smoke.
M5 DRY-RUN MVP e2e dry-run plan and orchestration validator.

Blocker Posture

If GitHub issues are not readable in the runner, the report marks issue-read as blocked and uses only committed repository artifacts plus the task prompt. This keeps #33-#39 status visible without treating issue comments as silently available.

The report is blocked until real DEV-LIVE evidence is attached for the DEV route and downstream HWLAB runtime services. Current source, local, and dry-run contracts are useful readiness signals, but they are not live DEV proof.

Next-Round Buckets

The JSON output groups recommended next actions into:

  • artifact/base image: real publish or provenance evidence for frozen HWLAB service IDs.
  • edge/network: read-only DEV route observations for ingress, edge, frp, and D601 router.
  • runtime/health: DEV health JSON for cloud, gateway/simulator, patch-panel, agent, worker, skills, and CLI surfaces.
  • M3/M4 live: narrow authorized DEV-only loop evidence with trace, audit, operation, session, evidence, and cleanup IDs.

Boundaries

The aggregator does not deploy, call DEV, call PROD, run browser tests, run heavy e2e, read secrets, restart services, or replace HWLAB runtime services with UniDesk services. It is a local report generator and static contract checker only.