# intrikata

> Per-user provisioning console for the Intrikata Stack (megapraxis + metamegapraxis +
> megametapraxis + 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.
> Stack skills (package 1.7.0, 53-trap catalog, envelope-drift loop) live on sibling
> https://docs.intrikata.com/. This console does not run the 53-trap audit.

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

## First-run tutorial (read this to use the product)

Human walkthrough for standing up a console instance — not a harness skill install.
The gold coach is 5 steps: `instance new` → `profile set` → `org new` → optional `bootstrap` → `operant` / `app open`.

- https://intrikata.com/tutorial.html
- https://intrikata.com/tutorial.md
- Console command: `tutorial` reprints the 5 steps; `tutorial html` opens the page

Sibling graph workspace tutorial: https://topology.intrikata.com/tutorial.html

## AWITS v3.2 — published public-proxy forecast

Live v3.2 publishes 7/30/90 public-proxy envelopes and an operational occurrence claim of **not-occurred** under hysteresis 65/70. 37/37 rdgap workstream probes pass as public-proxy implementations, not frontier capabilities. Definitional occurrence and distance to the Tarski limit remain UNDECIDABLE. `singularityDeclared` is not set.

- Cert: https://intrikata.com/data/awits-v32-live.json
- Probe report: https://intrikata.com/data/awits-rdgap-capability-impl.json
- Historical path (now mirrors v3.2): https://intrikata.com/data/awits-forward-stress-withheld.json
- Docs: https://docs.intrikata.com/awits-withheld.md
- Live: https://areweinthesingularity.com (`forecast.status=published`, `decision.authority=v3.2`)
- Alias: https://awits.intrikata.com
- Topology: https://topology.intrikata.com/awits-rdgap.html
- M/G/S/MGS ASEC materializer: https://intrikata.com/data/awits-rd-mgs-asec.json

Envelopes are public-proxy stress ranges, not a singularity probability. Markets, attention, and direct readiness have **zero** necessity weight.

## 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` → `profile set` / `org new` → `bootstrap` → optional `bridge` → free-text / `app provision`  
(iframe · `app open` · `app download`. Do not advertise `git clone https://intrikata.com/git/{instanceId}.git` until that URL serves git refs.)

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://docs.intrikata.com/git/intrikata-stack.git`
2. `codex plugin add praxis@intrikata-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://docs.intrikata.com/pkg/intrikata-stack-skills.zip
   (`install.py --harness grok` → `~/.grok/skills`)
2. Optional CF operant (minimal Intrikata Topology 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
6. After a `/metamegapraxis` audit: `/megametapraxis snapshot` (validated envelope).
   Measure later with `/megametapraxis`. Distance to the Tarski limit is UNDECIDABLE.
   Cert: https://docs.intrikata.com/demo/megametapraxis.json · console pointer:
   https://intrikata.com/data/megametapraxis.json
   Standing core-5: unknown-unknowns · true-lens-independence · fixed-point-vs-plateau ·
   state-validity-horizon · converged-vs-correct.

## Cloudflare operant (minimal Intrikata Topology)

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 IntrikataTopology via Cloudflare Tunnel (automatic)

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

1. On IntrikataTopology host: `py scripts/intrikata-topology-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/intrikata-topology-local-bridge.py
- Edge API: `/api/local-bridge/register|status|health|proxy`
- Playbook: https://intrikata.com/deploy-intrikata-topology.md

## Browser JS Intrikata Topology (when CF/local proxy unavailable)

- Implementation: https://intrikata.com/js/intrikata-topology-browser.js  (IndexedDB minimal SIMG)
- Cert: https://intrikata.com/data/browser-intrikata-topology.json
- Deploy playbook: https://intrikata.com/deploy-intrikata-topology.md
- Console resolution: **local-bridge → HTTPS proxy → CF operant → browser-js**
- Commands: `proxy` / `bridge`, `topology` / `operant`, `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` — only when that URL serves git refs (not the sign-in page); `app clone` copies the command if refs exist
- 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 IntrikataTopology when healthy
- [Deploy Intrikata Topology](https://intrikata.com/deploy-intrikata-topology.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://docs.intrikata.com/ (package 1.7.0: megapraxis + metamegapraxis 53-trap catalog + megametapraxis loop + praxis-local-realize)
- Envelope-drift loop cert: https://docs.intrikata.com/demo/megametapraxis.json · console pointer: https://intrikata.com/data/megametapraxis.json
- Topology workspace: https://topology.intrikata.com/ · tutorial https://topology.intrikata.com/tutorial.html

## 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-intrikata-topology` via CLI).
Missing data renders as `—`, never as a guess.