Add an organization-level /decisions/ lineage and impact view

[szmyty]

Outcome

Add a first-class organization-level /decisions/ module that helps a human architect understand consequential decisions across repositories, their ownership and supersession lineage, and their cross-repository impact.

This is the fleet counterpart to the delivered repository /decisions/ experience in egohygiene/relay#30 and a bounded child of #27 and #30.

Primary question

Which accepted decisions shape the organization now, what superseded them, which repositories are affected, and what requires fresh human review?

Data and ownership

Consume versioned ADR/decision entities and relationships from the completed Observatory Repository Intelligence graph (#7). Canonical ADR prose and status remain in Hygiene or the owning repository. The UI must not infer acceptance from implementation activity.

Required experience

• Recent consequential decisions, pending/review-due decisions, and material supersessions.
• Filters by organization/repository owner, domain, status, date, affected system, and roadmap initiative.
• Decision lineage across organization and repository authority boundaries.
• Explicit authoritative versus inferred impact relationships.
• Cross-repository impact and unresolved conflicts with links to dependencies, roadmap, sanity, audits, and source ADRs.
• Stable deep links and printable/text-friendly summaries.
• Honest missing, stale, incompatible, unavailable, private, and partial-adoption states.

Acceptance criteria

• A canonical organization /decisions/ surface is registered through egohygiene/hygiene#25.
• The module consumes the versioned ADR and Repository Intelligence contracts rather than scraping Markdown in the browser.
• Organization and repository decision authority remain distinct.
• Supersession/history remains visible and unambiguous.
• Cross-repository impact distinguishes authoritative and inferred relationships.
• No merge, commit, or continued development is presented as decision ratification.
• Every item preserves canonical source, represented revision, provenance, freshness, and affected-scope links.
• Public output cannot leak private ADRs, repositories, counts, or impact metadata.
• Current, superseded, proposed, stale, conflicting, inaccessible, and partial-adoption fixtures pass.
• Mobile, keyboard, screen-reader, reduced-motion, no-color-only, and long-history behavior is verified.

Dependencies / related

• Parent shell: Evolve Organization Intelligence into a modular fleet control plane #27
• Master epic: [EPIC] Finish Repository Intelligence, Organization Intelligence, and site control-plane surfaces #30
• ADR standard: Define the global Architecture Decision Record standard and inheritance contract hygiene#15
• Repository Intelligence provenance contract: Define the Repository Intelligence event and provenance contract hygiene#19
• Normalized graph: Build the normalized Repository Intelligence graph and query snapshots observatory#7
• Repository view: Render ADR history as a decision ledger at /decisions/ relay#30
• Fleet ADR rollout: [Capability 1] Roll out and reconcile the ADR baseline and Decisions views across the fleet pace#5

Non-goals

• Editing or approving ADRs from the dashboard.
• Inventing decision impact without evidence.
• Replacing repository decision ledgers.
• Treating activity as approval.