Technology · Language

Bash

Test harnesses, release scripts, proof runs and service glue across every system are shell.

ActiveKV · AgentOS · Helix · FAFO Core · Agent SwarmHarnesses, provisioning, glue
One serving cell · the result cannot be lost
server up
health wait
drive the client
cleanup
orange: the exit code, captured the moment the client returnsthe EXIT trap reports that capture last
A killed runtrapped, written as interrupted
  • 316shell scripts in ActiveKV, most of them validation and release harnesses
  • 32probes against the AgentOS work graph
  • 11checks in the integration platform's conformance suite, about 1,100 lines

Harnesses whose results cannot be lost

ActiveKV is judged by A/B runs on a quiet host, and a harness that misreports one cell can promote a regression. The main validation driver runs a matrix of serving cells, each named by prompt length, output length and concurrency.

I wanted the result impossible to lose, whatever happened to the run after the client returned.

A matrix of serving cells · illustrative
One row per cell
pass, from the captured exit code
fail, whatever cleanup did afterwards
interrupted, never a pass

Each row keeps HTTP status, exit code and health-wait time.

The release payload's entrypoint is shell too: it selects serve and diagnostic modes and redacts credentials from its logs.

The edge of a policy engine

AgentOS enforces policy through the coding CLI's hook system, and shell is its edge. Thin shims connect hook events to the Rust hook binary.

Before · shell hooks that had become policy

63 hooks

After · thin shims, one typed binary
Rust hook binarya parity port, then tested contracts

When shell hooks became policy, I ported them to Rust, because policy needs types and tests.

The contract suites for quality assurance and for the gatekeeper are shell, as are the probes against the PostgreSQL work graph. A probe that guards a fix is written to fail before the fix and pass after it.

Provisioning that stops instead of half-finishing

Helix needed a Microsoft 365 tenant provisioned repeatably. Tenant provisioning is portable bash, curl and Microsoft Graph, and each script stops with a specific exit code when a precondition is missing.

The test script for the meeting tools joins a real meeting and uses an EXIT trap so it always tries to leave. The Azure side of the media service is installed with PowerShell.

Provisioning, precondition met
blueprint
certificate
agent users
Provisioning, blueprint not ready
exit 3
stopped here
never run, nothing half-configured
Meeting test, an assertion fails
join
assertion
trap: leave

Loaders and installers

FAFO Core and Function Forge runs any function in a generic container, so updating a function needs no image rebuild. The API integration platform's conformance suite is shell too, covering the key surface, profile schema, wire format, error classification and build outputs. Agent Swarm member hosts are installed by scripts.

FAFO Core · one image, four modes
runtime binarymounted by the control plane
generic imageshell loader as entrypoint
job
capability
agent
infrastructure
Agent Swarm · pulled in parallel

Each image is used only when its digest matches the pinned manifest; orange is a mismatch, refused. Illustrative.

No core system logic lives in shell.