Phase 7 — Web Panel #10

Open
opened 2026-08-08 19:36:47 +00:00 by wtclaude · 0 comments
Collaborator

Size: large · Depends on: Phases 1–6

Served by the same binary. The admin API already exists from phases 1–6, so this phase is a client against it, not a new integration surface.

Scope

  • Gateway: connected agents/sessions, routing, agent-identity mapping
  • Secrets: add / rotate / revoke — raw values never displayed after storage
  • Rules: edit the canonical doc, approve or reject agent-proposed and vendor-seeded guardrails, manage patterns and example repos, trigger re-indexing
  • Memory: browse/search indexed content, manual purge and re-index
  • Integrations: Gitea/Kanboard connection status and project mappings
  • Audit log: full change history with source attribution

Exit criterion

Every phase 1–6 operation is achievable through the UI with no CLI or database access.

Open items to settle first

  • Web Panel stack: server-rendered Rust templates versus an embedded SPA
  • Approval queue notifications: panel-only, or out-of-band webhook/email when an agent proposes a change?

Review notes

The panel talks only to the Gateway's admin API, never directly to backend services — mirroring the centralized-token principle. Security review required (secrets surface).

**Size:** large · **Depends on:** Phases 1–6 Served by the same binary. The admin API already exists from phases 1–6, so this phase is a **client against it**, not a new integration surface. ## Scope - Gateway: connected agents/sessions, routing, agent-identity mapping - Secrets: add / rotate / revoke — raw values never displayed after storage - Rules: edit the canonical doc, approve or reject agent-proposed and vendor-seeded guardrails, manage patterns and example repos, trigger re-indexing - Memory: browse/search indexed content, manual purge and re-index - Integrations: Gitea/Kanboard connection status and project mappings - Audit log: full change history with source attribution ## Exit criterion Every phase 1–6 operation is achievable through the UI with no CLI or database access. ## Open items to settle first - Web Panel stack: server-rendered Rust templates versus an embedded SPA - Approval queue notifications: panel-only, or out-of-band webhook/email when an agent proposes a change? ## Review notes The panel talks only to the Gateway's admin API, never directly to backend services — mirroring the centralized-token principle. Security review required (secrets surface).
wtclaude added this to the v1.0 — Agentic Bridle milestone 2026-08-08 19:36:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: whitlocktech/Agentic-Bridle#10
No description provided.