okengine 0.10.2 → 0.10.3

package/site/content/docs/console/gates.mdx

@@ -1,73 +0,0 @@
----
-title: "Gates"
-description: "Permission inquiry, rate counters, and continuous audit of unguarded vs explicitly public flows."
-icon: "Shield"
-source: "docs/spec/console.md"
----
-
-The Gates panel answers **who may do what** without dumping a giant roles×permissions matrix as
-the home screen. Inquire from a principal or from a flow; the simulator shows the chain in
-evaluation order.
-
-<Callout title="The one rule">
-  Refuse the giant roles×permissions matrix as the entry point — inquire from principal or from
-  flow.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card title="Simulator" description="Gate chain in evaluation order — where a denial stopped." />
-  <Card
-    title="Unguarded vs public"
-    description="Empty chain (missing posture) vs gate.public (intentional)."
-  />
-  <Card title="Deploy diff" description="Permission widening caught from Manifest Diff." />
-  <Card
-    title="Plane separation"
-    description="Operator holding an application scope is a violation."
-  />
-</Cards>
-
-## Unguarded vs explicit public
-
-| Flag            | Meaning                                                                      |
-| --------------- | ---------------------------------------------------------------------------- |
-| Unguarded       | User-plane flow with an **empty** gate chain — missing auth posture          |
-| Explicit public | Chain includes the reserved `public` sentinel (`gate.public` on the trigger) |
-
-App boot fails on unguarded HTTP triggers (`GateBootError`) unless `env === "test"` and
-`gate: { unguardedHttp: "allow" }`. Prefer fixing the flow: attach a policy, or attach
-`gate.public` when the surface is intentionally open.
-
-App authors configure Gate under `oke({ gate: { policies, auth, unguardedHttp } })` — see
-[Gate](/docs/elements/gate). Builtin `/auth/*` Flows from `gate.auth` are audited the same way.
-
-## Catalog
-
-Policies, rates, and `/auth/*` Bindings from the Manifest — inquire and audit, not a live
-rate editor. Rate `overridable` is a catalog flag; schedule edits live under
-[Clock](/docs/console/clock).
-
-<Cards>
-  <Card title="Dev" description="full catalog + simulator" />
-  <Card title="Prod" description="same inquire surface; no silent ungated HTTP" />
-</Cards>
-
-## Learn more
-
-- [Gate](/docs/elements/gate) — policies, rate limits, `gate.auth`, posture
-- [Plugins](/docs/plugins) — plugged sign-in method plugins
-- [Access](/docs/console/access) — roles and API keys
-
-## Next
-
-<Cards>
-  <Card title="Gate" description="Declare policies and auth." href="/docs/elements/gate" />
-  <Card title="Access" description="Roles and API keys." href="/docs/console/access" />
-  <Card
-    title="Overview"
-    description="Console panels from the Manifest."
-    href="/docs/console/overview"
-  />
-</Cards>

package/site/content/docs/console/index.mdx

@@ -1,54 +0,0 @@
----
-title: "Console"
-description: "Manifest-derived operator panels on :6533 — health, elements, traces, access, and more."
-icon: "LayoutDashboard"
-source: "docs/spec/console.md"
----
-
-The Console is derived from your Manifest. Each panel answers one operator question.
-
-## Pages
-
-<Cards>
-  <Card
-    title="Overview"
-    description="Is the system healthy right now?"
-    href="/docs/console/overview"
-  />
-  <Card
-    title="Flows"
-    description="What exists; call it; read its contract."
-    href="/docs/console/flows"
-  />
-  <Card title="Signals" description="Queue depth, in-flight, DLQ." href="/docs/console/signals" />
-  <Card title="Store" description="Browse sql/kv/files/index." href="/docs/console/store" />
-  <Card title="Clock" description="Crons, sleeps, journal." href="/docs/console/clock" />
-  <Card
-    title="Gates"
-    description="Permission matrix and rate counters."
-    href="/docs/console/gates"
-  />
-  <Card title="Vault" description="Secret contracts and rotation." href="/docs/console/vault" />
-  <Card
-    title="Channels"
-    description="Templates, receipts, opt-outs."
-    href="/docs/console/channels"
-  />
-  <Card title="AI" description="Prompts, evals, cost, agents." href="/docs/console/ai" />
-  <Card title="Architecture" description="How it all connects." href="/docs/console/architecture" />
-  <Card title="Traces" description="One timeline across effects." href="/docs/console/traces" />
-  <Card title="Runs" description="Wide events per execution." href="/docs/console/runs" />
-  <Card
-    title="Manifest Diff"
-    description="Blast radius of a deploy."
-    href="/docs/console/manifest-diff"
-  />
-  <Card title="Access" description="Identities, roles, API keys." href="/docs/console/access" />
-  <Card title="Plugins" description="Installed plugins and panels." href="/docs/console/plugins" />
-  <Card title="Privacy" description="Where PII lives (conditional)." href="/docs/console/privacy" />
-  <Card
-    title="Tenancy"
-    description="Per-tenant usage (conditional)."
-    href="/docs/console/tenancy"
-  />
-</Cards>

