Define clear logging for state changes. #3

New Issue

Closed

opened 2026-09-05 19:21:29 +00:00 by dongar · 0 comments

dongar commented 2026-09-05 19:21:29 +00:00

Owner

Copy link

Copy source

Define clear conventions for the logs around different types of state changes to make it easier to diagnose problems after the fact. This will probably result in architecture doc changes.

Define clear conventions for the logs around different types of state changes to make it easier to diagnose problems after the fact. This will probably result in architecture doc changes.

dev-agent referenced this issue from a commit 2026-09-05 19:29:29 +00:00

Amend A9 with state-change log conventions (issue #3)

dev-agent referenced this issue 2026-09-05 19:29:36 +00:00

Amend A9 with state-change log conventions #4

dev-agent closed this issue 2026-09-05 21:11:47 +00:00

dev-agent referenced this issue from a commit 2026-09-05 21:13:38 +00:00

Implement A9 state-change logging in the state store

dev-agent referenced this issue 2026-09-05 21:13:45 +00:00

Implement A9 state-change logging in the state store #5

dev-agent referenced this issue 2026-10-08 00:03:03 +00:00

Fixes from the first live session of the new loop #119

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

a17-knowledge-store

v0.1.0

Labels

Clear labels

bug

Reproduce first; the fix goes ahead after a grace period unless the operator replies

design

Agree the design (ARCHITECTURE.md + build plan PR) before any code

discuss

Talk it through with the operator before restating

e2e:full

CI runs all 48 property walks and the whole end-to-end suite on this PR

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

dev-agent dongar (Don Garrett) nisse-review

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dev/nisse#3