Skip to content

Build an organization-level Intelligence portal at egohygiene.io/intelligence/ #15

Description

@szmyty

Goal

Create a public organization-level Intelligence portal at:

https://egohygiene.io/intelligence/

It should aggregate each repository's published Intelligence summary from https://<repo>.egohygiene.io/intelligence/summary.json, provide an organization-wide directory/status view, and link into each repository's full dashboard.

Proven foundation

Requirements

  • Maintain a checked-in manifest of public repository names, dashboard URLs, and summary URLs.
  • Fetch public summaries over HTTPS without a GitHub API request, browser token, secret, backend, or database.
  • Validate the supported schema/version before presenting a summary as available.
  • Show unavailable, invalid, unreachable, and stale repositories explicitly; missing data must never appear healthy.
  • Preserve availability, freshness, execution, and findings as separate dimensions rather than inventing a single organization-wide health score.
  • Isolate failures so one repository cannot prevent the rest of the portal from loading.
  • Link every result to its repository dashboard and represented source commit when available.
  • Provide responsive, keyboard-accessible search and filters for repository and status dimensions.
  • Treat fetched JSON as untrusted: render text safely and allowlist navigable URLs.
  • Keep the portal dependency-light, telemetry-free, and usable on mobile.

Acceptance criteria

  • egohygiene.io/intelligence/ loads Akashic and Optiflow as the first live canaries.
  • Each repository card shows identity, represented commit, generated time, availability, and freshness.
  • Missing or malformed summaries render readable unavailable/invalid states.
  • Stale data remains visible and clearly labeled.
  • Search and filters work with keyboard and assistive technology.
  • The browser receives no token and makes no authenticated GitHub requests.
  • The portal remains functional when one or more repository endpoints fail.
  • Documentation explains how to add another repository to the manifest.

Dependencies

  • Publish the main egohygiene.io site and its /intelligence/ route.
  • Complete repository subdomain/CNAME rollout.
  • Verify cross-origin reads from the repository subdomains. If Pages does not expose suitable CORS headers, use a public static aggregation build without introducing browser credentials.
  • Decide which root-site repository owns the implementation and manifest.

Out of scope

  • Private repository data or authenticated dashboards.
  • Browser-side GitHub organization discovery.
  • Server-side APIs, databases, telemetry, tracking, or user accounts.
  • Replacing repository-level Intelligence dashboards.
  • Automatic Relay installation/upgrades across repositories.
  • A synthetic organization-wide health score.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions