Community · the public layer
The category needs a public language.
Open Intent is open because the category only exists if the language is. A governance layer that every vendor must trust cannot be owned by one of them — so the vocabulary, the schema, and the RFC process all live in the open under Apache 2.0. Bring proposals, ship taxonomy terms, fork the adapter, coordinate disclosures. 173 canonical intents across 29 domains, and counting.
01 · Where the work happens
Main repo + Open Intent repo
Issues, PRs, RFC drafts. All discussion happens in the open. Squash-merge on green tests; the taxonomy ships under semantic versioning so nothing you build against breaks underneath you.
Open Intent repo →Working sessions + drafting
Weekly office hours for open-source contributors, integration help, and live taxonomy-term drafting. The fastest way to pressure-test a proposal before you open an RFC.
Join Discord →Taxonomy proposals
New Open Intent domains and categories go through a public RFC. Three pre-merge reviews are required, and backwards-compatibility is a hard constraint — codes are stable family identifiers and never change meaning once assigned.
security@intended.so
Coordinated disclosure, acknowledged within 48 hours. Read the policy before you file.
Disclosure policy →02 · How a term enters the standard
Public proposal, three reviews, a versioned release.
A taxonomy change is not a casual edit — a policy somewhere is written against every code. So the path is deliberate: open an RFC describing the gap the new domain or category fills, defend it against three independent reviews, and ship it in a versioned release. Existing codes keep their meaning; additions extend the standard rather than mutating it. That stability is what makes OI-104 mean Deployment & Release in v2.0 and every version after.
03 · Ways to contribute
Fill a gap in the taxonomy
Found an agent action with no canonical code? Open an RFC. Physical and digital domains are both in scope — embodied-AI terms are as welcome as software ones.
Map a new runtime
Build a connector or normalizer that maps a framework’s actions to Open Intent codes. The adapter surface is open; you do not need a relationship with Intended to extend it.
Run it independently
The taxonomy is Apache 2.0 and runs without an account. Fork it, build your own enforcement against it, and report what breaks.
Coordinated security
Found a verification or enforcement weakness? Report it through coordinated disclosure and we will acknowledge within 48 hours.
Disclosure policy →