Security
Application boundaries, infrastructure hardening, authorization, evidence, and practical risk reduction.
See security reviewsTechnical writing for teams building, automating, securing, and operating real systems.
Discuss a systemRead about the systems BlueDot reviews, automates, and ships through three practical tracks.
Application boundaries, infrastructure hardening, authorization, evidence, and practical risk reduction.
See security reviewsAgents, tool permissions, human approval, observability, workflow design, and controlled integrations.
See AI automationApplications, APIs, data, deployment, maintainability, and the production concerns around the code.
See full-stack deliveryTechnical notes stay grounded in the systems, boundaries, and decisions they describe.
BlueDot IT's September 5 release work shows how to validate downloadable artifacts, repair a test harness without rebuilding the candidate, and keep platform claims tied to evidence.
A practical look at immutable inputs, exact-page verification, durable receipts, and compensating rollback in an unattended publishing pipeline.
This week was about public beta evidence, fail-closed publishing, queued social adapters, live system notes, and keeping automation narrow enough to audit.
Ódinn Forge is a local-first personal AI agent runtime built around durable memory, model freedom, audited tools, explicit approvals, and release evidence you can verify.
This week focused on proof-driven automation, public-post guardrails, remote report delivery, sensor cleanup, and infrastructure work that fails closed.
A practical look at a High-severity OpenClaw vulnerability where Browser CDP discovery could accept WebSocket URLs that policy should have blocked.
This week was about recovery paths, scoped automation, greenhouse signal quality, robotics control, and infrastructure that leaves proof when it acts.
A practical week across automation, greenhouse IoT, robotics, printing, security checks, and client infrastructure. The useful lesson: small systems need boring proof.
How I constrained ffmpeg memory and CPU to stop the radio automation from OOM-killing the VPS
Bring a security concern, automation idea, or application problem to the same conversation.
Discuss your project