Systems nominalUTC --:--:--Session 00:00:00Frame rate --Addresses shown 000

Built in the shed, with AI

Built for the climb.

Radio kit, network tools, engineering models, AI skills, apps for the bike and the kayak, and the air traffic tools where it all started. Each one started as a real problem. I set the requirements, AI writes the code, and I test it until it’s useful.

See the apps Fly the 3D airspace ASTERIX case study

3D airspace: simulated traffic only

Simulated airspace · drag to orbit
Point at an aircraft

Route 1 · apps Engineering & AI Surveillance data, network tools, radio, systems engineering, verification and AI development. Show these apps Route 2 · apps Personal projects Cycling, kayaking, detecting and other outdoor and workshop apps. Show these apps

Start here

Three Tools. Start With These.

If you only look at three things, make it these. Each card says the problem, what I built and how I checked it. All data shown is simulated.

Evidence figures come from my own bench tests, run on simulated data. The Feed Suite and Simulator clips are simulated demos made for this site, not recordings of the tools.

My role

AI Types. I Engineer.

“AI writes the code” does not mean the engineering is done for me. The model is the programmer. I am the systems engineer who decides what to build, how it is checked and whether it is right.

What I Do on Every Tool

Define the problem and the interfacesInputs, outputs and formats, traced to a published standard where one exists.
Write the requirements before any codeEach one gets a test or check that will show it is met.
Investigate how the format really behavesThen turn that into made-up test data that still exercises the awkward cases.
Choose the verification methodInspection, analysis, demonstration or test, chosen per requirement.
Review every failureTrace it to a cause, number it and keep it in a defect record.
Challenge the generated codeAsk for the edge cases and reject answers that look right but are not.
Decide if each requirement is metAnd say plainly when it is not, or has not been checked.

What the AI Does

Writes and refactors the code from my brief.
Drafts test scaffolding, which I then check.
Explains code and options when I ask.

What it never does: decide what correct looks like, or sign off a result.

Example: in the Feed Suite, most faults sat at the seam between 2 parts that had each passed their own tests. Finding them needed an end-to-end check, not more code.

Systems engineering

Need to Evidence. Every Tool, Every Time.

The tools on this page are small, but they are built the way a system is built. Each one starts from a stated need, gets requirements traced to a published source, is verified against those requirements and validated with the person who asked for it. This section maps that work to the life cycle processes of ISO/IEC/IEEE 15288:2023, using only facts from the tools below.

Figure 1

The Vee, Applied

Select a stage to see what I do there and which tools show it. Dashed lines join each design stage to the stage that checks it (after Forsberg & Mooz, 1991).

Table 1

Practice to Evidence Traceability

Each row is a systems engineering practice, the 15288 process it belongs to, the evidence in my own work, and how that evidence was verified. Select a tool name to open its card.

Practice	15288 process	Evidence in my work	Method

I InspectionA AnalysisD DemonstrationT TestThe 4 common verification methods

Case study

ASTERIX Feed Suite, Through the Life Cycle

A transmitter and receiver for surveillance data feeds, built for Windows, Linux and 2 single-board computer cards. All figures come from its own test and defect records. Test data is simulated.

Figure 2. Simplified, SysML-style block view, drawn from the suite’s evidence summary. The orange ring marks the interface where most faults were found.

196,852Records, 0 gaps

11/11Feeds passed

649Automated tests

15Faults traced

Read the full case study

Honest limits

What This Is Not

These are independent and prototype tools. None is certified, and none forms part of a formal safety case.
Verification is by my own tests and reviews. No independent body has assessed them.
AI writes the code. I control the requirements, the tests and the acceptance, and a passing test is evidence, not proof.
All radar, radio and network data shown is simulated. No operational data is used.
Where a requirement value was unknown, the tools hold a placeholder rather than an invented limit.

References

Sources

Forsberg, K., & Mooz, H. (1991, October 21–23). The relationship of system engineering to the project cycle [Conference paper]. Joint conference of the National Council on Systems Engineering and the American Society for Engineering Management, Chattanooga, TN, United States.
INCOSE. (2023). INCOSE systems engineering handbook: A guide for system life cycle processes and activities (5th ed.). Wiley.
International Organization for Standardization. (2018). Systems and software engineering: Life cycle processes: Requirements engineering (ISO/IEC/IEEE Standard No. 29148:2018).
International Organization for Standardization. (2023). Systems and software engineering: System life cycle processes (ISO/IEC/IEEE Standard No. 15288:2023).
National Aeronautics and Space Administration. (2016). NASA systems engineering handbook (NASA/SP-2016-6105 Rev2).

AI Writes the Code. I Decide What’s Correct.

I’m not a programmer. I’ve spent 30 years in engineering: defence, air traffic, medical imaging, networks and field service. Since June 2026 I’ve used AI as the programmer while I work as the systems engineer, all of it in my own time, on my own kit. NOTE 9

The Loop, Every Time

Real problemSomeone brings a repetitive job and a made-up example file.
RequirementsI trace them to a published standard, with a test for each.
AI buildsI brief the model like a contractor: purpose, inputs, standard, good result.
I verifyAgainst the standard and against real files, because the code can look fine and still be wrong.
FeedbackThey tell me what’s wrong.

Then round again. The best fixes start with “that’s not how we actually do it.”

What I Can Do with AI, and the Proof

Skill	What I actually do	See it in

The Climb So Far

Mid-June 2026First build: one HTML file that encodes every plot as real ASTERIX and decodes the same bytes back.
June 2026Within days it was decoding large recorded files at full speed.
August 2026The toolkit replayed long recordings in a 3D airspace view.
September 2026A 15-minute talk on how it was built and checked.
October 2026A cited knowledge base design, a brand system and this collection of apps.
November 2026This page rebuilt with Claude Code and audited with Lighthouse.

What I’ve Learned NOTE 10

Knowing what correct looks like is the bottleneck now. Writing code isn’t.
AI gets things wrong with total confidence. Engineering discipline makes the output trustworthy.
Be careful what data you demonstrate with. Anything shared uses made-up values.
Design for the operator. Most of these run in a browser, in one file, with no install.
The human keeps the decision. The tools take the drudge work and show their reasoning.

Everything I Have Built

Select a card for the full story. Card screens are illustrations, or short clips on made-up data. Two clips are simulated demos made for this site.

One Rider. A Bit of Everything.

I’m Paul Sloper and Slopes is my workshop label. Road, track, touring and a 987-mile End to End on the bike side; air traffic engineering, radio and single-board computer builds on the other. These apps come from the second half, with a few that help the first.

Scrubbed for sharing

IP addresses, port numbers, hostnames, site names, people’s names, frequencies and customer details are removed or generalised on this page. It describes what each app does, not where it runs. Where an app has a short clip, it shows the app running on made-up data. The Feed Suite and Simulator clips are simulated demos built for this site instead, so no real airfield or network data appears. Brand names, real site names and airline callsigns were swapped out before recording.

Got a Repetitive Job? Bring a Made-Up Example File.

That’s where every one of these started. Find me at @cyclingslopes or email info [at] slopes-creations [dot] co [dot] uk.