package/site/content/docs/console/manifest-diff.mdx

@@ -1,34 +0,0 @@
----
-title: "Manifest Diff"
-description: "Blast radius of a deploy: new effects, widened permissions."
-icon: "Diff"
-source: "docs/spec/console.md"
----
-
-Answers: **blast radius of a deploy: new effects, widened permissions**
-
-<Callout title="Governing rule">
-  Compares meaning rather than lines — behaviour change, sorted by blast radius.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card title="Contract breaking" description="Existing clients will fail." />
-  <Card
-    title="Permission widening"
-    description="Attack surface grew — gate removed or scope widened."
-  />
-  <Card title="Effect widening" description="New write, external effect, or secret read." />
-  <Card
-    title="CI gate"
-    description="Blocks undeclared breaks; intended breaks need `breaking: true`."
-  />
-</Cards>
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="✓" />
-  <Card title="Prod" description="✓" />
-</Cards>

package/site/content/docs/console/meta.json

@@ -1,24 +0,0 @@
-{
-  "title": "Console",
-  "icon": "LayoutDashboard",
-  "pages": [
-    "index",
-    "overview",
-    "flows",
-    "signals",
-    "store",
-    "clock",
-    "gates",
-    "vault",
-    "channels",
-    "ai",
-    "architecture",
-    "traces",
-    "runs",
-    "manifest-diff",
-    "access",
-    "plugins",
-    "privacy",
-    "tenancy"
-  ]
-}

package/site/content/docs/console/overview.mdx

@@ -1,40 +0,0 @@
----
-title: "Overview"
-description: "Is the system healthy right now?"
-icon: "Activity"
-source: "docs/spec/console.md"
----
-
-Answers: **is the system healthy right now?**
-
-<Callout title="Governing rule">
-  Built on declared objectives — burn rate and ranked findings, not a wall of charts nobody reads.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card
-    title="Declared SLOs"
-    description="Objectives enter the Manifest; lowering a target is a reviewable code change."
-  />
-  <Card
-    title="Burn rate"
-    description="Error rate over tolerable rate — pages and investigates with clear thresholds."
-  />
-  <Card
-    title="Journeys"
-    description="Causal paths, not service lists — impossible compositions rejected at compile."
-  />
-  <Card
-    title="Ranked findings"
-    description="Union of panel findings: user harm first, then irreversibility, then trend."
-  />
-</Cards>
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="✓" />
-  <Card title="Prod" description="✓" />
-</Cards>

package/site/content/docs/console/plugins.mdx

@@ -1,41 +0,0 @@
----
-title: "Plugins"
-description: "Installed plugins and their contributed panels."
-icon: "Puzzle"
-source: "docs/spec/console.md"
----
-
-Answers: **installed plugins and their contributed panels**
-
-<Callout title="Governing rule">
-  Scope is the attachment point — `app.plug()` / `unit.plug()` / `flow.plug()`. The Console never
-  installs anything.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card
-    title="Origin × state"
-    description="Core / Local / Community; state derived from code, not a flag."
-  />
-  <Card
-    title="Declares vs intercepts"
-    description="Boot contributions vs per-request hooks with measured cost."
-  />
-  <Card
-    title="Supply chain"
-    description="No lifecycle scripts; capability widening hits Manifest Diff."
-  />
-  <Card
-    title="Install path"
-    description="Shows state and hands you the command — no browser install."
-  />
-</Cards>
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="✓" />
-  <Card title="Prod" description="✓" />
-</Cards>

