The egohygiene/.github repository is the organization-level intake and coordination surface. It is not the default implementation repository for work that already has a durable owner.
Route work to the narrowest durable owner that can complete it without copying another repository's implementation.
Use .github when work is genuinely organization-facing or when ownership is not yet known. Once an owner is established, keep the umbrella issue here only when cross-repository coordination remains useful and link to the implementation issue instead of duplicating its checklist.
| State | Meaning | Next action |
|---|---|---|
needs-routing |
No durable owner is established yet. | Identify the capability and candidate owners. |
routed |
An implementation owner is known. | Link the owning issue/repository. |
cross-repo |
Multiple repositories must coordinate through explicit contracts. | Keep an umbrella issue and link bounded implementation issues. |
blocked |
A dependency prevents useful implementation. | Record the dependency and unblock condition. |
ready |
Scope, owner, dependencies, and acceptance criteria are sufficient for implementation. | Execute in the owning repository. |
These names are governed by the machine-readable label catalog. Label creation and synchronization should be performed by the organization automation owned by Relay rather than hand-maintained independently in every repository.
The organization taxonomy should remain deliberately small.
priority:p0— correctness, security, or data-integrity blocker.priority:p1— required foundation or near-term release work.priority:p2— important planned capability.priority:p3— research, exploration, or later direction.
type:architecturetype:featuretype:bugtype:documentationtype:researchtype:maintenance
Use area:<domain> only for stable domains that improve filtering. Do not create a label for every component or repository.
cross-reponeeds-routingblockedready
The canonical catalog also defines a deliberately small area:* set for
automation, developer experience, governance, and security. Add another
universal area only when it is stable across the organization; repository or
domain concepts belong in overlays.
The approved expressive catalog is classified into five opt-in overlays:
| Overlay | Scope |
|---|---|
ecosystem |
Named Ego Hygiene capabilities. |
engineering |
Engineering changes, platforms, packages, and specifications. |
creative-publishing |
Creative production, design, publishing, and outreach. |
human-practice |
Human domains, practices, philosophy, and journeys. |
research-funding |
Research and the resources that support it. |
Repository-specific additions may add labels, but must not redefine universal or overlay semantics. See label governance for the versioning, collision, deprecation, and removal rules.
An umbrella issue owns coordination, not duplicated implementation.
It should contain:
- the organization-level outcome;
- the owning repositories;
- dependency edges;
- links to implementation issues;
- integration acceptance criteria.
Implementation details belong in the repository that owns them. Closing an implementation issue does not automatically close the umbrella issue until the cross-repository outcome is verified.
| Request | Owner |
|---|---|
| Organization profile/community defaults | .github |
| Canonical architecture/policy/catalog | hygiene |
| Repository baseline/template contract | empathy |
| Repository materialization | holon |
| AI artifacts and provider projections | aether |
| Reusable GitHub Actions | relay |
| Lint semantics | egolint |
| Development environments | realm |
| Portable shell/workstation behavior | mantle |
| Fleet convergence | pace |
| Fleet visibility/evidence | observatory |
| Unknown experimental capability | .github for routing, then sanctuary when incubation is appropriate and available |
Issues involving secrets, signing, production infrastructure, billing, destructive migration, personal/private data, or external publication must state the trust boundary and required human approval. Do not place credentials or sensitive values in issues.