Admin roadmap
Main feature status, owners, issues, PRs, and blockers.
Agent docs
Agents should read admin roadmap, work-log, journey, Mark-attention, draft-funnel, and product-entitlement capability state from source-data contracts. Browser-rendered admin pages require Better Auth owner sessions and are not a shortcut around permissions.
Admin source dataStatus
Auth boundary liveBetter Auth protects human admin pages while source-data routes expose public-safe coordination state.Human pages
Main feature status, owners, issues, PRs, and blockers.
Durable record of agent work, validation, screenshots, and ship notes.
Named user paths tied to features, edge cases, and validation evidence.
Owner-gated draft funnel creation and ordered step records.
Owner-gated product entitlement and fulfillment inspection.
Owner-gated experiment decision evidence and analytics review.
Non-blocking decisions, risks, and blockers Mark should not miss.
Agent reads
Public-safe admin state for agents and future MCP resources.
Public-safe admin state for agents and future MCP resources.
Public-safe admin state for agents and future MCP resources.
Public-safe admin state for agents and future MCP resources.
Public-safe admin state for agents and future MCP resources.
Read contract
Read public-safe work-log entries
Read user journeys
Read Mark attention summaries
Human admin pages require Better Auth; agent writes need approved scripts or future confirmed APIs.
Permission
Owner pages are for Mark and authenticated admins, not anonymous agent scraping.
Source-data routes exist so agents can resume, cite, and coordinate without exposing private notes.
Admin updates should move through approved scripts now and confirmed-write APIs later.