Takoform API and common model

This non-normative page maps the family-neutral contracts for portable identities, data-only Form Packages, immutable Snapshot compilation, Host lifecycle messages, trust inputs, and conformance language. It does not add to or reinterpret those contracts.

Current Host API

The current Host API is the unchanged literal v1 lane:

• discovery: GET /.well-known/takoform/v1;
• API root: /apis/forms.takoform.com/v1;
• wire contract: host-api/v1.md; and
• generic corpus: ../conformance/takoform-v1/generic.json.

API v1 normative bytes are frozen by host-api/v1.freeze.json. Errata are non-normative and cannot reinterpret v1; every behavior change requires a future v2 proposal. There is no Host API minor lane such as /v1.1, and no separately numbered Specification 1.x lane. Form compatibility is versioned independently by each Form's definitionVersion.

Authority and contract map

The current Host API v1/common-model normative closure is exactly the prose, machine roots, and recursive schema identities named by host-api/v1.freeze.json. The broader append-only release/public-schema-identities.json also retains identities outside that frozen closure; this map and the schema index do not promote those identities into v1. All publishers use the same package, verification, trust, revocation, installation, and support paths; provenance is selected by the operator, and a FormRef has no official bit.

• form-definition/ defines the exact four-field FormRef and portable desired, observed, and output shapes.
• form-package/ defines one closed data-only package for one exact Form.
• host-api/ defines discovery, lifecycle requests, asynchronous Operations, identity fences, and portable errors.
• interface-contract/, binding-contract/, artifact-transport/, and standard-services/ define digest-bound data contracts.
• trust/ defines caller-supplied provenance and offline verification inputs.
• form-families.md defines versionless reverse-DNS group ownership and group-first lookup.
• versioning.md defines the four named version streams—Host API major, each Form's definitionVersion, Core library SemVer, and Provider SemVer—and their compatibility rules.

Requirement keywords and conformance classes are defined in conformance.md. Generic conformance uses synthetic reverse-DNS families and must pass without a built-in family; concrete Host adapters and family semantics belong to their publishers and Hosts.

Individual Form definitions, Form-specific examples, catalogs, and Form pages are published by each Form publisher on that publisher's own site. This site does not collect or republish them as a central registry.

Form publication, Host support, activation, and commercial offerings are decisions made by their respective owners. No central Form status record is part of the current contract.