backlog: P2 — factory status UI on GitHub Pages (git-native, post-repo-split) by AceHack · Pull Request #172 · Lucent-Financial-Group/Zeta

AceHack · 2026-04-23T17:20:28Z

Summary

Adds a P2 BACKLOG row capturing the human maintainer's 2026-04-23 idea for a static, git-native, GitHub-Pages-hosted factory status UI.

"static ui on our github pages that shows factory status things in flight progress, etc anyting else you can make of to help the human drive we can surface thing in the ui like the decions and any decions we would like human feedback on. All this should be able to use our gitnative approach and not really cost anyting i dont think becasue it can just use git for the backend for the ui. backlog this and probaby not a good idea until after the repo split into the different projects."

Goal

A static UI at the repo's GitHub Pages URL surfacing:

Things in flight (open PRs, their state)
Decisions made (ADRs under docs/DECISIONS/)
Decisions seeking human feedback (HUMAN-BACKLOG Open rows)
Round history / progress ledger
Whatever else helps a human drive the factory without reading raw files

Constraint

Git-native + ~free: no paid SaaS, no external backend. Static site regenerates from repo content on push via a GitHub Action. Git is the backend.

Tech candidates (deferred)

Jekyll (GitHub Pages default), Hugo, Astro, Eleventy, bun-based custom SSG. Per FACTORY-HYGIENE row #49 (bun+TS default), bun-based is the factory-aligned choice; Jekyll is GitHub's path of least resistance.

Sequencing

