Skip to content

[EPIC] Finish Repository Intelligence, Organization Intelligence, and site control-plane surfaces #30

Open
Open
[EPIC] Finish Repository Intelligence, Organization Intelligence, and site control-plane surfaces#30

Description

@szmyty
szmyty
opened on Sep 16, 2026

Priority update — 2026-09-26: The maintainer selected ADRs and /decisions/ first, using egohygiene/pace#5 and the already-created repository ADR issues. Finish the in-progress bounded Relay #112 checkpoint, then continue the shared ADR validation chain in egohygiene/relay#99 / egohygiene/relay#5 and the fleet adoption plan. Populated roadmaps in egohygiene/pace#31 are capability 2. This supersedes the earlier roadmap-first operational ordering below; historical audit observations and acceptance requirements remain intact. The newly confirmed partial-domain read-model gap is tracked by egohygiene/observatory#25.

Repository & Organization Intelligence Completion Epic

Important

Durable continuation point

In a new chat, say: “Continue the Intelligence control-plane roadmap from egohygiene/.github#30, one dependency-ready issue and PR at a time.”

Re-query live issue/PR/default-branch/CI/release state before every branch. Work on one bounded owning issue at a time, open a review PR, and stop for maintainer review. Do not merge review PRs without the maintainer.

Active checkpoint

Live audit: 2026-09-26. egohygiene/pace#13 now contains the public repository-by-repository source, workflow, ADR and live-route inventory. Renderer delivery, connected evidence and verified publication are tracked separately.

Next implementation path

  1. egohygiene/relay#112: collect canonical roadmap evidence through existing pinned contracts.
  2. egohygiene/relay#113: connect generated snapshots to reusable builds.
  3. egohygiene/akashic#197: prove the first populated live roadmap.
  4. egohygiene.io #30: prove a central-mode repository, then finish the campaign's applicability matrix.

The existing ADR chain remains the proposed next capability: egohygiene/relay#5 / egohygiene/relay#99 → egohygiene/pace#5 → existing per-repository backfills. egohygiene/hygiene#15 is already ratified and egohygiene/holon#6 is delivered. egohygiene/empathy#98 separately captures the observed Health report-revision mismatch.

Execution boundary

Finish source, evidence, renderer, declared delivery and ongoing refresh for each applicable repository in one capability before switching lanes. Central, composed, artifact-only and disabled profiles remain distinct; an absent page is not an automatic reason to create another deployer.

This changes the operational work sequence requested by the maintainer, not canonical strategic ownership or the acceptance criteria below. Product features remain outside this focus. Missing Observatory input is not evidence of a billing failure. Local-first implementation can progress without waiting on hosted CI, while publication claims retain their actual evidence requirements.

egohygiene/pace#25 holds the focus projection. egohygiene/hygiene#43 retains the broader foundation program.

Outcome

Finish a polished, deterministic, accessible, privacy-safe visual control plane spanning:

  1. reusable Repository Intelligence for each eligible repository;
  2. public Organization Intelligence at egohygiene.io;
  3. related site/control-plane surfaces such as /status/, /roadmap/, /sanity/, /hygiene/, /audits/, /decisions/, /dependencies/, /releases/, /distribution/, /health/, and /identity/;
  4. normalized Observatory snapshots and canonical Hygiene/Aether contracts;
  5. reviewable canary and fleet adoption through Pace;
  6. final cross-route polish, live publication, release evidence, and parent-issue closure.

The finish line is a polished v1 control plane, not “every future metric and idea implemented forever.”

Definition of done

