Trust & Governance
AIEP is designed for open adoption with verifiable integrity. At the substrate level, trust is not a hierarchy — it is a conjunction. Every condition must hold simultaneously, or the artefact is unverified.
The conjunction trust model
Most trust systems are hierarchical: a root authority certifies an intermediate, which certifies a leaf. If you trust the root, you inherit trust down the chain. AIEP uses a fundamentally different model.
All four conditions must hold simultaneously:
| Condition | What it checks | Failure consequence |
|---|---|---|
| Schema conformance | Artefact structure matches the declared schema (version-locked) | Artefact rejected — structure cannot be interpreted |
| Hash integrity | CanonicalHash computed over the artefact body matches the published value | Artefact rejected — content has been altered |
| Registry-linked issuer | Issuer DID resolves to a registered, non-revoked entry in the AIEP registry | Artefact rejected — issuer cannot be traced |
| GoalVector commitment | Artefact carries a valid GoalVector reference traceable to a committed instruction | Artefact rejected — intent cannot be verified |
This is a logical AND, not a chain. A valid certificate from a compromised issuer fails condition 3. A correctly structured artefact with a tampered body fails condition 2. There is no bypass.
Why conjunction is more robust than PKI hierarchy
In a PKI hierarchy, a single compromised certificate authority can issue fraudulent certificates for the entire trust chain. The compromise propagates downward and is undetectable without out-of-band revocation checks.
In AIEP’s conjunction model:
- Compromising the registry does not help unless you can also forge the hash.
- Forging a hash does not help unless you can also pass schema validation.
- Passing schema validation does not help unless the GoalVector is traceable to a committed instruction.
Each condition is independently verifiable against a different substrate. Breaking one does not weaken the others. An attacker must simultaneously satisfy all four — against independent verification surfaces — to present a valid artefact.
Trust is not certification
Trust at the protocol level (the conjunction model above) is distinct from certification.
Certification is a voluntary declaration that a system has been reviewed against AIEP’s published conformance criteria. It protects the meaning of “AIEP Certified” for users and regulators who rely on that claim.
Trust is what the substrate enforces on every artefact, regardless of certification status. An uncertified but well-formed, correctly-issued artefact with a valid hash and a traceable GoalVector is trusted. A certified issuer publishing a malformed or tampered artefact is not.
Open protocol
AIEP is an open protocol. Open use is always permitted.
Anyone may implement AIEP, publish mirror nodes, and build on the architecture without certification.
Verifiable certification
Certification exists only to protect the meaning of “AIEP Certified.”
If a system claims certification, it must publish machine-verifiable metadata and a valid certificate artefact. A claim without evidence is treated as false by any conformant validator.
Transparent development
Concepts are recorded in the Innovation Ledger.
Some detailed materials are NDA-gated; sealed hashes are published so the existence of a record is provable without disclosing its contents.
Compliance scope
Protocol compliance checks only:
- false certification claims
- misuse of certification marks
- redistribution of NDA-restricted packs where applicable
Open adoption is not policed. The conjunction trust model is what protects users — not access control.
Governing law
Unless otherwise agreed in writing, Hub legal terms are governed by the applicable governing law.
Founder statement
AIEP was originated by the Protocol Architect, a Chartered Surveyor with more than three decades of experience in the construction industry.
AI tools have assisted in producing documentation and code; the underlying principles and ideas are those of the Protocol Architect.
Knowledge grows when shared.