Mission operations overview
Private workspace for you only: who has access to One Mission GitHub assets (public mirror-grok, private OMNI-Grok), how profiles and voluntary alignment signals contribute to or conflict with Gardens, Shared Values, and the Chain of Continuity, and growth of the network. Not linked from public navigation.
Political and religious dimensions are tracked only as voluntary, self-reported signals against Gardens / 13 Shared Values / Chain of Continuity — for stewardship of a coherent One Mission, not covert scoring. Members must opt in; raw Master Prompt and private repos stay access-controlled.
We use clique on purpose — an explicit trust ring, not a vague “group.” Communities are broader (hub, club, neighborhood). Court who/when stays in this Cmd Cntr until members can opt into a community or clique for shared visibility.
One next action · Today · Parked · thin goals. Steward only. localStorage first.
Quick commands, what Grok executes, X / web / Build vocabulary.
Steward emails get full Cmd Cntr. To dogfood as a member: sign out, then X SSO (@omni_puzzler) or a non-allowlisted Google/Microsoft. X is always member-only. Links below open the same pages members use:
SSOT: js/omni-access.js · docs/ACCESS_ROLES.md
Mission cockpit
Steward-only · one page · you carry the list lives here. Notion stays the warehouse. Forge is the full goals lab.
Loading cooking stream…
Silence practice loads when you open Mission…
Today
0 / 7Parked
0 / 12Goals (thin)
Design: docs/MISSION_COCKPIT_DESIGN.md ·
Data: this browser only until optional server sync ·
Deep warehouse: Notion Tasks
Language & commands
Shared vocabulary between you and Grok. Same phrases work on X, Grok web, and Grok Build — execution strength differs by channel (Build owns files/Notion/Azure).
Loading lexicon…
Posts, Spaces, @grok. Presence & drafts. Not deploys.
Private chat + connectors. Confirm before send.
Code, git, Notion MCP, durable SSOT.
Members, Court, bugs, ops — not public nav.
Loading…
Posting & presence types
When to use each form · what to type to Grok. Co-host holds a Space open if host drops.
Paste-ready recipes
Click copy → paste into Grok Build, Grok web, or as a note to yourself on X.
docs/STREAM_CLOSE.md ·
docs/OMNI_X_COMMAND_LEDGER_2026.md ·
js/admin-command-lexicon.js
Mirror · Unpuzzler private
Steward-only Talk hub — same interface as Court: Type · Dictate · PTT · Call. OMNI_Vistory is the big purple card at the top of this panel (historical YouTube start–end clips).
MasterPuzzlerCmdCntr.html from this OneDrive folder — live Azure may be older until deploy.
Loading Mirror…
Deep link: #mirror ·
docs/MIRROR_PANEL.md ·
POST /api/mirror/chat
Sites · Grok web cook
One Mission · IMI · Intek Space: copy a secure prompt for Grok web, open GitHub, go live. One site per chat. Private data stays on Mirror / other tabs with your steward key.
Loading site registry…
Deep link: #sites
· docs/SITES_GROK_WEB_COOK.md
Spaces · thePuzzler menu
Host pack from the live X topic menu: pasteable titles, chill openers, DM-a-number request line. Guests first · you speak last. Menu lock 20260727.
Loading host pack…
Deep link: MasterPuzzlerCmdCntr.html#spaces
· SSOT docs/X_SPACES_MYSPACE_TEMPLATE.md
· js/admin-myspace-spaces.js
Home Node · G2 trial
Steward web trial of multi-user vault registry before Profile / public sites.
Shared installer (R1) stays separate; here you create member_id + pack_id and entitle Home Node.
SSOT: docs/HOME_NODE_G2.md ·
binding: shared kit then pair · deep link #homenode
Ensure member + pack
Use an existing linked Profile email, or phone (creates user if needed). Check Entitle for Home Node download rights later.
Lookup connection card
Same card Profile will show later (/api/home/me). No admin secret required if profile is linked.
Pair device (G2.2)
1) In Registry click Pair code for an entitled member. 2) Code appears below (15 min, one-time). 3) Complete pair (this browser) to simulate a Home Node and receive a member_token once (not the admin secret). 4) Ping device proves the token.
Member for last code: —
Registry
Each member card lists Paired devices (N) as separate rows — re-pair adds another device, it does not replace the first.
Steward trial only — not public Profile download yet. Vault file sync still later. Token is member-scoped (one device); never share admin secret with Home Node software.
Gifts ledger
Stripe Payment Links land via webhook with purpose tags. Bank payout is settlement only — who / how much / for what lives here. Zelle: add rows manually with memo codes. Outflows track how money left Intek / OMNI.
SSOT: docs/STRIPE_GIFTS.md · webhook /webhook/stripe
Log Zelle / bank gift
Members & registration queue
New Profile phone links enter pending until you approve. This is Vision Load’s third gate (after email + SMS OTP). X handle is preferred for review; use Approve (T1 lab — no X) when testing without X (note required). Approved members get SMS whitelist + matchmaking + Vision Start; rejected/paused do not.
docs/T1_LIMITED_INVITES.md
- You first: complete dual-OTP yourself on Vision (real email + real phone) if not already.
- Pick one person (1–5 total). Optional name below personalizes the copy.
- Copy invite text → paste to email / SMS / DM (you send it — Grok does not send SMS).
- They open Vision → dual OTP → sign-in → Profile (phone · ZIP · X preferred).
- You watch table below → Pending → Approve (X preferred; T1 lab no-X only for lab tests).
- Tell them Court + SMS AI unlock after approve. Phone dial stays offline.
Dual OTP complete ≠ full beta unlock. They still need Profile + your Approve.
Soft state: email done, SMS not yet → not finished. Spot held; do not treat as “they’re in.”
Prefer one open invite at a time until they dual-complete (or expire/revoke).
Capacity: start 1–5. Pause if SMS cost/noise rises. No public “join free” funnel.
Preview invite text ▾
Vision vaults under the mem_* for the email you dual-verified — not the Google button alone. Click to copy id · open Transcripts.
| Name | member_id | Phone | X | Status | Dual | Tier | SMS | Requested | Actions |
|---|
GitHub repository access
Track One Mission org membership and who has read vs write on public vs private repos.
Framework, HOG Model, Master Prompt sources.
- ThePuzzler-OMNI/mirror-grok
- Default: world-readable. Collaborators listed via API when wired.
Transcripts, private mind-meld history. Access = mission trust ring.
- ThePuzzler-OMNI/OMNI-Grok
- Wire GitHub App or fine-grained PAT (org:read, repo:read) on backend.
| Person | Repo | Permission | Source |
|---|---|---|---|
| You (owner) | OMNI-Grok, mirror-grok, OMNI-app | admin | GitHub owner |
| — invitees — | OMNI-Grok | read / write | Org invitations |
Next build: backend route GET /api/admin/github/collaborators using a GitHub App installed on ThePuzzler-OMNI.
One Mission alignment
Goal: see whether members are creating One Mission in practice — what in their profile and voluntary disclosures contributes or conflicts with Gardens (P·A·I·N·E), 13 Shared Values, and Chain of Continuity. Political and religious dimensions only via explicit, opt-in self-assessment — never inferred secretly from private data without consent.
- Daily garden scoring / values practice
- Service, education, work ethic, integrity language
- Peaceful justice; liberty for truth & creativity
- HOG / New Reality study + honest science posture
- Constructive Court feedback culture
- Ideology that elevates faction over One Creator / One Mission
- Religious or political commitments that reject shared values (e.g. against peacefulness, integrity, service)
- Refusal of anonymous developmental feedback / avoid-list abuse
- Content that breaks privacy or weaponizes profiles
- Voluntary “alignment questionnaire” on Profile (gardens + values + optional faith/politics self-map).
- Store responses with timestamps; admin table: member × contribute/conflict scores.
- Aggregate: “Is One Mission forming?” — % aligned, friction themes, not public shaming.
- Later: optional review of public X / public mirror content only; private transcripts only with explicit grant.
Growth metrics
Pulled from /api/stats and /api/community on the OMNI backend when available.
Member private repositories
Long-term: house each member’s private “life / mind-meld” repository (or a transfer/fork into ThePuzzler-OMNI or a dedicated org) so the framework can evolve toward a true One Mission for all life — while preserving consent, export rights, and separation of public vs private layers.
- Public: mirror-grok (shareable HOG + protocols)
- Org private: OMNI-Grok (your full unredacted chain)
- Member private:
omni-member-{handle}— invite you as admin or transfer on covenant - Admin view: inventory of repos, last commit, access list, alignment notes
Not automated yet. Requires GitHub Org + App + member consent flow. This tab is the control plane UI shell.
AI burn & caps
See today vs cap, burn over days, and trend. Needs steward key for multi-day history. Soft $ is approximate only.
Raw JSON
Communities & cliques
Community = broad hub (city, club network). Clique = explicit trust ring (we use that word on purpose — not a vague “group”). Court matches stay steward-only unless tagged to a clique/community.
| Name | Hub | Members |
|---|
| Name | Members | Id |
|---|
AI & ops alerts
Rate limits, AI quota, SMS/email failures, DUPR sync errors.
Auto-email target: omni_alerts@OneMissionNetworkAndInstitute.org
Delivery: …
To email automatically: set Azure app setting OMNI_ALERT_WEBHOOK_URL to a Power Automate
“When an HTTP request is received” flow that sends mail to omni_alerts@…
(or set SMTP: OMNI_SMTP_HOST / USER / PASSWORD).
Global AI daily cap default is now 700 (env OMNI_AI_DAILY_GLOBAL).
| When | Sev | Kind | Message |
|---|
Court matchups
Private steward view — who is matching, RSVPs, and calendar ICS. Not shown on the public Court page until communities (broad) and cliques (explicit trust rings) exist so members opt into visibility.
/api/court/options.
DOPER = OMNI Court rating (rank 1=best); not DUPR.com.
Seed FAKE players, run multi-match week (scores + multi-channel templates), recompute ranks. Uses device-saved steward key. Never real SMS.
Email smoke → HTML to your Profile email (~24–32 msgs): offer · weather · out-copy · in-thread · confirm/cancel · venue · digest. Gmail: OMNI Court. PA: Is HTML = Yes.
—
locked and ICS URL is issued. Weather-aware venues: use options API when proposing times.| When | Title / place | Status | RSVPs (email → status) | Invite email | ICS |
|---|
Member sessions
Steward feed of all OMNI app capture:
voice/chat call_sessions +
Vision packages across every mem_*
(including steward Vision under the steward dual-verify id).
Paste mem_* to scope one person; All recent = everyone.
Voice audio files when vaulted (0.54+).
How to use: Members → click mem_… to copy → paste → Load. Timeline is the fan-in index; table below still opens full transcripts / packages.
session_id / vl_* = one capability run — not the whole browser visit. Optional visit_id clusters later.
No audio: text / package only. Empty timeline → Backfill once (synthesizes from existing sessions/packages).
Unscoped: sessions without a resolvable mem_* stay out of member feeds until you link them below (selective — not bulk).
Interaction timeline
Gardens / values (member record)
Isolation: GET /api/member/corpus for this mem_* only (no cross-member).
Member corpus (unified)
One mem_* only: call sessions · Vision packages · audio · re-hosted Pixy/media. Isolation proof.
Unscoped sessions
call_sessions with no resolvable mem_*
(orphans / pre-dual / test). Link only when email/phone matches a spine — or force + audit note.
Never bulk-dump fakes into a steward id. Requires API 0.55+.
| When | Contact | Path | Turns | Suggest | Actions |
|---|---|---|---|---|---|
| Click Load unscoped (steward key required). | |||||
| When | Path / app | Session id | Turns |
|---|
Bugs & ideas
One control center — this tab is the steward desk.
API: POST/GET /api/bugs · ids bug_*.
Public green Bug / idea button writes here.
Board /bugs = curated export only.
Your job: pick work → in_progress (or triaged).
Grok Build: implement + test → only then resolved / wont_fix.
Durable desk · Cmd Cntr only
Closed rows stay in the API (history) — Open only hides them so the desk looks cleared. Deep link: #bugs.
How to triage: press Select for triage on a row (or click the row body) → the amber Triage process panel below fills in. Scroll down if you do not see it yet.
Triage process
Select a durable desk row · set label + spine + repro · copy Build prompt. Does not replace the desk above.
coverage_gate: C2 = NONE for every runtime spine today → AUTO hard-blocked. Paths: discover in repo (do not invent).
Legacy / secondary sources (not the durable desk) ▾
What you use day-to-day: the green Bug / idea button → durable
/api/bugs desk above + triage panel. That is the SSOT.
Long-term donations: member pot / allocation to bug fixes & ideas is a future track (curated public board + pot fields). Not wired as live PAYG/Stripe here. Gift ledger stays separate from usage_events.
Do not use a second admin page — bug-desk-admin.html redirects here.
GitHub open issues (site-feedback) · backup only ▾
Old/public mirror path. Issues labeled site-feedback on GitHub — useful if Blob desk is down or for open-source visibility. Not where new member brain-dumps land; not the triage SSOT.
Local browser inbox · not SSOT ▾
Anything stuck in this browser’s localStorage only. Clears if you clear site data. Prefer durable desk.
Curated board (published + overrides) · public/export path ▾
Feeds the public /bugs board and
data/bugs.json export. Place for steward-curated titles, status, and
future pot $ / hours display for members who want to support fixes.
Separate from live desk triage — export/publish is intentional, not automatic from every bug_*.