package/site/content/docs/console/privacy.mdx

@@ -1,32 +0,0 @@
----
-title: "Privacy"
-description: "Where PII lives, who touches it, export/erase (conditional)."
-icon: "EyeOff"
-source: "docs/spec/console.md"
----
-
-Answers: **where PII lives, who touches it, export/erase**
-
-<Callout title="Governing rule">
-  Conditional panel — appears when the privacy plugin is plugged. Catalog row is the durable
-  reference.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card title="PII map" description="Where personal data lives and who touches it." />
-  <Card title="Export / erase" description="`oke privacy export|erase --subject` across stores." />
-</Cards>
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="✓" />
-  <Card title="Prod" description="✓" />
-</Cards>
-
-<Callout title="Conditional">
-  This panel appears when the optional core plugin is plugged. There is no separate detailed
-  subsection beyond the catalog row.
-</Callout>

package/site/content/docs/console/runs.mdx

@@ -1,50 +0,0 @@
----
-title: "Runs"
-description: "Wide events — one record per flow execution."
-icon: "Play"
-source: "docs/spec/console.md"
----
-
-Answers: **wide events — one record per flow execution, queried by dimension**
-
-<Callout title="Governing rule">
-  One flow execution = one wide event = one span. Analysis by dimension, not a text search box.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card
-    title="Wide events"
-    description="Dimensions from effects — no manual instrumentation tax."
-  />
-  <Card
-    title="Error patterns"
-    description="Failed runs in the lookback window, grouped by error code."
-  />
-  <Card
-    title="Outlier explanation"
-    description="Compare all dimensions between slow and baseline populations."
-  />
-  <Card
-    title="Storage tiers"
-    description="Default Parquet + DuckDB; optional postgres / clickhouse."
-  />
-  <Card
-    title="Lifecycle"
-    description="Retain by default; redaction and crypto-shredding for compliance."
-  />
-</Cards>
-
-Use **Since** (`5m` · `1h` · `24h` · all time) to bound the population. Error patterns count
-`error_code` occurrences in that window — the same store Traces and Overview read.
-
-Local replay: `oke replay --request-id <runId>` re-invokes from the stored input snapshot
-(dry-run when the ledger has `send` / `ask`).
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="✓" />
-  <Card title="Prod" description="✓" />
-</Cards>

package/site/content/docs/console/signals.mdx

@@ -1,40 +0,0 @@
----
-title: "Signals"
-description: "Queue depth, in-flight, DLQ, live monitors, orphaned config."
-icon: "Radio"
-source: "docs/spec/console.md"
----
-
-Answers: **queue depth, in-flight, DLQ, live monitors, orphaned config**
-
-<Callout title="Governing rule">
-  One list grouped by delivery physics — not three tabs that re-split the element.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card title="once" description="Pending, in-flight (leased), DLQ, retry policy." />
-  <Card title="broadcast" description="Per-subscriber lag and targeted replay." />
-  <Card
-    title="live"
-    description="Connection count, throughput, newest-50 payload monitor (full history still retained)."
-  />
-  <Card
-    title="DLQ repair"
-    description="Schema form, typed errors, causal chain, dry-run bulk replay."
-  />
-  <Card
-    title="Orphaned"
-    description="Config still listed after the declaration left code — messages kept; dry-run refused."
-  />
-</Cards>
-
-Dry-run is refused for orphaned signals and for signals with no Manifest consumer — unknown handler shapes are not invoked unsafely. Restore the `signal(…)` declaration (and a consumer) before replaying DLQ rows. Lease / at-least-once physics live on [Signal](/docs/elements/signal).
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="full" />
-  <Card title="Prod" description="replay/purge per gates" />
-</Cards>

package/site/content/docs/console/store.mdx

