Skip to content

Glossary

Common terms used across the Takoform documentation. Definitions here are summaries; the normative meaning always lives in the specification documents.

TermMeaning
FormOne portable desired-state contract: a named, versioned definition of what a workload needs from any host.
FormRefThe exact immutable identity of a Form: API group, kind, definition version, and schema digest. Compatibility is never inferred from a name alone.
Form DefinitionThe deterministic, data-only JSON document describing one Form: desired/observed/output schemas, immutable fields, lifecycle capabilities, and interface descriptors (form definition).
Form PackageA closed, data-only distribution of one Form Definition plus its fixtures, bound by a canonical content digest (form package). No executable or credential content is allowed.
schemaDigestSHA-256 over the RFC 8785 canonical Form Definition bytes.
packageDigestSHA-256 over the RFC 8785 canonical package index; it is the publication locator (sha256-<hex>) of a package.
EpochThe API-group boundary of the specification: forms.takoform.com/v1alpha1 is the frozen Legacy epoch; forms.takoform.com/v1alpha2 is retained as the provider-v2 epoch. Current design work uses namespaced Form Family groups instead of a new bare epoch.
Form FamilyA namespaced Form group (Form Families) such as edge.forms.takoform.com/v1alpha1, the Edge Platform Family: related Forms sharing exact Interface and Binding contracts. Family membership grants no maturity.
Resource RoleThe closed v1alpha3 role enum — identity, revision, deployment, attachment, policy — deciding one Form's lifecycle mechanics: revisions are immutable, deployments move traffic, attachments activate inward events.
EnvelopeThe package API version used to carry a Form: packages.forms.takoform.com/v1alpha4 for the current family lane; packages.forms.takoform.com/v1alpha3 retained for provider-v2 packages.
SpaceAn opaque, case-sensitive scope identity (SpaceID) that scopes Resources, Interface reads, idempotency, and provider configuration.
HostAny implementation of the Host API that advertises exact FormRefs, executes the portable lifecycle, and owns placement, credentials, and recovery.
Host APIThe versioned HTTP contract (host API): discovery, exact Form availability, preview/apply, read/import/observe/refresh/delete, fencing, and stable errors. The current wire is forms.takoform.com/v1alpha3; forms.takoform.com/v1alpha2 is the retained provider-v2 wire.
DiscoveryThe versioned well-known endpoint at which a host advertises its API, Forms, and features: /.well-known/takoform/v1alpha3 for the current Host API; /.well-known/takoform/v1alpha2 retained for provider v2.
LaneA usage path through the single provider address: published v1.0.3 for Legacy state and recovery; published v2.0.0 for the nine retained provider-v2 Forms; v2.1.0 (source candidate, not yet published) for the Edge Platform Family over the v1alpha3 Host API.
SubstrateThe concrete backend or cloud an implementation runs on. Substrate operation is never portable Form state.
Interface declarationA read-only (name, version) descriptor embedded in a Form Definition, projected by the host after the Resource is Ready (interface declaration).
Interface contractOne exact named capability contract a Form's service exposes, such as edge.kv@1.0.0 (interface contracts). A service with different semantics is a different contract, never a variant.
Binding contractThe typed contract behind one outward capability binding a revision holds, such as module-worker.edge-kv@1.0.0 (binding contracts). Inward activation (routes, domains, cron, consumption) is an attachment, never a binding.
artifact manifestThe content-addressed manifest (artifacts.takoform.com/v1alpha1) that commits a bundle's modules by exact size and sha256 digest through the artifact transport upload API.
uid / generation / revisionThe v1alpha3 resource identity triple: uid is the host-issued immutable resource identity; generation increments only when the portable desired spec changes and fences updates; revision increments on any representation change and fences deletes.
ProposalMutable, unversioned design material for a Form that has not earned a public FormRef.
ExperimentalA reproducible public Form on a 0.x line whose semantics may still change under the documented compatibility policy.
StableAn evidence-earned Form contract with independent implementations, interoperability, and operational experience.
LegacyAn immutable published identity retained for compatibility, recovery, and explicit migration but no longer the basis for new specification work.
AdmissionThe retired historical central-evidence process. There is no current central approval or admission.
resource_versionThe retained v2 lane's canonical positive-decimal desired-state version; its quoted value is that lane's optimistic-concurrency fence (ETag). On the v1alpha3 lane the ETag is instead the quoted revision.
Idempotency-KeyA deterministic client-supplied key scoping mutation replay; a retry must reuse the same key and request bytes.
CheckpointA cumulative, hash-chained revocation checkpoint carrying every statement from sequence 1 through the current sequence.
DriftA lifecycle outcome derived from validated observed evidence; it is not a separate host operation.

Takoform is an Experimental specification project. The current design lane is the edge.forms.takoform.com/v1alpha1 family, served over the forms.takoform.com/v1alpha3 Host API with packages.forms.takoform.com/v1alpha4 package envelopes. The forms.takoform.com/v1alpha2 epoch and its packages.forms.takoform.com/v1alpha3 envelope are retained as the provider-v2 compatibility surface. Provider v2.0.0 is the current published client and provider v1.0.3 is the published Legacy client. Provider v2.1.0 is an unpublished source candidate. The 34 published Form Package identities from forms.takoform.com/v1alpha1 are immutable Legacy evidence. There is no current central approval or admission, and no Form has an Experimental publication yet.