Airspace for modern software delivery

The codebase should decide what agents can touch.

gndctrl adds zone markers, stability tiers, and clearance rules directly into your project so any agent — Claude, Gemini, Copilot, Codex — can ship fast without breaking critical systems.

Read the technical docs Why this matters now

6 stability tiers
5 agent weight classes
1 persistent project memory

What gndctrl does

Gives structure to every agent edit

Zones define where agents may work, which dependencies matter, and what risk profile each part of the code has.

Enforces clearance, not just advice

Locked and sensitive zones require explicit handling, preventing accidental edits in high-impact surfaces.

Persists engineering memory

Node markers and CRID logbook entries retain non-obvious context between sessions so the next agent starts informed.

How it works

gndctrl uses a three-layer system: directory zones in .gndctrl, file-level @gndctrl:zone markers, and function-level @gndctrl:node markers for critical caveats. Enforceable context lives in and beside the code itself — not in a separate wiki or prompt.

# @gndctrl:zone START | id=PAYMENT | stability=sensitive | deps=[AUTH_CORE]
# @gndctrl:node id=PAYMENT.charge_user | risk=high | crid=PMT-20260430-001
async def charge_user(...):
    ...
# @gndctrl:zone END | id=PAYMENT

Works with every agent

gndctrl is provider-agnostic. The spec defines a weight class system that maps to any agent — from large frontier models down to lightweight scripted tools. Whether you run Claude, Gemini, Copilot, or Codex, governance stays consistent across the whole fleet without rewriting rules for each provider.

Weight class	Aviation reference	Role	Example providers
Super	A380, An-225	Frontier reasoning models — locked zone access, critical architectural decisions	Claude Opus
Heavy	747, 777	Large capable models — sensitive zones, complex planning, security review	Claude Sonnet
Medium	737, A320	Mid-size models — code generation, UI work, active-zone tasks	Gemini, GPT-4o
Light	Cessna 172	Small fast models — summaries, markdown, simple checks	Small local models
Ultralight	Drone / glider	Scripted or rule-based agents — audits, linting, file watching. No LLM required.	gndctrl Auditor / Writer

Weight class is a floor, not a ceiling — a heavier agent is always cleared to enter a lighter zone. Clearance is only denied when the agent's class falls below a zone's declared minimum.

Built for developers shipping with agents

Velocity is no longer the bottleneck

Agents can produce code instantly. The new bottleneck is trust: deciding whether that code should land in critical paths.

Context loss creates hidden risk

Most agent sessions are stateless. Without durable memory, every run repeats old mistakes and misses known edge cases.

Start alone. Scale when you need to.

Single mode is one file, no overhead, no ceremony. When you're ready for parallel agents across multiple services, fleet mode uses the same spec and mental model.

gndctrl gives your codebase a voice

Instead of relying on prompts alone, governance lives in the repository itself — surviving session resets, tool switches, and new agents without you having to repeat yourself.

Ship fast. Keep control.

gndctrl is built for developers who want to move fast with agents without surrendering architectural safety — from a single project to a full fleet.

Read the technical docs