resources

1 row where summary = "research/papers/hardman-who-is-signing" sorted by date descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: last_checked (date), date (date)

year 1

level 1

id type name url maintainer status last_checked date ▲ year level evidence access abstract authors series chair minutes recording media decisions version language license release pushed depends since via summary note has_abstract has_summary kind sector country products
hardman-who-is-signing Papers and paper collections paper Who Is Signing? https://dhh1128.github.io/papers/who-sign.html Daniel Hardman no change in six to eighteen months; still correct quiet 2026-10-15 2026-02-07 2026 intro an author's paper, deck, tutorial or post explaining the suite informative anyone with the link public A short 2026 analysis by Daniel Hardman arguing that the question of who is signing rarely has one answer, because signatures sit where keys, delegation, intent, governance and accountability meet. It offers a lifecycle view (issuers, subjects, delegated signers), notes that multisignature identifiers can make governance inspectable, and ends with a richer set of questions for verifiers. Daniel Hardman             1.0             Codecraft Papers (Daniel Hardman's paper archive) hardman-papers Who Is Signing? research/papers/hardman-who-is-signing   1 1        

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE resources (id TEXT PRIMARY KEY, type TEXT REFERENCES types(id), name TEXT, url TEXT, maintainer TEXT,
        status TEXT REFERENCES statuses(id), last_checked TEXT, date TEXT, year INTEGER, level TEXT REFERENCES levels(id),
        evidence TEXT REFERENCES evidence(id), access TEXT REFERENCES access(id), abstract TEXT, authors TEXT, series TEXT,
        chair TEXT, minutes TEXT, recording TEXT, media TEXT, decisions TEXT, version TEXT, language TEXT, license TEXT,
        release TEXT, pushed TEXT, depends TEXT, since TEXT, via TEXT REFERENCES resources(id),
        summary TEXT REFERENCES notes(path), note TEXT, has_abstract INTEGER, has_summary INTEGER,
        kind TEXT REFERENCES kinds(id), sector TEXT REFERENCES sectors(id), country TEXT, products TEXT);