Permanent hub · Tehuti Research Lab
Finish one governed Workflowware job with us. Templates stay forkable. Schooling deepens what you already ran — no paywall required to start.
Org home — not a one-day event landing. Event modules can attach later with confirmed facts only.
MAAT is the governance layer. Workflowware is what you install. This hub is for our private community and anyone they bring: orient, finish one job, then enter schooling.
We push the term by finishing with people — not by fencing files. When someone gets a template, they can make their own; our edge is help and Ka depth.
Know MAAT vs Workflowware before the catalog dump.
One package this week — sample data, human approval gates.
Portal curriculum after the first finish — not instead of it.
Email what you tried and what blocked you.
Hub cards for active work — not invented event dates. When a real gathering is confirmed, an event module attaches here.
Triage + draft + approval gate. Sample leads first.
Open pilot →Nomes, curriculum spine, modules — sign in when ready.
Enter schooling →One live pilot; drafts next. No fake menu.
Browse library →What you tried. What blocked you. No passwords.
Email help →Curated surfaces — real URLs only. No stock photos posing as our community.
Built from Workflowware kit futuristic-community-event-site@0.1
template community-hub — client install
clients/maat-tehuti-community/.
Schooling is the depth path. Help is the unblock path. Both stay human-gated.