Skip to content
METHODOLOGY

How producer-declared information becomes structured, portable, and readable.

HEDAMO earns methodological trust through what it structures — and what it refuses to claim.

8schema fieldsProducer-declaredGap-marked3ownership pillarsVersion history
Contents · 5 sections
  1. 01
    OverviewThe structure that lets producer-declared information travel.
  2. 02
    Disclosure structureEight schema fields. Origin, practices, sources, gaps, versions, and what they each carry.
  3. 03
    Source and confidenceHow claims are attributed to documents, records, and tests. Why HEDAMO never infers.
  4. 04
    Claim ownershipProducers own claims. Jurisdictions own admissibility. HEDAMO maintains the structure.
  5. 05
    Use boundariesWhat a HEDAMO disclosure does. What it does not. Where the methodology stops.
Overview

The structure that lets information travel.

PRODUCERS OWNTheir claims.
JURISDICTIONS OWNAdmissibility decisions.
HEDAMO MAINTAINSThe disclosure structure.
i
PRODUCER-DECLARED

Every claim is authored by the producer. HEDAMO does not create claims on the producer's behalf, infer undeclared information, or fill gaps.

ii
PORTABLE

The same disclosure structure is designed to be legible to buyers, researchers, institutions, and procurement bodies without requiring the producer to rebuild the explanation for each context.

iii
METHODOLOGY-LEGIBLE

Testing cadence, source attribution, and declared gaps are all visible within the structure. HEDAMO does not infer what is undeclared. It marks the gap and moves on.

HEALTH · A THREAD

Health is not reduced to nutrition facts alone. It includes origin, practices, processing, claims, risks, use context, and consumer understanding. Health is the first public-interest reason the disclosure gap matters.

Disclosure structure

What a structured disclosure contains.

A HEDAMO disclosure organises producer-declared information into a consistent schema. The core structure remains consistent. Product-specific fields may vary, but the treatment of claims, sources, gaps, and updates stays stable.

01
Origin

Geographic and agricultural source of the product.

GEOGRAPHIC
02
Practices

Production and cultivation methods declared by the producer.

METHODOLOGICAL
03
Processing

How the product was handled between field and final form.

METHODOLOGICAL
04
Claims

Producer-declared attributes — health, quality, heritage, and other declared product attributes.

DECLARATIVE
05
Sources

Documentation supporting each claim.

DOCUMENTARY
06
Testing cadence

Frequency and methodology of product testing where declared.

CADENCE
07
Declared gaps

Fields not completed, testing not conducted, or documentation not provided.

MARKED · NOT INFERRED
08
Updates

Version history — when the disclosure was last updated and what changed.

VERSIONED

A gap in a HEDAMO disclosure is a visible methodological position. It may mean information was not declared, testing was not conducted, documentation was not provided, or the field is incomplete. Readers see the gap. They do not see an inference.

Where information is not declared, HEDAMO marks the gap rather than converting absence into judgment.
Source and confidence

How sources are attributed.

Every claim in a HEDAMO disclosure can carry source attribution — the document, laboratory, institution, or producer record that supports it. Source attribution is not mandatory, but where it is absent, that absence is visible.

Doctrine

“Where a source, test, or method is not declared, HEDAMO does not infer. It marks the gap and moves on.”

Claim ownership

Who owns what.

The ownership architecture of a HEDAMO disclosure is precise and non-negotiable.

iPRODUCERSOwn their claims.

HEDAMO may structure the presentation of the claim, but it does not become the author, validator, or endorser of the claim.

iiJURISDICTIONSOwn admissibility decisions.

HEDAMO does not make that decision. It does not position disclosures as pre-approved or accepted.

iiiHEDAMOMaintains the disclosure structure.

The disclosure schema — how information is organised, what fields exist, how gaps are marked — is maintained by HEDAMO. The structure is what travels.

Use boundaries

Where disclosure sits alongside operations.

HEDAMO DOES5
Structures producer-declared information into a consistent, portable schema.
Makes that information readable across markets, institutions, consumers, and research contexts.
Marks gaps explicitly where information has not been declared.
Maintains version history so changes are visible over time.
Provides a schema legible across jurisdictions.
How disclosure relates to existing functions4

Certification evaluates against thresholds.

Disclosure structures what the producer declares.

These functions coexist.

Traceability tracks movement through a supply chain.

Disclosure structures what the product is at any point in that chain.

Both are needed.

Regulation determines admissibility.

Disclosure makes producer-declared information legible to the regulator.

The decision remains with the jurisdiction.

Laboratory testing generates evidence.

Disclosure gives that evidence a structured, portable home alongside the producer's own declarations.

HEDAMO does not relocate any of these functions. It adds a layer that currently does not exist.

Existing systems perform essential operational functions. HEDAMO structures a disclosure layer so that producer-declared attributes become portable across buyers, institutions, and markets — without relocating operational responsibility.

The methodology is being developed first in food systems, where gaps between producer knowledge, buyer understanding, and institutional documentation are already visible. The same disclosure logic may apply to cosmetics and textiles, where ingredient origin, formulation practices, fibre source, chemical treatment, and health-adjacent attributes are producer-declarable but not currently portable to buyers and institutions.

Technology implements the methodology. It does not define it.

HEDAMO is a disclosure methodology developed by Altibbe. Altibbe Research publishes the Structural Gaps in Product Information Systems series that informs the methodology.

The methodology earns trust through what it structures — and what it refuses to claim.

Request a briefingView the Sample DisclosureRead the Research Basis