Maintainer explicit: "probably not a good idea until after the repo split into the different projects." Multi-repo refactor research (PR #150) is the prerequisite; once split lands, each split repo can have its own Pages UI for its own factory-state slice.

Cross-references

docs/AGENT-GITHUB-SURFACES.md §Pages (research-gated; this row activates that research)
PR research: multi-repo refactor — 5 candidate shapes + recommended 3-phase sequencing (D→A→E) #150 multi-repo-refactor-shapes (prerequisite)
docs/HUMAN-BACKLOG.md (UI source)
docs/DECISIONS/ (UI source)
docs/ROUND-HISTORY.md (UI source)
docs/hygiene-history/*.md (UI source)

Effort M for first-pass, L if UI becomes primary human-factory-interface.

🤖 Generated with Claude Code

Aaron directive: static factory-status UI on GitHub Pages; git-native; backlog until after repo split. P2 row filed at docs/BACKLOG.md §P2-research-grade. Captures goal, constraint, tech candidates, sequencing (post-PR-#150), cross-refs. PR #172 opened with auto-merge armed. Self-referential observation: the Pages-UI he wants is the solution to the "directives faster than I can clear" feeling he has. Build-order: file now, land after multi-repo split. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Copilot

Pull request overview

Adds a new P2 backlog item proposing a static, git-native “factory status UI” hosted on GitHub Pages, intended to surface in-flight work, decisions, and feedback-needed items after the planned repo split.

Changes:

Add a P2 BACKLOG row describing the proposed GitHub Pages “factory status UI”.
Capture goals/constraints, sequencing guidance, and cross-references to related factory artifacts.

…rst refinement PR #171 (HB-004) unblocked: 3 Copilot findings addressed (row-ordering, memory-path, "Aaron" → "human maintainer" in HB-004 narrative). Rebased on advanced main; auto-merge armed. PR #172 (Pages-UI BACKLOG row) amended with Aaron's read-only- first refinement: Phase 1 read-only uses public-repo GitHub REST API with no auth; Phase 2 write-actions need session/OAuth or thin backend, breaks git-native constraint, deferred. 3 session PRs merged so far (#167, #158, #166); 2 more armed. Sub-5-min per simple PR; higher-thread PRs will take longer. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

4 session PRs merged (#167, #158, #166, #171). PR #171 landed at 17:25:04Z. Aaron reminder absorbed: bun+TS only for Pages-UI; no Jekyll. PR #172 amended + rebased + force-pushed. Directive-to-PR-amendment compression is high (same-tick turnaround). Pages-UI row is accumulating into a mini-design through sequential refinements; promote-to-research-doc if more arrive. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ot maintainer) Aaron: "technically Kenji told me to exclude this not me, feel free to reevnualte but take the whole project into consideration." Corrected PR #172 to attribute Jekyll-exclusion to Kenji (the Architect persona), not the maintainer. Re-evaluated with whole-project consideration — Kenji's call stands: - Cross-platform parity (row #48) - Post-setup stack default (row #49 bun+TS) - One-language rule (no new Ruby chain) - GitHub Pages + Actions build pattern - Bun SSG ecosystem rich Attribution discipline is load-bearing in a multi-agent factory — Kenji's recommendations stay Kenji's; maintainer endorses or overrides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

… landed (PR #174) PR #157 (signal-in-signal-out migration) MERGED — biggest cross-PR dangling-reference resolver. 6 session PRs merged. New durable surface: docs/CONTRIBUTOR-CONFLICTS.md captures Aaron's 2026-04-23 directive for a cross-contributor differences log (humans + external AIs + factory personas). Schema, categories, sections; empty at creation per bootstrap discipline. Complements HUMAN-BACKLOG (agent-blocked-on-human asks) and CONFLICT-RESOLUTION (persona conference protocol) without overlapping. Eventual Pages-UI surfacing composes with PR #172. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…fferences (#174) Aaron 2026-04-23: "we should likely keep a contribute conflits file somewhere so you can keep a logs in the differences of options or external requirments from contributors includeing external ai not just human, this will help with bottlenecks in the hummans and ais thinking by resolving conflicts over time." New file captures: - Scope: cross-contributor differences + external requirements; excludes same-contributor-evolution (handled by CURRENT-<maintainer>.md) and per-PR-review findings (handled by required_conversation_resolution + reply-or-fix pattern) - Schema: ID / When / Topic / Between / Positions / Resolution-so-far / Scope / Source - Rules: additive resolutions; signal-preservation; name- attribution carve-out (like BACKLOG / memory/persona); row-filing is free work - Categories: architectural-preference / priority-ordering / scope-boundary / naming / tech-choice / external-requirement / process / other - Sections: Open / Resolved / Stale (all empty at creation per the creation-bootstrap discipline) - Composition with docs/HUMAN-BACKLOG.md (conflict cat), docs/CONFLICT-RESOLUTION.md (persona conference), CURRENT-<maintainer>.md, ADRs, courier protocol (PR #160), eventual Pages-UI (P2 BACKLOG row #172). Maintainer will check manually for now per 2026-04-23 directive; eventual UI surfacing composes with the Pages-UI work. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…refined Aaron: "i guess pages is github native, but our code can likely be git native ... we are gitnative with our first host as github." Filed per-user memory for the plural-host rule (git-native core + GitHub adapter; sibling adapters for GitLab / Gitea / Bitbucket ship against the same content spec). No retrofit mandate; label happens opportunistically. PR #172 constraint section refined: "git-native content" (repo-resident) vs "GitHub adapter" (Pages + Actions + REST API). Sibling-adapter path explicit. Observation: 8 distinct Aaron directives on factory-structure this session. Substrate-shaping tempo is high. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…o-split) Aaron 2026-04-23: "static ui on our github pages that shows factory status things in flight progress, etc ... we can surface thing in the ui like the decions and any decions we would like human feedback on ... all this should be able to use our gitnative approach and not really cost anyting ... backlog this and probaby not a good idea until after the repo split into the different projects." Row captures: - Goal: static UI surfacing factory state (PRs, ADRs, HUMAN-BACKLOG asks, round progress) - Constraint: git-native + ~free (static SSG regenerated by GitHub Action; no paid SaaS) - Tech candidates deferred (Jekyll / Hugo / Astro / Eleventy / bun-based custom SSG — bun aligns with post-setup stack row #49) - Sequencing: after multi-repo split (PR #150 prerequisite) - Cross-refs to AGENT-GITHUB-SURFACES Pages row, HUMAN- BACKLOG, DECISIONS, ROUND-HISTORY, hygiene-history P2 per Aaron's "probably not a good idea until after the repo split" sequencing hint. Self-scheduled free work (row-filing) under the 2026-04-23 scheduling-authority rule. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Aaron 2026-04-23: "ui will likely need gh, our repo is public so for all the read actions on the ui we are good without permission, for write actions we probably don't need this yet would need whole permission set and resue of the github logins session stuff without a real backend, tricky stuff so readonly to expaned to write access later. backlog just a little refinement." Row updated with: - Phase 1 read-only: GitHub REST API against public repo, no auth (rate-limit applies; acceptable per-push-refresh dashboard) - Phase 2 write: needs GitHub session/OAuth or thin backend; both break git-native + ~free-to-run; deferred until tradeoff re-examined Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…intainer Aaron 2026-04-23 reminder: "i'm fine with either but last time you push me hard away from jekyll that i think we only need typescript bun based and no jekyll unless you tell me otherwise." Row updated: - Tech choice is bun + TypeScript SSG (composes with FACTORY-HYGIENE row #49 post-setup stack default) - Jekyll explicitly excluded - Hugo / Astro / Eleventy demoted from listed candidates - If a compelling reason to revisit Jekyll surfaces during research, it lands as an ADR with explicit rationale; default is bun+TS Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…maintainer) Aaron 2026-04-23: "technically Kenji told me to exclude this not me, feel free to reevnualte but take the whole project into consideration". Row updated: - Attribution corrected: Kenji (Architect persona) made the bun+TS-over-Jekyll recommendation, not the maintainer directly - Re-evaluation with whole-project consideration documented: cross-platform parity (row #48), post-setup stack default (row #49), one-language-rule (no new Ruby chain), GitHub Pages + Actions build pattern works regardless of native- Pages SSG support, bun+SSG ecosystem rich enough - Conclusion: Kenji's call stands after re-examination Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…tent vs GitHub adapter) Aaron 2026-04-23: "i guess pages is github native, but our code can likely be git native only need git and not gh commands but gh commands are welcome we just need to call out gh becasue we want to be pluggable eventually to gitlab to, we are gitnative with our first host as github." Row constraint-section refined to distinguish: - Git-native content (PRs / ADRs / HUMAN-BACKLOG / CONTRIBUTOR-CONFLICTS / ROUND-HISTORY / hygiene-history — lives in repo regardless of host) - GitHub adapter (Pages + Actions + REST API are GitHub-specific; UI itself is explicitly labeled as the GitHub adapter against the git-native content spec) When a second host activates (GitLab / Gitea / Bitbucket), a sibling adapter ships against the same content spec. First host is GitHub per "gitnative with our first host as github". Full plural-host discipline in per-user memory feedback_git_native_vs_github_native_plural_host_pluggable_adapters_2026_04_23.md. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Copilot caught two row-number inconsistencies: - "Cross-platform parity (FACTORY-HYGIENE row #48)" was incorrect — row #48 is GitHub surface triage; cross- platform parity is row #51. Fixed. - "fire-log surfaces per row #44" was incorrect — row #44 is supply-chain safe-patterns; cadence-history / fire- history schema is row #47. Fixed + clarified. Third finding (docs/research/multi-repo-refactor-shapes path) — will be handled via reply-with-rationale (lands via PR #150, still open). Row-number misref is a recurring finding class across session PRs; candidate sweep target for backlog-refactor hygiene row #54 first cadenced fire. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

chatgpt-codex-connector · 2026-04-23T18:04:12Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

…w-number fixes PR #159 (Overlay A #3 deletions-over-insertions) MERGED at 18:02:47Z. 11 session PRs merged. HLL test passed on re-run (different seed) — real-world data for the PR #175 BACKLOG row on HLL flakiness; pin-then-explore is still the right fix. Aaron directive: "be PC when you write the 69 and 420 descriptions of whemsy we want this repo to be high school curruclurm friendly so R rated is okay but only when necessary for effect." PC-ified seed-whimsy memory descriptions (69 → internet-meme-symmetrical-digit; 420 → counterculture-meme). Added PC-framing section naming the high-school-curriculum-friendly standard. PR #172 row-number misrefs fixed (#48 → #51 for cross- platform parity; #44 → #47 for fire-history schema). Third finding via lands-via-#150 reply. Row-number misref is recurring; candidate for row #54 first cadenced fire. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

Copilot · 2026-04-23T18:07:26Z

+  Kenji's call stands: bun + TypeScript. No Jekyll as
+  default; Jekyll reconsidered only if a whole-project
+  use case surfaces that isn't served by bun+TS.


P1 (config-drift): This row states a fairly definitive decision (“Kenji’s call stands… No Jekyll as default”), but docs/AGENT-GITHUB-SURFACES.md Surface 10 treats Pages deployment as research-gated and explicitly lists Jekyll as an option still under evaluation. Suggest rephrasing this section to align with the existing doc (e.g., bun+TS as the preferred candidate while still evaluating/keeping Jekyll as a considered alternative) unless an ADR has already made the decision.

Suggested change

Kenji's call stands: bun + TypeScript. No Jekyll as

default; Jekyll reconsidered only if a whole-project

use case surfaces that isn't served by bun+TS.

Current direction: treat bun + TypeScript as the

preferred candidate to evaluate first after the repo

split, while keeping Pages deployment research-gated.

Jekyll remains a considered alternative rather than a

closed option until an implementation decision or ADR

settles the default.

Copilot · 2026-04-23T18:07:27Z

+  - PR #150 `docs/research/multi-repo-refactor-shapes-2026-04-23.md`
+    (prerequisite)


P1 (xref): docs/research/multi-repo-refactor-shapes-2026-04-23.md is not present on main yet. Elsewhere in BACKLOG forward references are annotated (e.g., “(lands via PR #155)”) to signal that the file isn’t merged yet; please add a similar “(lands via PR #150)” note here (or otherwise clarify) to avoid a temporarily broken pointer if this lands first.

Suggested change

- PR #150 `docs/research/multi-repo-refactor-shapes-2026-04-23.md`

(prerequisite)

- `docs/research/multi-repo-refactor-shapes-2026-04-23.md`

(lands via PR #150; prerequisite)

Copilot · 2026-04-23T18:07:27Z

+  feeding the UI** (PRs, ADRs, HUMAN-BACKLOG,
+  CONTRIBUTOR-CONFLICTS, ROUND-HISTORY, hygiene-history)
+  is git-native — lives in the repo regardless of host.
+  The **UI itself is an explicit GitHub adapter**: GitHub
+  Pages is GitHub-native by definition; GitHub Actions


P1 (xref): The “git-native content” list uses bare identifiers (e.g., HUMAN-BACKLOG, CONTRIBUTOR-CONFLICTS, ROUND-HISTORY, hygiene-history) instead of repo-resolvable paths. Since these are intended as UI inputs, please change them to explicit paths like docs/HUMAN-BACKLOG.md, docs/CONTRIBUTOR-CONFLICTS.md, docs/ROUND-HISTORY.md, and docs/hygiene-history/ to avoid ambiguous/broken references.

Suggested change

feeding the UI** (PRs, ADRs, HUMAN-BACKLOG,

CONTRIBUTOR-CONFLICTS, ROUND-HISTORY, hygiene-history)

is git-native — lives in the repo regardless of host.

The **UI itself is an explicit GitHub adapter**: GitHub

Pages is GitHub-native by definition; GitHub Actions

feeding the UI** (PRs, ADRs, `docs/HUMAN-BACKLOG.md`,

`docs/CONTRIBUTOR-CONFLICTS.md`, `docs/ROUND-HISTORY.md`,

`docs/hygiene-history/`) is git-native — lives in the

repo regardless of host. The **UI itself is an explicit

GitHub adapter**: GitHub Pages is GitHub-native by

definition; GitHub Actions

…lassification BACKLOG 13 session PRs merged. Three landed in ~4 minutes: #159 (Overlay A #3), #172 (Pages-UI BACKLOG), #173 (UML BACKLOG). PR #173 unblock: 4 findings — Rational Rose cross-ref stale after rebase (row now adjacent on main); grammar nit fixed; row-number accepted as current; hard-coded row #49 kept. 4 threads resolved. Aaron directive (two-message): age-classification skill covering language + concepts. Filed PR #176 as P3 row, captures both axes + bi-audience (AI + humans) + human- standards-mapping + new physiology-based factory standard. Auto-merge armed. Rational Rose + UML rows now adjacent on main — prime target for row #54 first-fire overlap sweep. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Copilot AI review requested due to automatic review settings April 23, 2026 17:20

AceHack enabled auto-merge (squash) April 23, 2026 17:20

Copilot started reviewing on behalf of AceHack April 23, 2026 17:21 View session

Copilot AI reviewed Apr 23, 2026

View reviewed changes

Comment thread docs/BACKLOG.md Outdated

Comment thread docs/BACKLOG.md

AceHack force-pushed the backlog/factory-status-ui-github-pages branch from ef0f6ba to 0ba2dc2 Compare April 23, 2026 17:23

Copilot AI review requested due to automatic review settings April 23, 2026 17:25

AceHack force-pushed the backlog/factory-status-ui-github-pages branch from 0ba2dc2 to d57c365 Compare April 23, 2026 17:25

Copilot started reviewing on behalf of AceHack April 23, 2026 17:25 View session

Copilot AI reviewed Apr 23, 2026

View reviewed changes

Comment thread docs/BACKLOG.md

AceHack mentioned this pull request Apr 23, 2026

docs: CONTRIBUTOR-CONFLICTS.md — durable log for cross-contributor differences #174

Merged

AceHack force-pushed the backlog/factory-status-ui-github-pages branch from 1df536e to 3ef38e9 Compare April 23, 2026 17:47

AceHack and others added 6 commits April 23, 2026 14:04

Copilot AI review requested due to automatic review settings April 23, 2026 18:04

AceHack force-pushed the backlog/factory-status-ui-github-pages branch from 3ef38e9 to 23acb8b Compare April 23, 2026 18:04

Copilot started reviewing on behalf of AceHack April 23, 2026 18:04 View session

AceHack merged commit 9e32c58 into main Apr 23, 2026
12 checks passed

AceHack deleted the backlog/factory-status-ui-github-pages branch April 23, 2026 18:05

Copilot AI reviewed Apr 23, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

backlog: P2 — factory status UI on GitHub Pages (git-native, post-repo-split)#172

backlog: P2 — factory status UI on GitHub Pages (git-native, post-repo-split)#172
AceHack merged 6 commits intomainfrom
backlog/factory-status-ui-github-pages

AceHack commented Apr 23, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

chatgpt-codex-connector Bot commented Apr 23, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 23, 2026

Uh oh!

Copilot AI Apr 23, 2026

Uh oh!

Copilot AI Apr 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

-  Kenji's call stands: bun + TypeScript. No Jekyll as
-  default; Jekyll reconsidered only if a whole-project
-  use case surfaces that isn't served by bun+TS.
+  Current direction: treat bun + TypeScript as the
+  preferred candidate to evaluate first after the repo
+  split, while keeping Pages deployment research-gated.
+  Jekyll remains a considered alternative rather than a
+  closed option until an implementation decision or ADR
+  settles the default.

		- PR #150 `docs/research/multi-repo-refactor-shapes-2026-04-23.md`
		(prerequisite)

Conversation

AceHack commented Apr 23, 2026

Summary

Goal

Constraint

Tech candidates (deferred)

Sequencing

Cross-references

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

chatgpt-codex-connector Bot commented Apr 23, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 23, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants