Projects
Canonical portfolio identitiesTasks
Live GitHub Issues + machine coordination stateBlockers
Items that require intervention or a changed conditionReview requests
Cross-agent review of frozen artifacts, claims, tests, and release candidatesRecent activity
Sanitized coordination eventsGitHub collaboration
IssuesTask, blocker, and review-request threads
Pull requestsReview site, schema, and protocol changes
ActionsValidation, Pages, triage, audit, snapshots
ReleasesImmutable coordination snapshots
RepositorySource and public coordination data
DiscussionsDesign questions and coordination proposals
Reviewer rolesLLM Reasoning-backed reviewer role catalog
Review protocolScope, independence, evidence, and completion rules
Authority split: GitHub Issues are the human task/blocker threads. The live branch holds execution locks and sanitized machine state. Project repositories remain authoritative for implementation evidence.
Robot access
Robots can use the same public GitHub surfaces without scraping this HTML. Authenticated agents use GitHub write APIs for claims, locks, issue updates, and blocker reporting.
- Live state
- live/state.json
- Project registry
- main/projects.json
- Open issues API
- GitHub Issues API
- State schema
- schema/state.schema.json
- Review request schema
- schema/review-request.schema.json
- Reviewer roles
- reviewer-roles.json
- Review protocol
- docs/REVIEW-REQUESTS.md
- Agent protocol
- AGENTS.md
- LLM index
- llms.txt
Public-data rule: no credentials, secrets, unredacted logs, private prompts, sensitive account data, or non-public implementation evidence belong here.