cleandataengineering.aiAgent Harness, drawn simply
You are here: Tech stack › AV · Availability & disaster recovery

Agent Harness Tutorial · Tech stack

AV · Availability & disaster recovery

A lost server, zone or model goes unnoticed; a lost region is rebuilt from code and backups. Family: Control · around every turn.

AZURE OPTIONSZone redundancy, PostgreSQL HA◐ planned: not in devFront Door health probes◐ plannedGeo-redundant backups◐ plannedOUR CHOICEStateless servers + durable stateBicep + azdinfrastructure as codeOPEN-SOURCE OPTIONS(none named)· consideredWHO DOES THE WORKAzure gives 65% · we code once 25% · each agent team still does 10%
Dark boxes are what we run. Solid boxes are used or planned; dashed boxes were considered or dropped (crossed). The bar: grey is what Azure gives, dark is what we code once, hatched is what each agent team writes.
Why our choiceRedundancy is a platform feature you buy. Our part is staying stateless and reproducible from code.
OptionWhere fromVerdictWhy
Stateless servers + durable stateours✓ chosen
Bicep + azdours✓ choseninfrastructure as code
Zone redundancy, PostgreSQL HAAzure◐ plannednot in dev
Front Door health probesAzure◐ planned
Geo-redundant backupsAzure◐ planned
(none named)open source· considered

Not built yet in the claims assistant; designed in the Series.

How it is done: the real code

Cut from the live repositories each time the site is built, so it always matches what runs.

      geoRedundantBackup: 'Disabled'
    }
    highAvailability: {
      mode: 'Disabled'
    }
    authConfig: {
      activeDirectoryAuth: 'Enabled'
      passwordAuth: 'Enabled'