METHOD
BUILT BY AGENTS. Gated by machines. Approved by people.
Six layers, from the brief to the product’s own answer. At every one, agents do the work, a check can refuse it, and a person signs — or is deliberately absent, and the layer says so.
What comes in
Products
- VELA — satellite anomaly investigation
- Argus — autonomous testing
- Routera — AI model gateway
Inputs
- Telemetry and sensor streams
- Documentation and operations records
- Codebases and running applications
- Synthetic reference sets
People
- Engineers, who approve the plan
- Reviewers, who own the reference sets
- Operators, who execute every step
SKOPAQ AIAGENT WORKFORCE
Agents do the work|The machine refuses|A person signs
- 01 · IntentAgents draft. People approve. Nothing is built from an inferred requirement.
- 02 · ArchitectureSchema first, so the contract exists before the implementation does.
- 03 · BuildParallel, sandboxed, and reachable only through a typed bus.
- 04 · VerificationEvery diff meets the same gates. Any failure blocks. There is no warning tier.
- 05 · OperationSystems patch what they can and escalate what needs a decision.
- 06 · The answerEvery claim carries its source, or it is not served.
What it connects to
Models
- Frontier models
- Open-weight models
- Fine-tuned models
Tools and data
- Typed tool bus
- Telemetry and document stores
- Version control
- Sandboxed execution
Runtimes
- Cloud
- Edge
- Fully air-gapped
Every box names something the products run today · no vendor logos, because none of these are partnerships
Layer 01 · Before code
This layer, in fullIntent
Agents draft. People approve. Nothing is built from an inferred requirement.
Layer 01 · Intent
What the agents do
- Draft the specification, the acceptance criteria and the constraints from a brief.
- Propose the implementation plan and declare its blast radius before writing a line.
- Restate the spec as machine-readable contracts, so the next layer can check against it.
What the machine refuses
- Any work with no approved specification behind it.
- A plan whose blast radius was not declared.
- A requirement inferred rather than written — an agent asked to guess will invent one.
Where a person signs
Approves the plan
No agent starts without a signature, and the signature goes on the plan, not on the diff. A rejected plan costs minutes; a rejected implementation costs days.
The difference
Prompting a model vs. engineering with agents
The same four layers, with and without a check that can say no.
Intent
PromptingA conversational prompt. Requirements inferred by the model. Drift from the first commit.
SKOPAQA human-approved spec and plan before any agent starts, restated as contracts the next layer can check.
Build
PromptingOne assistant with shell access, pasting into a shared working tree.
SKOPAQSpecialised agents in sandboxed worktrees, reaching data only through a typed bus, handing off passing artefacts.
Verification
Prompting“Looks good to me” on a diff nobody can reproduce.
SKOPAQSix blocking gates on every diff, seeded replay for the runs that matter, and a citation check that fails the release.
The answer
PromptingA confident paragraph with no way to check it.
SKOPAQA claim without a source is discarded. An honest refusal is served instead.
One page per layer