{"schema":"signet.certification/v1","profile_name":"Signet compatibility profile","profile_version":{"value":"v1","provenance":"recorded","as_of":"2026-07-22"},"better_auth_version":{"value":"1.6.23","provenance":"recorded","as_of":"2026-07-22"},"certification_gap":{"value":"0","provenance":"recorded","as_of":"2026-07-22"},"e2e_acceptance":{"value":"14 / 14","provenance":"recorded","as_of":"2026-07-22"},"support_posture":"Self-serve documentation plus best-effort support. No SLA is offered or implied.","operating_envelope":{"status":"unmeasured","note":"Not published: the operating envelope (max users, sustained request rate, resource footprint) has not been measured under load, so no capacity number is claimed. A measured envelope will be added here once recorded."},"certification_scope":"The compatibility profile is a public, replayable set of checks; the same checks run against the better-auth reference implementation and against Signet, and the gap is the count of checks the reference passes and Signet does not. Gap 0 means that on every check in the profile, a client cannot tell the two apart. It is not a claim that every better-auth route is implemented: the profile is scoped to what those checks exercise, and anything they do not exercise sits outside it. Ask about a specific route and we will tell you plainly whether it is in the profile.","sweep_files":29}