← all repositories

ams-demo-0

2 work segments · 5 turns · 0 of 175 commits attributed
· click a segment to open it
2026-09-13 23:56 → 2026-09-14 00:090.2h · 0 commits · 2 asked · 2 replied · session d7cef7ad
the exchange, in order (4)
23:56 · askedso is this enough to connect to ams-demo-0?
23:56 · repliedI don't know what ams-demo-0 expects yet, so I'll look before answering.
23:58 · repliedNot as-is. I checked: `ams-demo-0` is now `assist-demo` (the rename is noted in `AMS_PORTFOLIO_STATUS.md`). The engine has the content assist-demo needs, but the two sides don't speak the same language yet. ## Where they already line up - assist-demo's demo chart set (1-1, 1-2, 1-3, 3-6, 12-1, 16-3, 43-5) is fully compiled and tested here. - The overall design is the same: four-valued matching, both A/B role bindings tried, unknown never excludes, modifiers with judged amounts. - The engine already has an HTTP API (`/v2/cases/evaluate`, `/v2/cases/plan`, `/v2/programs/{chart}/evaluate`), so assist-demo could call it as a separate service. ## What blocks a direct connection 1. **Different fact model.** - assist-demo, and the answerer contract AX is building against, use flat per-vehicle questions (`question-set.v2`: 121 questions such as `c.vehicle.signal_at_entry`, `AR-01`) with no events. - This engine needs an event graph: named events, an interpretation of which event is which, and answers tied to those events. - None of the question IDs match. 2. **Different decision flow.** - assist-demo gives a ratio once the adjuster marks each modifier 적용/미적용 and presses 확정. - This engine only gives a final number after about 100 reviewed inputs, including completion reviews. Until then it returns a range. - In front of a 손해사정사, that difference will be the first thing they notice. 3. **Different runtime.** assist-demo's matcher runs inside the TypeScript app from a compiled `rules.json`, and this engine is Python. Connecting them means a sidecar service plus an adapter, not dropping in a file. ## The flat → event-graph adapter I already built one version of it for the 68-case replay: `tools/replay_qlre_cases.py` turns flat answers into an event graph. - …
00:09 · askedi just want to see how this new question set is meant to work with adjuster. if ams-demo-0 project way is not fit, show me how it should be done.
2026-09-23 01:31 → 01:310.0h · 0 commits · 0 asked · 1 replied · session 1a5c223a
the exchange, in order (1)
01:31 · repliedThere's no `ams-demo-0`. The likely candidates are `lense-demo` and `visus-astra` (a visus variant). Let me check both rather than guess.