docs: consistency pass after the review
README status, release notes and predictions/personality docs no longer describe 0.2 work as future or 0.1 as current; predictions.md states which processes create predictions and which do not; ENVIRONMENT.md records that the host cluster now has pgvector.
This commit is contained in:
+1
-1
@@ -6,7 +6,7 @@ Recorded at project start (2026-09-14) on the primary development machine.
|
||||
|---|---|---|
|
||||
| Go | 1.26.1 linux/amd64 (`GOTOOLCHAIN=auto`) | `go 1.26` in `go.mod`; stdlib `net/http` routing, `log/slog`, `embed` |
|
||||
| Git | 2.43.0, no `init.defaultBranch` configured | default branch is `master` (git's default) |
|
||||
| PostgreSQL | 16 local cluster on 5432 **without pgvector**; `pgvector/pgvector:pg16` image available | Dev/test DB is the compose container on **5433**. Vector features are optional and detected at migration time |
|
||||
| PostgreSQL | 16 local cluster on 5432 with the `postgresql-16-pgvector` package installed (since 2026-09-15); `pgvector/pgvector:pg16` image available | Dev/test DB is the compose container on **5433**. Vector features are optional and detected at migration time |
|
||||
| Docker | Engine + Compose v5.5 | `deploy/docker-compose.yml` provides db + app |
|
||||
| Static analysis | staticcheck 2026.2.1, gosec, govulncheck in `~/go/bin` | `make lint`, `make security` |
|
||||
| golangci-lint | not installed | not required; staticcheck + vet + gosec suffice |
|
||||
|
||||
@@ -16,6 +16,10 @@ First release: every phase of the plan is implemented, tested and documented.
|
||||
|
||||
`go vet`, `go test -race ./...`, staticcheck, gosec (G104 excluded) and govulncheck are clean with Go 1.26.8.
|
||||
|
||||
## Since 0.1.0 (unreleased)
|
||||
|
||||
The review pass recorded in PLAN.md §7 and summarised in [epistemics.md](epistemics.md) is in the [Unreleased] section of the changelog. Its remaining limitations are listed at the end of that document.
|
||||
|
||||
## Known limits
|
||||
|
||||
- Replays diverge honestly when retrieval scoring depends on wall-clock recency; a virtual clock for replay is future work.
|
||||
|
||||
+1
-1
@@ -29,7 +29,7 @@ A template is a reusable personality. When a mind is based on a template, each v
|
||||
|
||||
## Traits and the runtime
|
||||
|
||||
Later phases consume the personality as follows:
|
||||
The runtime consumes the personality as follows:
|
||||
|
||||
- attention weights are biased by traits such as curiosity and novelty preference;
|
||||
- affect baselines derive from traits (patience, confidence);
|
||||
|
||||
+1
-1
@@ -25,7 +25,7 @@ Outcomes emit `prediction_resolved` or, for refutations, `prediction_error` with
|
||||
|
||||
- Operators, through the Predictions page, the API or `noemactl`.
|
||||
- Causal hypotheses: when the associate process turns "A may have caused B" into a belief, a prediction is derived automatically — the effect should recur within 24 hours if the cause is real — with the belief's confidence, so a miss lowers the hypothesis.
|
||||
- Later phases add predictions from consolidation and reflection.
|
||||
- Reflection reads calibration over the last ninety days and raises an overconfidence warning through metacognition; it does not create predictions. Consolidation creates none either. Prediction outcomes also feed source reliability (docs/beliefs.md).
|
||||
|
||||
## Calibration
|
||||
|
||||
|
||||
Reference in New Issue
Block a user