Proposal flow
Every change to a shared envelope, vocabulary, schema, or registry entry follows the same path, whether it originates from the umbrella initiative or one of its child specifications.
Proposal→Discussion→Evidence / implementation→Review→Accepted / Contested / Rejected→Versioned release
A proposal can be accepted, contested, or rejected. Contested proposals are not silently dropped — disagreement and its reasoning stay part of the record.
Read our project principles →Proposal families
- AIP
- AI Attributes Proposal — changes to the umbrella envelope, provenance model, adapter manifest, or registry.
- OEP
- Open Emotions Proposal — changes to the Open Emotions™ specification.
- OSP
- Open Sensations Proposal — changes to the Open Sensations™ specification.
- OMP
- Open Morals Proposal — changes to the Open Morals™ specification.
Proposal template
A proposal should include:
TitleProblemScopeMotivationProposed changeAlternativesCompatibility impactScientific evidenceSecurity / privacy impactMigration plan
Conformance is not scientific validation. Technical compatibility with a specification is a separate question from whether the underlying classifier or framework is scientifically valid. Proposals should not conflate the two.