SpecsCLIM4-trust-telemetry-lifecycle

M4 Trust, Telemetry, and Lifecycle Issue Matrix

M4 Trust, Telemetry, and Lifecycle Issue Matrix

Blocker Verdict

M4 may proceed.

Dependency	Status	Evidence	Verdict
IP-100	Done	Linear status `Done`; repo has implemented and ingested spec at `apps/wiki/specs/cli/IP-100-harness-methodology-domain/SPEC.md`.	Unblocked IP-104 and IP-107 dependency chain.
IP-102	Done	Linear status `Done`; repo has M3 implementation notes and control-plane baseline contract/API/CLI evidence under `apps/wiki/specs/cli/M3-authenticated-distribution/`.	Unblocked IP-105 and IP-106 dependency chain.

Dependency Order

Order	Issue	Reason
Wave A	IP-104 and IP-105	Both blockers are Done. Work scopes can run in parallel if implementation files remain disjoint.
Wave B	IP-106	Blocked by IP-105 because reporting uses the telemetry envelope and persistence model. Related to IP-143.
Wave C	IP-107	Blocked by IP-104 because colleague trust material needs the codified lifecycle. Blocks IP-108.

Parent Coverage

Parent	Title	Linear status	Children	Related/dependency issues	Spec	Plan	Implementation	Review	Validation	Docs	Tracker
IP-104	Codify the Harness Intelligence lifecycle	Backlog	IP-128, IP-129, IP-130	Blocked by IP-100; blocks IP-107	Created: `../IP-104-harness-lifecycle/SPEC.md`	Created: `../IP-104-harness-lifecycle/PLAN.md`	Implemented	Passed	Full validation passed	Docs ingest updated source/routed lifecycle pages	Ready after PR
IP-105	Track adoption through runtime telemetry	Backlog	IP-131, IP-132	Blocked by IP-102; blocks IP-106 and IP-138	Created: `../IP-105-runtime-telemetry/SPEC.md`	Created: `../IP-105-runtime-telemetry/PLAN.md`	Implemented	Passed	Full validation passed	Docs updated telemetry/reporting boundary	Ready after PR
IP-106	Support CLI-backed harness issue reporting	Backlog	IP-133, IP-134	Blocked by IP-105; related to IP-143	Created: `../IP-106-cli-harness-reporting/SPEC.md`	Created: `../IP-106-cli-harness-reporting/PLAN.md`	Implemented	Fixed	Full validation and CLI smoke passed	Docs updated CLI report path/support loop	Ready after PR
IP-107	Create the colleague trust gate bundle	Backlog	IP-135, IP-136	Blocked by IP-104; blocks IP-108	Created: `../IP-107-colleague-trust-gate/SPEC.md`	Created: `../IP-107-colleague-trust-gate/PLAN.md`	Implemented	Passed	Full validation and `next start` browser proof passed	Docs ingest created trust-and-adoption bundle	Ready after PR

Child Coverage

Child	Parent	Title	Linear status	Acceptance coverage required	Source link
IP-128	IP-104	Requirements-to-backlog workflow is explicit in the harness	Backlog	`requirements-grill` artifacts are structured inputs; `write-backlog` produces module/epic/story hierarchy from locked decisions; parked branches stay deferred; backlog stays product-facing.	https://linear.app/devpunks/issue/IP-128/requirements-to-backlog-workflow-is-explicit-in-the-harness
IP-129	IP-104	Planning workflow produces specs, plans, and parallel-ready task pipelines	Backlog	`create-spec` anchors one epic and all children; `create-plan` closes planning questions; `swarm-planner` defines precedence-aware parallel work with skill assignments; `opensrc` is part of source discovery.	https://linear.app/devpunks/issue/IP-129/planning-workflow-produces-specs-plans-and-parallel-ready-task
IP-130	IP-104	Implementation workflow records execution mode and closeout evidence	Backlog	Execution mode recorded before coding; sequential and parallel modes are not mixed; `PLAN.md`, implementation notes, and spec-linked debt update after tasks/waves; finalization includes acceptance audit and docs/backlog follow-through.	https://linear.app/devpunks/issue/IP-130/implementation-workflow-records-execution-mode-and-closeout-evidence
IP-131	IP-105	Backend records trusted baseline usage events	Backlog	Persist only the five v1 happy-path product events; link events to `ProjectUsage` and observed repository when available; carry authenticated operator when available and git identity only as metadata/fallback; include CLI/baseline/source/timestamp fields; keep noisy lifecycle/failure data in logs/OTel/debug.	https://linear.app/devpunks/issue/IP-131/backend-records-trusted-baseline-usage-events
IP-132	IP-105	Telemetry filters local, debug, test, and retry noise	Backlog	Identify or exclude localhost/dev usage, CI/publish validation reads, repeated retries/cache misses, and debug reads from adoption stats.	https://linear.app/devpunks/issue/IP-132/telemetry-filters-local-debug-test-and-retry-noise
IP-133	IP-106	Agent can submit structured harness friction through dp	Backlog	CLI report submission emits `cli.harness.report.submitted` only after successful submit; payload includes project usage, observed repository, authenticated operator when available, git identity fallback/context, title/body/type/severity, timestamp; `dp-cli` guidance makes reporting natural; reports persist for backoffice triage; GitHub is v1 follow-up target.	https://linear.app/devpunks/issue/IP-133/agent-can-submit-structured-harness-friction-through-dp
IP-134	IP-106	Systemic harness reports can become central backlog items	Backlog	Reports can be triaged as local quirks or systemic issues; systemic reports can create or link central Linear issues; resulting fixes flow into wiki, skill, hook, CLI, or baseline updates without rewriting project-specific issue bodies as execution handoffs.	https://linear.app/devpunks/issue/IP-134/systemic-harness-reports-can-become-central-backlog-items
IP-135	IP-107	Internal onboarding path explains what to trust and what not to trust	Backlog	Onboarding explains harness purpose and misuse boundaries; distinguishes automatic verification, human verification, and remaining judgment; includes known failure modes.	https://linear.app/devpunks/issue/IP-135/internal-onboarding-path-explains-what-to-trust-and-what-not-to-trust
IP-136	IP-107	Golden repo walkthrough demonstrates harness adoption	Backlog	Walkthrough shows scaffold setup/update on a realistic repo; explains scoped prompts, tools, hooks, validation gates, expected agent behavior, and failure handling.	https://linear.app/devpunks/issue/IP-136/golden-repo-walkthrough-demonstrates-harness-adoption

Issue	Status	Relationship	Boundary
IP-108	Backlog	Blocked by IP-107	Public landing narrative remains out of M4 scope. IP-107 may provide private trust material that later informs sanitized public copy.
IP-138	Backlog	Blocked by IP-105	M4 creates telemetry/reporting foundation. Primary adoption UI and full backoffice app belong to M4.5.
IP-143	Backlog	Related to IP-106; child of IP-138	M4 supports CLI/API/report contract and GitHub-linked follow-up shape. Full backoffice triage UI belongs to M4.5 unless needed for an API smoke boundary.

Linear Closeout Evidence

Evidence comments were added to IP-104, IP-105, IP-106, and IP-107 after implementation/review/validation. Tracker status is ready to close after PR #6 merges.

PR #6 telemetry review findings

M3 Issue Matrix: Authenticated Distribution

Previous Page

PR #88 Review Remediation

Next Page

On this page

M4 Trust, Telemetry, and Lifecycle Issue Matrix Blocker Verdict Dependency Order Parent Coverage Child Coverage Related Out-Of-Milestone Coordination Linear Closeout Evidence Related Tech Debt