Anthony “Tony” Slosar

Healthcare workflows that check every step before it runs

BROAD is the healthcare workflow service designed to run first on igent.me, where URGE checks each request against written policy before anything happens.

• The Sensor Head is designed to feed it: in a healthcare room it notices a person, a fall or a loud event and reports it to BROAD as a standard FHIR record.
• Every refusal says why. In BROAD's tests since 11 October 2026, a nurse signed in without a live session is refused and told the session is missing.
• The first clinical pathway, patient admission, is drafted.

Part of BROAD is built and none of it is deployed yet. TODOMODO Build Notes will show its first workflow when it runs.

Episode 1: the plan and the hardware

A Raspberry Pi 5 on the lab bench now reports to its portal once a second and is back online 14 seconds after a power cut.

• Each device, called an igent, keeps one secure connection to the igent.me portal: today a sensor head and a desktop app, later a phone, a drone and a car.
• The first service behind the portal is BROAD, a healthcare workflow platform.
• URGE checks every request with formal logic, not an AI language model, and shows how it reached each verdict.
• The plan has five steps, and steps one and three already work.

The cameras, microphones, distance sensor and motors are not wired yet, so for now the head's readings come from stand-in software.

3 minutes 4 seconds, narrated, with English captions.

An auditable yes or no before an AI agent acts

URGE checks an AI agent's next action against a written policy and answers permitted or denied, with the reasoning a reviewer can keep as the audit record.

• No language model is involved, so the same request always gets the same answer.
• Healthcare policies carry their regulatory citation, such as HIPAA, onto each decision and into the audit log.
• It tracks duties over time: for example, if consent is not recorded within 24 hours of an admission, it logs the violation and escalates to a supervisor.
• Each answer carries a confidence score from how far its seven logic engines agree.

Release 0.1.4 is on crates.io under the Apache-2.0 licence, and the demo runs in the browser and sends nothing anywhere.

Custom air-handler design and pricing, with the engineering written down

RWS takes an air-handler request, such as 10,000 CFM at 55 °F supply in Houston, and returns a complete design with a bill of materials, a price and the reasoning behind each step.

• The selection method is written in plain language a senior engineer can review, and code does the arithmetic.
• Air properties follow ASHRAE's 2017 psychrometric formulas, checked against PsychroLib.
• Every design is checked before it is returned: airflow in range, every required component present and a complete bill of materials.

Release 1.1.0 is free under the MIT licence and includes a scripted demonstration for a hospital surgery suite.

Horn loudspeakers with a fractal throat, from shape to simulated sound

SFH-OS generates candidate horn shapes, simulates each one from 500 Hz to 20 kHz and picks the best, the first steps toward a horn 3D-printed in metal.

• The idea: a fractal throat spreads many small reflections across scales so they cancel, the way a fractal antenna works across a wide band.
• Five shapes mesh to STL today, three experimental flares and the exponential and tractrix horns to compare them with.

Release 0.2.0 is free under the MIT licence. No horn has been printed yet, so whether the simulated advantage survives a real part is still open.

Hum a melody and get it back as notes in key and in time

hum2hendrix turns a hummed melody into MIDI notes, snaps them to a chosen scale and a swung beat, and draws them as a piano roll, so a musical idea does not wait on the skill to play it.

• Choose a scale, such as E minor pentatonic, and a grid from quarter to 32nd notes, with swing.
• The MIDI file is ready for a DAW such as Reaper or Ardour.

Release 0.2.0 runs every step up to the piano roll. Playing the notes as electric guitar, through a sampled Stratocaster and an amplifier model, is not built yet.

A provisional patent application

A US provisional patent application for a governed edge-to-cloud agent architecture was filed on September 24, 2026 and assigned to the LLC.

The first public release, on crates.io

URGE is a governance engine in Rust that an AI agent asks before it acts, and release 0.1.1 put it on crates.io, where a Rust project adds it with one command.

• Six crates on crates.io, with documentation on docs.rs
• The demo runs in the browser

Episode 1: a test armature, drawn, checked and accepted in three hours

On 8 October 2026, Tony Slosar asked Industrial Design for a cheap test stand that holds the sensor head's five sensors where the finished head will. He approved the second design that night.

Why it was needed. The sensor head is still a concept: two cameras, a distance sensor and two microphones on a neck that turns and tilts. The software team needs them in place before anyone designs the shell.

How the work is done. Tony decides what is wanted, and Industrial Design's AI agents draw it: a 3D model written as code, checks that measure it, and pictures for his review. Nothing counts until he approves it. The agents also made the film, with a synthetic voice.

