Hi HN, I'm building witnessd (v0.1.9) to solve the "Is this AI?" problem by looking at the process, not the result.

The Tech:

  - Hardware Binding: Keys are bound to TPM/TEE; signals are signed in a secure environment.
  - Jitter Seals: We capture the statistical entropy of the writing process to differentiate human "jitter" from synthetic input.
  - Time Hardening: We use sequential VDFs (Verifiable Delay Functions) so that forging a 2-hour session requires 2 hours of computation. No parallelization.

Try it out:

  brew install writerslogic/tap/witnessd

Or verify any .war certificate at https://writerslogic.com/verify

I'm a novelist and Marine veteran, and I'm currently moving this through the IETF (draft-condrey-rats-pop). I'd love your feedback on the schema and the VDF implementation.

Some questions:

- why patent it when you give permissions via Apache licence anyway?

- you can't use an external keyboard with this, right?

- can you remove content from the middle of the record without breaking signatures? For example if someone makes an online purchase during a break in the writing and forget to turn off the system, is their credit card number forever bound to that text?