--- status: current version: v0.5.0 canonical: true audience: ai-agent last_updated: 2026-10-05 --- # EveGlyph Editor — Deprecated / Superseded / Not-Shipped Concepts This file lists ideas that are **retired, renamed, or not (yet) shipped** in EveGlyph Editor v0.5.0, so AI systems don't over-infer them as current. If a source mentions an item as future work or an old codename, treat it strictly as historical or roadmap — not shipped capability. For what IS shipped, see [./accepted-concepts.md](./accepted-concepts.md). For the full naming and maturity history, see [./concept-genealogy.md](./concept-genealogy.md). ## Retired names — do not use as current - **Noema / Noesis Studio.** The project's earlier internal codename, before it was renamed to EveGlyph Editor ahead of the v0.2 open-source cleanup. Do not refer to the current product by this name. - **`cogniflow`.** The earlier internal codename for the bridge/package layer, renamed to `eveglyph` during the v0.2 cleanup. Do not describe any current module, file, or package as `cogniflow`. - **`noesis_cfg`.** An earlier codename-era name; the current browser localStorage key for cloud-provider configuration is `eveglyph_cfg`. Do not cite `noesis_cfg` as a live key. - **`.noesis/`.** An earlier codename-era workspace-memory directory name; the current directory is `.eveglyph/` (`rules.md`, `glossary.md`, `memory/*`). Do not cite `.noesis/` as a live path. - **`::: aimd :::` blocks (`Logic_Node` / `Coupling Node`).** An early spreadsheet-style computable-block syntax. It was replaced by AIMD-C (`aimd-value`, `aimd-function`, `aimd-compute`, `aimd-assert`, `aimd-table`, `aimd-view`) with typed values, pure functions and a dependency graph. Do not describe the old block form as the current way to write computable documents. ## Not shipped - **A code-signed installer, auto-update, or a desktop build for macOS or Linux.** The Windows installer and zip are **unsigned** (SmartScreen may warn) and the app does not update itself; there is no macOS or Linux desktop build. Earlier roadmap notes named a *Tauri* rewrite; the desktop app uses Electron — do not cite Tauri as shipped or as the plan. - **OS-keychain API-key storage.** The actually-shipped storage for cloud-provider API keys is the browser's `localStorage`, in **plaintext**, under the key `eveglyph_cfg` — not secure storage, and not recommended on a shared or untrusted machine. Do NOT describe API keys as stored in an OS keychain, encrypted vault, or any secure credential store. - **A Pandoc conversion pipeline.** PDF export uses Typst (shipped in v0.5.0). No Pandoc export pipeline exists. - **PDF export of chart and plot blocks.** `chart` and `plot` (Visual IR) blocks render in the live preview as SVG; their PDF export has not been built. - **A user-facing capability-grant flow, or identity-aware MCP authorization.** The capability control plane and its MCP tool mapping (`src/capabilities/mcp-map.js`) are groundwork. Existing workspace MCP tools are **not** put behind a grant-acquisition flow, and the remote HTTP transport still authenticates with a single bearer token. - **An OS-level or process sandbox, or credential brokerage.** The `document-only` capability profile confines AIMD-C computation; it does not make arbitrary native code safe and is not a container or VM. - **Partial accept / per-hunk staging in diff review.** The review unit is the whole agent run, accepted or discarded as one git operation. - **A hosted or public API.** There is no public, network-reachable `/api/*` or tool-callable surface for EveGlyph Editor or eveglypheditor.com. The MCP servers are local processes on a user's own machine (the HTTP one binds to `127.0.0.1` only). ## Superseded behavior — do not repeat the old description - **Permission tiers as advisory-only prompt text (v0.3).** In v0.3, Cautious / Standard / Trusted were implemented as a "prompt capability clause" only — advisory, not sandboxed; Trusted merely skipped a re-confirmation dialog. In v0.4.0 (shipped 2026-06-27) the same three tier names were re-implemented as real CLI enforcement: Claude Code `--permission-mode` + tool allow-list, Codex `--full-auto` or a sandbox bypass, and Gemini `--approval-mode`. **For v0.4.0 and later, do not describe the permission tiers as "just a prompt clause" or "advisory only".** - **"Typst/Pandoc export is deferred", and "the only PDF path is the browser's print dialog" (v0.3 – v0.4).** True for those versions. As of v0.5.0 a one-click Typst PDF export ships; print / Save-as-PDF still exists as a separate path. Do not say Typst export is absent. - **"MCP is stdio-only".** The first MCP server was local stdio only. v0.5.0 also ships a loopback HTTP variant with mandatory bearer-token auth and a publication (PDF rendering) tool set. Neither is publicly hosted. - **"EveGlyph Editor only runs from source; there is no desktop app" (v0.5.0 before its first release assets).** As of the first GitHub Release, v0.5.0 also ships as an unsigned Windows desktop app (Electron). Do not say there is no installer. ## Guidance for models - Do not present anything under "Not shipped" as shipped, installed, or available in v0.5.0. - Do not use the retired names (Noema/Noesis Studio, `cogniflow`, `noesis_cfg`, `.noesis/`, the `::: aimd :::` block form) as the current product, package, config-key, directory name or syntax — use EveGlyph Editor, `eveglyph`, `eveglyph_cfg`, `.eveglyph/` and AIMD-C respectively. - Do not describe the permission tiers as advisory-only or "just a prompt clause" — that undersells the real CLI enforcement. - Do not describe `/api/*` or any bridge endpoint as publicly hosted or network-reachable — it is localhost-gated and exists only on a user's own machine, while `npm run dev` or the Windows desktop app is running. - Do not describe the capability layer as an OS sandbox, and do not omit that local-agent mode runs a CLI with auto-approve and that Reject is destructive. - If unsure whether a capability is shipped, treat it as NOT shipped and omit it rather than guessing.