[PR #5042] feat(example): add editable Civic Atlas graph #6754

Open
opened 2026-11-01 21:42:48 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5042
Author: @ScarednAlone
Created: 10/18/2026
Status: 🔄 Open

Base: main ← Head: scarednalone-civlab-graph-recreation


📝 Commits (1)

  • 891147d feat(example): add editable Civic Atlas graph

📊 Changes

4 files changed (+1648 additions, -0 deletions)

View changed files

➕ examples/civlab-graph/README.md (+22 -0)
➕ examples/civlab-graph/app.js (+1024 -0)
➕ examples/civlab-graph/index.html (+293 -0)
➕ examples/civlab-graph/styles.css (+309 -0)

📄 Description

Summary

Add a self-contained, locally hostable Civic Atlas example so users can explore and maintain a graph of public institutions without relying on a remote backend. The overview retains the reference site's dashboard patterns while clearly distinguishing its reference totals from the illustrative local records.

Problem and expected behavior

The reference graph is useful as an overview, but this recreation needs to work locally and let users shape its information and structure. Users can browse an overview, graph, directory, and local edit timeline, then add or edit institutions, leadership status, hierarchy, relationships, categories, and relationship types. Edits persist in the browser and can be exported or restored as JSON.

Change and scope

Adds a static HTML/CSS/JavaScript application and local hosting instructions under examples/civlab-graph/. The graph and directory share browser-local workspace state; JSON import is validated before replacing that state. Starter entries are an illustrative subset, the 482 organizations and 339 sub-agencies are reference-site totals, and leadership status is explicitly untracked by default. This example does not integrate a provider, alter REA runtime behavior, or claim to be an authoritative government directory.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Standalone example application; no REA domain or application layer changed.
  • Contribution scope fit and linked maintainer decision: Local static example, not a provider or target-execution capability; maintainer scope decision not applicable.
  • CLI and MCP/tool-catalog contract: None.
  • Provider, bridge, target-format, or platform compatibility: None; static hosting and modern browser APIs (local storage, file input, Blob download).
  • Evidence, artifact, provenance, or reconstruction contract: None.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable; no analysis target is selected or executed.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): None.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: None; this is a standalone static example.
  • Base reproduction or other evidence: Served the app locally and verified the dashboard and graph render; added/edited institution fields and a parent relationship, created a category, added/edited a relationship, reloaded to confirm browser-local persistence, and validated JSON workspace data and export behavior in the browser.
  • User-visible CLI/MCP output (if applicable): Not applicable.
  • Remaining proof gaps: No automated browser test, file-based JSON import round-trip, or authoritative directory/leadership verification. Starter records and leadership are not represented as authoritative.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • node --check examples\civlab-graph\app.js — passed.
  • git diff --check — passed before commit.
  • Local browser verification — dashboard/graph rendering, institution add/edit, category creation, relationship add/edit, persistence after reload, and JSON export validation passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: None.
  • Real Hopper/Ghidra, browser, or OS coverage: Local browser preview only; no real-provider or OS analysis workflow applies.
  • Package or release metadata impact: None; the example is static and has no additional dependencies.
  • Security, privacy, process, or containment review: Workspace state remains in browser local storage; import reads only a user-selected JSON file, and export downloads a JSON backup. No backend or target interaction was added.

Author readiness

Human owner:

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5042 **Author:** [@ScarednAlone](https://github.com/ScarednAlone) **Created:** 10/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `scarednalone-civlab-graph-recreation` --- ### 📝 Commits (1) - [`891147d`](https://github.com/morluto/rea/commit/891147dc386860bb55b2fbefa162ceebf55d5ff3) feat(example): add editable Civic Atlas graph ### 📊 Changes **4 files changed** (+1648 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `examples/civlab-graph/README.md` (+22 -0) ➕ `examples/civlab-graph/app.js` (+1024 -0) ➕ `examples/civlab-graph/index.html` (+293 -0) ➕ `examples/civlab-graph/styles.css` (+309 -0) </details> ### 📄 Description ## Summary Add a self-contained, locally hostable Civic Atlas example so users can explore and maintain a graph of public institutions without relying on a remote backend. The overview retains the reference site's dashboard patterns while clearly distinguishing its reference totals from the illustrative local records. ## Problem and expected behavior The reference graph is useful as an overview, but this recreation needs to work locally and let users shape its information and structure. Users can browse an overview, graph, directory, and local edit timeline, then add or edit institutions, leadership status, hierarchy, relationships, categories, and relationship types. Edits persist in the browser and can be exported or restored as JSON. ## Change and scope Adds a static HTML/CSS/JavaScript application and local hosting instructions under `examples/civlab-graph/`. The graph and directory share browser-local workspace state; JSON import is validated before replacing that state. Starter entries are an illustrative subset, the 482 organizations and 339 sub-agencies are reference-site totals, and leadership status is explicitly untracked by default. This example does not integrate a provider, alter REA runtime behavior, or claim to be an authoritative government directory. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: Standalone example application; no REA domain or application layer changed. - Contribution scope fit and linked maintainer decision: Local static example, not a provider or target-execution capability; maintainer scope decision not applicable. - CLI and MCP/tool-catalog contract: None. - Provider, bridge, target-format, or platform compatibility: None; static hosting and modern browser APIs (local storage, file input, Blob download). - Evidence, artifact, provenance, or reconstruction contract: None. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable; no analysis target is selected or executed. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): None. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: None; this is a standalone static example. - Base reproduction or other evidence: Served the app locally and verified the dashboard and graph render; added/edited institution fields and a parent relationship, created a category, added/edited a relationship, reloaded to confirm browser-local persistence, and validated JSON workspace data and export behavior in the browser. - User-visible CLI/MCP output (if applicable): Not applicable. - Remaining proof gaps: No automated browser test, file-based JSON import round-trip, or authoritative directory/leadership verification. Starter records and leadership are not represented as authoritative. For evidence-bearing changes: - [ ] Observed, derived, and inferred claims remain distinguishable. - [ ] Artifact identity, source provenance, and failed attempts remain preserved. - [ ] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `node --check examples\civlab-graph\app.js` — passed. - `git diff --check` — passed before commit. - Local browser verification — dashboard/graph rendering, institution add/edit, category creation, relationship add/edit, persistence after reload, and JSON export validation passed. ## Compatibility, safety, and release - Breaking changes or migration steps: None. - Real Hopper/Ghidra, browser, or OS coverage: Local browser preview only; no real-provider or OS analysis workflow applies. - Package or release metadata impact: None; the example is static and has no additional dependencies. - Security, privacy, process, or containment review: Workspace state remains in browser local storage; import reads only a user-selected JSON file, and export downloads a JSON backup. No backend or target interaction was added. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: <!-- @GitHub-handle --> - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6754
No description provided.