# AIP Specification Suite

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

## Normative Specification

- [AIP 1.0](AIP-1.0.md) defines the native semantic model, envelope, message
  registry, lifecycle behavior, transports, security, versioning, and
  conformance classes.
- [JSON Schemas](schemas.md) 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](../reference/implementation-status.md) 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](compatibility-profiles.md) describes profile-owned
  mappings and implemented endpoints.
- [Connector Contract](connector-contract.md) identifies the external-product
  boundary. The practical authoring guide is
  [Build a Connector](../guides/build-a-connector.md).
- [Schemas](schemas.md) 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.