Acorn Labs

We built remote execution and left it switched off.

Our own record, still being checked

What happened

On 21 September the way in for remote work was written down with remote execution empty. Nothing was switched on. On 22 September the piece that would run that work was built, and left unarmed. The command refuses to run until Chris arms it.

How it was caught

It was not a fault that slipped out. The same morning, another model attacked it. The command still refused. It held.

Evidence

Both days were written down. The attack was recorded as held. The work was then kept, still unarmed.

What changed

Remote execution is built. It is not armed. The command will not run until Chris arms it. The attack did not arm it, and keeping the work did not arm it either.

Why an owner cares

Able is not the same as allowed. Building the switch is not the same as throwing it. Chris decides what is switched on. This was our own machine.

The log