Evolve Organization Intelligence into a modular fleet control plane

[szmyty]

Outcome

Evolve the organization-level Intelligence portal from a directory/summary aggregator into a low-cognitive-load fleet control plane that composes the same normalized evidence used by repository-level Repository Intelligence.

The portal should let an organization architect answer "where are we?" without opening 29 repository dashboards, while always preserving drill-down to the canonical repository evidence.

This is a follow-up/expansion of #15, not a replacement for repository-level Intelligence.

Product principle

canonical repository + GitHub evidence
        ↓
normalized Observatory snapshots
        ↓
repository-level Relay Intelligence
        +
organization-level Intelligence projection

The organization UI is a projection. It must never become a second source of truth.

Initial organization views

Provide modular organization-level views/tabs that aggregate safe repository summaries for domains such as:

• Now — active work, blockers, stale repositories, next ready actions;
• Roadmap — portfolio/quest-line view across repository roadmaps;
• Decisions — ADR/decision posture and recent significant decisions;
• Identity — Brand Kit/identity adoption and links to repository identity surfaces;
• Hygiene — contract applicability/conformance from egohygiene/observatory#5;
• Audits — audit coverage/findings posture from egohygiene/observatory#20;
• Health — broad operational evidence without collapsing domains into one score;
• Releases / Distribution — release and installability posture where applicable;
• Dependencies — cross-repository dependency graph/impact;
• Repositories — searchable fleet directory with lifecycle/class/profile.

The exact navigation should reuse the Repository Intelligence information architecture where practical rather than creating a second incompatible vocabulary.

Progressive disclosure

Optimize the default experience for quick architectural orientation:

1. compact organization overview;
2. exceptions/blockers/stale evidence;
3. repositories needing attention;
4. domain summaries;
5. drill-down into repository Intelligence;
6. direct source/evidence links when deeper inspection is needed.

Do not place every metric on one giant dashboard.

Aggregation semantics

For every organization-level object preserve:

• source organization/repository;
• represented revision;
• snapshot/generated time;
• freshness;
• state/uncertainty;
• source module/contract version;
• deep link to repository-level view;
• deep link to canonical evidence when authorized.

Unknown, unavailable, stale, partial, blocked, exempt, and not-applicable must remain distinct.

Audits

The organization audit view should support:

• latest audit coverage by repository/profile;
• unaudited/stale/partial repositories;
• confirmed findings by severity/classification;
• feature opportunities and experimental opportunities as separate categories;
• recurring cross-repository patterns;
• organization audit campaigns/runs;
• candidate issue materialization status.

Do not turn speculative ideas into organization-health failures.

Hygiene

The organization Hygiene view should reuse Observatory #5 and allow:

• rows/columns by repository and contract domain;
• filters by repository class/profile/lifecycle;
• explicit migration/advisory states;
• deep links to repository /hygiene/;
• prioritization by missing/stale/blocked evidence without pretending every contract applies everywhere.

Identity / decisions / other modules

Aggregate summary metadata only. Detailed Brand Kits, ADR prose, audit reports, roadmaps, etc. remain owned by the repository or their canonical semantic owner.

The portal should answer "which repository needs attention and why?" and then link out instead of copying every source document into one mega-store.

Data-source evolution

#15 initially permits fetching repository summary.json endpoints. Preserve that simple public path where useful, but allow the mature implementation to consume a deterministic organization snapshot produced by Observatory/Relay when that avoids N browser requests, CORS fragility, or inconsistent schema versions.

No browser token, authenticated GitHub scraping, database, or hosted backend is required for the static public implementation.

Privacy

• Public portal output must not reveal private repository existence, counts, names, issues, paths, findings, or inferred gaps.
• Private/local organization projections may compose authorized private snapshots separately.
• Visibility classification is enforced before aggregation, not merely hidden with CSS.

Acceptance criteria

• Build an organization-level Intelligence portal at egohygiene.io/intelligence/ #15's repository directory/summary behavior remains supported.
• The portal has a modular information architecture aligned with Repository Intelligence.
• Hygiene and Audits organization views consume Observatory snapshots rather than reimplementing collection/policy.
• Identity, decisions, roadmaps, releases, distribution, dependencies, and health can be added as independent modules without redesigning the shell.
• Default view emphasizes exceptions, blockers, freshness, and next attention rather than vanity metrics.
• Every aggregate item preserves represented revision/provenance/freshness and deep-links to repository detail.
• Unknown/stale/partial/blocked/exempt/not-applicable states remain explicit.
• Public output cannot leak private repository existence or metadata.
• One broken/unavailable repository/module cannot break the entire portal.
• Responsive, keyboard, screen-reader, and reduced-motion behavior is verified.
• The architecture supports an offline/local private build from precomputed snapshots.

Dependencies / related

• Existing organization Intelligence portal: Build an organization-level Intelligence portal at egohygiene.io/intelligence/ #15
• Repository Intelligence: egohygiene/relay#27
• Hygiene fleet conformance: egohygiene/observatory#5
• Audit fleet read model: egohygiene/observatory#20
• Repository /audits/: egohygiene/relay#74
• Repository /hygiene/: egohygiene/relay#75
• Portable organization snapshots: egohygiene/observatory#17

Non-goals

• Replacing repository-level Intelligence.
• Centralizing canonical Markdown/ADRs/audit prose.
• Creating one opaque organization health score.
• Adding a hosted multi-tenant backend.
• Mutating repositories from the dashboard.

[szmyty]

Dedicated visualization children / tracker

The modular Organization Intelligence program now has explicit follow-up surfaces:

• Add an organization-level /sanity/ architecture alignment view #28 — organization /sanity/ architecture alignment
• Add an organization-level /roadmap/ quest-line to Organization Intelligence #29 — organization /roadmap/ quest-line / portfolio roadmap
• Roadmap: complete the Repository Intelligence and Organization Intelligence visual control plane #30 — visual-control-plane implementation roadmap spanning repository + organization Intelligence

The organization roadmap consumes egohygiene/hygiene#60 through egohygiene/observatory#22 and reuses the already-delivered repository /roadmap/ renderer from egohygiene/relay#31.

Use #30 as the dashboard-focused execution tracker; keep #27 as the architectural shell/aggregation parent.