livy-tee

livy-tee is Livy's attestation support for programs that need to bind computation outputs to public values and verifier evidence.

It is useful when a source, adapter, policy program, or custom runtime needs proof material beyond the default MCP policy flow.

What It Does

livy-tee can help a program:

• commit ordered public values
• commit private or large values by hash
• bind public-value bytes and commitments into TDX report data
• request appraisal from the configured verifier path
• serialize attestation material for storage or later verification

Privacy

Trusted execution environments keep runtime memory isolated from the host while the program runs. livy-tee uses that boundary to let private inputs affect execution without making those inputs public.

For private or large values, the runtime can use commit_hashed to commit a canonical hash instead of publishing the raw value. The verifier can later check the attested runtime, the public values, and any private openings against that commitment.

Read Privacy in Livy TEE for the full model.

What It Does Not Prove

livy-tee does not make every external input true.

It proves narrower statements about the program, committed values, runtime identity, and verification path. Source truth, data quality, and policy requirements still need to be modeled explicitly.

When To Use It

Use livy-tee when you need attestations for:

• custom source adapters
• transformation programs
• policy programs
• decision programs
• private evidence commitments
• verifier-facing audit records

For basic protected agent actions, start with MCP. Add livy-tee only when the integration needs attested computation or source claims.

Support

For implementation details, contact Livy support with the program type, verifier path, public values, and privacy requirements.