Role authors describe durable intent once, without embedding a platform matrix.
One role.
Any harness.
Keep identity portable: prompt, skills, capability intent, approvals, and evals live in one universal role. Pick a compatibility package only when it is time to run.
Compatibility is selected at export or runtime and evolves on its own release cycle.
Effective access intersects role intent, compatibility support, host and room policy, and explicit user grants.
Invite the right mind.
Every role is platform-neutral by definition. Search by purpose; decide where it runs later.
Bridge at the edge.
Install only the platform layer you need. Roles stay unchanged while harness APIs move.
Declare purpose, non-goals, skills, capabilities, and approval gates.
Validate content, paths, digests, provenance, and adversarial evals.
Choose an independent compatibility package for the target harness.
Review effective grants, pin the digest, and attach an isolated role session.