Roll out continuous roadmap reconciliation across the repository fleet

[szmyty]

Outcome

Roll out the canonical Aether roadmap-impact completion hook across applicable Ego Hygiene repositories so repository roadmaps remain current as AI agents and humans complete work.

This is the fleet-adoption counterpart to egohygiene/aether#88.

The intended result is that any supported repo-changing agent or workflow entering an Ego Hygiene repository can discover the same rule:

Before PR handoff, evaluate roadmap impact and either reconcile ROADMAP.md, propose a human-governed roadmap change, record a justified no-change disposition, or report the check as blocked.

Dependencies

Do not begin broad fleet mutation until the upstream capability is releasable and pinned:

• Aether roadmap-impact reconciliation: egohygiene/aether#88
• Organization roadmap contract: egohygiene/hygiene#60
• Observatory roadmap read model: egohygiene/observatory#22
• Existing repository roadmap rendering: egohygiene/relay#31

Use immutable released/pinned Aether artifacts rather than mutable default-branch assumptions.

Current baseline

A prior organization scan found ROADMAP.md broadly present across the active fleet. Re-observe the live organization at implementation time rather than relying on that point-in-time count.

Classify each repository as:

• current canonical roadmap + hook;
• roadmap present, hook missing;
• roadmap structurally stale/legacy;
• provider projection drift;
• custom local roadmap behavior requiring migration;
• blocked;
• exempt/not applicable;
• inaccessible/private.

Desired state

For each applicable repository, Pace should be able to determine:

• canonical ROADMAP.md presence and contract version;
• stable roadmap step identifiers where required by Repository Intelligence;
• installed/pinned Aether roadmap-impact capability;
• managed agent/provider projections containing the shared completion hook;
• repository-specific configuration/overlays;
• latest roadmap-impact disposition/evidence where available;
• roadmap freshness/drift state;
• organization-roadmap relationships where declared;
• reviewed exception state.

Installation model

Prefer shared managed composition over copied agent prose.

Repository-local changes should be limited to what the host/repository actually requires, such as:

• Aether distribution/profile pin;
• generated provider-agent projection;
• local roadmap configuration/step IDs;
• local instructions pointing to the canonical shared behavior;
• validation/workflow integration.

Do not hand-copy the entire roadmap specification or reconciliation procedure into every repository.

Rollout protocol

1. Observe current roadmap and agent-hook state across the fleet.
2. Produce a no-write adoption/drift plan.
3. Pilot on Aether, Hygiene, Observatory, Relay, Pace, and at least two materially different consumer repositories.
4. Validate that ordinary no-roadmap-impact PRs remain low-friction.
5. Validate that roadmap-changing PRs update the canonical roadmap/evidence correctly.
6. Validate that read-only agents can suggest but not mutate roadmap state.
7. Roll out in bounded repository-sized PRs or explicitly reviewed waves.
8. Re-observe after merges and reconcile desired state.
9. Keep enforcement advisory until adoption/freshness evidence supports ratcheting.

Organization-roadmap signals

When a repository PR emits an organization-roadmap impact signal from Aether #88:

• collect/observe it as evidence;
• surface it to the owning organization-roadmap review process;
• do not let the local repository automatically rewrite organization strategy;
• preserve pending/reviewed/accepted/rejected disposition.

Validation

Prove at least:

• one feature PR completing a roadmap node;
• one maintenance PR correctly reporting no roadmap impact;
• one blocked/stale roadmap case;
• one cross-repository/organization initiative signal;
• one provider projection upgrade;
• one legacy/custom roadmap migration;
• one private/inaccessible repository state;
• deterministic re-planning on unchanged inputs.

Acceptance criteria

• A fresh fleet observation inventories roadmap and roadmap-hook adoption.
• Desired state pins the canonical Aether capability/version.
• No-write planning distinguishes current, missing, drifted, stale, incompatible, blocked, exempt, and migration states.
• Repo-changing agents receive the shared roadmap-impact completion behavior without copied policy drift.
• Ordinary PRs can explicitly report no roadmap impact without unnecessary roadmap edits.
• Strategic roadmap changes remain human-governed.
• Read-only agents cannot mutate roadmap state through rollout.
• Organization-roadmap impact signals are observable without granting local repos organization-strategy write authority.
• Provider projections remain generated from canonical Aether source.
• Repository rollout remains reviewable and reversible.
• Repeated planning on unchanged evidence is deterministic.
• Advisory adoption is supported before organization-wide enforcement.

Related

• egohygiene/aether#88 — roadmap-impact completion hook
• egohygiene/hygiene#60 — organization roadmap
• egohygiene/observatory#22 — roadmap read model
• 🧭 Establish a dependency-aware portfolio map and focus queue #25 — portfolio map/focus queue
• Roll out repository continuity handoffs across the Ego Hygiene fleet #26 — continuity rollout pattern
• Roll out the canonical Aether audit capability across the repository fleet #28 — Aether audit capability rollout pattern

Non-goals

• Rewriting all repository roadmaps in one pass.
• Forcing a roadmap edit on every PR.
• Auto-merging roadmap changes.
• Allowing local agents to reprioritize organization strategy.
• Replacing GitHub Issues with roadmap documents.