[Acceptance] Complete Organization Intelligence integration and release proof

[szmyty]

Outcome

Complete the cross-module integration, public/private safety proof, resilience testing, live canaries, documentation, and release closeout needed to call Organization Intelligence a polished finished control plane.

This is the final organization-level acceptance gate under #27 and the master epic #30. Route-specific features remain in their owning issues; this issue begins only when those modules are implementation-complete or explicitly dispositioned.

Entry criteria

Resolve or explicitly disposition:

• Build an organization-level Intelligence portal at egohygiene.io/intelligence/ #15 — baseline /intelligence/ portal;
• Evolve Organization Intelligence into a modular fleet control plane #27 — modular fleet-control-plane shell;
• Add an organization-level /sanity/ architecture alignment view #28 — /sanity/;
• Add an organization-level /roadmap/ quest-line to Organization Intelligence #29 — /roadmap/;
• Add an organization-level /status/ view and incident directory #33 — /status/;
• Add an organization-level /hygiene/ contract-conformance view #34 — /hygiene/;
• Add an organization-level /audits/ evidence and findings view #35 — /audits/;
• Add an organization-level /decisions/ lineage and impact view #36 — /decisions/;
• Add an organization-level /identity/ adoption and asset-discovery view #37 — /identity/;
• Add an organization-level /dependencies/ impact and ownership view #38 — /dependencies/;
• Add organization-level /releases/ and /distribution/ views #39 — /releases/ and /distribution/;
• Add an organization-level /health/ operational-evidence view #40 — /health/;
• egohygiene/egohygiene.io#27 — implementation/hosting parent;
• egohygiene/relay#101 — polished repository-level drill-down and publication.

Scope

Coherent product

• One organization navigation model, route registry, visual grammar, state vocabulary, filter conventions, evidence drawer, provenance/freshness treatment, and responsive layout.
• Compact default orientation emphasizing Now, blockers, human decisions, stale/unknown evidence, and next attention.
• Stable cross-links among organization modules, repository Intelligence routes, canonical sources, and GitHub execution evidence.
• Preserve route/filter/selected-entity context where useful.
• Ensure each module answers one distinct primary question.

Public/private safety

• Visibility filtering before aggregation.
• Prove that public outputs cannot reveal private repository names, counts, identifiers, routes, issues, findings, dependencies, services, releases, or inferred gaps.
• Prove separately authorized offline/local private builds.
• Treat snapshot text as untrusted and allowlist navigable URLs.
• Document threat model, redaction, and review boundaries.

Failure isolation and freshness

• One malformed, incompatible, stale, unreachable, or unavailable repository/module must not break the rest of the portal.
• Last-known context remains visibly stale/provider-unavailable.
• Snapshot and module schema compatibility errors are actionable.
• Unknown, stale, partial, blocked, unavailable, incompatible, exempt, redacted, and not-applicable remain explicit.

Accessibility, performance, and visual quality

• Mobile/desktop layouts, keyboard navigation, screen readers, focus management, reduced motion, high contrast, no color-only state, zoom, and text equivalents.
• Performance budgets for initial load, large fleet snapshots, graphs, matrices, search, and route transitions.
• Visual regression fixtures for clean, large, stale, partially adopted, incident-active, finding-heavy, private/redacted, incompatible, and multi-failure states.
• Direct navigation, refresh, canonical URLs, aliases, sitemap, search index, print, and low/no-JavaScript behavior where promised.

Live proof and operations

• Prove at least one small, one large/active, and one partially adopted public repository.
• Prove a mixed organization snapshot with unavailable/stale modules.
• Verify canonical egohygiene.io hosting, HTTPS, navigation, deployment provenance, rollback, and degraded/static fallback.
• Verify preview/review artifacts and production deployment use the exact reviewed source state.
• Document adding/removing a repository, upgrading schema/generator versions, restoring a failed build, and rolling back a publication.

Closeout

• Reconcile every parent/child checklist and cross-repository dependency against live evidence.
• Reconcile site navigation, README/architecture/roadmap/continuity, route registry, screenshots, public claims, and operator runbooks.
• Publish a reviewed release candidate/private preview as appropriate, perform clean smoke tests, then publish the stable public version.
• Route remaining optional ideas to named post-v1 issues; do not keep the program open for an undefined perfect-forever standard.

Acceptance criteria

• Every route/module has one documented primary question, owner, canonical data source, and drill-down path.
• Repository and organization Intelligence use one coherent information/visual grammar.
• Public/private non-disclosure tests cover direct fields, counts, errors, links, search indexes, maps, and inferred gaps.
• One or multiple unavailable/malformed/stale modules fail independently.
• All human-governed states remain explicit and cannot be inferred from activity.
• Complete mobile, keyboard, screen-reader, reduced-motion, high-contrast, zoom, text-equivalent, and no-color-only verification passes.
• Performance, large-fleet, visual-regression, direct-navigation, canonical URL, and low/no-JavaScript checks pass where promised.
• Small, large/active, partially adopted, mixed-failure, and privacy-boundary canaries pass.
• Deployment provenance, preview, publication, rollback, schema upgrade, and recovery paths are proven and documented.
• Canonical route registry, site navigation, docs, screenshots, public claims, and live output agree.
• Every issue in [EPIC] Finish Repository Intelligence, Organization Intelligence, and site control-plane surfaces #30 is completed, superseded, or explicitly assigned to a named post-v1 milestone with rationale.
• A stable public Organization Intelligence release is smoke-tested from clean browsers/devices.
• Build an organization-level Intelligence portal at egohygiene.io/intelligence/ #15, Evolve Organization Intelligence into a modular fleet control plane #27, and [EPIC] Finish Repository Intelligence, Organization Intelligence, and site control-plane surfaces #30 can close on inspectable evidence.

Dependencies / related

• Master epic: [EPIC] Finish Repository Intelligence, Organization Intelligence, and site control-plane surfaces #30
• Site implementation parent: Implement and host the Organization Intelligence control plane egohygiene.io#27
• Repository Intelligence polish: [Polish] Complete Repository Intelligence integration and release acceptance relay#101
• Route registry: Define the canonical public-site surface and route registry hygiene#25
• Portable organization/privacy model: Add organization namespaces and portable multi-organization read models observatory#17
• Repository rollout: Roll out the Repository Intelligence profile across eligible repositories pace#13

Non-goals

• Implementing every route inside this issue.
• Replacing canonical evidence or GitHub execution.
• Requiring every repository to reach full conformance before the portal can release.
• A universal organization score.
• An authenticated mutation console.