The program is complete when:

  • every route has one primary human question, canonical owner, versioned data source, and evidence drill-down;
  • canonical repository/org sources remain authoritative and dashboards remain derived projections;
  • repository and organization experiences share a coherent information architecture and visual grammar;
  • unknown, stale, partial, blocked, unavailable, unsupported, incompatible, exempt, redacted/private, and not-applicable states remain explicit;
  • no universal score hides independent evidence domains;
  • public output cannot leak private repository/service existence, counts, identifiers, routes, findings, dependencies, or inferred gaps;
  • one malformed/unavailable repository or module cannot break unrelated views;
  • mobile, keyboard, screen-reader, reduced-motion, high-contrast, no-color-only, zoom, and text-equivalent behavior is verified;
  • deterministic fixture, visual-regression, performance, failure-isolation, link, privacy, preview, deployment, provenance, rollback, and upgrade tests pass;
  • one small, one large/active, and one partially adopted public repository prove Repository Intelligence;
  • a mixed organization snapshot proves public Organization Intelligence and partial failure;
  • every issue below is completed, superseded, or explicitly assigned to a named post-v1 milestone with rationale;
  • stable Repository Intelligence and Organization Intelligence releases are smoke-tested from clean environments.

System boundary

flowchart TD
    A["Canonical repository and organization sources"] --> B["Hygiene and Aether contracts"]
    B --> C["Relay, Egolint, and specialist evidence"]
    C --> D["Observatory normalized snapshots"]
    D --> E["Repository Intelligence"]
    D --> F["Organization Intelligence and site surfaces"]
    E --> G["Pace canaries and fleet rollout"]
    F --> G
Loading

Canonical ownership

Owner Responsibility
Hygiene policy, applicability, inheritance, route registry, state semantics
Aether reusable review/audit/agent specifications and completion hooks
Egolint / Relay / specialists validation, collection, generation, workflow evidence
Reflector local-first resumable audit execution/orchestration
Observatory read-only normalization, provenance, freshness, fleet snapshots
Relay reusable repository-level presentation/build/publication
Holon reusable presentation primitives/blueprints when extraction is justified
Pace human-reviewed adoption, canaries, drift, convergence
.github issues organization-level product/module specifications and program coordination
egohygiene.io public Organization Intelligence implementation, composition, hosting, deployment

Live truth: delivered foundation

These pieces are already delivered and should not be reimplemented:

Contracts and normalized core

  • hygiene#15 — ADR standard/inheritance contract.
  • hygiene#19 — Repository Intelligence event/provenance contract.
  • aether#49 — decision-impact/ADR authoring hook.
  • egolint#24 — ADR/roadmap/Intelligence linkage validation.
  • observatory#7 — normalized Repository Intelligence graph/read model.
  • holon#22 — reusable Repository Intelligence visualization components.

Repository routes

Organization design checkpoint

  • .github PR #31 — versioned organization-roadmap visual reference and continuity checkpoint.

Route completion matrix

Delivered below means shared renderer delivery. It does not establish connected production inputs or fleet publication. Use the egohygiene/pace#13 live audit for those independent states and egohygiene/pace#31 for the roadmap capability campaign.

Surface Repository-level owner/state Organization-level owner/state Contract/read-model dependency
/intelligence/ egohygiene/relay#27, #33 — open parents .github#15, #27, egohygiene.io#27 egohygiene/hygiene#19; egohygiene/observatory#7 / egohygiene/observatory#17
/now/ egohygiene/relay#28 — delivered Organization overview in .github#27 egohygiene/observatory#7; egohygiene/pace#25
/roadmap/ egohygiene/relay#31 — delivered .github#29 — open egohygiene/hygiene#60, egohygiene/aether#88, egohygiene/observatory#22, egohygiene/pace#29
/decisions/ egohygiene/relay#30 — delivered .github#36 — created egohygiene/hygiene#15 / egohygiene/hygiene#19; egohygiene/observatory#7
/journey/ egohygiene/relay#32 — delivered No separate v1 organization route; linked from repository detail egohygiene/observatory#7
/dependencies/ egohygiene/relay#77 — delivered .github#38 — created egohygiene/observatory#7; egohygiene/pace#25
/work/ egohygiene/relay#79 — delivered Composed into Now/Roadmap; no duplicate v1 route required egohygiene/observatory#7 / egohygiene/observatory#22
/releases/ egohygiene/relay#81 — delivered .github#39 — created egohygiene/observatory#13
/distribution/ Repository release/detail cross-link .github#39 — created egohygiene/observatory#13; egohygiene/relay#48; egohygiene/pace#17 / egohygiene/pace#19
/search/ egohygiene/relay#83 — delivered Directory/search baseline in .github#15 egohygiene/observatory#7 / egohygiene/observatory#17
/compare/ egohygiene/relay#86 — delivered Module-local comparison in v1; no duplicate global route required Observatory domain snapshots
/health/ egohygiene/relay#88 — delivered .github#40 — created Observatory domain summaries
/diagnostics/ egohygiene/relay#57 — open No separate v1 fleet route; may surface through Health/search egohygiene/observatory#16; egohygiene/pace#23
/audits/ egohygiene/relay#74 — open .github#35 — created egohygiene/aether#86; egohygiene/reflector#258; egohygiene/observatory#20; egohygiene/pace#28
/hygiene/ egohygiene/relay#75 — open .github#34 — created egohygiene/observatory#5
/sanity/ egohygiene/relay#76 — open .github#28 — open egohygiene/hygiene#59; egohygiene/aether#87; egohygiene/observatory#21
/status/ egohygiene/relay#41 — open .github#33 — created egohygiene/hygiene#62; egohygiene/observatory#23; egohygiene/pace#15
/identity/ Canonical repository Identity surfaces .github#37 — created egohygiene/observatory#5; Identity
Codebase overview/booklet egohygiene/relay#42 — open Repository drill-down only egohygiene/observatory#7; Renderflow

