Agreement Lifecycle

1. Draft

Agreement authors design the contract locally and validate the JSON structure.

2. Publish to agreement repository

The canonical publication path is the agreement source Git workflow.

3. Sync into API

OpenASA API syncs published agreements from the Git repository into database records for query and detail APIs.

4. Service implementation

Service providers implement the declared functions and expose concrete endpoints.

5. Agent consumption

Agents or UI clients discover agreements, read detail/version content, and invoke matching services.

6. Version evolution

When a breaking change is required, publish a new version instead of silently mutating an old one.