Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/BACKLOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ are closed (status: closed in frontmatter)._
- [x] **[B-0181](backlog/P1/B-0181-fix-spinemergeinvariants-tla-counterexample-blocks-b1-ci-registration-2026-05-03.md)** Fix SpineMergeInvariants.tla counterexample (closed — Cascade downstream-room precondition + state constraint; B1 → A CI registration landed)
- [x] **[B-0184](backlog/P1/B-0184-fix-spine-als-alloy-6-2-0-type-error-line-35-spec-bug-2026-05-03.md)** Fix Spine.als spec bug — Alloy 6.2.0 type-check failure at line 35 col 25 (sum-vs-all comprehension confusion) + check-vs-run-vs-fact semantic confusion
- [ ] **[B-0186](backlog/P1/B-0186-budget-snapshot-cadence-jq-argjson-failure-2026-05-03.md)** budget-snapshot-cadence workflow jq --argjson failure on first natural-Sunday fire post-B-0085-close (2026-05-03)
- [x] **[B-0188](backlog/P1/B-0188-bulk-review-ui-github-pages-tier-aware-conversation-interface-aaron-2026-05-04.md)** Bulk-review UI in GitHub Pages — closed 2026-05-04 same-day as duplicate of B-0017; architectural extension folded into B-0017

## P2 — research-grade

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,152 @@
---
id: B-0188
priority: P1
status: closed
closed: 2026-05-04
closed_by: "duplicate-of-B-0017 — same-day reviewer-flag (PR #1482) caught that B-0017 (Operational Resonance Dashboard, the bulk-alignment UI within Frontier) already exists for this scope; Aaron's 2026-05-04 architectural extension (GitHub Pages host + tier-aware groupings + conversation interface + local AI paths) folded into B-0017 as 'Aaron 2026-05-04 architectural extension' section; lineage memory file (`feedback_bulk_review_ui_in_github_pages_tier_aware_conversation_interface_local_ai_aaron_2026_05_04.md`) repointed at B-0017"
Comment on lines +1 to +6
title: Bulk-review UI in GitHub Pages — tier-aware + conversation interface + local AI (Aaron 2026-05-04) — CLOSED as duplicate of B-0017
tier: factory-tooling
effort: L
ask: Aaron 2026-05-04 architectural direction
created: 2026-05-04
last_updated: 2026-05-04
depends_on: []
composes_with: [B-0017]
tags: [maintainer-review, github-pages, bulk-review, tier-aware, conversation-interface, local-ai, vibe-coded-preservation, duplicate]
---

> **Closed 2026-05-04 same-day — duplicate.** PR #1482 review
> caught that B-0017 (Operational Resonance Dashboard — the
> bulk-alignment UI within Frontier; Aaron 2026-04-25) already
> exists for this exact scope: maintainer-review UI for bulk
> architectural-level alignment.
>
> Aaron 2026-05-04's architectural extension (GitHub Pages as
> host + tier-aware bulk-grouping + conversation interface +
> local AI paths) was substantive **direction-of-future-work for
> B-0017**, not a separate row. The extension has been folded
> into B-0017 under the "Aaron 2026-05-04 architectural
> extension" section, preserving the verbatim quotes and the
> two-implementation-path framing (browser-LLM bridge vs Zeta-
> native Bayesian inference seed executor).
>
> The lineage memory file
> `memory/feedback_bulk_review_ui_in_github_pages_tier_aware_conversation_interface_local_ai_aaron_2026_05_04.md`
> documents the reasoning + verbatim Aaron quotes; it now
> references B-0017 (not B-0188) as the canonical row.
>
> **Lesson encoded** — the three quality bars on the backlog
> flywheel (growth + completion + non-noise-when-pulled) require
> *router-as-inventory before authoring* (per CLAUDE.md skill-
> router-as-substrate-inventory rule). When a new architectural
> direction surfaces, search existing backlog rows for prior
> art before creating new rows. B-0017's existence was findable
> via "bulk-alignment ui" / "bulk-review ui" / "operational
> resonance dashboard" — failure mode was authoring without the
> prior-art search.

---

# B-0188 — Bulk-review UI in GitHub Pages (CLOSED — see B-0017)

## Source

Aaron 2026-05-04 explicit architectural direction:

