Building and validating
The recent engineering work is concentrated in MeshSat and Territory Grounder. I direct AI-assisted implementation, choose the architecture and test what comes back. That does not turn a passing test into a field deployment.
MeshSat
Prototype · field validation next
Recent work connects Reticulum/LXMF messaging across the Bridge, Hub and apps, improves kit access and public-warning handling, and develops the portable hardware. Feature availability varies by transport and client.
Next: The public plan is a six-month field programme starting November 2026: two portable kits for Dutch volunteer organisations, satellite measurements including failures, and usability work.
Capabilities, limitations and sources
Territory Grounder
Experimental · mode-gated actuation
Recent development concentrates on evaluation, recorded harness changes and testing proposed improvements. The hard part is showing when an agent should act—and when it should stop.
Next: Publish stronger evidence from real-action prediction checks, bounded canary runs and reproducible evaluations before widening confidence in autonomous operation.
Capabilities, limitations and sources
Published work with outstanding validation
CubeOS
Beta · untested pre-releases
No substantive committed development appeared in the inspected repositories during the last 90 days. I am keeping the published beta visible without presenting a new release as imminent.
Next: Hardware and installation validation is the outstanding release gate. There is no verified date for a production-ready release.
Capabilities, limitations and sources
MuleCube
Pre-production · delivery unverified
The inspected product website has no substantive commits in the last 90 days. Current availability needs clarification before making a new delivery commitment.
Next: Confirm hardware and content readiness and publish a credible availability update. No revised shipment date is established.
Capabilities, limitations and sources
Operating and learning
I continue to work on the multi-site lab: Kubernetes, Cilium, BGP under AS214304, storage and GitOps. It is where I can own the consequences of an architecture decision, including the inconvenient ones. Agentic ChatOps records the earlier operations platform that informed Territory Grounder.
The June 2026 inventory counted 13 Kubernetes nodes across two sites: 7 in the Netherlands and 6 in Greece. Earlier references to 7 described the Netherlands cluster alone. A Netherlands snapshot from 28 October 2026 still records 7; a comparable current whole-estate count has not been verified. Historical counts are not live capacity.
Learning remains practical: understand the infrastructure well enough to explain and debug it without asking the tool that wrote it. I am not treating an old exam-preparation note as a current certification.
Research, at a different pace
- logos tests claims about undeciphered scripts. Recent work is corpus checking and watching new evidence, not a claim to have deciphered Linear A.
- groundnet is a draft protocol for sharing remediation knowledge that each receiving system must validate locally. It is a specification, not an operating network.
- Setun Reloaded has a balanced-ternary CPU demonstrated on an FPGA; its neural-network accelerator remains simulation work. The documented next step is a combined CPU-and-accelerator hardware build.
These are research projects, not announced businesses. Projects separates them from the product work.
This is a Now page. Plans are plans; the dates above say when I reviewed the evidence.