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>
1.6 KiB
1.6 KiB
State Machines
Tests the machine toolbox: create, add_state, transition, reset, destroy. Machines are persistent UI components with states, buttons, content, and local transitions.
Setup
- clear history
Steps
1. Create a machine
- send: create a navigation machine called "nav" with initial state "main" showing two buttons: Menu 1 (goes to sub1) and Menu 2 (goes to sub2)
- expect_trace: has tool_call create_machine
- expect_trace: machine_created id="nav"
2. Verify machine renders
- send: what machines are on my dashboard?
- expect_response: contains "nav" or "machine"
3. Navigate via button click (local transition)
- action: first matching "menu_1"
- expect_trace: has machine_transition
- expect_trace: no thinker
4. Add a state to existing machine
- send: add a state "sub3" to the nav machine with a Back button and content "Third submenu"
- expect_trace: has tool_call add_state
5. Reset machine
- send: reset the nav machine to its initial state
- expect_trace: has tool_call reset_machine
- expect_response: contains "main" or "reset" or "initial"
6. Create second machine alongside first
- send: create a counter machine called "clicks" with initial state "zero" showing a Click Me button and content "Clicks: 0"
- expect_trace: has tool_call create_machine
- expect_trace: machine_created id="clicks"
7. Both machines coexist
- send: what machines are running?
- expect_response: contains "nav"
- expect_response: contains "click"
8. Destroy one machine
- send: destroy the clicks machine
- expect_trace: has tool_call destroy_machine
- send: what machines are running?
- expect_response: contains "nav"