1.22.0 — Sovereign Workbench
The Sovereign deployment concept now has a maintained, bounded operating path. It uses the existing signed runtime to calculate a project portfolio, schedule its approved projects and prepare an evidence brief. Each stage stops for explicit review, and downstream inputs derive from approved predecessors.
- Private loopback console with authentication, strict input validation, durable pause/recovery, saved mandates and result-bound review. No wallet, model download or payment is needed.
- Independent budget, risk, baseline, allocation optimum, resource-schedule and source checks.
- Signed complete workflow packets with per-stage receipts and pinned-key verification.
- Three synthetic examples, a responsive visual console and a public gallery of actual native fixtures.
- Runnable catalog entry and installed-wheel smoke coverage; native Python 3.11–3.13 and real Chromium gates.
- Updated the Insight browser brace-expansion override to the patched 2.1.7 release after the current dependency audit detected denial-of-service advisories.
- Original deployment source and README archived byte for byte, original standalone HTML retained,
and original gallery presentation preserved as
research.html.
Use the Sovereign guide to install, run, review, verify and recover. Existing shared-runtime journal formats remain compatible; no migration is required. Keep existing environments and a private verified backup before upgrading.
The supported profile remains a private single operator. The workbench does not establish ENS ownership, independent validator approval, mainnet commissioning or autonomous spending. Example benefits are assumptions; no business return, general intelligence or comprehensive production certification is claimed. The separate Ascension reference contracts and runtime settlement controls retain their existing scope.
Start here for the wider agent installation and operator workflow.