AIP Specification Suite

This directory contains the versioned protocol contract and supporting profile references.

Normative Specification

• AIP 1.0 defines the native semantic model, envelope, message registry, lifecycle behavior, transports, security, versioning, and conformance classes.
• JSON Schemas defines the normative JSON Schema Draft 2020-12 wire contract and its implementation-owned export process.

An implementation must satisfy both the behavioral specification and the applicable schemas.

The Implementation Status page records what the current Rust workspace and retained evidence prove. It is informative and does not weaken the normative contract.

Supporting References

• Compatibility Profiles describes profile-owned mappings and implemented endpoints.
• Connector Contract identifies the external-product boundary. The practical authoring guide is Build a Connector.
• Schemas explains schema generation and validation ownership.

Change Process

An incompatible protocol change starts as an RFC, updates the normative specification and schemas, adds positive and negative conformance fixtures, and receives a new protocol or message-family major version. Documentation examples must be validated against the same release artifacts.