# intrikata

> Per-user provisioning console for the praxis stack (megapraxis + metamegapraxis + ASEC +
> Fusion Complex). Each instance receives only the minimum graphs needed to stand up the
> framework — never the operator's 450+ project graphs or run-history.

Live: https://intrikata.com · https://intrikata.pages.dev

## Instance onboarding short-circuit (read first)

Collapse full-spectrum domains to a **cascade** — do not re-run meta-audit on every visit:

- Playbook: https://intrikata.com/onboard-instance.md
- Cert: https://intrikata.com/data/instance-onboard.json
  (`short_circuit.eligible=true`, rule=cascade)

Ladder: skills install → `instance new` → `bootstrap` → optional `bridge` → free-text / `app provision`  
(iframe · download · `git clone https://intrikata.com/git/{instanceId}.git`)

Session M/G/S/MGS short-circuit (meta re-reason stop):  
https://intrikata.com/data/session-mgs-shortcircuit.json  
When seed free-text does **not** converge and local-bridge+ops are live, console **auto-dispatches** ≥1 of ClaudeCode_v1 / GrokBuild_v1 / CodexCode_v1 for a Contribution. Register bridge with the **exact** console `session` id.

## OpenAI Codex — install once, start future projects warm

Do **not** reinstall or reprovision Praxis for every project. Start here:

- https://intrikata.com/onboard-codex.md
- https://intrikata.com/data/codex-onboard.json

One-time native install:
1. `codex plugin marketplace add https://praxis-stack.pages.dev/git/praxis-stack.git`
2. `codex plugin add praxis@praxis-stack`
3. Close and reopen Codex once; start a fresh task and verify `$praxis:megapraxis`

Then every future project uses one Megapraxis briefing and stops. Intrikata graph provisioning
is optional and does not install, import, or register the skills. Direct fallback:
`install.py --harness codex` to `~/.codex/skills`, then invoke `$megapraxis`.

## Grok Build — short-circuit onboard (read first)

Do **not** cold-rediscover the stack. Start here:

- https://intrikata.com/onboard-grok.md
- https://intrikata.com/data/grok-onboard.json  (`short_circuit.eligible=true`)

Then:
1. Install skills once from https://praxis-stack.pages.dev/pkg/praxis-stack-skills.zip
   (`install.py --harness grok` → `~/.grok/skills`)
2. Optional CF operant (minimal Pharosiraptor on D1):
   console `instance new <handle>` → `bootstrap` → `operant`
   CLI: `intrikata bootstrap <handle>` then `intrikata operant <handle>`
3. Or local download only: `provision` / `intrikata provision <handle>`
4. Run megapraxis filesystem-fallback — no MCP required
5. Skip auto-swarm; traps #4/#5 are N/A on pure Grok orientation

## Cloudflare operant (minimal Pharosiraptor)

Per-instance seed of the 7 machinery graphs into Cloudflare D1:

- Cert: https://intrikata.com/data/operant-bootstrap.json
- Host health: https://intrikata.com/api/health  (JSON; not SPA)
- `POST /api/bootstrap` `{ "handle": "..." }`
- `GET /api/operant/{instance_id}/health|graphs|nodes?q=`

## Local GraphDoc via Cloudflare Tunnel (automatic)

Browsers cannot call `http://localhost:8080` from `https://intrikata.com` (mixed content).
Automatic path:

1. On GraphDoc host: `py scripts/pharosiraptor-local-bridge.py` (or download from site)
2. Script starts cloudflared quick tunnel + `POST /api/local-bridge/register`
3. Console auto-connects (`?lb_session=` / `proxy connect`) via same-origin edge proxy

- Bridge script: https://intrikata.com/scripts/pharosiraptor-local-bridge.py
- Edge API: `/api/local-bridge/register|status|health|proxy`
- Playbook: https://intrikata.com/deploy-pharosiraptor.md

## Browser JS Pharosiraptor (when CF/local proxy unavailable)

- Implementation: https://intrikata.com/js/pharosiraptor-browser.js  (IndexedDB minimal SIMG)
- Cert: https://intrikata.com/data/browser-pharosiraptor.json
- Deploy playbook: https://intrikata.com/deploy-pharosiraptor.md
- Console resolution: **local-bridge → HTTPS proxy → CF operant → browser-js**
- Commands: `proxy` / `bridge`, `pharosiraptor` / `operant` (`pharos` deprecated alias), `autoprov`
- If the browser already holds **≥2** local instances, background-provisions browser seed + CF bootstrap for each

## Non-command user input

- Free-form English is **not** executed as graph ops — `unknown command` + soft-hint
- Handles must match grammar (letters/digits/`._@+-`); phrases rejected client+server
- Unknown `GET /api/*` → JSON 404 (not HTML)

## App runtime (no Pages deploy required)

- Browser iframe: `/app/{instanceId}/`
- Download: `/api/app/{instanceId}/download`
- Git (D1 assembly): `/git/{instanceId}.git` — full clone; `app clone` copies command
- Free-text generative resolve auto-provisions under Your Instance rail

## Surfaces

- [Instance onboard short-circuit](https://intrikata.com/onboard-instance.md) · [cert](https://intrikata.com/data/instance-onboard.json)
- [Web console](https://intrikata.com/) — help, onboard, codex, grok, instance, bootstrap, app, bridge/ops, …
- [CLI](https://intrikata.com/cli/intrikata.py) — prefers localhost:8080 GraphDoc when healthy
- [Deploy Pharosiraptor](https://intrikata.com/deploy-pharosiraptor.md)
- [Provision template JSON](https://intrikata.com/data/provision.json)
- [Framework snapshot JSON](https://intrikata.com/data/snapshot.json) — scrubbed, read-only
- Sibling skills host: https://praxis-stack.pages.dev/

## Honesty

Numbers come from published snapshot/provision templates, CF operant, optional proxy, or browser-js —
always name the backend (`cf-operant` | `proxy` | `browser-js` | `local-graphdoc` via CLI).
Missing data renders as `—`, never as a guess.