Documentation · Releases · Talos

Talos — the Pantheonic automaton

v.Chronos.Talos.3 — legacy v.H.1.65

The Hub takes its place as a Pantheonic automaton — it signs from its own Codex, fires its Dalos on the shared Khronoton engine, redeploys its own containerized body blue/green, and meters its own reads back to Pythia — and none of it can be blocked by a Pythia outage.

Talos.0 migrates the Hub from a hand-run control surface into a report-metered automaton in the Pantheon alongside Pythia and Mnemosyne. Its Codex moves off the legacy package onto @ancientpantheon/codex, carrying the existing master-key-sealed vault + scheduled transactions across intact. Its Dalos — the codex-signed on-chain cronotons — adopts the shared @ancientpantheon/khronoton-core engine. The whole site + hub + API is containerized (Next.js standalone on a slim image) and deployed by a zero-downtime blue/green swap the operator drives from an in-dashboard Update & Deploy panel — build the idle color, health-check it (database + token-signing both proven), flip nginx, retire the old color, and restart the worker gracefully with no missed fire. The admin surface is re-shelled into the Pantheonic 3-level header + a sidebar Admin Dashboard, gated by a 4-tier role ladder (operator ⊂ baron ⊂ modern ⊂ ancient). And a dual-link Pythia connector mints an ephemeral key through which the Hub reports its OWN direct reads to the oracle for PythXP — best-effort and self-healing, so a Pythia restart re-mints on its own and a Pythia outage never blocks the Hub, which is more foundational: it feeds Pythia her nodes.

Why “Talos”

Talos was the giant bronze automaton of Greek myth — forged by the smith-god to walk his circuit and guard the shore on his own, with no hand at the tiller. It is the archetype of the thing that runs itself.

For this release, “Talos” names the shape of the change: the Hub stops being a control surface a human drives step by step and becomes an automaton — it holds its own signing keys (the Codex), fires scheduled on-chain transactions on its own engine (the Khronoton-driven Dalos), carries a containerized body it can rebuild and swap under itself, and reports its own work back to the oracle. It takes its place beside Pythia and Mnemosyne as a full Pantheonic entity.

What Talos delivers

Codex on the Pantheonic package. The master-key-sealed operator Codex — the vault the Dalos signs from — moves onto @ancientpantheon/codex, carrying the existing sealed keys + scheduled transactions across byte-for-byte (no re-format).
Khronoton engine. The Dalos — the codex-signed, scheduled on-chain cronotons — adopts the shared @ancientpantheon/khronoton-core engine, keeping every existing schedule + its exactly-once atomic claim intact.
Containerized, self-deployed body. The whole app runs as a slim standalone container, deployed by a zero-downtime blue/green swap driven from the dashboard: build the idle color, prove it is healthy (database open + token-signing working), flip nginx, retire the old color, and restart the worker gracefully.
Pantheonic admin surface.A 3-level header + a sidebar Admin Dashboard, gated by a 4-tier role ladder (operator ⊂ baron ⊂ modern ⊂ ancient) — non-admin actions in the header, admin actions behind the dashboard.
Pythia connector + report metering. A dual-link connector mints an ephemeral key; the Hub keeps reading direct-to-node and reports its own reads to Pythia for PythXP — best-effort, bounded, and self-healing, so a Pythia outage never blocks the Hub.
Fleet Mesh — push telemetry replaces the SSH status sweep.Each box runs a small signed reporter that reads its own chainweb containers locally and pushes an HMAC-authenticated report to the hub over outbound HTTPS. At cutover the reports become the source of truth for node sync state, and the hub’s fleet-wide SSH status sweep — the historical stall source — is parked behind a flag (instantly reversible). Works on every network type (permanent, rotating-home, and CGNAT boxes) with no tunnel required for telemetry. A public live Fleet Mesh maprenders the whole fleet reporting in real time. The reporter also runs each box’s own Pythia-servability probe locally (does its external:443 present a valid cert and answer chainweb /info) and pushes the verdict, so the hub no longer SSH-probes eligibility either — the last status probe moves onto the reliable outbound-HTTPS push, ending the intermittent all-red Pythia slot map that a contended SSH sweep used to cause.
Per-container version in the node registry. The Nodes viewshows each chainweb container’s running version in the Role column — the/info package version captured on the last successful probe — so an operator can confirm at a glance that every container is on the intended image after a fleet upgrade (a container running image tag v3.2.1-stoa.2 reads v3.2.1). A container the hub can’t currently reach reads unknown until its next successful probe.
Talos.1 — live-floor cronoton gas.The Hub’s own codex cronotons no longer carry a fixed gas price. The executor prices every autonomic fire freshat the moment it builds the transaction — the current network floor plus an optional per-cronoton priority buffer (default 0) — so a job set up months ago always pays the minimum in force today instead of a stale flat rate. The Config tab shows the live floor read-only and an editable buffer; existing cronotons migrate automatically to “pay exactly the floor” with no re-editing, and scheduled pool payouts inherit the same fix.

See the documentation index for the current, version-stamped reference of everything the site and hub can do.