Ivorleaf Developers

Changelog

Staged v1 supplied/acquisition migration

  • Explicit acquire requests acquisition; supplied text and citation metadata do not. New provenance includes acquired. Historical replay is unchanged. Distribution requires the coordinated cutover.

Historical entries (before this migration)

2026-09-15 — Developer Experience

  • Documented POST 200/202 acceptance and GET retrieval of active, completed, and failed validations.
  • Clarified Source Inspection: supported public HTML is retrieved and inspected; inspected material is authoritative and submitted text is a retrieval hint.
  • Added JSON File Input and canonical downloadable examples.
  • Aligned authentication, organization policy, idempotency, errors, and zero-VU cases with the frozen product contract.
  • Updated raw HTTP examples to submit or retrieve once without automatic retries or polling.

Phase 12 — Validation Intelligence developer release

Verification date: September 5, 2026

Phase 12 establishes Validation Intelligence as the primary Ivorleaf developer product:

  • POST /v1/validation accepts supplied information and supplied evidence and determines what that evidence actually supports.
  • Completed responses expose one determination plus relationships, signals, and provenance.
  • supported, unsupported, conflicting, and uncertain are all completed HTTP 200 outcomes.
  • Organization-backed API credentials, required idempotency, vu_v1 usage, capacity modes, and operational error handling are documented.
  • Executable cURL, TypeScript, and Python examples exercise the public contract without importing backend logic.
  • The API Reference loads authoritative production OpenAPI and presents Validation Intelligence before advanced and persistent workflows.
  • An explicit, credential-gated production smoke command verifies one 1×1 validation, replay, idempotency conflict, and exact VU accounting.

Run the opt-in acceptance smoke with a controlled organization credential:

IVORLEAF_PRODUCTION_SMOKE=1 \
IVORLEAF_API_KEY='ivl_...' \
npm run validation-smoke:production

The smoke consumes exactly 1 VU when successful and is intentionally excluded from ordinary tests and builds. See the Phase 12 verification record.

Advanced and persistent workflows

Technical Sessions, learning and technical workflows, history, artifacts, assessments, and packaged experiences remain available as secondary surfaces. Phase 12 does not remove or redesign those APIs.

Known reference limitations

  • Several advanced history, artifact, workflow, usage, and packaged-output operations lack complete response models.
  • Nested technical-analysis and orchestration objects remain only partially typed in OpenAPI.
  • Phase 12 does not publish pricing, SDK availability, or new CLI behavior.

Integrations should use the live API Reference and avoid relying on undocumented fields. Breaking-change policy and commercial packaging require separate product approval.