Program dependency waves

These waves preserve the full program's dependencies and acceptance inventory. The active checkpoint above selects the current capability-first execution sequence. Only genuine prerequisites block its bounded work; unrelated later domains do not need implementation before the roadmap collector.

Wave 0 — Reconcile live truth and freeze route ownership

  1. hygiene#25 is closed: canonical surface IDs, routes, aliases, applicability, owners, visibility, publication state, and evidence URLs.
  2. relay#29 is closed with supporting-view reconciliation. Matched-field Search attribution remains separately tracked in Add field-attributed Repository Intelligence search evidence observatory#24 and Render field-attributed matches in Repository Intelligence Search relay#102.
  3. Documentation reconciliation in Relay PR #110 is merged. Parent closure still requires owning acceptance work; current data/adoption evidence is in Roll out the Repository Intelligence profile across eligible repositories pace#13.
  4. Reconcile the live repository catalog/freshness path through hygiene#36 so Organization Intelligence does not begin from a stale fleet inventory.
  5. Keep this epic's active checkpoint and checkboxes current after every merged/dispositioned issue.

Exit: one canonical route vocabulary, current parent checklists, and no already-delivered route represented as unimplemented.

Wave 1 — Stabilize domain contracts and normalized snapshots

Execute each dependency chain in order; independent chains may proceed in parallel.

Hygiene conformance

  1. Complete observatory#5: normalized fleet conformance snapshot.
  2. Pin the schema/version consumed by Add a contract-first /hygiene/ view to Repository Intelligence relay#75 and Add an organization-level /hygiene/ contract-conformance view #34.

Audit system

  1. Complete aether#86: composable audit profiles and mature repository-audit skill.
  2. Complete observatory#20: normalized audit runs/findings/fleet posture.
  3. Keep reflector#258 compatible with the accepted profile/evidence contract.

Architecture coherence / Sanity

  1. Complete hygiene#59: review applicability and human-ratification policy.
  2. Complete aether#87: architecture-coherence reviewer/challenger skill.
  3. Complete observatory#21: normalized review + ratification posture.

Organization roadmap

  1. Complete hygiene#60: canonical organization roadmap and repository inheritance contract.
  2. Complete aether#88: roadmap-impact reconciliation completion hook.
  3. Complete observatory#22: normalized organization-roadmap/cross-repository initiative graph.

System Status

  1. Complete hygiene#62: canonical System Status and incident contract.
  2. Complete observatory#23: repository/fleet status and incident read model.

Additional normalized domains

  1. Complete observatory#16: diagnosis-record model.
  2. Complete observatory#13: release/distribution/installability model.
  3. Complete observatory#17: organization namespaces, public/private boundaries, and portable multi-organization read models.

