Home

This Wiki is the canonical home for Release Radar operating standards, product specifications, architecture decisions, and ticket-owned implementation plans. Owner direction authorizes work; the current GitHub ticket defines its bounded scope and acceptance criteria and records status, verification, and results.

Find what you need

Task	Start here
Create, structure, or plan GitHub work	GitHub Issue Standard
Initialize or coordinate a development task	RR Development Delegation Model, then its linked role prompt
Understand or change product behavior	Product Specifications, then the ticket-relevant sections and every required dependency they identify
Understand an architectural boundary	Architecture Decisions, preserving each decision's recorded status
Read a ticket-owned implementation plan	Implementation Plans; use the plan revision recorded in the owning issue
Review preserved agent-workflow research	Agent Workflow Research; source records are historical research, not approved policy or implementation authority
Inspect current work or approval	The current GitHub issue and owner direction; the Wiki does not authorize work
Inspect code, assets, fixtures, or application-owned catalog machinery	The repository at the revision relevant to the ticket

Authority boundaries

• Wiki standards and role prompts govern how development work is performed.
• Product specifications govern current product behavior, subject to their explicit approval and dependency qualifications.
• Accepted ADRs preserve architectural decisions. Proposed or pending ADRs are not promoted by appearing in an index, cannot authorize work, and cannot silently resolve a conflict; surface the conflict to the owner.
• GitHub issues own current work records; owner direction grants authority.
• Repository code, assets, fixtures, mockups, and documentation catalog tooling remain repository-owned.