You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**VS Code extension** — chat, dashboard, Explorer (interactive 2D/3D graph + curated mutations), changed-files view, daemon connection, and local support tools
93
93
-**Knowledge graph + cognitive engine** — features, workflows, data model, tensions, validated relationships, and dream-cycle reasoning
94
+
-**Adaptive Future Engine** — advisory candidate-future ranking, future-fit scoring, compact objections, and bounded audit metadata for graph-tool and cognitive-workflow decisions
94
95
-**Datastore-as-Hub** — first-class `datastore` entities, live schema introspection (`scan_database`), and the `schema_grounding` dream strategy for multi-repo SaaS projects sharing a backend (set `DATABASE_URL`; inert otherwise)
95
96
- **Plugin host & SDK (v9.0.0 — stable seams M0–M6)** — in-process plugin runtime (`@dreamgraph/sdk` + `@dreamgraph/host`) with manifest discovery from `<instance>/plugins/<id>/plugin.json`, capability/effect gate registry, telemetry bridge, trust banner, and `dg plugin` CLI (`list`, `inspect`, `register`, `enable`, `disable`, `trust`, `reload`, `unload`). Hot reload/disable plus enriched `system://plugins` (activation, subscriptions, contributed tools/resources). Plugin-contributed MCP tools and resources via `ctx.tools.register` / `ctx.resources.register`, gated by `tools:register` / `resources:register` capabilities and naming/namespace prefix rules. M5 ships outbound webhooks as a *core* subsystem (`dg webhook` CLI; HMAC-signed delivery; persistent dead-letter; replay). M6 adds the UI/closure seams (archetypes, policies, markdown fences, UI hooks). Opt-in via `DG_ALLOW_INPROCESS_PLUGINS=true` plus per-plugin `trusted: true` in `instance.json`. See `examples/hello-events/` for a reference plugin and [`docs/sdk/`](docs/sdk/) for the developer guide and reference manual.
96
97
@@ -304,6 +305,7 @@ DreamGraph has six major surfaces:
304
305
305
306
-**Knowledge graph** — features, workflows, data model, ADRs, UI registry, tensions, and validated edges
v11.0.0 ships the Adaptive Future Engine release line. This release promotes candidate-future ranking, bounded future-fit scoring, and compact audit trails from the v11 plan into the released DreamGraph distribution.
6
+
7
+
## Headline Changes
8
+
9
+
### 1. Adaptive Future Engine
10
+
11
+
- Adds the shared Adaptive Future scaffold in `src/cognitive/adaptive-future-scaffold.ts`.
12
+
- Classifies planning-doc, adapter, graph-tool, and cognitive-workflow task classes.
13
+
- Records selected and rejected candidate IDs, score factors, evidence anchors, objections, route/fallback provenance, and validation failures as compact audit metadata.
14
+
- Keeps all Adaptive Future output advisory and subordinate to accepted ADRs, workflows, API surface, data-model contracts, graph evidence, and explicit user intent.
15
+
16
+
### 2. Runtime Consumers
17
+
18
+
-`enrich_parser_nodes` now emits Adaptive Future audit metadata for graph-tool enrichment work.
19
+
-`solidify_cognitive_insight` now carries Adaptive Future audit metadata through cognitive-workflow planning metadata.
20
+
- Focused tests cover the scaffold, graph-tool audit consumer, and cognitive-workflow audit consumer.
21
+
22
+
### 3. Documentation And Release Alignment
23
+
24
+
- Adds dedicated Adaptive Future Engine documentation in `docs/adaptive-future-engine.md`.
25
+
- Adds a user-guide page in `guide/14-adaptive-future-engine.md`.
26
+
- Updates package versions, SDK docs, install guide references, VS Code extension metadata, root docs, and release notes to the v11.0.0 release line.
27
+
28
+
## Upgrade Notes
29
+
30
+
- No instance migration is required for v11.0.0.
31
+
- Existing deterministic behavior remains available; Adaptive Future metadata is advisory context, not a hard enforcement mechanism.
32
+
- Consumers that do not inspect `adaptive_future_audit` continue to behave as before.
33
+
34
+
## Artifacts
35
+
36
+
Expected release artifacts:
37
+
38
+
-`dreamgraph-11.0.0.tgz`
39
+
-`dreamgraph-sdk-11.0.0.tgz`
40
+
-`dreamgraph-host-11.0.0.tgz`
41
+
-`dreamgraph-vscode-11.0.0.vsix`
42
+
43
+
## Verification
44
+
45
+
Release verification for this cut should include:
46
+
47
+
- focused Adaptive Future tests;
48
+
- full `npm test` where practical;
49
+
-`npm run build`;
50
+
- package artifact creation with `npm pack` for root, SDK, and host packages;
51
+
- VS Code extension packaging with `npm --prefix extensions/vscode run package`.
Copy file name to clipboardExpand all lines: docs/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ This directory contains DreamGraph documentation, but the **canonical living doc
20
20
21
21
Some files in this directory are hand-written narrative or reference documents. They may provide additional background, but they are not the authoritative inventory of the current system state unless explicitly regenerated.
The Adaptive Future Engine is the v11 preference layer for DreamGraph. It ranks compliant candidate futures using graph evidence, accepted ADRs, workflow context, API/data-model contracts, and learned project preference signals.
4
+
5
+
It is advisory by design. ADRs, workflow contracts, API surface, and explicit user instructions remain the hard constraints. The engine helps choose among valid futures; it does not create a new enforcement path or a new cognitive lifecycle state.
6
+
7
+
## What It Adds
8
+
9
+
-**Candidate-future ranking** — compares plausible next actions instead of treating every valid change as equivalent.
10
+
-**Future-fit scoring** — records compact score factors such as evidence coverage, workflow alignment, governance compatibility, blast radius, and reversibility.
11
+
-**Future objections** — preserves why a candidate was rejected, including missing evidence, ADR conflicts, weak anchors, or uncertain fallback behavior.
12
+
-**Adaptive audit trails** — stores selected and rejected candidate IDs, route/fallback provenance, score factors, evidence anchors, objections, and validation failures without persisting raw prompts or full model responses.
13
+
-**Bounded task-class coverage** — classifies planning-doc, adapter, graph-tool, and cognitive-workflow changes for consistent audit metadata.
14
+
15
+
## Runtime Boundaries
16
+
17
+
Adaptive Future Engine output is subordinate to:
18
+
19
+
1. Accepted ADR guard rails.
20
+
2. Registered workflows and lifecycle rules.
21
+
3. API surface and data-model contracts.
22
+
4. Knowledge-graph evidence and provenance.
23
+
5. User intent for the current task.
24
+
25
+
If the engine has insufficient evidence, deterministic fallback behavior must remain available and visible in the audit trail.
26
+
27
+
## Where It Is Used
28
+
29
+
The v11 release wires the shared scaffold into graph-tool and cognitive-workflow consumers:
The Adaptive Future Engine is the v11 advisory preference layer. It compares compliant candidate futures after higher-authority constraints have already been applied: accepted ADRs, workflow/lifecycle rules, API and data-model contracts, graph evidence, and current user intent.
23
+
24
+
Architecturally it provides:
25
+
26
+
- deterministic task-class inference for planning-doc, adapter, graph-tool, and cognitive-workflow changes;
27
+
- future-fit score factors for evidence coverage, governance compatibility, workflow alignment, blast radius, reversibility, and fallback confidence;
28
+
- compact objections for rejected candidates;
29
+
- audit metadata that records selected/rejected candidate IDs, score factors, anchors, route/fallback provenance, and validation failures without storing raw prompts or full model responses.
30
+
31
+
The engine is not an enforcement subsystem and does not add a cognitive lifecycle state. Its output remains advisory and must degrade to deterministic fallback behavior when evidence is insufficient.
32
+
18
33
## Instance Model
19
34
20
35
Each DreamGraph instance has its own root directory under the master directory (typically `~/.dreamgraph/<uuid>/`). The instance stores:
Copy file name to clipboardExpand all lines: docs/release-notes.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,11 @@
1
1
# DreamGraph Release Notes
2
2
3
+
## v11.0.0 - Adaptive Future Engine
4
+
5
+
DreamGraph v11.0.0 ships the Adaptive Future Engine release line: advisory candidate-future ranking, future-fit scoring, compact objections, route/fallback provenance, and bounded audit metadata for graph-tool and cognitive-workflow consumers.
6
+
7
+
See [`../RELEASE_NOTES_v11.0.0.md`](../RELEASE_NOTES_v11.0.0.md) for the full distribution notes.
8
+
3
9
## Codex CLI native Architect adapter
4
10
5
11
The VS Code Architect now includes native `codex-cli` provider support following ADR-201's native CLI adapter constraints. The adapter keeps Codex-specific help probing, isolated `config.toml` generation, login-status validation, process execution, prompt serialization, and ProviderPort projection inside `extensions/vscode/src/architect-core/adapters/codex-cli/`.
0 commit comments