View raw

Releases

Hypercerts Protocol 1.4#

Features and shared vocabulary · 2026-08-24

Describe subjects such as land areas, ecological zones, or participant cohorts with feature records. Shared vocabulary tags let projects and features reuse the same definitions instead of relying on inconsistent free-text labels.

  • Introduces org.hypercerts.entity.feature for subjects that are not people or organizations, with descriptions, optional locations, and external identifiers.
  • Introduces org.hypercerts.vocab.tag for reusable classification, including broader terms, alternative names, external equivalents, and replacement terms.
  • Collections can include features alongside activities and other collections. Existing activities continue to reference locations directly.

Additive: existing records remain valid. Applications can add support for the new records as their use cases require.

Component releases#

Hypercerts Protocolv1.4

Describe land areas, ecological zones, and other subjects with feature records and shared vocabulary tags.

Lexiconsv1.5.0

Shared record schemas, types, and permission sets.

Hypercerts APIv0.2.0

The production XRPC read API for Hypercerts and Certified records.

Hypercerts SDKUnder development

The new SDK is under development; no package release is available yet.

Certified Group Servicev0.6.0

Group accounts, permissions, and shared repository management.

EntrywayUnder development

The account entryway is under development; its release history will be linked here.

Hypercerts RelayUnder development

Network ingestion and relay infrastructure.

Hypercerts Feed Servicev0.2.0

Feed selection and read interfaces.

How versions work#

Major and minor versions identify the shared protocol release line, such as 1.4. Included components can advance their patch versions independently within that line. A new coordinated major or minor release brings the components into alignment again.

A compatible addition, such as the new feature and vocabulary-tag Lexicons in 1.4, is a minor release. Fixes advance the affected component's patch version. Breaking changes require a major release and migration guidance; a breaking change to an existing record format also needs a new schema identifier.

Within a shared release line, use the latest stable patch of each component. A hosted service may run a different version from its latest published release.