How Keel's honesty gates actually work

Description and use

Keel employs three honesty gates—Truthfulness, Fail‑Closed, and Explicit Confirmation—to ensure autopilots do not fabricate answers, halt unverified processes, and require evidence before counting a submission, providing transparent and reliable job‑application automation.

Problem

Ensuring job‑application autopilots do not fabricate information and only submit verifiable data.

Outcome

Keel’s honesty gates ensure that autopilots only submit verifiable data, preventing fabrication and duplicate applications, and providing transparent audit trails.

Workflow

• 1. Resolve form answers from applicant’s answer bank; abstain if missing.
• 2. Prescreen posting against applicant policy; park if commitments cannot be verified.
• 3. Record intent before attempt; mark ambiguous attempts as UNKNOWN and refuse retries.
• 4. Require explicit confirmation text (e.g., Ashby confirmation page) to close the intent.
• 5. Count submission only after confirmation evidence is present.

Evidence

When Keel fills an application form, every answer comes from an answer bank: the applicant's own stored answers, each with provenance (what they stated, and when). If the form asks something the bank doesn't carry, the resolver doesn't improvise. It abstains.

Source

Before a launch packet goes anywhere, the prescreen step checks the posting against the applicant's policy. In the demo, a posting for "Staff Operations Manager" demands five days a week on-site; the policy cap is three. The prescreen verdict is PARK.

Source

Only explicit confirmation text closes the attempt — in the demo, an Ashby confirmation page quoting "Application submitted" with a reference number.

Source