The lab

The systems I build run on e-lab.dk. This page shows how they are put together.

e-lab Status on e-lab.dk

How the systems are built and run

PEOPLE AGENTS When something has to change, the brief changes. Nothing is corrected by hand in the output. 1 Brief One file per agent says what the job is, which sources, how often, and what counts as done. 2 Build AI writes the code from the brief. Tests run on synthetic data before anything is shown. 3 Accept A person tests the result against the brief. Plugins by ear, the register against held-out data. 4 Run On a schedule. Reads registers, own files and mail as data, read-only. Writes the run and a draft. 5 Decide A person reads the draft, approves any change and does the sending. Exceptions land here. Ledger Every run and every change of status, kept in plain files. The site is generated from it. Nothing on it is typed by hand. Guardrails that hold throughout •Agents never send. •Mail is read as data. Instructions inside a mail are ignored. •Names are removed before anything is stored. •Keys sit outside the code and never reach the site. •Access to hosting and mail is read-only until a person approves a change.

Taking it to the next level

A more complex operating model rests on people, decisions and data as much as on code. The difference shows in six places.

In the labIn a larger operation
PeopleOne person designs, approves and fixes.Named owners for each system and each step, and people trained to run them when the designer is not there.
Decision rightsI approve every change.Agreed rights over who may change a rule, a process or a system, and who signs off.
DataSmall data sets, public or my own, corrected by hand when they are wrong.Shared definitions, an owner for each data set, and quality measured and fixed at the source.
ProcessRuns on a schedule and is checked when something looks off.Documented processes, service levels and a change procedure that still holds when people move on.
TechnologyAI writes the code. I test it against the result.Engineering standards, code review, tests that someone owns, and security review.
ControlA ledger of every run.An audit trail, risk management and reporting a board can rely on.