Eight Things Hedamo Refuses to Do

Hedamo maintains a list of structural refusals — things the system is designed not to do, regardless of who requests it.

These are not limitations that might be resolved later. They are architectural decisions that define what the system is.

Hedamo does not verify claims. The producer owns accuracy. The system structures information. It does not check whether declarations are factually correct.

Hedamo does not rank products. Disclosure depth — how completely a producer has documented their product — is measured. Product quality is not. There is no "better" or "worse" in the system's outputs.

Hedamo does not recommend choices. The system presents information. It does not tell consumers, buyers, or governments what to choose.

Hedamo does not enforce penalties. There is no enforcement authority within the system. Enforcement belongs to governments and regulatory bodies.

Hedamo does not create eligibility thresholds. Disclosure scores cannot be used as procurement criteria or market access gates. A product with a lower disclosure score is not excluded from anything.

Hedamo does not enable trade barriers. Disclosures cannot be used as the sole basis for market access decisions.

Hedamo does not share data across jurisdictions without consent. Each government instance is sovereign. Data does not move between jurisdictions unless explicitly authorized.

Hedamo does not allow "best to worst" sorting. No output — for any audience — ranks products against each other. Disclosure indicators are self-contained completeness meters, not comparative hierarchies.

These refusals are not negotiable. They are not features that can be unlocked at a higher subscription tier or requested by a government partner. They are invariants — structural constraints that prevent the system from becoming something it is not.

A system that refuses clearly is a system that can be trusted precisely.