Skip to main content

/data/src Atlas

This site documents the current project landscape under /data/src.

It is intentionally broader than a single project README. The goal is to make the workspace legible at three levels:

  1. Portfolio scope: what kinds of work live here and how they relate.
  2. Per-project scope: what each repository or working directory appears to do.
  3. Status clarity: which things look like products, which are experiments, which are infrastructure, and which should be treated as restricted or archival.

Top-level structure​

  • products/: the commercial or product-shaped work.
  • experiments/: exploratory apps, framework spikes, and prototype interfaces.
  • infra/: operational tooling, migration scripts, and publishing pipelines.
  • private/: restricted research or security-adjacent material; document carefully and share selectively.
  • archive/: superseded prototypes kept for historical context.
  • vendor/: third-party code vendored into the tree.

Strongest active clusters​

Articulate​

The most substantial product family in the tree. It includes a headless WordPress commerce platform, hardened WordPress runtime work, mail infrastructure, and related operational tooling.

DetCordon​

A separate security track focused on containment-first malware observation rather than generic WAF blocking.

Shipwrecks.se​

A niche vertical application with enough app surface to become a real user-facing data product if deployed and tightened.

How to read the docs​

Use the sidebar to move by category:

  • Products for the things most likely to become sellable offers.
  • Experiments for exploratory work and UI or architecture spikes.
  • Infrastructure for host, packaging, publishing, and migration tooling.
  • Private for restricted material that should not be treated as public product documentation.
  • Archive for superseded codebases.
  • Vendor for third-party code checked into the repo.

Where a project already had a README, these docs summarize and reframe it. Where a project was poorly documented, the page is generated from the file layout, package manifests, and neighboring project context.