AugmentClaude
DevOpsSecurity

OIA Manifest Generator

By ruvnet· ruvnet/metaharness· 0

Generate and validate architecture compliance manifests for the Open Intelligence Architecture framework.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/oia-manifest-ruvnet/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

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

harness oia-manifest ./my-harness                # write .harness/oia-manifest.json
harness oia-manifest ./my-harness --check        # validate existing manifest
harness oia-manifest ./my-harness --dry-run      # stdout, no file write
harness oia-manifest ./my-harness --json         # stdout JSON

Verdict + exit codes (--check)

VerdictExitMeaning
PASS0manifest shape ok, oiaVersion echoed
DRIFT1shape mismatch — per-field reasons surfaced
FAIL no manifest2.harness/oia-manifest.json missing

Sample manifest (excerpt)

{
  "schema": 1,
  "oiaVersion": "0.1",
  "harnessId": "my-bot@0.1.0",
  "layerAlignment": {
    "L4_toolsAndIntegrations": "full",
    "L7_governanceAndPolicy": "full"
  },
  "horizontalSpans": {
    "identity": { "status": "none", "implementation": null },
    "security": { "status": "full", "implementation": "mcp-policy.json + ADR-022" }
  },
  "adjacentStandards": {
    "mcp": { "mode": "local", "policyPath": ".harness/mcp-policy.json" }
  },
  "discoveryEndpoint": null,
  "registryUrl": null
}

Pre-emptive composition rule (ADR-034 §120)

If a future OIA identity primitive ever wants to widen an MCP permission, the composition is denied at the policy gate. The mcp-policy.json default-deny posture is not negotiable for external identity claims.

Related skills

  • validate-harness (iter 22) — release-readiness umbrella
  • threat-model (iter 114) — MCP threat-model for PR/compliance review
  • diag-harness (iter 70) — kernel-version skew check

See also

Related skills

N

n8n Architect

EtienneLescot

Create, edit, and validate n8n workflows and automation configurations.

D

Deploy to Vercel

vercel-labs

Deploy your app to Vercel with preview or production environments.

V

Vercel CLI with Tokens

vercel-labs

Deploy and manage Vercel projects using token-based authentication instead of interactive login.

U

Understand Diff

Egonex-AI

Analyze git diffs and pull requests to understand changes, affected components, and risks.