Posts

08 Connecting Edge Sites Through NAT the customer's networkno rule gets opened for youEdge server10.77.0.2no inbound listenerCustomerrouterNAT outwardHub10.77.0.1listens on UDP 51820never dials a sitethe site dials out, UDP 51820the NAT mapping carries every replynothing dials inkeepalive every 25 sholds the mapping open Robot FleetEdgeDeployments
07 Separating OS and Application Updates App planeseconds, reversible by another commitGit commitapp planeControllerapplies itPod restartsedge serverno rebootOKOS planerare, reversible by switching slots backRAUC bundlesignedInactive slotinstalled, not liveMaintenance window+ safe-to-reboot gateboth must clearswitchRebootedge serverNeither path blocks the other. A build can sit in the inactive slot for dayswhile app releases keep shipping through the top path without waiting on it. Robot FleetDeploymentsOta Updates
06 Platform Adoption: Tooling, Training, Buy-In TEAM PERFORMANCETIMEOld status quoResistanceChaosIntegrationNew status quoChangeTransformative idea Robot FleetDeployments
05 A Reference Architecture for Robot Fleets Hubthe one reachable addressEdge serversoutbound only, to HubRobots(no internet access)HubInternetno route between sitesN robotsN robots10.1.0.0/2410.1.1.0/24Site ASite Blocal linktunnelgateway Robot FleetEdgeGitops
04 What a Fleet Platform Costs BeforeSpeed1 monthControl3 to 6 monthsVisibility3 monthsSecurity6 monthsCompliance3 months Robot FleetDeploymentsOta Updates
03 Updating Robots in the Field Robot FleetDeploymentsRos2
02 PROVEN: Six Checks Against AI Slop Six checks against AI slopOn top, a diff moves along an unguarded, wobbling path straight to a merge, with only a magnifying glass hovering nearby. Below, the same diff moves through six named gates — Planned, Reviewable, Observed, Verified, Exercised, Narrated — in a straight line to a trusted, merged origin.SLOPPROVENskimmed oncemerged, unverifiedPlannedReviewableObservedVerifiedExercisedNarratedtrusted, merged AICode ReviewOpen Source
01 Zero Overhead MetaHomelabAI