Network/Roadmap/Internal Admin Dashboard
Roadmap
P-011ShippedCaptured retroactively

/internal admin dashboard (Phase 4)

Combined admin-only view across Journal, Backlog, and Register, gated by `await requireRole("admin")`. Surfaces internal-visibility entries that are filtered out of public indices, with stat counts and per-row visibility badges.

Milestone
Pre-roadmap (Phase 4)
Posted credit value
8credits
Founder credits accrued
8of 8
Owner
Creator
Related
Entry 017

Captured retroactively. This project shipped before the roadmap surface existed. The credit value is a post-hoc estimate per the methodology in Entry 017 and is subject to revision under G-038's calibration mechanism.

What shipped

  • src/app/internal/page.tsx route gated at the top with await requireRole("admin"). Non-admins get redirected via the helper's built-in 404 fallback.
  • Stat cards counting Journal entries, Backlog items, Register entries (broken down by tier and visibility).
  • Row components per corpus: JournalRow, BacklogRow, RegisterRow, each rendering visibility badges including the otherwise-hidden internal-only badge.
  • A single dashboard view rather than three separate admin sub-routes, to keep the cognitive load on admins low.

Why

Phases 1–3 produced public-facing surfaces. Phase 4 was the matched admin-side surface — without it, internal-visibility register entries would be writeable in the corpus but invisible to anyone trying to review them. The dashboard is the admin's reading view of the full governance state.