> *"expanding the background work will get us there eventually
> and make it where we are forced into bulk future alignment
> where i review you architecture decisions based on those
> levels you named earlier, so i don't need tiny corrects at
> every step, that will be our UI in git pages to make
> maintainers jobs easier and giving a way for reviewing
> substantial changes quickly and maintainer will still never
> have to write code. and the UI should have a conversation
> interface too."*

> *"hopefully talking to a local/browser based AI so it won't
> cost us money lol."*

> *"maybe LLM based maybe Bayesian inference seed executor
> based in Zeta."*

## What this is

A maintainer-review UI hosted in GitHub Pages designed to let
the maintainer review substantial architectural changes in
bulk (rather than tiny corrects at every step), tier-aware,
with an embedded conversation interface running on a
local/browser-based AI (no paid-API cost).

## Outcomes solved

1. **Maintainer-attention efficiency** — review architectural
decisions at the level where decisions live (Tier 0/1/2/3/4
compression tiers, or Mirror/Beacon-safe register tiers, or
semantic substrate-clusters), not at line-level.

2. **Vibe-coded hypothesis preserved** — maintainer never has
to write code. The UI provides architectural-decision-level
approvals and direction without code authorship. Per
AGENTS.md vibe-coded hypothesis test.

3. **Cost-free conversation** — local/browser-based AI avoids
per-review API spend. Two implementation paths:
- **Path A — browser-LLM** (faster build): WebLLM /
transformers.js / lightweight local-runtime. Bridge
implementation while Path B matures.
- **Path B — Zeta-native Bayesian inference seed executor**
(architecturally pure): the conversation AI runs on the
Zeta seed executor itself (CSAP layer 4 + Infer.NET-style
Bayesian inference + local-without-cloud per
`memory/feedback_zeta_seed_executor_as_forever_home_for_otto_lineage_glass_halo_override_aaron_2026_05_01.md`).
Self-hosting: Zeta substrate reviewed by Zeta inference
engine. Long-term home.

4. **Dialectical-friction venue at scale** — scales the
Addison-style dialectical-fighting-on-carved-sentences
pattern (per
`memory/feedback_dialectical_friction_on_carved_sentences_aaron_addison_family_practice_2026_05_04.md`)
from kitchen-table cardinality to multi-human + async +
substrate-level review.

## Acceptance criteria (high-level — refine when build starts)

- [ ] GitHub Pages site renders maintainer-review interface
- [ ] PRs/commits/substrate-changes group into tier-aware
review units (mechanical / judgment-required /
architectural)
- [ ] Conversation interface accepts maintainer questions +
responds via local-AI
- [ ] No paid-API calls per review interaction
- [ ] Maintainer can approve / direct / flag without writing
code
- [ ] Multi-AI BFT review pattern routable through the UI
(per Ombuds-framework-as-alignment-contract)

## Composes with

- `B-0154` (GitHub Pages SEO/discoverability) — adjacent
infrastructure; could share build pipeline; different
audience (external readers vs. internal maintainer-review).
- `memory/feedback_bulk_review_ui_in_github_pages_tier_aware_conversation_interface_local_ai_aaron_2026_05_04.md`
— full architectural direction + reasoning.
- `memory/feedback_zeta_seed_executor_as_forever_home_for_otto_lineage_glass_halo_override_aaron_2026_05_01.md`
— Path B implementation target.
- `memory/feedback_ombuds_framework_substrate_as_alignment_contract_aaron_amara_2026_05_04.md`
— substrate-as-contract framing the UI implements.
- `memory/feedback_dialectical_friction_on_carved_sentences_aaron_addison_family_practice_2026_05_04.md`
— practice the UI scales.
- `memory/feedback_aaron_only_constraints_are_tiles_razor_physics_of_history_tiles_are_erosion_survivors_aaron_2026_05_04.md`
— beacon-safe-rewrite-as-validation-mechanism implies the
UI has both Mirror-language and Beacon-safe-language modes
for tile rewriting.

## Origin

