Teacher Box
K-12 educators, subdivided by subject — science, math, English, history, art, and special education.
The roadmap
Each category was chosen because it has a clear set of tools, a clear set of practitioners willing to serve on a board, and clear unmet demand. They ship in order, because getting one stack right teaches you how to build the next two.
Education and nonprofit first, where the partner organisation already has reach.
K-12 educators, subdivided by subject — science, math, English, history, art, and special education.
Small-to-mid nonprofit executives: donor relations, board governance, grant management, impact reporting.
Independent event planners and small event firms.
Broadening from institutions to individuals and households.
Sole proprietors and businesses under ten employees.
Journalists, analysts, and civic researchers. Heavy overlap with open-source research work.
Parents managing a household, family finances, kids' schools, and aging-parent care.
Fields with the strictest compliance needs, and the ones closest to the mission.
Private-practice mental health practitioners. Configured for clinical confidentiality by default.
Small congregation leaders: communication, scheduling, financial stewardship.
Volunteer fire, EMT, and search-and-rescue. Field-grade and offline-capable where possible.
Veterans transitioning to civilian work.
Homeschooling parents: curriculum, scheduling, and record-keeping.
Local volunteer civic watchdogs. Open-source research, lightly scoped.
Browse boxes by profession. Each page lists every app, the configuration philosophy, the board members, and the date the stack was last updated.
Once you're set up, this is the dashboard: every app with a status indicator — signed in, configured, or needs attention — and one click to launch any of them.
The wizard that installs and configures each app in sequence, handling the sign-in flows and applying opinionated defaults. Roughly 30 to 60 minutes for a full stack the first time.
When the board changes a stack, you see the change in your dashboard and choose whether to apply or defer it. Nothing changes without your say-so.
Every stack and every app inside it carries a signed certificate. Public, hash-chained, and verifiable — the same machinery already used to certify data sets.
One open repository of configuration scripts, per app, per stack. Anyone can open a pull request; the board reviews and merges.
Built on Conduit, which already handles short-lived credentials and 24-hour rotation. You hold your own credentials — Trade Box never sees them in plaintext.
Your credentials stay yours. The vault holds them per-subscriber, and the platform never sees them in plaintext — the same pattern already used for short-lived credentials elsewhere in the ecosystem.