a2bc6347fc
Architecture: - Graph engine (engine.py) loads graph definitions, instantiates nodes - Versioned nodes: input_v1, thinker_v1, output_v1, memorizer_v1, director_v1 - NODE_REGISTRY for dynamic node lookup by name - Graph API: /api/graph/active, /api/graph/list, /api/graph/switch - Graph definition: graphs/v1_current.py (7 nodes, 13 edges, 3 edge types) S3* Audit system: - Workspace mismatch detection (server vs browser controls) - Code-without-tools retry (Thinker wrote code but no tool calls) - Intent-without-action retry (request intent but Thinker only produced text) - Dashboard feedback: browser sends workspace state on every message - Sensor continuous comparison on 5s tick State machines: - create_machine / add_state / reset_machine / destroy_machine via function calling - Local transitions (go:) resolve without LLM round-trip - Button persistence across turns Database tools: - query_db tool via pymysql to MariaDB K3s pod (eras2_production) - Table rendering in workspace (tab-separated parsing) - Director pre-planning with Opus for complex data requests - Error retry with corrected SQL Frontend: - Cytoscape.js pipeline graph with real-time node animations - Overlay scrollbars (CSS-only, no reflow) - Tool call/result trace events - S3* audit events in trace Testing: - 167 integration tests (11 test suites) - 22 node-level unit tests (test_nodes/) - Three test levels: node unit, graph integration, scenario Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
39 lines
1.1 KiB
Markdown
39 lines
1.1 KiB
Markdown
# Counter State
|
|
|
|
Tests that Thinker can create a counter, either via stateful controls (inc/dec bindings)
|
|
or via state machines. Both approaches are valid.
|
|
|
|
## Setup
|
|
- clear history
|
|
|
|
## Steps
|
|
|
|
### 1. Create counter
|
|
- send: create a counter starting at 0 with increment and decrement buttons
|
|
- expect_response: contains "counter" or "count"
|
|
- expect_actions: length >= 2
|
|
- expect_actions: any action contains "increment" or "inc" or "plus" or "add"
|
|
- expect_actions: any action contains "decrement" or "dec" or "minus" or "sub"
|
|
|
|
### 2. Check state
|
|
- expect_state: topic contains "counter" or "count" or "button"
|
|
|
|
### 3. Ask for current value
|
|
- send: what is the current count?
|
|
- expect_response: contains "0" or "zero"
|
|
|
|
### 4. Increment
|
|
- action: first matching "inc"
|
|
- expect_response: contains "1" or "one" or "increment" or "Navigated"
|
|
|
|
### 5. Increment again
|
|
- action: first matching "inc"
|
|
- expect_response: contains "2" or "two" or "increment" or "Navigated"
|
|
|
|
### 6. Decrement
|
|
- action: first matching "dec"
|
|
- expect_response: contains "1" or "one" or "decrement" or "Navigated"
|
|
|
|
### 7. Verify memorizer tracks it
|
|
- expect_state: topic contains "count"
|