Developer contract changelog

v6 — conditional automation destination

• Added optional definition.assistantName plus set_metadata.assistantName; null clears the identity-label override while Elicitra keeps AI identity and recording/transcription wording server-owned.
• Added com.elicitra.automation.triggered.v1 with a fixed, data-minimized analysis and activation payload.
• Added deliveryMode metadata to distinguish the three unchanged lifecycle_subscription events from the new conditional_destination event. Automation is not subscribable and omits lifecycleSequence.
• Advanced the hosted public MCP runtime to the parallel v6 contract while keeping exactly fourteen tools and three lifecycle-subscription events.
• Published AsyncAPI 3.0.0 document version 1.1.0 and the parallel /developers/v6/ artifact tree.
• Preserved /developers/v1/ through /developers/v5/ byte-for-byte with no scheduled sunset.

v5 — bilingual Elicitra product knowledge

• Added the read-only elicitra_knowledge_search tool for customer-safe product concepts, campaigns, credits, pricing tiers, and use cases in en-US or it-IT.
• Kept the existing scenario:read scope, Growth/Scale entitlement, shared rate limits, and 0-credit weight; read PATs now expose 10 tools and full PATs expose 14.
• Kept product-reference search separate from organization scenario Knowledge Base administration and respondent data.
• Published /developers/v5/ while preserving /developers/v1/ through /developers/v4/ byte-for-byte. The three webhook events and payload contracts are unchanged.

v4 — account context and campaign DRAFT authoring

• Expanded the public catalog from seven to thirteen tools with allowlisted account context and campaign list/get/create/update/review operations.
• Added campaign:read and campaign:write. Legacy read and write PAT profiles gain the matching effective campaign scopes without rotation.
• Added atomic, idempotent DRAFT campaign updates for scenario, channel, intake, and constrained theme configuration, plus deterministic review and operator handoff.
• Added CAMPAIGN_LOCKED; kept publishing, access configuration, provider operations, live testing, and respondent data outside public MCP.
• Published /developers/v4/, preserved /developers/v1/ through /developers/v3/ byte-for-byte, and kept all three webhook events and payloads unchanged.

v3 — Live Fit policy

• Added optional definition.liveFit to scenario drafts and exports, with at most ten ordered typed gates.
• Added the closed set_live_fit operation to create/update drafts, including explicit acknowledgement for gate removals.
• Kept the public catalog at exactly seven tools and left webhook event types, payloads, signature syntax, and the Scenario export envelope unchanged.
• Published /developers/v3/ as the current contract and preserved /developers/v1/ and /developers/v2/ byte-for-byte.

v2 — form-first scenario fields

• Added stable machine value plus respondent-facing label objects to public select options while continuing to accept legacy string options.
• Published a parallel /developers/v2/ contract and made v2 the contract advertised by the hosted MCP endpoint.
• Kept webhook event types, webhook payload shapes, HMAC signature syntax, and the Scenario export format unchanged.
• Preserved /developers/v1/ byte-for-byte as the previous immutable contract. It is not currently scheduled for sunset.

v1 — initial public contract

• Added hosted, stateless Streamable HTTP MCP with seven semantic scenario tools.
• Added personal bearer PATs with scenario:read and scenario:write scopes.
• Added signed interaction.ended, analysis.completed, and analysis.failed lifecycle webhooks.
• Added CloudEvents envelopes, HMAC-SHA256 signatures, replay, JSON Schema, and AsyncAPI artifacts.
• Developer Access is included in Growth and Scale at 0 incremental credits.

No public REST API is part of v1.