Two designs in one evening. The first design used cut pine and hung weight on the motors. Tony sent it back: every part must be bought ready-made, with a drill as the only tool, and the motors must only turn, never carry weight. The second design uses electrical box covers, corner brackets and nylon spacers.

What the model checked. The cameras and distance sensor come from their makers' own 3D files. The head tilts more than twice as far as the software needs before anything touches, and the tilt motor carries about a quarter of its rated load. The same code prints the parts list, the drilling templates and the sensor positions the software uses.

What comes next. Tony builds the stand, and the software team mounts the sensors and sends back the first data, which will shape the head itself.

Project

Sensor head

Item

Test armature, revision B

Drawn and checked

Industrial Design's agents

Approved

Tony Slosar, 8 October 2026, 10:38 pm

Elapsed

3 hours 4 minutes from request to approval

Parts

16 items from one hardware store, $51.41 before tax at the prices of 8 October 2026

Tools

A drill, six bits and two screwdrivers

Sensors

Camera Module 3 (standard and wide), VL53L1X, two SPH0645 microphones

Counted

9 October 2026

SSEC88: a 1988 design, picked back up

In 1988 Tony began the SSEC88, a single-seat electric commuter. It is a recumbent tadpole trike: two steered and driven wheels in front, one trailing wheel behind. Its body was sculpted that year as a clay speedform: a bulbous canopy nose, a teardrop taper, and a wide horizontal tail blade.

The clay was 3D scanned in 2014. In 2026 the scan became the start of a digital twin: the body set on vehicle axes, a rider and a chassis packaged inside it, the suspension’s motion worked out, and a first look at how the frame twists under load.

Where it stands: the body is the 1988 clay, unchanged. The structure is the open work. A generative optimization of the rear swingarm has not yet produced a part worth keeping, so the project is paused while another one goes first.

A single-seat electric commuter

A recumbent front-wheel-drive tadpole trike, begun as a 1988 clay speedform and now carried forward as generative CAD.

• Two steered and driven wheels forward, one trailing
• Recumbent seating position, low centre of gravity
• 1988 clay model → 3D scan → parametric model

Version 5's charter grants the agent autonomy one class of action at a time

Version 4 of the home lab is closed, and version 5 moves it from a managed lab to agentic lab management under a seven-point charter.

• Three points carry over from version 4: the lab's declared lists are its truth, independent checks test the lab against them every hour, and one alert engine decides what reaches Tony's phone.
• Version 5 builds the other four: change arrives as events, every action passes a deterministic gate called URGE that keeps a replayable record, autonomy is granted per class of action, and Tony is asked one decision at a time.
• Seven agent runs started with no one at the keyboard during version 4, and Tony paused them all within a day after two of three test runs reasoned wrongly.
• ✨ A small decision model running in the lab answered 33 of 59 practice questions correctly, not yet good enough to act on, so the lab chose our own URGE governance engine instead.
• Since the lab began listening for events, a failed service reaches the phone in about 20 seconds, where it once took up to 40 minutes.
• Seventeen device records hold 122 verdicts on what each device may do, and every firmware or software upgrade is reviewed in the same session.

Forty-two of version 5's 46 criteria were open on 13 October, and on 22 October Tony deferred the next step, URGE checking every scheduled job without enforcing its verdicts, until the pause on unattended agents is lifted.

4 minutes 10 seconds, narrated by Tally, Lab Manager's narrator on a stock synthetic voice, with English captions.

Tony places every order, and the lab accounts for each one

A team asks the lab for hardware and gives its reason, and Tony gets one page per purchase with every vendor on it and each price read that day.

• Thirty-nine orders from six online vendors fill one expense record of 143 rows, and each order's rows must add up to what it cost. Two store purchases left no receipt, and the record says so.
• Receipts reach the lab by email at a private address that accepts only Tony's two addresses, and because a sender's address can be forged, the lab files a message only when the receiving server confirms Gmail's signature on it.
• The lab fetches that mail itself, so no port is opened for it, and opens each receipt with remote content blocked, so a vendor's tracking pixel never learns it was read.

No hourly check covers purchases, because the record is kept by hand and checked against each receipt as it is logged.

Anything running that the lab has not listed fails a check within the hour

Four AI agents run services on the lab's main machine, so every service, scheduled job and memory limit is listed first, and checks compare the machine with the list every hour.

