Dreamgraph

Current project state: Established behavior and maintainer field confirmations, including permanent Architect operational tabs, the configuration redesign, working Codex CLI Computer Use and successful graph upgrade on all seven tested instances.

Current patch: v14.0.1 release notes cover legacy graph upgrade recovery, Codex CLI Computer Use cleanup, and consistent validation counts across Status and Explorer. Install and graph migration are separate operations; stop a legacy instance before running dg graph-upgrade <instance>. Native API Computer Use remains unqualified in the field, and legacy unresolved references require separate review.

Ashoka's legacy migration procedure provides a reviewed preview, backup, cutover and recovery path. Installing v14 does not migrate a graph automatically. The sealed system gate records 2,040 passing root tests, 546 compiled editor tests and eleven Windows browser checks. The maintainer's original instance remains a separate migration decision.

The Computer Use implementation extends original execution/job/graph owners with scoped grants, durable action receipts, an isolated browser worker and compact Architect/companion controls. SDK/editor controls retain the original owner and captured endpoint; selection issues no grant. Slice 31 is verified for the maintainer's Windows and accepted WSL installer/browser scope. Additional platforms/native desktop backends are deferred; unqualified native CLI/provider control remains unavailable without silent substitution.

Ashoka native-host spend admission joins editor/SDK API and CLI transport to the durable ledger without transferring provider credentials. Generated core contracts separate possible-dispatch permits, trusted host reports and read-only recovery.

The matched answer collector previews exact context/model/retention/tariff disclosures before an operator-approved native API run. Both answers share one job/spend allocation; partial answers survive failure and remain unscored. The public GPT-4.1 pilot records quality failures and does not establish improved understanding or cost savings.

Ashoka's canonical analytics separates current proof, coverage, currency and workload across thirteen Python modules and the daemon. Narrative/lucid interaction preserves historical outcomes, derived ancestry and explicit human contributions through cancellation/recovery.

Ashoka strategy alignment uses one executable catalogue for eleven active dream strategies, exact combined budgets and explicit focus. Reflective is retired explicitly; model hypotheses remain speculative. Implementation modules: src/cognitive/strategy-catalog.ts and src/cognitive/strategy-registry.ts.

Typed plan authority keeps current ownership, running leases, dependency eligibility and reviewed verification in one core reducer and publication journal.