Under the hood

How TAP works under the hood

TAP sits in the middle of the system, linking Cheqd for identity and EigenCloud for computation.

[Agent] → [TAP] → [Cheqd] → [EigenCloud]
↓
[Audit Logs]

It runs a few main modules like below:

Policy Engine	Stores and enforces trust rules
Verification Module	Checks credentials through Cheqd APIs
Attestation Module	Confirms execution proofs from EigenCloud
Compliance Logger	Records all decisions with timestamps
Alert System	Flags expired or invalid credentials
Ratings module	Giving a trust score for the request

Example TAP Rules:

{
"policies": [
{
"id": "TAP-001",
"rule": "Agent must hold a valid passport from an approved issuer",
"verify_vc": true
},
{
"id": "TAP-002",
"rule": "Only public_data tasks can be executed in this PoC",
"enforce_attestation": true
},
{
"id": "TAP-003",
"rule": "Every task must have an EigenCloud attestation hash",
"require_attestation": true
}
]
}

These rules are simple and readable. They define what’s allowed, how credentials are verified, and what happens if something fails.