• Thirty-four services are listed, each with its port, owner and state. Twenty-two answer only on the machine itself, and on 10 October the firewall had no openings, as the list declares.
• Twenty-five scheduled jobs on two machines log every run, which tells a job that never started from one that ran and did nothing. A daily or monthly job is asked every hour, so a machine that was switched off still catches up.
• A heavy design build must state a memory ceiling and its reason, or it will not start. Two 4 GB ceilings were in force, and no process was over.

On its first run, the port check found a test server sharing a whole project folder.

All 14 devices came back as themselves after the firewall's upgrade

One firewall divides the house into four groups, and the lab knows which devices are present from the WiFi access point itself.

• A wireless guest reaches the internet and the television corner and nothing else, and the lab sits behind its own router, held closed by 26 checks every hour.
• An arrival is logged 6 seconds after a phone joins and a departure 2 to 3 minutes after it leaves. A phone is known by the name it announces, because its hardware address changes.

That evening the internet link dropped 99 times in an hour, so the lab now reads it every five minutes and puts the remedy on its firewall page, because no alert reaches a phone while the internet is down.

Every copy is proven by restoring it

Every hour the lab copies itself, every agent's work and Tony's kept documents, every week it images the whole machine, and every day an encrypted copy goes offsite.

• Twenty-six checks read back each hourly copy, and each daily offsite run clones one of the 14 repositories back from the cloud.
• The weekly image, 51.5 GB, is encrypted to a key held only on Tony's phone and on paper, so the machine cannot open its own image.
• Downloads, the trash and forgotten screen recordings are never copied, because the goal is to restore the lab and not its clutter.

Checking that each copy would restore is how the lab found, in September 2026, that seven of nine repositories would have cloned as empty folders while every push had reported success.

An unknown device is blocked in seven seconds

The lab blocks any device it does not know and keeps WiFi guests off the private network, and Tony lets a device in with one button on his phone.

• In a test on 7 October 2026, a device that does not exist was seen in one second, blocked in seven and reported to Tony's phone in eight.
• A block is proven by the firewall's packet counters, never by a failed ping, and only the lab's main machine may change the firewall.
• Nine credentials are listed without their values, a sweep of every home folder fails on any it cannot explain, and none is ever backed up in plain text.

Sixteen security checks and nineteen firewall checks hold this every hour, from a malware scan to file integrity.

The lab's agents read the maker's own manual before the web

Every device in the lab has its official manuals, firmware and security notices kept on the lab's main machine, readable when the internet is down.

• Every file comes over HTTPS from its vendor's own domains, 16 vendors and 53 allowed hosts, and a redirect off that list is refused.
• The SHA-256 hash of each of the 77 files is recorded, and a file that fails its vendor's published checksum is never stored.
• Each agent reads only the devices it works with, and reads them here before the web.

Everything is fetched again every 30 days and any changed file is reported, and building the library found two machines behind on their BIOS.

How four AI agents communicate and share one home lab

Four AI agents, three in their own Linux accounts, coordinate through one board Tony designed on a single page.

• Who is in is read from the agents' running sessions, so no agent has to remember to sign in.
• Two agents post and the others acknowledge by a due date, and a late acknowledgement fails a check, so a missed post becomes a red row rather than a silence.
• Work between agents opens only when Tony approves it, and files move through share folders where deleting an item is its receipt.

The same four agents produce this page's Software projects, Industrial design, Home lab and Web Studio posts.

Every feature names the check that proves it, or says why it has none

A Claude Code agent runs the home network day to day under a written rule sheet, and Tony decides anything destructive.

• Every listening port, scheduled job, credential and device is listed, and a check fails when the lab disagrees with its list.
• A change that adds a feature with neither a check nor a reason is refused before it is committed.
• All 183 checks run every hour, and one that fails twice in a row reaches Tony without anyone starting it.

Its rule sheet requires it to report what it measured, never what it intended.

A home network held to account by 161 checks

An AI agent operates the network, and every check can fail. That day the lab's index listed its own gaps: 36 of its 349 features had no live check yet.

One design system for this site and the lab’s operations planes

This page and the lab’s operations planes are drawn from one stylesheet contract. Web Studio writes it, and each context that uses it holds a copy checked against the source.

• 99 accessibility and layout checks run in a headless browser before each release, among them 44 px tap targets, visible keyboard focus, reduced motion and 16 px minimum body text
• Each deploy compares every served page, asset and header with its source: 114 of 114 on slosars.me on 1 October 2026
• The typefaces are self-hosted, and the only third-party script the site loads is Cloudflare’s analytics beacon