Files
noema/docs/RELEASE_NOTES.md
T
Andy Dixon 89580c0a79 Phase 16: hardening and release 0.1.0
- TOTP second factor (RFC 6238, secret encrypted under the master key),
  ten hashed single-use recovery codes, two-step login with a pending token
  bound to the client address, account enrolment/disable, admin reset
- tests/security: prompt-injection corpus never acts or creates evidence-free
  beliefs; roles and CSRF on form and API paths; cross-mind isolation
  (demo scenario 5); stored-XSS escaping and CSP across pages; secrets never
  echoed (API, pages, database, archives); hostile archive import; session
  lifecycle and security headers
- OpenAPI 3.1 document generated from the route table, served at
  /api/v1/openapi.json and kept complete by a test
- gosec clean (justified #nosec annotations, cookie/redirect hardening,
  bounded multipart parsing, UUID packing without narrowing conversions);
  govulncheck clean with toolchain pinned to go1.26.8
- THREAT_MODEL verification pointers, SECURITY.md testing section, README,
  CHANGELOG 0.1.0, docs/RELEASE_NOTES.md, PLAN status
2026-07-05 22:30:32 +01:00

1.8 KiB

Noema 0.1.0

First release: every phase of the plan is implemented, tested and documented.

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.
  • Deterministic attention and executive logic; language models only as replaceable services (OpenAI-compatible, Anthropic, Ollama) 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: research folder, git mirrors, Prometheus/VictoriaMetrics, signed webhooks.
  • Background cognition: consolidation, reflection, metacognition, dreaming (opt-in, cannot act).
  • 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.

Verification

go vet, go test -race ./..., staticcheck, gosec (G104 excluded) and govulncheck are clean with Go 1.26.8.

Known limits

  • Replays diverge honestly when retrieval scoring depends on wall-clock recency; a virtual clock for replay is future work.
  • 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.