Director
Executive one-pager for recent changes, risks, due work, and nested workstreams.
Agent docs
Agents should read the director dashboard, admin roadmap, work-log, journey, owner-attention, draft-funnel, and product-entitlement capability state from non-admin source-data aliases. Browser-rendered admin pages require Better Auth owner sessions and are not a shortcut around permissions. The director contract includes due-now, in-flight, pending-next, and watchlist queue lanes plus recent-change digests with workstream provenance for executive summaries, along with stable briefing controls for past-day, past-week, queue, and workstream-map reads.
Project source dataStatus
Auth boundary liveBetter Auth protects human admin pages while agent-docs aliases expose public-safe coordination state.Human pages
Executive one-pager for recent changes, risks, due work, and nested workstreams.
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 owner decisions, risks, and blockers.
Agent reads
/agent-docs/director-status-source-data
/agent-docs/project-source-data
/agent-docs/project-roadmap-source-data
/agent-docs/project-work-log-source-data
/agent-docs/user-journey-source-data
/agent-docs/owner-attention-source-data
Read contract
Read public-safe work-log entries
Read user journeys
Read owner attention summaries
Human admin pages require Better Auth; agent writes need approved scripts or future confirmed APIs.
Permission
Owner pages are for 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.