Add an organization-level /dependencies/ impact and ownership view

[szmyty]

Outcome

Add a first-class organization-level /dependencies/ module that presents evidence-backed cross-repository dependency direction, ownership, versions, drift, and impact paths while keeping conceptual relationships distinct from execution blockers.

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

Primary question

If this repository, package, workflow, or contract changes, what is actually affected, which direction does the dependency run, and what can still proceed independently?

Data and ownership

Consume the completed Observatory Repository Intelligence graph (#7), accepted architecture sources, and the human-reviewed Pace portfolio projection (#25). Do not infer canonical ownership or dependency direction from activity alone.

Required experience

• Repository/system/package/workflow/contract nodes with canonical owner and lifecycle.
• Explicit depends-on, consumes, provides, migrates-from, supersedes, and related-to relationship types.
• Authoritative versus inferred edges, evidence basis, confidence, represented revision, and freshness.
• Direct and transitive impact paths, version drift, blockers, cycles, contradictions, and unknowns.
• Safe parallel lanes visually distinct from blocked work.
• Deep links to repository /dependencies/, roadmap, decisions, releases, source manifests, issues, and evidence.
• Complete text/table alternative for graphs.

Acceptance criteria

• A canonical organization /dependencies/ surface is registered through egohygiene/hygiene#25.
• The module consumes Observatory feat(reflector): bootstrap pass-based organization discovery audit engine #7 and accepted Pace evidence rather than building a second graph.
• True execution dependencies are distinct from conceptual relationships.
• Direction, owner, version, drift, evidence basis, confidence, revision, and freshness are inspectable.
• Cycles, contradictions, missing references, stale inputs, and inferred edges are explicit.
• Impact paths and safe parallel work are navigable.
• Public output cannot leak private repositories or dependency metadata.
• Every node/edge drills down to canonical repository evidence where authorized.
• Small, cyclic, stale, inferred, partial, private/redacted, and large-fleet fixtures pass.
• Mobile, keyboard, screen-reader, reduced-motion, text-equivalent, and large-graph 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
• Normalized graph: Build the normalized Repository Intelligence graph and query snapshots observatory#7
• Repository view: Render dependency impact at /dependencies/ in Repository Intelligence relay#77
• Portfolio/focus projection: 🧭 Establish a dependency-aware portfolio map and focus queue pace#25
• Organization sanity: Add an organization-level /sanity/ architecture alignment view #28
• Organization roadmap: Add an organization-level /roadmap/ quest-line to Organization Intelligence #29

Non-goals

• Making every conceptual relation a blocker.
• Mutating dependencies or repositories from the dashboard.
• Replacing canonical manifests or architecture sources.
• Inferring ownership from commit volume.