The first engagement

One arm in a spray booth

I’ll begin with a single robot arm spraying coffins in an investor’s business, after rehearsing the workflow on lab prototype arms. Access and the exact engagement still need arranging. The aim is a useful first account of the machine, followed by a second arm that can show what carries over.

The requirements cover reach, joint speed and torque, guard zones, interlocks, cycle time and the arm’s current configuration. Existing safety-rated controls stay in place; we work beside the customer’s engineering process.

A spray booth brings conditions an arm datasheet cannot establish: ventilation, explosive-atmosphere rating, solvent exposure, overspray, the booth’s protective stop, and coating thickness and cure. These need evidence from the installation. The lab rehearsal exercises the assurance workflow; the booth supplies its own physical questions.

My customers manufacture products with robotic equipment. They gain from faster commissioning, fewer surprises and better production. Machine builders and integrators can help us carry the service across related installations.

The signal

A controller requests fixture engagement, receives confirmation and starts the robot. After an interruption, yesterday’s confirmation may still be visible. Accepting it can start today’s routine before the fixture has confirmed today’s request.

Our worked model makes that failure inspectable. It compares two rules across their complete reachable finite state spaces, including cycles and optional environmental actions.

The failure takes five steps: request 1, acknowledge 1, restart, request 2, start using acknowledgement 1. The corrected rule lets both operations start with their own acknowledgements.

The model uses two sequential, non-wrapping operation identities. It checks confirmation at start; timeout and progress are separate questions. It has no PLC translation or physical fixture model. Delayed messages, signal integrity, scan timing and lifetime identifier reuse need further work before deployment.

That is what a checked result should give the reader: an exact claim, its scope and evidence they can inspect.

The requirements and the methods available

The first arm needs the following questions answered. Reach is the first robotics method to qualify; the available arithmetic checks do not supply a robotics model.

Each new checking method needs a core release. Changing a physical requirement into a different mathematical question requires Director approval; a formaliser cannot relabel it to obtain a result.

What a first engagement delivers

The customer supplies the arm and firmware identities, motion model, mount, fixtures, layout, candidate change, requirements and available measurements. We agree responsibilities, confidentiality and reuse rights. Missing inputs become visible gaps.

I’ll return a claim tree and matching human report, the work needed to close each gap, and a record of what the change affects. The forecast is about fifteen obligations: at most two or three checked leaves and twelve or thirteen typed gaps. The planned API gives the deployment a route to submit further evidence for review. A request for work grants no approval authority.

We will record specialist effort and failed attempts where measured. Core files edited must remain zero; rebuilding the core to serve the engagement fails that test. New platform code is measured, with zero expected on the second engagement.

Motion-profile and firmware outputs begin as unassessed observations under an admitted, monitored driver. Independent checking determines what they support. Simulation and vendor specifications keep their own evidence kinds; physical validity needs installation evidence.

The second arm measures the inheritance. Common knowledge may transfer while local timing or configuration needs renewal. Count the saving after that work and continuing maintenance.

Give the buyer a fair comparison

Compare Symbolia, the existing workflow and readily available tests on the same changes. Fix the property set in advance. Include permitted historical faults and blinded defects chosen by an independent engineer.

Measure missed and confirmed defects, unresolved questions, false alarms, review effort, specialist hours, elapsed time and accepted evidence. Separate a wrongly stated or translated problem from unsuccessful proof search.

This tests usefulness on the agreed cases. The programme turns the result into a decision about the next engagement.

Expansion path

The second arm can inherit the method, question structure and evidence templates. A related cell may also inherit controller meanings and component contracts. Each needs its own configuration, measurements and approval.

A new controller family requires its language, runtime and interfaces to be understood. Factory-wide coordination adds interactions and production modes. Process industry and mobile robotics add different dynamics and hazards.

I’ll expand where the knowledge already earned does useful work.