@techreport{brezun-human-continuity-http-00,
    number =    {draft-brezun-human-continuity-http-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-brezun-human-continuity-http/00/},
    author =    {aurélien brézun},
    title =     {{Human Continuity for HTTP}},
    pagetotal = 80,
    year =      2026,
    month =     aug,
    day =       5,
    abstract =  {This document defines an HTTP extension for origins that need to attribute repeated participation to the same verified unique human within a declared continuity scope, without requiring a global human identifier or replacing existing authentication. Within a continuity scope, the same human yields one verifier-local handle across all of their accounts, devices, and agents and cannot present as two, distinguishing the signal from authentication, which identifies a credential a human may hold many of. An origin server can publish policy for client-presented unique-human artifacts, issue an explicit challenge, and receive a client-presented artifact on a subsequent request. The framework is independent of any realm operator, credential technology, proof system, or definition of humanness. Companion profiles define artifact syntax, issuance, verification, challenge binding, replay behavior, holder binding, privacy properties, realm metadata, and verifier output. A conforming profile produces a verifier-local continuity\_handle scoped to a realm, attestation audience, and purpose. This version defines no initial profile.},
}