The canonical ecosystem architecture and platform-control repository for the Ego Hygiene organization.
Hygiene owns the repository registry, cross-repository architecture decisions, platform policy, adoption model, organization contract index, and migration context. It does not own the implementations of every policy or product capability.
Current work is handed off through the repository-owned
CONTINUITY.md. Reconcile it against live Git and GitHub
evidence; it is not a substitute for the canonical sources below.
- Holistic architecture
- Repository catalog
- Migration plan
- Agent context
- Diagram sources
- Architecture acceptance decision
- Machine-readable repository catalog
- Repository catalog schema
- Generated repository catalog
- Repository-local context contract
- Repository context policy
- Deprecated repository context v1 schema
- Proposed repository continuity policy
- Repository continuity policy source
- Repository continuity policy schema
- Repository context v2 schema
- Proposed Agent-Ready Web integrated profile and conformance contract
- Agent-Ready Web profile source
- Agent-Ready Web profile schema
- Agent-Ready Web conformance evidence schema
- Agent-Ready Web compatibility fixtures
- Dependency-boundary register
- Dependency-boundary schema
- Generated dependency-boundary view
- Dependency-boundary guide
- Proposed Repository Intelligence contract
- Repository Intelligence schema
- Repository Intelligence vocabulary
- Complete quest fixture
- Proposed repository presentation profile
- Repository presentation profile source
- Repository presentation profile schema
- Repository presentation evidence schema
- Repository presentation fixtures
The accepted written architecture and versioned machine-readable catalog are authoritative. Rendered diagrams, local repository context, and future landscape sites are projections of those sources.
- ADR policy
- Accepted governing decision
- Proposed Repository Intelligence decision
- Proposed Agent-Ready Web foundation decision
- Proposed Agent-Ready Web discovery decision
- Proposed Agent-Ready Web capability and commerce decision
- Proposed Agent-Ready Web integration and conformance decision
- ADR reference template
- ADR migration guide
- ADR validation plan
- ADR-002 ratification evidence
- ADR front matter schema
- Repository ADR policy-reference schema
- ADR compatibility fixtures
- Organization contract index
ADR-002 and policy v1.1.0 are accepted organization authority. This repository provides their canonical schemas, fixtures, and reference checks; it does not claim that downstream fleet validation, generated decision/activity data, or dashboard publication is complete.
The public organization repository, egohygiene/.github, remains the
organization-facing inbox, profile, public defaults, and fallback coordination
surface. Hygiene is the canonical long-term home for ecosystem architecture,
the repository catalog, organization contracts, and cross-repository ADRs.
See issue #1 for the initial architecture import and issue #2 for the validated repository catalog contract.
Validate the existing repository catalog and its generated view with:
python3 tools/catalog.py --catalog catalog/repositories.yaml validate
python3 tools/catalog.py \
--catalog catalog/repositories.yaml \
check-generated \
--output docs/generated/REPOSITORIES.md
python3 tools/context.py validate
python3 tools/continuity.py validate-profile
python3 tools/continuity.py validate-repository --repository .
python3 tools/agent_ready_web.py validate-profile
python3 tools/agent_ready_web.py validate-fixtures
python3 tools/boundaries.py validate
python3 tools/boundaries.py \
check-generated \
--output docs/generated/DEPENDENCY_BOUNDARIES.md
python3 tools/boundaries.py scan \
--repository-root . \
--repository egohygiene/hygiene
python3 tools/intelligence.py validate \
--snapshot fixtures/repository-intelligence/complete-quest.json \
--vocabulary catalog/repository-intelligence-vocabulary.json
python3 tools/presentation.py validate-profile
python3 tools/presentation.py validate-evidence \
--evidence fixtures/repository-presentation/minimal.valid.json
python3 tools/presentation.py validate-evidence \
--evidence fixtures/repository-presentation/rich.valid.json
python3 tools/decisions.py decision \
--input fixtures/architecture-decisions/decision.proposed.valid.json
python3 tools/decisions.py decision-set \
--input fixtures/architecture-decisions/decision.superseded.valid.json \
--input fixtures/architecture-decisions/decision.accepted.valid.json
python3 tools/decisions.py policy-reference \
--input fixtures/architecture-decisions/policy-reference.valid.json
python3 -m unittest discover --start-directory tests --pattern "test_*.py"The Agent-Ready Web fixture command validates both mechanism compatibility and the five synthetic whole-profile conformance records. It does not assess or publish a live site.
The dependency-free Repository Intelligence and decoded ADR checkers are contract references, not fleet enforcement or full Markdown parsers. Production lint semantics belong to Egolint and reusable collection, generation, and publication workflows belong to Relay.