{"id":"ops/evidence-script-ownership","relativePath":"ops/evidence-script-ownership.md","title":"Evidence Script Ownership","markdown":"# Evidence Script Ownership\n\nThe readiness scripts are part of the product, not a parallel app. Every\nhigh-churn evidence command has one accountable owner lane, one artifact surface,\nand at least one package-script check that must stay valid when the script\nchanges.\n\nThe machine-readable source of truth is\n`src/services/evidence-script-ownership.ts`. The guard is\n`tests/services/evidence-script-ownership.test.ts`, which fails when a\nhigh-churn package command loses its owner, points at a missing script, or names\na non-existent required check. It also fails when a colon-delimited\n`package.json` script namespace such as `launch:*`, `activity:*`, `pilot:*`, or\n`monitoring:*` lacks a namespace owner, preferred entry points, and pruning\nguidance.\n\n## Owner Lanes\n\n| Owner lane | Scope | Default cadence |\n|---|---|---|\n| Strict readiness owner | `pnpm review:goals*`, closeout, and the local-vs-strict claim boundary | Per change |\n| Launch readiness owner | preflight, launch review, launch evidence, a11y, crawler, public trust, and smoke packet commands | Per launch |\n| Long-term evidence owner | public k6, telemetry, Era C exit gate, 30-day runway, and maintenance evidence | Weekly |\n| ActivityStreams adoption owner | external consumer, durable subscription guard, adoption, and partner handoff evidence | Weekly |\n| Managed pilot owner | outreach, buyer pack, activation, support, KPI, packaging, and paid-pilot proof | Weekly |\n| Continuity hardening owner | DR, pentest, disabled-system staging drill, and projection readiness evidence | Weekly |\n| AI eval owner | golden-question evals, AG2 worker evals, and AI baseline artifacts | Per change |\n| Worker operations owner | outbox, publication queue, projection drain, dead-letter, and alert commands | Weekly |\n| Product governance owner | privacy, product constraints, credibility, validation drift, docs stats, and conformance proof | Per change |\n\n## Change Rule\n\nWhen adding or changing any high-churn evidence command:\n\n1. Update `src/services/evidence-script-ownership.ts` with the package alias,\n backing script, artifact path, required check, owner lane, and review cadence.\n2. Update the matching runbook or artifact contract doc when operator behavior\n changes.\n3. Run\n `node --import tsx --test tests/services/evidence-script-ownership.test.ts`.\n4. Preserve the strict-readiness distinction: local checks may prove the\n machinery is healthy, but partner, customer, uptime, SLO, and paid-pilot\n proof must remain real-world evidence until observed.\n\n## Escalation\n\nIf ownership is unclear, assign the command to the lane that consumes the\nartifact in `/readiness` or `pnpm review:goals`. If two lanes consume it, choose\nthe lane that can verify the artifact without enabling external side effects,\nthen document the dependent lane in the purpose text.\n\nNo command should be owned only by a README paragraph, CI workflow, or one-off\noperator memory. The registry is the durable handoff.\n\n## Namespace Grouping\n\nPackage-script prefixes are treated as operator-facing command groups. When\nadding a new `namespace:command` alias, keep it inside an existing namespace\nwhen possible. If a new namespace is necessary, add it to\n`PACKAGE_SCRIPT_NAMESPACE_CONTROLS` with:\n\n- a registered owner lane\n- the preferred entry point commands maintainers should try first\n- a pruning rule that explains when variants should be collapsed or removed\n\nCurrent operations-risk evidence measures 42 classified package-script\nnamespaces, with no unclassified namespaces and the largest namespace at 16\naliases.\n","sections":[{"level":2,"heading":"Owner Lanes","anchor":"owner-lanes"},{"level":2,"heading":"Change Rule","anchor":"change-rule"},{"level":2,"heading":"Escalation","anchor":"escalation"},{"level":2,"heading":"Namespace Grouping","anchor":"namespace-grouping"}],"html":"

Evidence Script Ownership

\n

The readiness scripts are part of the product, not a parallel app. Every

\n

high-churn evidence command has one accountable owner lane, one artifact surface,

\n

and at least one package-script check that must stay valid when the script

\n

changes.

\n

The machine-readable source of truth is

\n

`src/services/evidence-script-ownership.ts`. The guard is

\n

`tests/services/evidence-script-ownership.test.ts`, which fails when a

\n

high-churn package command loses its owner, points at a missing script, or names

\n

a non-existent required check. It also fails when a colon-delimited

\n

`package.json` script namespace such as `launch:`, `activity:`, `pilot:*`, or

\n

`monitoring:*` lacks a namespace owner, preferred entry points, and pruning

\n

guidance.

\n

Owner Lanes

\n

| Owner lane | Scope | Default cadence |

\n

|---|---|---|

\n

| Strict readiness owner | `pnpm review:goals*`, closeout, and the local-vs-strict claim boundary | Per change |

\n

| Launch readiness owner | preflight, launch review, launch evidence, a11y, crawler, public trust, and smoke packet commands | Per launch |

\n

| Long-term evidence owner | public k6, telemetry, Era C exit gate, 30-day runway, and maintenance evidence | Weekly |

\n

| ActivityStreams adoption owner | external consumer, durable subscription guard, adoption, and partner handoff evidence | Weekly |

\n

| Managed pilot owner | outreach, buyer pack, activation, support, KPI, packaging, and paid-pilot proof | Weekly |

\n

| Continuity hardening owner | DR, pentest, disabled-system staging drill, and projection readiness evidence | Weekly |

\n

| AI eval owner | golden-question evals, AG2 worker evals, and AI baseline artifacts | Per change |

\n

| Worker operations owner | outbox, publication queue, projection drain, dead-letter, and alert commands | Weekly |

\n

| Product governance owner | privacy, product constraints, credibility, validation drift, docs stats, and conformance proof | Per change |

\n

Change Rule

\n

When adding or changing any high-churn evidence command:

\n
  1. Update `src/services/evidence-script-ownership.ts` with the package alias,
\n

backing script, artifact path, required check, owner lane, and review cadence.

\n
  1. Update the matching runbook or artifact contract doc when operator behavior
\n

changes.

\n
  1. Run
\n

`node --import tsx --test tests/services/evidence-script-ownership.test.ts`.

\n
  1. Preserve the strict-readiness distinction: local checks may prove the
\n

machinery is healthy, but partner, customer, uptime, SLO, and paid-pilot

\n

proof must remain real-world evidence until observed.

\n

Escalation

\n

If ownership is unclear, assign the command to the lane that consumes the

\n

artifact in `/readiness` or `pnpm review:goals`. If two lanes consume it, choose

\n

the lane that can verify the artifact without enabling external side effects,

\n

then document the dependent lane in the purpose text.

\n

No command should be owned only by a README paragraph, CI workflow, or one-off

\n

operator memory. The registry is the durable handoff.

\n

Namespace Grouping

\n

Package-script prefixes are treated as operator-facing command groups. When

\n

adding a new `namespace:command` alias, keep it inside an existing namespace

\n

when possible. If a new namespace is necessary, add it to

\n

`PACKAGE_SCRIPT_NAMESPACE_CONTROLS` with:

\n\n

Current operations-risk evidence measures 42 classified package-script

\n

namespaces, with no unclassified namespaces and the largest namespace at 16

\n

aliases.

","updatedAt":"2018-10-20T01:46:40.000Z","checksum":"8432d0529cf4799d5b3aa481e85a63004723d51b66cd7162f80268f06fbbe045","checksumPrefix":"8432d0529cf4","anchorCount":4,"lineCount":69,"rawUrl":"/api/docs/content?path=ops%2Fevidence-script-ownership.md","htmlUrl":"/docs?doc=ops%2Fevidence-script-ownership.md","apiUrl":"/api/docs/content?path=ops%2Fevidence-script-ownership.md"}