Summary
Clarify org-level role/lane policy so future agents can distinguish authority roles from executable repo-local agents and PR-body markers.
Problem
The ecosystem uses names such as Release-Admiral, Project-Lieutenant, Issue-Admiral, Project-Captain, and Open-Admiral. Some are authority roles, some are recognized by workflow policy as PR markers, and some may become executable automation later. Current docs do not consistently separate those meanings.
Acceptance Criteria
- Org docs define each role as one or more of: authority role, executable command/agent, PR marker/configuration signal, or future automation.
- Release-Admiral and Project-Lieutenant marker behavior in github-workflows role policy is explicitly documented.
- Docs state that a role name does not imply a repo-local command exists.
- Related F-roadmap issues are cross-linked without duplicating implementation scope.
Related
Summary
Clarify org-level role/lane policy so future agents can distinguish authority roles from executable repo-local agents and PR-body markers.
Problem
The ecosystem uses names such as Release-Admiral, Project-Lieutenant, Issue-Admiral, Project-Captain, and Open-Admiral. Some are authority roles, some are recognized by workflow policy as PR markers, and some may become executable automation later. Current docs do not consistently separate those meanings.
Acceptance Criteria
Related