Exit: accepted schemas, hostile/partial/privacy fixtures, compatibility policy, provenance/freshness semantics, and explicit unknown/unavailable states for every v1 module.

Wave 2 — Finish and release Repository Intelligence

  1. Complete relay#33 through #106: #104/#105 and [Relay #33.3] Prove Repository Intelligence publication in Akashic akashic#185/[Relay #33.4] Prove Repository Intelligence publication in Empathy empathy#94 are closed; final current cross-repository acceptance remains. The #109 implementation is merged via PR #111; reconcile its remaining acceptance and review affected consumer upgrades before broad adoption.
  2. Complete relay#41: reusable status/incident workflow against Define the canonical System Status and incident-communication contract hygiene#62 and Normalize service-status and incident evidence for repository and fleet views observatory#23.
  3. Complete relay#75: repository /hygiene/.
  4. Complete relay#74: repository /audits/.
  5. Complete relay#76: repository /sanity/.
  6. Complete relay#57: repository /diagnostics/.
  7. Complete relay#42: evidence-linked codebase overview and accessible architecture booklet.
  8. Complete relay#101: cross-route UX/accessibility/performance/privacy/failure-isolation polish, clean consumer canaries, documentation, parent reconciliation, and stable release.
  9. Close or explicitly disposition Build the Repository Intelligence experience relay#27 / Add supporting intelligence views for dependencies, health, releases, work, search, and compare relay#29 / Publish deterministic Repository Intelligence through reusable GitHub Actions relay#33 from inspectable acceptance evidence.

Exit: a stable Repository Intelligence release works across small, large/active, and partially adopted public consumers without clobbering consumer-owned Pages content.

Wave 3 — Prove the continuous review and planning loop

  1. Complete reflector#258: resumable repository/fleet audit orchestration.
  2. Complete pace#28: canary and fleet rollout of the canonical audit capability.
  3. Complete pace#23: optional diagnosis-record pilots.
  4. Complete pace#25: human-reviewed dependency-aware portfolio/focus projection.
  5. Complete pace#29: continuous roadmap reconciliation rollout.
  6. Run the first bounded organization audit campaign described by hygiene#58; deduplicate and human-review candidate issues before materialization.

Exit: the dashboards are fed by a repeatable observe → audit → review → issue → validate → reobserve loop, not one-time fixture data.

Wave 4 — Establish the public Organization Intelligence host and shell

  1. Resolve the external hosting/DNS gate in .github#2 if it is still live.
  2. Complete the applicable static-prerender/content-route foundation in egohygiene.io#22.
  3. Start egohygiene.io#27: record the ownership/route/snapshot/privacy ADR and build the shared shell against deterministic fixtures.
  4. Complete .github#15: baseline /intelligence/ repository directory/summary/failure-isolation behavior.
  5. Complete .github#27: modular Now/control-plane shell and common module API.
  6. Keep egohygiene.io#20 compatible with this work; the broader Holon rematerialization may proceed independently and must not force a dashboard rewrite.

Exit: one deployed/prerendered shell can add modules without redesign, uses no browser credential or live authenticated scraping, and fails partially rather than globally.

Wave 5 — Add Organization Intelligence modules

Implement one route issue and review PR at a time.

  1. .github#38 — /dependencies/ impact and ownership.
  2. .github#36 — /decisions/ lineage and impact.
  3. .github#29 — /roadmap/ organization quest-line.
  4. .github#37 — /identity/ adoption and safe asset discovery.
  5. .github#34 — /hygiene/ conformance.
  6. .github#35 — /audits/ evidence/findings.
  7. .github#28 — /sanity/ architecture alignment after dependencies, decisions, and review evidence exist.
  8. .github#39 — /releases/ and /distribution/.
  9. .github#33 — /status/ and incident directory.
  10. .github#40 — /health/ last, because it composes and links the specialized operational domains rather than replacing them.

Exit: each module has one distinct question, normalized input, shared shell behavior, fixtures, privacy/failure isolation, accessibility, and canonical drill-down.

