Form and package
A Form Definition describes desired state. A data-only Form Package binds exact canonical bytes and evidence to that versioned identity.
portable specification
A map of Takoform's four public contracts: exact Form/Package
data, desired Resource lifecycle, read-only Interface projection,
and trust/version/release identity.
exact Form/Package、Resource lifecycle、read-only Interface、
trust/version/releaseという4つの公開contractへの入口です。
forms.takoform.com/v1alpha1.forms/admissions/v1.0.6.v1.0.1 does not make the API stable.The specification fixes portable identities and lifecycle semantics. It does not prescribe a Cloud, backend, scheduler, credential system, price, or operator policy.
A Form Definition describes desired state. A data-only Form Package binds exact canonical bytes and evidence to that versioned identity.
A host advertises exact availability, admits packages, realizes Resources, selects concrete backends, and owns authorization.
The typed provider discovers the host and drives preview, apply, read, observe, refresh, import, and delete operations.
This page is navigation, not a second specification. The linked Markdown and JSON files in the repository are canonical.
Form Definition
Exact FormRef and desired/observed/output data, packaged as one immutable data-only Form Package.
spec/host-api/
Desired Resource discovery, preview/apply, lifecycle, fencing, and portable errors.
spec/interface-declaration/
Open Form-derived descriptors and their read-only host projection; data.indexed@1 is the current minimal four-operation descriptor.
spec/trust/
Publisher evidence, revocation, and independent API/Form/Package/provider version identities.
Schemas, conformance classes, generated inventory, and decisions
support these four contracts; they are evidence and rationale, not
additional product interfaces. Start from
spec/README.md.
Similar-looking version numbers do not imply shared stability or a synchronized release.
v1alpha1Protocol envelope, discovery, and lifecycle semantics. Still allowed to change incompatibly.
Each desired schema has its own exact FormRef and schema digest.
Immutable data-only bytes and evidence for one exact definition.
v1.0.1 publishedThe supported provider compatibility line, signed and verified by direct Terraform and OpenTofu Registry installation.
v1.0.1 Registry readback with both CLIs.portable-standard admission evidence.forms.takoform.com/v1alpha1.
Graduation from v1alpha1 has additional multi-host,
stability, Interface materialization, deprecation, and revocation
requirements. Read the
canonical versioning policy.