One application reference
Bring application purpose, release identity, health, and operating guidance into a consistent private reference.
Application case study
Atlas
A self-documenting application portfolio with verified release references.
Astro · TypeScript · OCI artifacts
From the application repository
Published project notes
Checking for accepted release documentation…
Project context
Why this project exists
Applications publish versioned metadata and documentation. Atlas turns those contracts into a consistent reference experience.
Ownership
An original Hallett Dev Labs application: the portfolio UI, Observer integration, documentation contract, and release automation are maintained together.
What it does
Application-owned documentation
Keep developer and operational guides with the application source, packaged as immutable documentation artifacts.
A curated public portfolio
Explain the applications and engineering behind the platform through explicitly selected public content.
How it fits together
Atlas
An Astro and TypeScript interface presents application and infrastructure references.
Observer
A separate service collects health and metadata for the private operational view.
Documentation artifacts
Data-only OCI images tie documentation to a release. Validated content synchronization updates the reference without rebuilding the UI.
Public edition
A separate image and content root use approved portfolio inputs and share the Atlas release process.
Engineering decisions
Separate health from knowledge
A failed metadata request should not change measured application health. Documentation remains available independently of application availability.
Make ownership explicit
Applications own their guides; deployment automation owns acceptance; infrastructure controls which sources and public pages are trusted.
Reduce release coupling
Validated metadata and documentation snapshots let application releases update Atlas content without requiring another Atlas image.
Operational approach
Releases pass through Stage validation before production promotion. That process includes a companion public image and independently validated documentation snapshots. Production acceptance, rather than a newly published image alone, controls public content updates.