Atlas project production

Project Atlas

Hugo-based cross-repo documentation system for the Aether workbench. Atlas consolidates implementation evidence from many repos into one operational knowledge layer with project metadata, lifecycle state, playbooks, and relationship mapping.

Type: System
Lifecycle: Active
Last touched: 2026-03-25
Visibility: Public

Purpose

Serve as the durable cross-repo reference layer so implementation reality across the workbench remains discoverable, connected, and maintainable.

Current state

Atlas is actively maintained and now includes richer repo-level alignment from the 2026-03-25 workbench documentation pass, including refreshed README coverage and clarified lifecycle notes for key integration repositories.

Next step

Continue phased repo passes for medium-priority projects and keep lifecycle validation notes current where runtime ownership or scheduling evidence is incomplete.

Interfaces

Inputs

Repo-level documentation
Implementation evidence from workbench repos
Atlas front matter metadata

Outputs

Static Atlas/Showcase site
Cross-repo project references
Playbook and taxonomy navigation

Reality to Action trace

Reality Ingestion

Not in scope.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Artifacts

Project pages under content/atlas/projects
Playbooks, taxonomy term pages, and journal update notes

Operational notes

Constraints and scars

Atlas quality depends on disciplined updates from implementation repos.
Large workbench scope requires phased, capacity-aware updates rather than full deep reads every pass.

Reliability posture

Build failures block deployment. Content quality and link health checks provide guardrails before publishing.

Observability

GitLab CI logs
Hugo build diagnostics
content_quality_check.py
link_health_check.py

Security and privacy

Atlas can contain internal operational context. Keep sensitive runtime details, credentials, and private connection data out of published content.

Dependencies

Upstream

Aether workbench repositories
GitLab CI runner with Hugo and Python

Downstream

Onboarding
Operational documentation
Cross-repo maintenance and audits

Ownership

Owners

Josh Barton

Users

Technology Services, Maintainers and automation agents

Project Atlas

Role In The Ecosystem

Project Atlas is the documentation layer for the Aether workbench.

It is not a runtime executor. Instead, it connects runtime truth from implementation and orchestration repos into one operator-facing system map.

Operational Highlights

Hugo-based static site with structured project schema.
Canonical project catalog at content/atlas/projects/.
CI validation for content quality and link health.
Incremental cross-repo reconciliation as workflows evolve.

Key Relationships

aether - shell-based integration toolbox documented in Atlas.
Integr8r and Integr8r-rebase - runner-layer integration ecosystems.
google-classroom-guardians and BOUSD extract repos - implementation workflows reconciled into Atlas entries.

Validation Notes

Atlas structure and deployment are production-backed.
Some downstream project lifecycle labels remain intentionally conservative until runtime schedule/ownership evidence is confirmed.