WHW-PORTFOLIO-EVIDENCE-METHOD-2026-08-26 · ready-for-evidence-intake

Evidence before investment or pruning

Current result: no portfolio decision has been issued. No private analytics or maintenance evidence has been imported and no product decision has been issued under this method. The method is live now so future decisions can be compared, challenged and reversed instead of being justified after the fact.

Evidence-method JSON · Blank decision card · Portfolio manifest

Five evidence families stay separate

The five evidence families remain separate; a single weighted score cannot authorize a decision. No product may be de-emphasised, noindexed, archived, merged or removed only because it falls below a traffic percentile.

search-demand

Search demand and discoverability

non-identifying impressions and clicks · query-theme coverage · indexed-route health

Boundary: Demand evidence is directional and cannot prove usefulness or product quality.

direct-use

Aggregate actual use or service

useful-session completion · aggregate return cohorts · caregiver-reported utility collected with consent

Boundary: Do not add remote child analytics. Family-product research requires consent and separate approval.

reliability-quality

Reliability, correctness and quality

release checks · reproducible defect rate · rule-fixture conformance · material corrections

Boundary: Automated checks do not replace expert content review or manual accessibility testing.

maintenance-burden

Maintenance burden

dependency and asset risk · hours required for critical fixes · release regressions · unowned operational work

Boundary: Estimate maintenance consistently and record uncertainty rather than inventing precision.

strategic-option-value

Strategic fit and option value

shared capability · distinct audience job · knowledge-engine contribution · reversible learning value

Boundary: Strategic intent is not evidence of market demand, efficacy or commercial viability.

Hard vetoes come first

An open veto blocks investment and may require remediation regardless of traffic. AI and automated validators cannot certify that a veto is truly clear.

  • child-safety: Unresolved child-safety or safeguarding risk
  • correctness: Repeated or material correctness failure
  • privacy-security: Unresolved privacy or security risk
  • critical-accessibility: Critical accessibility barrier
  • unsupported-claims: Unsupported educational, institutional, expert or compliance claim
  • ownerless: No accountable owner

Evidence grades

GradeMeaning
AMultiple recent, directly relevant and independently checkable evidence sources cover all five families, with limitations recorded.
BRecent, directly relevant evidence covers all five families, but one material limitation or validation gap remains.
CSome relevant evidence exists, but one or more evidence families are materially incomplete; only maintain, freeze or evidence-gathering changes are supported.
DEvidence is absent, stale, non-comparable or largely inferred; no portfolio reduction or investment claim is supported.

Allowed actions

ActionDecision meaning
investIncrease bounded development or distribution against a named hypothesis and rollback trigger.
maintainKeep the product live with defined reliability and review obligations.
freezeAccept critical fixes only while gathering evidence or resolving a veto.
mergeMove a product job or route into a named successor while preserving redirects and a rollback snapshot.
de-emphasiseReduce catalogue prominence without changing indexability or deleting the route.
noindexKeep the route accessible while requesting search engines not index it.
archivePreserve a readable record and source snapshot while ending active maintenance.
removeRemove the public route only after a preserved snapshot, successor or rationale and explicit rollback plan.

Reversibility ladder

step 1

snapshot

Record the current route, source revision, dependencies and public discovery state.

step 2

freeze

Stop feature work but retain critical safety, privacy, security and correctness fixes.

step 3

de-emphasise

Reduce promotion for a defined observation window without hiding the route.

step 4

noindex

Preserve direct access and monitor indexing changes with a rollback trigger.

step 5

archive

Keep a public record, reason, successor where applicable and recovery snapshot.

step 6

merge-or-remove

Require evidence grade A or B, a named owner, migration checks and a tested rollback path.

Data and automation boundary

  • Use aggregate route-week evidence only; child behaviour tracking is prohibited.
  • Private raw metrics do not belong in the public record.
  • The validator checks completeness and internal consistency, not whether evidence is true or an owner is authorised.
  • A validated card cannot automatically change the live site. Indexing, discovery and archive changes remain separately tested releases.

Local validation: node scripts/validate-portfolio-decision-card.mjs <completed-card.json>