@@ -1,32 +0,0 @@
----
-title: "Store"
-description: "Browse sql/kv/files/index; cache keys; replica lag."
-icon: "Database"
-source: "docs/spec/console.md"
----
-
-Answers: **browse sql/kv/files/index; cache keys; replica lag**
-
-<Callout title="Governing rule">
-  The most dangerous panel in production — gates, tenant isolation, PII masking, and audit on the
-  data path.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card title="Four facets" description="sql · kv · files · index with adaptive detail." />
-  <Card title="PII masking" description="Follows schema classification, including raw SQL." />
-  <Card title="Cache keys" description="Which read produced a key; which write invalidates it." />
-  <Card
-    title="Direct edit warning"
-    description="Names what will not happen — not a silent row patch."
-  />
-</Cards>
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="full + Studio link" />
-  <Card title="Prod" description="masked, gated, audited" />
-</Cards>

package/site/content/docs/console/tenancy.mdx

@@ -1,32 +0,0 @@
----
-title: "Tenancy"
-description: "Per-tenant usage, limits, isolation checks (conditional)."
-icon: "Building2"
-source: "docs/spec/console.md"
----
-
-Answers: **per-tenant usage, limits, isolation checks**
-
-<Callout title="Governing rule">
-  Conditional panel — appears when the tenancy plugin is plugged. Catalog row is the durable
-  reference.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card title="Usage &amp; limits" description="Per-tenant usage and configured limits." />
-  <Card title="Isolation" description="Checks that tenant boundaries hold." />
-</Cards>
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="✓" />
-  <Card title="Prod" description="✓" />
-</Cards>
-
-<Callout title="Conditional">
-  This panel appears when the optional core plugin is plugged. There is no separate detailed
-  subsection beyond the catalog row.
-</Callout>

package/site/content/docs/console/traces.mdx

@@ -1,38 +0,0 @@
----
-title: "Traces"
-description: "One timeline across http → store → signal → durable steps."
-icon: "Route"
-source: "docs/spec/console.md"
----
-
-Answers: **one timeline across http → store → signal → durable steps**
-
-<Callout title="Governing rule">
-  Folded time across async boundaries — a seven-day sleep is not 99.99% empty waterfall.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card title="Causal chain" description="Join parent/child across emit boundaries." />
-  <Card title="Effect tiers" description="Spans coloured by the same vocabulary as Flows." />
-  <Card
-    title="Filter by effect"
-    description="Everything that wrote a table, sent mail, or cost more than X."
-  />
-  <Card
-    title="Why slow / why fail"
-    description="Critical path highlight; open on the failing span."
-  />
-</Cards>
-
-Chains use `WideEvent.parentId`: producers stamp it on `fx.emit` / `fx.call`;
-consumers record it on their run. Per-effect timing comes from the ledger
-(`timestamp` + `duration`) — not a second instrumentation API.
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="✓" />
-  <Card title="Prod" description="✓" />
-</Cards>

package/site/content/docs/console/vault.mdx

@@ -1,41 +0,0 @@
----
-title: "Vault"
-description: "Secret contracts, who can read each, rotation due."
-icon: "KeyRound"
-source: "docs/spec/console.md"
----
-
-Answers: **secret contracts, who can read each, rotation due**
-
-<Callout title="Governing rule">
-  Secrets are write-only — the panel can set and rotate; it can never reveal.
-</Callout>
-
-## What this panel shows
-
-<Cards>
-  <Card
-    title="Contracts"
-    description="Optional description as the human title; technical key stays visible."
-  />
-  <Card
-    title="Fingerprints"
-    description="Salted hash per environment — rotation and drift without exposure."
-  />
-  <Card
-    title="Resolution chain"
-    description="Which source won: env, files, vault driver, or fallback."
-  />
-  <Card title="Who can read" description="Derived from effects that declare `fx.vault`." />
-  <Card
-    title="Rotation blast radius"
-    description="In-flight durable runs that wake with a new key."
-  />
-</Cards>
-
-## Catalog
-
-<Cards>
-  <Card title="Dev" description="full" />
-  <Card title="Prod" description="set/rotate only, never reveal" />
-</Cards>