docs: release notes, changelog and site for 0.3.0

2026-10-10 20:21:13 +01:00
parent d8c0f4d09a
commit 9db3159c32
4 changed files with 23 additions and 17 deletions
@@ -2,7 +2,7 @@
 All notable changes to Noema are recorded here. Format follows Keep a Changelog; versions follow SemVer.
-## [Unreleased]
+## [0.3.0] - 2026-09-22
 Volition, planning and cognitive research (PLAN.md §8; docs/volition.md, docs/planning.md, docs/agency.md, docs/cognitive-research.md).
@@ -117,7 +117,7 @@ noemactl fork dani --snapshot <id> --name dani-test
 ## Status
-Unreleased (after 0.2.0): volition, planning and cognitive research (PLAN.md §8) add wants, intentions and commitments as separate states, validated plans with a restart-safe executor that verifies outcomes and replans, typed host, service, log and read-only browser capabilities, temporary scoped authority requested by minds and decided by operators, forensic "why" explanations, attribution, introspection accuracy, and research experiments with ablations, workspace and self-model manipulations and counterfactual replays.
+0.3.0: volition, planning and cognitive research (PLAN.md §8) add wants, intentions and commitments as separate states, validated plans with a restart-safe executor that verifies outcomes and replans, typed host, service, log and read-only browser capabilities, temporary scoped authority requested by minds and decided by operators, forensic "why" explanations, attribution, introspection accuracy, and research experiments with ablations, workspace and self-model manipulations and counterfactual replays.
 Version 0.2.0: all sixteen phases of [PLAN.md](PLAN.md) are implemented, and the epistemic honesty review (PLAN.md §7, summarised in [docs/epistemics.md](docs/epistemics.md)) separated assertions from beliefs, recorded evidence provenance, labelled every score as uncalibrated, added explicit unknowns, temporal beliefs, per-subject source reliability, runtime identity for replay, cognitive forks per model, a causal timeline, audited redaction and Amazon Bedrock. Highlights beyond the first milestone: goals and motivation, predictions and calibration, metacognition, reflection and consolidation, the relationship graph, the capability and policy layer, integrations (research folder, git, Prometheus, webhooks), dreaming, snapshots and forks, cognitive replay, experiments, export/import, TOTP. See [CHANGELOG.md](CHANGELOG.md), [docs/RELEASE_NOTES.md](docs/RELEASE_NOTES.md) and the API document at [docs/openapi.json](docs/openapi.json) (also served at `/api/v1/openapi.json`).
@@ -1,32 +1,34 @@
-# Noema 0.2.0
+# Noema 0.3.0
-Second release: every phase of the plan is implemented, tested and documented, and the epistemic honesty review pass is complete.
+Third release: volition, planning and cognitive research (PLAN.md §8), on top of the 0.2.0 epistemic review and Amazon Bedrock support.
 ## What you get
 - A daemon (`noemad`) hosting many minds, each with identity, personality, configuration, working memory, workspace, memories, beliefs with evidence arithmetic, goals, drives, affect, predictions, self-model, narrative, notifications and an append-only cognitive history.
 - An inspectable model of volition: **wants** with origin, strength, urgency and decay; **want conflicts** with both sides and the recorded reason one was preferred; **commitments** (do or refrain, optionally unless approved) with due dates, expiry, beneficiary and normative weight; **intentions** with sources, expected result, confidence, priority, blocked reasons and subordinate intentions; and an append-only ledger of why each want did or did not become an intention ([volition.md](volition.md)).
 - Explicit **plans**: dependency graphs of typed steps with assumptions, expectations, preconditions, budgets, alternatives and completion criteria, validated by Go code against the registered capability vocabulary; a scheduler-owned executor that claims steps with conditional updates, acts only through the capability layer, verifies outcomes by observation, records prediction errors, replans into new revisions while keeping the old plan as history, recovers after restarts without repeating non-idempotent actions, and learns what worked as procedural memory ([planning.md](planning.md)).
 - Capability negotiation: structured **capability requests** (scope, duration, operation cap, reason, evidence, risk, mitigation, fallback, alternatives) decided only by named operators into **scoped grants** that expire, count operations and restrict targets, parameters and access; a frozen registry with access, side-effect, idempotency, timeout and cost metadata; typed `service.status`, `service.restart`, `logs.query` (personal data masked), `host.disk.usage`, `host.memory.status`, `host.process.list` and read-only `browser.navigate`, `browser.read`, `browser.links`.
 - Forensic **"why?"** explanations built only from recorded state, conservative **attribution** (caused, followed, independent, unknown), introspection intents for past beliefs, lineage and counterfactuals, and every introspective reply scored against provenance ([agency.md](agency.md)).
 - A **cognitive research** framework: ablations and workspace overrides in forks only, self-model manipulations, counterfactual replays that omit recorded events, protocol metadata, operational measures with definitions, reproducibility status, agency metrics and metacognitive calibration ([cognitive-research.md](cognitive-research.md)). Noema does not claim that any of these measures establishes phenomenal consciousness or sentience.
 - Deterministic attention and executive logic; language models only as replaceable services (OpenAI-compatible, Anthropic, Ollama, Amazon Bedrock) with recorded, replayable calls and encrypted secret references.
