# Open Ecosystem Readiness

KDNA has completed the asset-first protocol layer. The next open-source bar is
ecosystem dependability: external developers should be able to integrate,
verify, publish, and contribute without relying on private project knowledge.

## P0 Readiness Gates

- `@aikdna/kdna-core` exposes stable public asset APIs.
- Conformance tests exist for loaders and validators.
- Registry publishing flow is documented for third-party creators.

## P1 Readiness Gates

- MCP adapter exists for agent runtimes.
- Reference domains publish limitations, evals, and benchmark evidence.
- Skill + KDNA demo explains judgment-layer separation.
- RFC index defines protocol participation path.

## Completion Criteria

An external developer can:

1. Load and inspect a `.kdna` asset with `kdna-core`.
2. Run conformance tests to check compatibility.
3. Publish an asset through the Registry process.
4. Connect KDNA to an agent through MCP or a loader skill.
