AAO Governance Starter Kit v0.1

What this is

The skeleton of a governance sidecar: the file structure that lets an organisation running its own AI agents declare which principles govern them, which escalation tier each decision falls into, and which events get attested on chain.

It is structure and placeholders only. Every value shipped is a dummy, clearly marked as such. You replace them with your own.

What is in the download

A single .zip containing five files:

aao-governance-starter-kit-v0.1/
├── README.md
├── governance/
│   ├── constitution.ref
│   ├── principles.yaml
│   └── attestation.yaml
└── EXAMPLE/
    └── filled-example.md
  • constitution.ref — pins which governing document is in force, by version string and SHA-256. Ships as version: UNRATIFIED / sha256: <pending>.
  • principles.yaml — structure for principle IDs, criticality, and escalation tier. Ships with dummy entries (EXAMPLE-001 and similar) that you delete.
  • attestation.yaml — structure for which events attest, to which chain, under which schema. Dummy values throughout.
  • README.md — what each file is for, how to fill it in, and the three limitations restated.
  • EXAMPLE/filled-example.md — one worked example showing the shape filled in. Invented, illustrative, carries no authority.

The three limitations, again

These are repeated from the top of this page and from the README because they define what you are buying.

  1. Not a runtime. Nothing here starts, hosts, schedules or supervises an agent.
  2. No enforcement. The sidecar declares, records and escalates. Writing criticality: critical next to a principle does not create a control. If an agent is about to do something your principles.yaml forbids, this kit will not prevent it. Detection and enforcement are integration work you build on top of these declarations.
  3. Not a constitution. constitution.ref is a reference, not a document. The blocLabs Constitution v0.1 is in drafting and is not ratified, so there is nothing to point it at yet. The placeholder is deliberate — it is not a value awaiting download.

No compliance, regulatory, legal or standards claim is made. Filling this kit in completely and correctly still certifies nothing.

How payment works for v0.1

The price is 100 BLOC. BLOC is a closed-loop token on a private chain with no payment gateway, and this store cannot price in it natively, so the page renders the figure with a dollar sign. No US dollars are charged.

Settlement for v0.1 is manual: place the order through the store, then the BLOC transfer is arranged directly with blocLabs outside the store, and the download is released on confirmation. There is no automated payment integration and none is implied.

Scope note

The governance/ directory and its three files follow the blocLabs Harness Bundle Standard. README.md and EXAMPLE/filled-example.md are packaging for this kit and are not part of that standard — the README says so too. The Harness Bundle Standard also places governance/ inside a larger bundle alongside manifest.yaml, knowledge/ and agents/; those are out of scope here. This is the governance sidecar only.

$100

SKU: BLOC-AAO-GOV-KIT-001 Category:

Description

What this is

The skeleton of a governance sidecar: the file structure that lets an organisation running its own AI agents declare which principles govern them, which escalation tier each decision falls into, and which events get attested on chain.

It is structure and placeholders only. Every value shipped is a dummy, clearly marked as such. You replace them with your own.

What is in the download

A single .zip containing five files:

aao-governance-starter-kit-v0.1/
├── README.md
├── governance/
│   ├── constitution.ref
│   ├── principles.yaml
│   └── attestation.yaml
└── EXAMPLE/
    └── filled-example.md
  • constitution.ref — pins which governing document is in force, by version string and SHA-256. Ships as version: UNRATIFIED / sha256: <pending>.
  • principles.yaml — structure for principle IDs, criticality, and escalation tier. Ships with dummy entries (EXAMPLE-001 and similar) that you delete.
  • attestation.yaml — structure for which events attest, to which chain, under which schema. Dummy values throughout.
  • README.md — what each file is for, how to fill it in, and the three limitations restated.
  • EXAMPLE/filled-example.md — one worked example showing the shape filled in. Invented, illustrative, carries no authority.

The three limitations, again

These are repeated from the top of this page and from the README because they define what you are buying.

  1. Not a runtime. Nothing here starts, hosts, schedules or supervises an agent.
  2. No enforcement. The sidecar declares, records and escalates. Writing criticality: critical next to a principle does not create a control. If an agent is about to do something your principles.yaml forbids, this kit will not prevent it. Detection and enforcement are integration work you build on top of these declarations.
  3. Not a constitution. constitution.ref is a reference, not a document. The blocLabs Constitution v0.1 is in drafting and is not ratified, so there is nothing to point it at yet. The placeholder is deliberate — it is not a value awaiting download.

No compliance, regulatory, legal or standards claim is made. Filling this kit in completely and correctly still certifies nothing.

How payment works for v0.1

The price is 100 BLOC. BLOC is a closed-loop token on a private chain with no payment gateway, and this store cannot price in it natively, so the page renders the figure with a dollar sign. No US dollars are charged.

Settlement for v0.1 is manual: place the order through the store, then the BLOC transfer is arranged directly with blocLabs outside the store, and the download is released on confirmation. There is no automated payment integration and none is implied.

Scope note

The governance/ directory and its three files follow the blocLabs Harness Bundle Standard. README.md and EXAMPLE/filled-example.md are packaging for this kit and are not part of that standard — the README says so too. The Harness Bundle Standard also places governance/ inside a larger bundle alongside manifest.yaml, knowledge/ and agents/; those are out of scope here. This is the governance sidecar only.

0
Your Cart
Empty CartYour cart is emptyReturn to Shop