STEP 01
Submission
Anyone can propose a stack or an app for one.
Certification
Somebody has to stand behind the list.
A curated stack is only worth as much as the judgement behind it. So the judgement is on the record: every box is reviewed in seven steps by a named board, the certificate is written to a public ledger, and the disagreements are published alongside the decision.
The seven steps
STEP 02
Security review
The apps must respect the privacy of the person using them.
STEP 03
Content review
The apps must actually do what they claim to do for that profession.
STEP 04
Professional-fitness review
The stack must reflect how good practitioners in the field actually work — not how a vendor wishes they worked.
STEP 05
Test deployment
Real practitioners use the stack for 30 to 60 days before anything is granted.
STEP 06
Grant
The stack becomes certified, and the certificate is written to the public ledger.
STEP 07
Annual re-certification
The field changes, so the stack changes. Every stack is reviewed again each year.
What the certificate covers
The certificate covers the stack as a whole and each app inside it. An app that ships in three different boxes holds three context-specific certificates — because the same app in different fields may be set up in genuinely different ways, and the certificate records the configuration as well as the app.
Certificates render against the public ledger. Every appearance of the seal can be clicked and verified.
Who sits on a board
Each professional stack gets its own board: practitioners with at least ten years in the field, plus one editorial reviewer and one security reviewer. Three to five members per stack. Boards meet quarterly.
- Board membership is paid, by modest honorarium, and funded as a real budget line.
- Terms are two years, staggered, so a board can’t quietly calcify.
- Boards publish their dissents. You see the disagreement, not just the consensus — which is how you judge whether the review was real.