Back to corpus
architecturetechnical paper candidatescore 36
Stage 3 — FORGE: Pebble V0.8 Architecture
> The creative architecture distilled from Stages 1+2. > Audience: meta:omega (executes this) and meta:hydra (stress-tests this).
Full HTML reader
Read the full artifact
Extracted abstract or opening context
> The creative architecture distilled from Stages 1+2. > Audience: meta:omega (executes this) and meta:hydra (stress-tests this).
The whole V0.8 system is the result of mechanically applying that formula to each of the four phases. There is exactly one creative gesture per phase — every other decision falls out of the formula.
Every V0.8 artefact is one of six categories. Each category has fixed behavioural rules. Mixing categories within a single endpoint is forbidden.
| DNA | Plane | Lifetime | Failure rule | Storage | Examples | |-----|-------|----------|--------------|---------|----------| | **🟢 ControlOp** | Control | request/response | throws + user-visible banner | none | `/codex/inject?chat_id`, `/captain/ask`, `/state/restore` | | **🔵 DataStream** | Data | long-lived WS / poll loop | silent retry, banner only when stale > N min | App Group projection | ntfy WS, ntfy `.summarised`, snapshot polling | | **🟡 Bridge** | tmux-as-RPC (Captain) | long-lived daemon | restart via launchd; control ops 504 on timeout; data ops drop messages | none (bridge is stateless) | `captain-bridge.py` | | **🟠 Snapshotter** | Local→disk | long-lived launchd | KeepAlive + atomic-rename on writes; missing snapshots → "Captain unsure" | `[home-path]` | `mesh-state-snapshotter.py` | | **🟣 Projection** | Local SQLite | persistent | append-only mirror of authoritative SQLite; widget read-only | `Group/pebble-projection.sqlite` | conversations_top3, projection_captain, projection_health | | **🔴 Strategy** | Code-level | per-call | confidence-scored ladder; telemetry to caller | none | `AXStrategy`, `ShortcutStrategy`, `URLStrategy` |
A new endpoint or daemon must declare its DNA in its docstring. PR review rejects mixed-DNA artefacts (e.g., a `ControlOp` that returns a stream).
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.