- A capability layer that is the only way a mind can act: ALLOW / ASK / DENY policies, approvals bound to exact requests, locked capabilities, tool output treated as data.
+- Integrations, background cognition, study tools (snapshots, forks, comparison, replay, experiments), a complete web UI with wants, intentions, commitments, plans, agency timeline, why and research pages, a CLI (`noemactl`), an OpenAPI document, Prometheus metrics, audit log, roles, sessions, API tokens and TOTP.
- Integrations: research folder, git mirrors, Prometheus/VictoriaMetrics, signed webhooks.
+
- Background cognition: consolidation, reflection, metacognition, dreaming (opt-in, cannot act).
+## Security
- Study tools: snapshots, forks sharing history by reference, comparison, export/import, cognitive replay (exact / approximate / diverged), experiments with exportable results.
+
- A complete web UI, a CLI (`noemactl`), an OpenAPI document, Prometheus metrics, audit log, roles, sessions, API tokens and TOTP.
+Wants, intentions, commitments, plans and model output are data to the capability layer; nothing cognitive can set policy, approve, grant or revoke, and a mind cannot decide its own request. Forks no longer inherit policy rules unless the operator asks (`inherit_policies`), and work inherited mid-flight is quiesced. Dreams may want but cannot request authority, plan awake or act. Every invariant in PLAN.md §8.4 has a test in `tests/security`.
 ## Verification
-`go vet`, `go test -race ./...`, staticcheck, gosec (G104 excluded) and govulncheck are clean with Go 1.26.8.
+`go vet`, `go test -race ./...`, staticcheck, gosec (G104 excluded) and govulncheck are clean with Go 1.26.8. govulncheck reports one module-level advisory (GO-2026-5932, `golang.org/x/crypto/openpgp`, no fix available) in a package Noema does not import; no reachable vulnerability is reported.
-## Since 0.1.0
+## Since 0.2.0
-The review pass recorded in PLAN.md §7 and summarised in [epistemics.md](epistemics.md), plus the Amazon Bedrock provider, are the 0.2.0 section of the changelog. Its remaining limitations are listed at the end of that document.
+The 0.3.0 section of the changelog lists everything added, changed and fixed, including the defects found by the release review: a plan model consulted when a deterministic strategy applied, intention and plan transitions without compare-and-set, and map-order iteration in decisions and cycle output.
 ## After 0.2.0 (unreleased)
 Volition, planning and cognitive research are in the [Unreleased] section of the changelog and PLAN.md §8. govulncheck reports one module-level advisory (GO-2026-5932, `golang.org/x/crypto/openpgp`, no fix available) in a package Noema does not import; no reachable vulnerability is reported.
 ## Known limits
 - Replays diverge honestly when retrieval scoring depends on wall-clock recency; a virtual clock for replay is future work.
 - Introspection accuracy is scored lexically against recorded facts; a paraphrase with no shared terms scores as unsupported, never as supported.
 - Browser write operations (click, fill, submit, download) are designed in ADR-0011 but not registered.
 - No screenshots yet; the build environment has no browser.
 - Model comparisons in experiments are made by changing role routing between runs; the routing in force is recorded with each result.
 - Embeddings need pgvector; without it retrieval is lexical and structural only.
@@ -26,6 +26,10 @@ Noema was built in sixteen explicit phases, each committed with tests and docume
 After the 0.1 release the project was reviewed against its own claims: is what the documentation says about evidence, security, reproducibility and privacy true of the code? Each finding was classified with evidence before anything changed, recorded in the plan, and fixed with the smallest coherent change, its own tests and its own commit. The outcome is summarised under [epistemic honesty](epistemics): assertions kept apart from beliefs, evidence provenance and per-family counting, honest score labels with gated calibration, explicit unknowns, temporal scope, source reliability per subject, association distinguished from causation, runtime identity on snapshots and replays, forks per model, a bounded causal timeline, audited redaction, a threat model rewritten from the implementation, and Amazon Bedrock. Eight migrations were added; none discarded data, and every one has a down file.
 ## 0.3: volition, planning and research
 The third release replaced the compressed goal-to-action path with explicit, persisted states that have different consequences: wants, want conflicts, commitments, intentions and plans, each with its own events, its own decision ledger and its own inspection page ([volition](volition), [planning](planning)). Acting still happens only through the capability layer, now with temporary scoped authority that a mind can request and only a named operator can grant, typed host, service, log and read-only browser capabilities, and a frozen registry. Forensic "why?" explanations and conservative attribution are built from the record alone ([agency](agency)), and a research framework makes the architecture's functional properties testable in forks without claiming consciousness ([cognitive research](cognitive-research)). Four migrations were added, all additive with down files. A release review then read the whole change against its specification and fixed three defects it found, each with a regression test.
 ## How it is verified
 Every subsystem has unit tests that run against a fresh database schema; an end-to-end acceptance test drives the whole daemon with a fake model through the first milestone (start, log in, create a mind, converse, inspect memory and beliefs, restart and continue); a security suite exercises prompt injection, roles, cross-mind isolation, stored scripts, secret disclosure and hostile archives; and an opt-in load test seeds a realistic volume and rejects any hot query that drifts off its index. The race detector, staticcheck, gosec and govulncheck were clean at release and at every commit of the 0.2 review, which added tests for provenance grouping, calibration gating, unknown status, temporal supersession, per-subject reliability, relation semantics, cursor gaps, chain traversal bounds, secret-free identity digests, variant comparison, fail-closed routing, redaction, injection by effect, assembled-SQL scanning, the deceived mind, garbage model output, drive vocabulary and Bedrock signing against reference vectors.