Skip to content
Product profile structureProducersInstitutionsResearchers
METHODOLOGY

Every product should have a readable profile.

Origin, practices, claims, sources, and gaps — in one structure.

A printed HEDAMO Structured Disclosure document beside a bottle of Zeitoun Heritage olive oil, photographed on slate

The deliverable

A structured disclosure for one product. One document. Producer-declared, source-attributed, gap-visible.

The methodology below is what makes the document consistent across producers and readable across markets.

Contents
  1. 01
    OverviewWhat the structure holds and who owns what.
  2. 02
    Disclosure structureEight fields. What each one carries.
  3. 03
    Source and attributionHow claims are linked to evidence.
  4. 04
    Claim ownershipProducers declare. Jurisdictions decide. HEDAMO maintains.
  5. 05
    Disclosure alongside operationsHow disclosure sits beside certification, traceability, and regulation.
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

One structure, legible to buyers, researchers, institutions, and procurement, without the producer rebuilding the explanation for each.

iii
METHODOLOGY-LEGIBLE

Testing cadence, source attribution, and declared gaps are all visible. What isn't declared is marked as a gap, not inferred.

Disclosure structure

What a product profile carries.

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 more.

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.
HEALTH · A THREAD

Health is not reduced to nutrition facts. It includes origin, practices, processing, and use context.

Source and attribution

How sources are attributed.

Every claim can carry source attribution. 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.

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 structure.

HEDAMO maintains the schema: what fields exist, how they are organised, and how gaps are marked.

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.

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.

A product can be fully compliant and still poorly understood.

In comparison

How HEDAMO sits alongside existing systems.

How HEDAMO sits alongside existing systems.

HEDAMO vs Certification
CertificationDisclosure
Answers“Does this meet the standard?”“What is the product?”
EvaluatesAgainst a defined thresholdWhat the producer declares
OutputCertificate (pass / fail)Structured profile (declared + gaps)
RelationshipHEDAMO does not replace certificationThey coexist as different layers
HEDAMO vs Traceability
TraceabilityDisclosure
RecordsWhere the product movedWhat the product is
TracksCustody, timestamps, handlingOrigin, practices, claims, sources, gaps
GapA product can be fully traceable and poorly understoodDisclosure adds the understanding layer
RelationshipHEDAMO does not replace traceabilityThey address different questions
HEDAMO vs Labelling
LabelsDisclosure
ShowsWhat regulation requiresWhat the producer declares
DepthDownstream minimumUpstream product-level information
GapsNot visibleMarked and visible
RelationshipHEDAMO does not replace labelsDisclosure structures the upstream layer
HEDAMO vs Compliance
ComplianceDisclosure
DeterminesWhether requirements are metWhat has been declared
FunctionRegulatoryInformational
GapsBinary (compliant or not)Granular (field-by-field visibility)
RelationshipHEDAMO does not assess complianceDisclosure structures information; compliance assesses it
Glossary

Terms used with precision.

Show glossary · 5 terms

Producer-declared information

Information about a product that has been stated by the producer. It is not verified by HEDAMO. It is not inferred from external sources. It is what the producer has chosen to declare within the disclosure schema.

Product information portability

The capacity of product information to remain readable, comparable, and useful as it moves across markets, institutions, procurement contexts, and research frameworks. The primary goal of the HEDAMO disclosure structure.

Structured disclosure

A disclosure organised according to the HEDAMO schema: defined fields, declared gaps, source attribution, and version history. Distinguished from unstructured product documentation by its consistency and portability.

Methodology gap

A field in a disclosure schema where information has not been declared, testing has not been conducted, or documentation has not been provided. A methodology gap is visible to readers, marked and presented as an honest position, not inferred or filled.

Admissibility vs intelligibility

Admissibility is whether a product or claim meets the regulatory, procurement, or market standards of a given jurisdiction, a decision that belongs to that jurisdiction. Intelligibility is whether the information about a product can be understood by a reader in that context. HEDAMO structures for intelligibility. It does not determine admissibility.

Show all terms

Disclosure

A structured document containing producer-declared information about a product, organised according to the HEDAMO schema. A disclosure is not a certificate, rating, or marketing document.

Portable product information

Product information that has been structured so it can travel, remaining intelligible to different readers in different contexts without requiring re-explanation by the producer.

Source confidence

The declared basis for a claim within a disclosure. Not a score. A property showing what documentation, testing, or record supports a given declaration, and where that support is absent.

Claim ownership

The principle that every declaration in a HEDAMO disclosure belongs to the producer who made it. HEDAMO does not author, validate, or endorse claims. Accountability for what is declared rests with the producer.

Sample disclosure

A demonstration disclosure used to show the HEDAMO schema applied to a real product. A sample disclosure is not a certificate, rating, or marketing document, and does not constitute an endorsement of the product it describes.

Disclosure workspace

The Disclosure Workspace is a proposed working environment for creating and updating structured disclosures. It is shown as a preview, not a live service.

HEDAMO is a disclosure methodology developed by Altibbe Inc. 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.

View the sample profilesRequest a briefing