oia-manifest

# oia-manifest > Codex skill: emit/validate the OIA cross-cutting manifest layer > (ADR-034, iter 121 → iter 122). ## What it does Emits `.harness/oia-manifest.json` — the harness's self-assessment against the **Open Intelligence Architecture (OIA) v0.1** 9-layer reference model published by the Agentics Foundation at <https://oia.agentics.org>. The manifest declares: - **9 layer alignments** — L1 physicalCompute → L9 humanAndBrowserInterface, each `full` / `partial` / `none` / `not-applicable` - **6 horizontal spans** — security · observability · identity · governance · policyEnforcement · interoperability, each `full` / `partial` / `none` with an `implementation` reference (file path or ADR number) - **4 adjacent standards** — `mcp`, `a2a`, `acp`, `agentProtocol` with current mode + wiring notes - **`discoveryEndpoint` + `registryUrl`** (both `null` at v0.1; OIA has no registry yet) ## Why a manifest, not a host adapter? OIA at v0.1 has no runtime and no wire protocol — it's a vendor-neutral vocabulary for assessing system alignment. The right plug-in shape is a **static cross-cutting manifest** (ADR-034 Decision: Option B). It plugs in ABOVE the host adapter contract and BELOW the MCP policy gate. ## Usage from Codex ``` /oia-manifest path=./my-harness /oia-manifest path=./my-harness check=true /oia-manifest path=./my-harness dry-run=true ``` ## Equivalent CLI ```bash harness oia-manifest ./my-harness # write .harness/oia-manifest.json h...