kskb: resources: 1 row where summary = "research/papers/papers-security-deep-dive-keri-necessary-and-sufficient" sorted by date descending

1 row where summary = "research/papers/papers-security-deep-dive-keri-necessary-and-sufficient" sorted by date descending

descending

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
papers-security-deep-dive-keri-necessary-and-sufficient	Talks and presentations talk	Security Deep Dive: Why KERI is Necessary and Sufficient	https://github.com/SmithSamuelM/Papers/blob/master/presentations/KERI_SecurityDeepDive.web.pdf	{'name': 'Samuel M. Smith'}	no change in six to eighteen months; still correct quiet	2026-10-15	2025-10	2025	practitioner	an author's paper, deck, tutorial or post explaining the suite informative	anyone with the link public	A 76-slide deck by Samuel M. Smith, undated on its title slide (the PDF was created in October 2025), arguing that every part of KERI (Key Event Receipt Infrastructure) is needed to defend against a known set of attacks. It walks through the KERI ecosystem components, key compromise and recovery, delegation, and the trust-basis and spanning-layer background. For practitioners and implementers.	{'name': 'Samuel M. Smith'}														SmithSamuelM/Papers (whitepapers and presentations) smith-papers	Security Deep Dive: Why KERI is Necessary and Sufficient research/papers/papers-security-deep-dive-keri-necessary-and-sufficient		1	1

Advanced export

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

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);