Atlas node · Systems / Distribution · active publishing system

bseverns.github.io

The public portfolio itself as a distribution, distillation, and evidence layer linking projects, methods, archives, and source trails.

Repository →

What the site is doing

This site is a public instrument for reading the work. It does not try to mirror every private source; it distills what can be shown, what should be bounded, and where a reader can follow the evidence.

A portfolio can become a surface of polish that hides the labor beneath it. This one is being shaped as a map of claims, proofs, methods, archives, and withheld details.

The Atlas, method pages, catalog data, source trails, and archive roots make the public layer navigable without flattening the projects into a single style of proof.

The site should keep improving the public route from claim to artifact while refusing to expose private topology, participants, classroom data, or unfinished work beyond what can be responsibly shown.

What it is

This site is not just a brochure. It is the public distillation layer that connects current project pages, method notes, archive roots, and source repositories without mirroring the private source layer behind them.

What it lets people do

It lets readers move from public claim to public artifact to source trail, while keeping evidence status and archive lineage visible.

What is public now

  • Site source repo Current implementation source for the portfolio.
  • Atlas Relationship map across the fleet.
  • Methods Reusable patterns that help readers interpret the claims.
  • Catalog JSON Machine-readable summary layer for public works.

Evidence status

Status: active publishing system. The site already shows the lineage and fleet structure, and this distillation pass adds clearer public/private boundaries, evidence language, and reader paths.

Next proof object: Continue replacing generic placeholders with linked proof objects and redacted diagrams where the public claims warrant them.

What remains unresolved

  • Several legacy Atlas nodes outside the priority batch still need fuller evidence-aware copy.
  • Some public project pages still need stronger direct media proof.

Methods surfaced

  • systems-atlas A neighboring systems page about documentation and legible operations.
  • studio-notes The cross-project note layer that lives beside the public portfolio.

Source trail

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next