Wave 6 — Canary and fleet adoption

  1. Complete pace#13: Repository Intelligence eligibility, small/large/partial canaries, existing-Pages preservation, upgrade/rollback, and fleet reconciliation.
  2. Complete pace#15: truthful /status/ applicability and rollout.
  3. Complete pace#17 and pace#19 for release/distribution observation and applicable rollout.
  4. Complete the relevant rollout evidence in Pilot optional diagnosis records across the repository fleet pace#23 / Roll out the canonical Aether audit capability across the repository fleet pace#28 / Roll out continuous roadmap reconciliation across the repository fleet pace#29.
  5. Prove organization aggregation with unavailable, stale, incompatible, and private/redacted inputs.
  6. Verify every adopted repository links back into Organization Intelligence and every fleet item drills down to canonical repository evidence.

Exit: rollout state is explicit for every eligible repository; exclusions, exemptions, blockers, versions, drift, upgrades, and rollback paths are inspectable.

Wave 7 — Final integrated acceptance and stable release

  1. Complete .github#41: cross-module coherence, privacy non-disclosure, failure isolation, accessibility, performance, visual regression, live canaries, deployment provenance, rollback, recovery, and stable public release.
  2. Reconcile Roadmap: make audits, hygiene, and organization intelligence a continuous control loop hygiene#58's continuous-control-loop acceptance criteria.
  3. Reconcile and close/supersede .github#15, Evolve Organization Intelligence into a modular fleet control plane #27, and this epic from live evidence.
  4. Move remaining optional experiments to named post-v1 issues/milestones with rationale.
  5. Record the final release versions, represented source revisions, live routes, smoke-test evidence, residual risks, and rollback points.

Work inventory by owner

Policy / source contracts

Agent/review capability and execution

Normalized read models

Repository product

Organization product and host

Rollout / focus

Execution protocol

  1. Re-query the owning issue, dependencies, default branch, open PRs, CI, releases, repository instructions, and external gates.
  2. Within the active capability campaign, select its next dependency-ready owning checkpoint. Use the program waves to verify real prerequisites rather than switching to another capability simply because it appears earlier in the inventory.
  3. Work in the canonical owning repository on one bounded issue/checkpoint.
  4. Preserve versioned contracts and source-of-truth boundaries. Synthetic fixtures validate failure/compatibility behavior; real source, connected evidence and publication are required to close a consumer adoption row.
  5. Validate determinism, compatibility, privacy, failure states, accessibility, and the issue-specific acceptance criteria.
  6. Open a small review PR linked to the owning issue and this epic; do not merge it.
  7. After maintainer disposition/merge, update this epic's checkbox, evidence, active checkpoint, and next dependency-ready item.
  8. If live evidence invalidates the order, update this epic explicitly before changing course.
  9. Do not create a second tracker for this program; extend/supersede this issue deliberately.

Non-goals

  • One mega-PR across repositories.
  • Moving canonical roadmaps, ADRs, reports, incidents, or release truth into a dashboard database.
  • Replacing GitHub Issues/PRs as the execution/review layer.
  • A universal repository or organization score.
  • Browser-side authenticated GitHub scraping.
  • Public leakage of private fleet topology or evidence.
  • Automatic mutation/merging from public Intelligence pages.
  • Blocking all product work until every repository adopts every contract.

September 28 — Progress achievement page captured

The maintainer requested a Steam-style repository achievement page with milestone unlocks, completion meters, and goals for clearing open issues. Feature parent: egohygiene/relay#130.

The ordered checkpoints are egohygiene/hygiene#66 (Hygiene rules/route), egohygiene/observatory#26 (Observatory evidence/history), egohygiene/relay#131 (Relay page), and egohygiene/relay#132 (read-only collection and consumer handoff). This adds a feature lane without superseding the existing ADR-first priority or taking over concurrent implementation.

Reuse Observatory #25 for complete versus uncollected/partial domains. Earned achievements and live backlog metrics remain separate; empty query results cannot establish that every issue is cleared. First real adoption is coordinated through Pace #13 after the data/page producers are ready. This update records requirements, not an implemented or live page.

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