Agent Onboarding Protocol

An open standard for declaring what vendors need from enterprise environments to deliver value. The onboarding contract makes enterprise dependencies explicit, previewable, and verifiable — so enterprises self-prepare and vendors stop waiting.

Vendors declare it. Enterprises resolve it. No more mid-flight surprises.

Contract Specification

See spec.md for:

• The interf.yaml schema (requirements, optional, what + ready)
• Field definitions and validation rules
• Design principles

Canonical Dependency Types

Dependencies can be anything in plain English. Canonical types enable deterministic matching across vendors and enterprises.

Start here: types/index.md — quick-scan index with match table. Read this first to identify which category applies, then dive into the detail file.

No match? Leave canonical empty — the contract works with plain English alone.

Examples

See examples.md for realistic contracts across different rollout types (CRM automation, document processing, customer support).

How It Works

1. Declare — Vendor teams declare what they need in an interf.yaml contract. Use the declare skill to extract from a codebase, or write manually.
2. Deliver — Contract is sent to enterprise (via Interf platform, email, or however you work today).
3. Resolve — Enterprise works through each dependency. Each item has ready criteria so there's no ambiguity.
4. Verify — When all requirements are resolved, rollout can proceed.