Invented app · built on Kindling · Why Kindling · The apps · The library · The spec
Under the hood
Threshold is a client. It hosts no Pools, reads the ones you keep from their own files, and writes back to them with your credentials. Here is every setting, the files it reads and writes, the block lists it honors, and what Kindling v0.1 can’t say yet.
| Setting | Value | Spec | Why |
|---|---|---|---|
| What Threshold opens | Pools whose manifest names you in curator | §3.2 | A desk shows only the Pools you keep. Visibility is the host’s business; Threshold never widens it. |
| Verification | In words and with an icon, beside every person and curator | §4.5 | Who is asking is always shown, including on the desk. |
| Handshake window | 14 days, carried in each request’s expires_at | §5.2 | The default. Every window is written out in dates. |
| A decline | Remembered per Pool and curator; “Ask again” is refused until the person allows it | §5.2 | The spec’s rule, enforced by the desk, not left to memory. |
| A lapsed request | Nothing is listed; you may ask again, once, with a new window | §5.2 | No answer is not a no, and not a yes. |
| Leaving | Shown to the curator as “left”, with no reason and no way to write about it | §5.3 | A member owes nobody an explanation. |
| Auto-accept | Shown on the member as “joined by their own rule” | §5.5 | Never silent: the person was told, and so are you. |
| Vouching | Recorded with its words, local to one Pool | §4.4 | The same person is email verified everywhere else. |
| Proposals | system note to each, then an intro to both | §5.4 §6.3 | For curator-only-adds Pools and matchmaker tables. Both say yes first. |
| Messaging | Structured email from your own identity | §6.1 §6.2 | Members answer from their own mail. They never need Threshold. |
| Block lists | Each Pool’s own block_list_subscriptions | §7.3 | The desk filters by the lists the manifest names, no more. |
| Consortium entries | One member proposes, two others second, then it is published | §7.3 | The Circular consortium’s rule. No personal details, ever. |
| The curation clock | 90 days from the last action the desk can see | §9.1 | Written in dates, never as an alarm. |
| Transition | 14-day window, two thirds of active members who answer | §9.2 §9.3 | Co-curators first. A host desk writes down votes given in person. |
| Archive | Readable, listed, closed to new requests | §9.4 | Revivable by a returning member. |
| Discovery | Threshold hosts no Pools; its well-known file lists none | §8.3 §10.2 | Your Pools are discovered where they live. |
| Loading a product | index.html#load-<product key>, from the Kindling registry, embedded when the app is built | §3.2 §8.3 | Opens that product’s Pools, and only for the curators their manifests name: the desk signs in as one of them, and the Pools they don’t keep open read-only. A curator who isn’t one of this example’s people is named, never signed in as. |
Threshold hosts no Pools, so its /.well-known/kindling-pool lists none (§8.3, §10.2). It names the operator, so a crawler that finds the domain knows what it is.
{
"schema_version": "0.1",
"pools": [],
"operator": {
"name": "Threshold, the desk for people who keep Pools",
"contact": "desk@threshold.example",
"url": "https://threshold.example"
}
}Four curators, and every Pool that names one of them, plus the dormant Pools their continuity work touches. Each links to its own file on its own site.
oauthoauthcurator-only-addspublicactiveemailoauthuniversal-opt-inpublicactiveemailoauthuniversal-opt-inpublicactiveoauthvouching-requiredpublicactiveemailoauthuniversal-opt-inpublicactiveoauthuniversal-opt-inpublicactiveemailoauthuniversal-opt-inpublicactiveemailuniversal-opt-inpublicdormantoauthcurator-only-addspublicactiveoauthcurator-only-addsunlistedactiveoauthcurator-only-addsunlistedactiveoauthoauthuniversal-opt-inpublicactiveoauthuniversal-opt-inpublicdormantoauthoauthvouching-requiredunlistedactiveoauthoauthcurator-only-addspublicactiveEvery Pool on these desks subscribes to both (§7.3). The desk filters by the lists each manifest names, and nothing else.
Sample files, validated against the repo’s schemas. The desk builds the same shapes live, and shows each one under “The messages, as JSON”.
handshake-request · New in Townsystem · Nadia would like to introduce you to Ireneintro · Gideon, meet Irenewithdrawal · Withdraw me from Tuesday Morning Walkerssystem · Would you keep New in Town?system · A vote given at the reference desk: Chess After Close§6.3 names four types and the schema six, adding withdrawal and system. None of them is a proposal. Threshold sends each note as a system message, then an intro to both once both said yes, as Late Supper does. It marks them with an X-Threshold-Kind: proposal header, which another client would not know to read.
A vouch is local to one Pool (§4.4), and the manifest records only curator-vouched and, in the parsed profile, a verifier and a date. The witness, the job and the words live in the host’s own vouch record, as at Seen Work. Threshold shows them, and says where they count.
There is no message for “will you keep this Pool?” and no field for “stepped back, stays listed, takes no action”. Threshold sends a system message and, on a yes, edits the curator list in the manifest.
§9.1 counts handshake reviews and removal responses as curation, and neither changes updated_at. Threshold shows the last action it can see: a manifest edit, a consent proof, or a request it sent. A host that keeps no log of the others can’t prove a Pool is active.
§5.2 says the 14-day window is configurable per Pool. The manifest has no field for it, so each request carries it in expires_at.
§5.2 says a decline MUST be recorded and a curator MUST NOT resubmit without permission. Neither the record nor the permission is a document in v0.1. Threshold keeps both per Pool and per curator.
A handshake request’s pool object carries the charter, curator, intent and visibility, but not consent_model. Threshold says it in words in every invitation.
v0.1 says how a Pool is read: a JSON document from a Git repository or an endpoint (§3.1). It says nothing about how a curator edits one. Threshold writes through each host’s own repository or API, with the curator’s own credentials, and hosts nothing itself.
Only the published list has a schema (§7.3). The Circular consortium’s rule, one member proposes and two others second, lives in its description. Threshold keeps the proposals at the desk and publishes an entry only when it has its two seconds.
§4.5 says email-verified, oauth-verified, curator-vouched and unverified. The schemas say email, oauth, curator-vouched, unverified and cryptographic. The JSON follows the schemas; the desk shows words.