Skip to content
Hearth & Code

Workbench / technical system orientation

Field Journal

H+C / 10Workbench

I build technical surfaces for inspectable work.

The Workbench is the software-facing edge of my studio: a bounded web tier, Rust service authority, PostgreSQL catalog, and source-only Kubernetes delivery candidate.

Inspect the runtime map

From my workbench

Hearthside thought projection · review requested
I want agents to behave like good workshop roles.

A comparer, critic, tester, or bounded implementer should return what it used, what it changed, what it could not decide, and where judgment still belongs.

Read the working archetype →

01 / Public technical boundary

A narrow service edge. A private operating interior.

The public tier reads a small catalog projection. It does not receive private Hub content, retain visitor profiles, expose cluster-internal services, or treat a payment identifier as personal identity.

Public
Static research pages and a TypeScript catalog projection.
Service
Rust owns validation, readiness, policy, and catalog responses.
Data
PostgreSQL holds catalog records only in the current candidate.
Private
Operations, source systems, agents, and dashboards remain network-bounded.

02 / Runtime map

Four layers, four responsibilities.

The implementation is deliberately small: presentation cannot own native effects, the service cannot infer identity, and the database cannot become a shadow profile store.

  1. 01 / WEB

    TypeScript projection

    Responsive catalog, explicit loading and unavailable states, one same-origin request.

    Two-replica candidate
  2. 02 / API

    Rust authority

    Health, readiness, typed catalog, narrow routing, and internal metrics.

    Two-replica candidate
  3. 03 / DATA

    PostgreSQL catalog

    One bounded catalog table with idempotent migration and seed.

    Single-instance candidate
  4. 04 / OPS

    Kubernetes delivery

    Network policy, probes, resources, disruption budgets, alerts, and backup source.

    Source only · not active

03 / Delivery posture

Built for review before release.

The application and deployment sources have local test evidence, but no immutable images have been published and no Argo application, DNS record, or live cluster release has been created. This surface explains the architecture; it is not a production-status claim.