ECC v2.0.0-rc.1 Preview Pack Manifest

This manifest defines the reviewed preview pack for 2.0.0-rc.1. It is not a release action by itself. Use it to verify that the public launch surface stays assembled after the GitHub prerelease and npm next publish, and before tagging plugin surfaces, uploading video, or posting announcements.

Pack Contents

Itô Skill Pack Boundary

The general product-integration contract is recorded in docs/architecture/platform-value-loop.md. The Itô pack is the first worked example: useful public workflows, separate gated API access, and sanitized operator patterns feeding back into ECC without merging business ownership.

The preview pack includes six public teaser skills for prediction-market and Itô-adjacent workflows:

• skills/ito-market-intelligence/SKILL.md
• skills/ito-basket-compare/SKILL.md
• skills/ito-trade-planner/SKILL.md
• skills/ito-data-atlas-agent/SKILL.md
• skills/prediction-market-oracle-research/SKILL.md
• skills/prediction-market-risk-review/SKILL.md

They are research, comparison, planning, and risk-review skills. They do not place trades, do not provide investment advice, and do not merge ECC Tools with Itô. Any Itô-backed data call requires explicit gated API access through ITO_API_KEY.

Hermes Skill Boundary

The preview pack includes one public Hermes-specialized skill:

• skills/hermes-imports/SKILL.md

That is intentional for rc.1. The skill is a sanitization and conversion workflow, not a dump of private Hermes automations. Additional Hermes-generated skills should enter ECC only after they pass the same rules:

• no raw workspace exports;
• no live account names, client data, finance data, CRM data, health data, or private contact graph;
• provider requirements described by capability, not by secret value;
• repo-relative examples instead of local absolute paths;
• tests or docs proving the workflow is useful without private state.

Reference-Inspired Adapter Direction

The preview pack uses outside systems as design pressure, not as copy targets:

Final Verification Commands

Run these from the exact release commit before publication:

git status --short --branch
node scripts/platform-audit.js --json
npm run preview-pack:smoke
npm run release:approval-gate -- --format json
npm run release:video-suite -- --format json
npm run harness:adapters -- --check
npm run harness:audit -- --format json
npm run observability:ready
npm run security:ioc-scan
npm audit --audit-level=moderate
npm audit signatures
node tests/docs/ecc2-release-surface.test.js
node tests/run-all.js
cd ecc2 && cargo test

Publication Blockers

The preview pack is assembled, and the first release/package surfaces are now live. Full publication is still blocked until these live surfaces and decisions are recorded in a final evidence file:

• final release URL ledger regenerated from the intended release commit;
• npm run release:approval-gate -- --format json returning ready true after owner approvals and live URL readbacks are recorded;
• final release name/plugin publication checklist rerun from the intended release commit;
• GitHub prerelease v2.0.0-rc.1 live readback;
• npm [email protected] on the next dist-tag live readback;
• Claude plugin tag / marketplace propagation for ecc@ecc;
• Codex repo-marketplace distribution evidence plus official Plugin Directory availability status;
• final announcement URLs in X, LinkedIn, GitHub release, and longform copy;
• ECC Tools billing/product readiness evidence remains fresh: the May 20 selected-target KV readback and live announcement gate passed through the operator bearer path. Repeat the billing readback and gate immediately before any native-payments announcement copy is published.

Result

The rc.1 preview pack is ready for a final clean-checkout release gate, but not for full public publication without the remaining approval-gated release, package, plugin, and announcement steps above. GitHub and npm are now recorded; plugin, video, billing, and outbound approvals remain open.