Skip to content
The methodArkOS · open governance for agentic delivery

Specs before code. Gates before ship.

ArkOS is the governance framework ARK360 ships software under. Agents write most of the code. Specs, gates and the audit trail decide what merges.

This website is governed by ArkOS, in public.

01 · Why governance

Agents made code cheap. Drift got expensive.

An agent can ship a plausible feature in minutes. The failure mode is no longer speed; it is confident code that quietly solves the wrong problem. The fix is not more prompting. It is structure: a spec that grounds the work, requirements with IDs, and gates that refuse what was never agreed.

ArkOS makes that structure the repository itself: files and conventions any agent and any reviewer can read, with CI enforcing what matters.

The guardrail is the architecture, not a promise layered on top of it.
Read the article
02 · The artifacts

Governance as files, not meetings.

Everything an agent needs to build safely, and everything an auditor needs to check it, lives in one directory under version control.

Constitution
.arkos/constitution.md

The non-negotiables: plan before code, issue before branch, no personal data without a spec.

PRD
.arkos/prd/product.md

Product intent and roadmap. Major pivots change this file first, so direction is durable.

Specs
.arkos/specs/NNNN-*.md

One per change, EARS requirements with IDs, out-of-scope lists and acceptance tables.

ADRs
.arkos/adr/NNNN-*.md

Immutable architecture decisions. Superseded, never edited.

Threat models
.arkos/threat-models/

STRIDE-lite analysis wherever a change crosses a trust boundary.

Contracts
.arkos/contracts/

OpenAPI and JSON Schema for every external interface.

03 · How a change ships

One loop, every change.

  1. 01

    A spec is drafted and approved: problem, EARS requirements, acceptance criteria.

  2. 02

    An issue anchors the change; a feature branch carries it.

  3. 03

    Agents implement against requirement IDs, with humans on judgment calls.

  4. 04

    Acceptance checks run: greps, builds, manual review against each REQ.

  5. 05

    The PR merges through the gates. The audit trail keeps the whole story.

plan-gate

Every commit references an approved spec. Requirements exist before implementation.

build-gate

Lint, strict types, full build with prerender, CHANGELOG present, banned patterns absent.

A method you can read before you buy it.

The framework is open. The first engagement is a fixed-fee review. Judge both on paper.

Prefer email? hello@ark360.com.au