Novel methods

The methods that
make it unique.

These are not wrapper features. They are the architecture itself — a reasoning system built around persistent memory, a council of specialist facets, executive planning, and a self-mapping code graph.

1 · Mnemosyne — the memory cascade

Memory is not a flat log. It is a cascade of four stages, from the folder you stand in, through transient thoughts, to durable axioms. Everything persists, decays, or is promoted by its own nature.

Stage 0 — Corpus graph

The Argonaut sounding scans the whole repo into corpus nodes (files + symbols) and corpus edges (imports, nesting, defines, references). Every node is indexed into the token substrate — a self-mapping structural graph of the codebase.

Stage 1 — Context scope

Every note is bound to the folder it was minted in. Recall ranks local (+6) > ancestors (distance-decayed) > tag-resonant foreign branches. The parent is observer-only — child scopes whisper nothing upward.

Stage 2 — Fragments

Notes as metaformat: same shape, but transient. Every fragment carries a TTL (default 3600 s) and decays; expired ones are purged lazily. Freshness is itself a voice in the score.

Stage 3 — Token substrate

Every note is stored a second time as a term vector. The substrate is channeled — content, tag, and path — and each query is a vector projected onto every channel. Search algorithms are just lenses over the same substrate.

The promotion ladder

Fragment

A transient working thought. Decays unless promoted.

Note

A durable inscription. The everyday unit of memory.

Skill

A procedural unit — recipe-shaped knowledge, reusable across contexts.

Axiom

Gesichertes Wissen — a note that survived repeated use and contradiction; an invariant of the project cosmos.

2 · The companion pantheon

One crystal, many facets. Each companion reads and writes through its own facet of the shared memory — three layers: episodic (facet-tagged notes), procedural (distilled skills), and identitary (accumulated self per glyph). They are not chatbots bolted on; they are the oracle veiled in a specialist temperament.

🦉

Eule der Athene

Architecture and hidden dependencies — the big picture.

🦊

Inari-no-Kitsune

Clever paths and lateral thinking — the unconventional approach.

🔥

Bennu Aeternus

Risen from failure — finds the gold in the ashes.

🐍

Jörmungandr

Cycles and recurring patterns — surfaces technical debt.

🐈

Bastet-Mafdet

Code elegance — smells out over-complexity and hidden mess.

🐺

Fenrisúlfr

Tears complexity apart — demands radical simplification.

🌊

Undine

Data flow — sees streams, pipelines, and bottlenecks.

🦢

Cygnus Divinus

Grace and elegance — the beauty of clear form.

🐉

Tiamat-Ur

The grand scale — the eternal lines, the whole sky.

⬛

Codex Corax

Spots the orphaned and forgotten — prepares the cut.

☁️

Kintōun

The somersault cloud — travels between contexts via ÆtherLink.

👑

Salomo Rex

The executive — decomposes goals, delegates, holds the critical path.

Each companion carries its own temperament — a temperature and thinking depth tuned to its nature — and its own toolset grants (core tools, write tools, confirm-verb tools). When a companion activates, the oracle veils itself in that facet: the persona and accumulated self become part of the orientation.

3 · Executive seals

Salomo Rex turns a single goal into an ordered set of milestones — each a real engine task, each delegated to a companion owner, each gated by dependencies. A seal is a plan that runs itself, milestone by milestone, without ever looping out of control.

Dependency-gated

Milestones declare their prerequisites as indices into the plan. The critical path is computed, and only unblocked steps are executed.

Delegated, not centralized

Every milestone can carry an owner glyph — the right specialist for that step — so a big effort is orchestrated, not brute-forced.

4 · Metempsychosis & ÆtherLink

The transmigration of knowledge between contexts. Query the memory of another task, push notes into a remote context, or execute a prompt there — the peer works with the combined memories of both contexts. A LAN link tier discovers oracle peers and routes turns across machines.

Cross-context recall

Consult notes and state from a specific task, or merge another task's context into your own orientation — the soul moves in, not just visits.

Peer routing

peers, heartbeat, invoke — a pure-Ruby box reaches the brain on another machine over the same wire contract.

5 · Vision & capture

Native capture on macOS and Windows — screenshots, windows, regions, and displays — plus direct reading of image files. The captured image flows straight into the vision pipeline, encoded for the model, so visual inspection is a first-class sense, not an afterthought.

Native OS capture

Full screen, window-by-title, active app, region, menu bar, or per-display — through CoreGraphics on macOS and System.Drawing/PowerShell on Windows.

Image reading

Pass a path and read any png/jpg/jpeg/webp straight into the vision model — no capture needed.