Extension development
The extension interface is available to approved partners and facility methods teams under the applicable license and development agreement. Version-specific interface definitions and validation tools are supplied through that controlled channel.
Proposal checklist
Section titled “Proposal checklist”- Scientific purpose, intended users, supported data, and known limitations
- Typed input and output contract with units, validation rules, and example records
- Resource, storage, permission, and network requirements
- Deterministic test fixtures, scientific controls, failure cases, and acceptance thresholds
- Complete provenance, license rights, required notices, dependency inventory, and security evidence
- Maintainer, vulnerability contact, update policy, compatibility range, and retirement plan
Design expectations
Section titled “Design expectations”Extensions should be deterministic where practical, preserve input identity, emit actionable progress and errors, avoid hidden external communication, request the least access necessary, and produce results that can be reviewed independently of raw logs.
Public binary submissions and source-level platform documentation are not available through this website. Contact your CryoMaestro deployment owner for the approved development package and review process.