| schema | aether.architecture-document/v1 | ||||
|---|---|---|---|---|---|
| id | organization-github-roadmap | ||||
| title | Ego Hygiene .github Roadmap | ||||
| kind | architecture-document | ||||
| version | 0.1.0 | ||||
| status | provisional | ||||
| owners |
|
||||
| created | 2026-08-19 | ||||
| updated | 2026-08-24 | ||||
| governed_by |
|
||||
| depends_on |
|
||||
| related |
|
||||
| supersedes |
This evidence-reconciled snapshot is the issue-generation and visual-roadmap handoff. The longer-horizon strategy below remains canonical context; generated HTML, JSON, progress, issue plans, and commit lists are projections.
Lifecycle: incubating foundation
Current gate: Finish the label and routing policy tracked in issue #8, then prove the organization defaults in a consumer repository.
North-star outcome: A thin, trusted set of organization defaults that makes contribution, security, and intake behavior predictable without hiding repository-owned policy.
Mode: central
Route: /roadmap/.github/
Current publication evidence: Organization-wide GitHub defaults; no Pages publication observed.
Publish the public-safe projection through egohygiene.io at /roadmap/.github/. This repository owns intent and acceptance evidence; it does not add a second site deployment.
State: complete
Depends on: None
Outcome: Organization profile and intake mechanisms provide a usable shared starting point.
Exit criteria:
- The shared profile and intake artifacts are present on the default branch.
- Their intended organization-wide scope is documented.
Current evidence:
- Merged PR #14 at 0b83d5270d0b.
- Merged PR #16 at 2c04a1f55cc0.
State: active
Depends on: ORG-Q01
Outcome: New work is labeled and routed consistently across the organization.
Exit criteria:
- Issue #8 has an accepted label taxonomy and routing contract.
- At least one repository demonstrates the policy without repository-specific ambiguity.
Current evidence:
- Issue #8 remains unfinished as of 2026-08-24.
State: ready
Depends on: ORG-Q02
Outcome: Repositories can tell which community files they inherit and which they must own.
Exit criteria:
- An automated check covers all intended inherited files.
- Exceptions and private-repository behavior are documented.
Current evidence:
- No organization-level validation workflow was observed.
State: planned
Depends on: ORG-Q03
Outcome: Human-facing defaults stay here while machine-readable portfolio policy is owned by Hygiene.
Exit criteria:
- Ownership is stated in both repositories.
- No policy is authoritative in two places.
Current evidence:
- Hygiene is the proposed canonical machine-readable organization definition.
State: planned
Depends on: ORG-Q03, ORG-Q04
Outcome: A dated, evidence-backed checkpoint makes changes to shared defaults auditable.
Exit criteria:
- All lightweight validation is green.
- The checkpoint links the policy changes and consumer proof.
Current evidence:
- No CI or release publication was observed.
- A step is complete only when its exit criteria and required evidence are satisfied; commit count never determines progress.
- Ready steps without an issue are candidates for the private, duplicate-aware roadmap.issue-plan.json dry run. Planned steps remain preview-only unless a reviewer explicitly opts them in with issue_policy: propose.
- Issue creation or reconciliation requires human approval or an explicitly authorized Pace operation and returns issue references through a reviewable roadmap pull request.
- Pull requests and commits should include Roadmap-Step: ; historical evidence may be linked through existing issue and pull-request relationships.
- Public rendering uses only allowlisted build-time evidence and never places a GitHub token or private issue plan in the browser artifact.
This roadmap describes capability evolution, not promised dates or an issue queue. Sequence follows architecture dependencies and may change when evidence or risk changes.
Outcome: A bounded capability advances from documented intent to validated, independently usable behavior.
Exit signals:
- The owning contract and acceptance criteria are versioned.
- Implementation and documentation agree.
- Relevant tests and safety checks pass.
- Downstream consumers and migration impact are understood.
- Remaining uncertainty is visible.
Outcome: A bounded capability advances from documented intent to validated, independently usable behavior.
Exit signals:
- The owning contract and acceptance criteria are versioned.
- Implementation and documentation agree.
- Relevant tests and safety checks pass.
- Downstream consumers and migration impact are understood.
- Remaining uncertainty is visible.
Outcome: A bounded capability advances from documented intent to validated, independently usable behavior.
Exit signals:
- The owning contract and acceptance criteria are versioned.
- Implementation and documentation agree.
- Relevant tests and safety checks pass.
- Downstream consumers and migration impact are understood.
- Remaining uncertainty is visible.
Outcome: A bounded capability advances from documented intent to validated, independently usable behavior.
Exit signals:
- The owning contract and acceptance criteria are versioned.
- Implementation and documentation agree.
- Relevant tests and safety checks pass.
- Downstream consumers and migration impact are understood.
- Remaining uncertainty is visible.
- Security, privacy, accessibility, licensing, and provenance.
- Documentation, architecture portals, examples, and onboarding.
- Packaging, release, compatibility, and self-hosting.
- Organization integration through explicit contracts.
- Observatory evidence and Pace conformance when those systems exist.
Optional managed services, enterprise controls, marketplaces, and the conversational organization compiler remain later architecture work. Current choices should preserve portability and avoid foreclosing them.
- Observed: The repository README establishes the intended boundary as the organization-facing GitHub profile, public defaults, contribution entry points, and fallback coordination surface; significant implementation remains incomplete.
- Decided for this draft: The repository owns the bounded concern described here and participates through versioned contracts.
- Proposed: Target systems and later roadmap phases remain proposals until accepted and implemented.
- Open question: Which parts of this draft should become active in the first independently versioned release?