TEE-ATTESTED AI NEGOTIATION

DealProof

Sealed input. Attested output. Nothing else crosses the line.

Khrystian Koci · FeelTech Ltd

Salary negotiation runs on�unverifiable claims.

Offer screenshots

Easy to fake — a doctored PNG is all it takes to invent a competing offer.

Résumés

Self-reported and unverifiable — real experience often sits in NDA’d or private work.

Manual negotiation

Slow, adversarial, and zero privacy — someone always shows their number first.

How it works

01 Sealed input

Offer, comp band, or GitHub credential — encrypted

02 INTEL TDX ENCLAVE · PHALA CLOUD

Candidate

Agent

Claude

Employer

Agent

Claude

Dual agents negotiate on each side’s behalf — memory sealed, no data leaves

03 Human gate

approve · decline · reopen

Verified

outcome

04 DCAP-attested · tamper-proof

Neither side ever sees the other’s number — only the gap.

Not just private — provable.

Sealed floors

Each side’s walk-away number is sealed inside the enclave. It never crosses to the other agent — only offers and moves do.

Human approval gate

Agents propose; people decide. Either side can approve, decline, or reopen for another round before anything is final.

Hardware attestation

A DCAP quote proves the exact published code ran, unmodified — tamper-proof, and independently checkable by anyone.

This isn’t a hackathon toy.

70%

agreement rate on real job-interview negotiation transcripts

48.4%

Pareto improvement vs. a 6.4% naive baseline

256+

automated tests passing · live on Phala Cloud today

Benchmarked on the Yamaguchi et al. job-negotiation corpus (EACL 2021) — real transcripts, not synthetic demos.

“The most complete working

implementation of that research.”

— Andrew Miller · IC3 / Flashbots · co-author, NDAI

Built on IC3 research — NDAI (non-disclosure AI agreements) · πCreds (provenance credentials)

Why salary negotiation first

Everyone recognizes it — and the harm is concrete: a real number gets faked or hidden, and someone loses real money over it.

The same mechanism fits anywhere two parties negotiate with data neither wants to expose.

ROADMAP

01 Verified compensation-band data as another sealed input

02 Provenance credentials beyond GitHub — NDAs, reference letters

03 New verticals on the same engine — procurement, deal rooms

Anywhere two parties negotiate with sensitive data —�this is the pattern.

LIVE DEMO

Scan to run a sealed negotiation right now.

frontend-five-eta-43.vercel.app

Khrystian Koci · kristian.koci@feeltech.co.uk · github.com/kkoci/Dealproof