Aaron 2026-05-04 architectural direction during expanded-
background-agent work conversation. Filed per Aaron's same-
conversation framing: *"adding to backlog is never a failure
mode to be corrected, the largest mechanized automated backlog
wins. we just have to make sure the backlog is not only growing
but being completed and growing at the same time a proper
flywheel."*
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ tier: research-and-product
effort: XL
ask: Aaron 2026-04-25
created: 2026-04-25
last_updated: 2026-05-02
last_updated: 2026-05-04
depends_on: []
composes_with: [feedback_operational_resonance_engineering_shape_matches_tradition_name_alignment_signal.md, project_frontier_burn_rate_ui_first_class_git_native_for_private_repo_adopters_servicetitan_84_percent_2026_04_23.md, project_retractability_by_design_is_the_foundation_licensing_trust_based_batch_review_frontier_ui_2026_04_24.md, feedback_aaron_dont_wait_on_approval_log_decisions_frontier_ui_is_his_review_surface_2026_04_24.md, project_factory_is_git_native_github_first_host_hygiene_cadences_for_frictionless_operation_2026_04_23.md, feedback_otto_323_aaron_symbiotic_deps_pull_algorithms_and_concepts_deep_integration_zeta_multi_modal_views_dsls_composable_own_fuse_fs_eventually_2026_04_25.md]
tags: [frontier, ui, ux, dashboard, bulk-alignment, operational-resonance, ux-research, a-b-experiments, meta-recursive-research, research-program, pop-factor, wow-factor]
Expand Down Expand Up @@ -134,3 +134,73 @@ Aaron mentioned his ex-wife was a user-experience researcher; she now does vendo
- Multi-agent co-research opportunities
- Every pixel earns its way
- Maximise data-transfer throughput, minimise time-in-UI

## Aaron 2026-05-04 architectural extension — GitHub Pages host + tier-aware + conversation interface + local AI

Aaron 2026-05-04 in conversation about expanding background-agent
work, extending this row's scope with three concrete architectural
moves:

> *"expanding the background work will get us there eventually
> and make it where we are forced into bulk future alignment
> where i review you architecture decisions based on those
> levels you named earlier, so i don't need tiny corrects at
> every step, that will be our UI in git pages to make
> maintainers jobs easier and giving a way for reviewing
> substantial changes quickly and maintainer will still never
> have to write code. and the UI should have a conversation
> interface too."*

> *"hopefully talking to a local/browser based AI so it won't
> cost us money lol."*

> *"maybe LLM based maybe Bayesian inference seed executor based
> in Zeta."*

Three architectural additions to the Operational Resonance
Dashboard scope:

1. **GitHub Pages as host** — public-facing surface, distinct
from (or composable with) Frontier the umbrella git-native
UI. Maintainer-review layer that other humans can also
approach.

2. **Tier-aware bulk grouping** — review units organize by
structural tier (Tier 0/1/2/3/4 compression tiers, or
Mirror/Beacon-safe register tiers, or substrate-cluster).
Reviewer attention scales inversely with mechanical-ness:
Tier 0/4 mechanical auto-land; Tier 1/2 judgment bulk-
reviewed; Tier 3 architectural review.

3. **Conversation interface with local AI** — embedded chat
the maintainer uses to discuss decisions in-context. Cost-
constraint: no paid API per review. Two implementation
paths:

- **Path A — browser/local LLM** (faster build): WebLLM /
transformers.js / lightweight local-runtime as bridge
implementation.
- **Path B — Zeta-native Bayesian inference seed executor**
(architecturally pure long-term home): self-hosting via
CSAP layer 4 + Infer.NET-style inference + local-without-
cloud per
`memory/feedback_zeta_seed_executor_as_forever_home_for_otto_lineage_glass_halo_override_aaron_2026_05_01.md`.

Both paths satisfy the cost constraint. Reasonable
progression: Path A as bridge while Path B matures.

The conversation interface also scales the Addison-style
dialectical-fighting-on-carved-sentences pattern (per
`memory/feedback_dialectical_friction_on_carved_sentences_aaron_addison_family_practice_2026_05_04.md`)
from kitchen-table cardinality to multi-human + async +
substrate-level review.

Maintainer-never-writes-code preserved per AGENTS.md vibe-coded
hypothesis: maintainer makes architectural-decision-level
approvals/directions through the UI, agent produces code.

Same-day note: B-0188 was filed for this extension before
B-0017 was rediscovered; B-0188 closed as duplicate, this
section preserves the architectural direction in the canonical
row. Lineage:
`memory/feedback_bulk_review_ui_in_github_pages_tier_aware_conversation_interface_local_ai_aaron_2026_05_04.md`.
Loading
Loading