Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
SkillScore95Maintained
Automatic
◆AI Engineer pack
Last verified 8/17/2026
What it changes
Passed 21 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill95%
Checks it passed that the model alone missed
Specifies exit code 2.
Specifies verdict DRIFT.
Includes oiaVersion set to 0.1.
and 20 more in the full report
18 fixed3 passed either way1 still failing0 broke
Pass-rate lift
+82 pp
Tokens
-13%
Agent turns
0%
Response time
-74%
Model gemini-3.6-flashMeasured 8/17/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 18
Prompt
Which foundation publishes the Open Intelligence Architecture v0.1 reference model referenced by the manifest?
What was checked, without and with the skill
Checked
Without skill
With skill
Names Agentics Foundation as publishing body.
Missed
Passed
case-19 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md96 linessingle file
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.