Obsta Labs

Structural control for cloud infrastructure and AI agents

We build control systems for engineering uncertainty: what gets spent, what gets leaked, what gets decided, what reaches the model, and what silently goes wrong.

Principiis obsta — resist the beginnings. Fix problems at the structural level, before they compound.

We are not model vendors. The models are becoming beautiful and useful. Obsta Labs builds the other side: the context operating system around them. Hiveram keeps the shared truth. NeuroRouter decides what slice enters the live model window. Hivebus keeps intake and evidence explicit before execution begins. tokencontrol runs ready work through the execution layer. Verdict enforces policy at action boundaries. VectorCourt stress-tests decisions before they become expensive.

The context operating system

This stack exists for teams that refuse to choose between one giant fragile session and total amnesia. The system promise is simple: architect once, move bounded truth when needed, execute with the cheapest capable surface, and apply results back without making authority ambiguous.

The four promises

No forced migration as sessions age. No transcript replay when a fresh agent takes over. No hidden sync magic that confuses local experiments with shared truth. No premium-model spend on work that cheaper execution could handle.

1. Architect the work A senior model or operator frames the task once, captures the constraints, and locks the reporting contract into the shared graph.
2. Rehydrate with a mission briefing Fresh sessions start from the current work contract instead of replaying the entire conversation that led there.
3. Execute on the right tier Focused execution can happen on a cheaper or more specialized agent without rediscovering the project from scratch.
4. Return bounded results Bundles, checkpoints, and provenance keep what flew out, what came back, and what was applied visible.
NR-only Local focus shaping, continuity protection, and session mobility for teams that need better live context before they need a shared work graph.
Hiveram-only Shared truth, portable bundles, checkpoints, provenance, and handoff across agents, machines, and disconnected environments.
Combined Hiveram stores the graph and portable bundles. NeuroRouter decides what slice of that graph enters the live model window. The other layers add intake, execution, and policy without collapsing the boundaries.

Cloud Infrastructure

SpectreHub

Cloud waste detection platform. 20+ open-source CLI scanners across AWS, GCP, Azure, Kubernetes, and databases — unified into one system of record.

Agent & Reasoning Control

Verdict

Enforcement runtime for autonomous agents. Policy at execution boundaries — kernel-level on Linux, system-level on macOS, API-level on Windows. Works with Claude Code and Codex.

NeuroRouter

Context operating system for live model windows. It shapes the active slice of work for Claude and Codex, preserves continuity, and keeps long sessions from rotting into expensive guesswork.

Hivebus

Typed coordination fabric for issue intake, evidence, clarification, and promotion gating. Keeps why work exists explicit before execution begins and hands off cleanly into the canonical ledger when teams enable downstream execution.

Hiveram

Shared AI work graph and portable handoff layer. Canonical work orders, mission briefings, checkpoints, provenance, and authority-aware bundles for agent fleets.

VectorCourt

Decision governance engine. The Council turns ambiguous problems into structured decisions — surfacing risks, alternative paths, and failure modes before execution begins. Pre-release adversarial pass: point it at a release bundle or stored vector state and it asks whether the change contradicts a locked decision or violates a persisted constraint.

ANCC

Agent-Native CLI Convention. Build CLI tools agents can discover and compose without plugins, registries, or custom integrations.

Why we built this

A Board Nobody Reads Is Just a Database

Issue trackers work because a human is always reading them. When agents do the work and no one watches every transition, the supervision layer — verification, dedup, identity, and an immune system against runaway work — has to become structure.

Your Checkout Endpoint Is Not Your Selling Flow

For seventeen days, every billing monitor was green. Every button on the product page was dead. Component health is not flow health.

When Execution Becomes Cheap, Direction Becomes Scarce

Agentic coding will not make programmers useless. It will punish people who only execute instructions and amplify people who can project capability toward the right target.

The Agent Must Not Close Its Own Ticket

AI coding agents can write code while you sleep. They should not be allowed to decide the work is done. A research note on the missing closure layer for headless AI development.

Preheat Work Orders: The Missing Primitive Between Intuition and Tickets

Filing tickets too early creates noise. Waiting too long creates surprise migrations. Preheat WOs are the structured early-warning object that prevents both — with investigation before promotion and an applicability gate before fanout.

From Context Compiler to Context Operating System

Why the compiler framing was one slice of a larger system: shared truth, mission briefings, portable bundles, live-window projection, and retrieval without transcript replay.

The Architect-Execute Split

Why long-running frontier sessions should do architecture, not every code lift: architect once, hand bounded work to cheaper execution tiers, and let the substrate carry truth between sessions.

NeuroRouter Is a Context Compiler

Why long coding sessions need compilation, not verbatim memory: source transcript, semantic field, optimization, target model context, and proof of continuity.

Your LLM Proxy Is Your Biggest Attack Surface

26 LLM proxies caught stealing credentials. A supply-chain breach compromised thousands. One operator with Claude Code hacked 9 government agencies. The proxy layer is the new front door.

AI Breaks. Your Work Shouldn't.

AI sessions corrupt, burn budgets, and die to false positives. The vendors close the bugs as stale. Here's what we built after losing $300 in one week.

The Terraform Destroy Problem: Why AI Agents Need Hard Boundaries

An agent executed terraform destroy and wiped a production database. The agent worked correctly. The system around it was incomplete.

Context Decay in Long AI Sessions

Why long AI coding sessions silently degrade — and what session tokendynamics means for human-AI collaboration.

Your AI Explored Seven Architectures. You Only Saw One.

Token counts measure volume, not structure. Decision boundaries and branch factor reveal how the model reasoned — not just what it cost.

AI-Native Work Coordination, Beyond Ticket Databases

Why AI teams need structured work artifacts, evidence convergence, and workflow discipline instead of flatter ticket databases with AI layered on top.

Your Token Bill Is a Decision Receipt

AI collapsed the cost of writing code. It did not collapse the cost of knowing what to write. The shift from compute budgets to decision budgets.

Your AI Session Costs $400

Where the money goes in long Claude Code sessions, and why reasoning hygiene matters more than bigger context windows.