// SPDX-License-Identifier: CC-BY-SA-4.0
= Standards — Future Work (Parked)
:status: Parked v0.1.0
:updated: 2026-04-05

Items deferred from the 2026-04-05 innervation build-out. Not active;
not on the ROADMAP's immediate phases. Revisit when precursors
(VeriSimDB deployed, panels live, ingest running) are in place.

== Parked items

=== 13. Standards Compliance SDK

**What:** A small importable library (Rust + ReScript bindings) that any
hyperpolymath repo can pull in to self-validate against RSR, CRG, A2ML,
K9, and language policy — then emit results directly to VeriSimDB.

**Why parked:** Needs VeriSimDB deployed (has Containerfile, no live
instance). Needs a stable RSR-validator CLI first (currently manual).
Building the SDK now = over-investment before the validator matures.

**When to revive:** After VeriSimDB goes live AND an RSR validator exists
as a CLI (separate repo).

=== 14. Automated CRG promotion/demotion rules

**What:** Hypatia rules that monitor evidence and automatically suggest
grade changes. Combines HYP-S001 (demotion detector) with its mirror,
an *evidence threshold* rule that suggests promotions.

**Why parked:** Requires CRG-grade octads populated in VeriSimDB (none
exist yet). The demotion detector (HYP-S001) is the skeleton — promotion
needs a larger evidence corpus.

**When to revive:** Once ≥ 50 repos have CRG grades recorded in
VeriSimDB with at least 3 assessments each (temporal depth).

=== 15. Cross-repo release dashboard

**What:** Full release telemetry — build status, test coverage, SBOM
completeness, proof status, CRG grade, compliance findings — aggregated
across all 290+ repos in one PanLL dashboard.

**Why parked:** Depends on *all* of: panels wired (#2), VeriSimDB live
(#3), ECHIDNA CI green (#4), ecosystem-link octads populated (#1), CRG
grades ingested. Five upstream dependencies.

**When to revive:** Once the full 5-layer innervation stack is running
end-to-end on at least 10 pilot repos.

=== 16. Cross-repo reusable-workflow pin propagation (auto-bump)

**What:** The cross-repo half of the workflow-pin staleness story. The
standards-side is done (ADR-003: the gate tolerates a recency window, and
`scripts/propagate-workflow-pins.sh` performs an audit-first bump). What
remains is the *fleet* wiring so a deliberate bump fans out automatically:

* Activate the Hypatia rule `lib/rules/sha_bump_propagation.ex`
  (hyperpolymath/hypatia) so a "consumer pin is behind standards HEAD"
  finding is routed (`:review`) rather than inert.
* Wire gitbot-fleet to run `propagate-workflow-pins.sh --fix` in the flagged
  consumer and open a DRAFT bump PR (mirrors the `.git-private-farm`
  dispatch pattern in `instant-sync.yml`; gated on a PAT, graceful-skip
  without it).
* Optional standards-side scheduled workflow (`propagate-workflow-pins.yml`)
  that, on a cadence, audits the fleet and dispatches the above — sketch
  only; do not ship the cross-repo dispatch without the PAT + owner sign-off
  (estate "no unattended mutations" guardrail).

**Why parked:** The actionable pieces live in *other* repos (hypatia,
gitbot-fleet) — out of scope for a standards PR. No technical precursor; it
needs cross-repo PRs + a dispatch PAT, not a VeriSimDB-style dependency.

**When to revive:** Whenever the deliberate-bump cadence is wanted. The gate
no longer forces it (consumers are green within the window), so this is a
convenience/freshness improvement, not a treadmill fix. Track via issues in
hypatia + gitbot-fleet referencing ADR-003.

== Out-of-scope (not parked — closed)

- Per-repo dashboards (PanLL handles this organically via manifests)
- Custom telemetry schema (covered by VeriSimDB octad schemas)
- Release gating beyond CRG (covered by ROADMAP Phase D)

== How to unpark

1. Move the item from this doc into `ROADMAP.adoc` under the right phase
2. Confirm precursors are satisfied
3. Open a task in the relevant repo's `STATE.a2ml v2`
4. Remove the entry from this doc
