admin/claw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: mark internal normalized writer plans as historical

Browse Source
This commit is contained in:
木炎
2026-05-06 09:47:38 +08:00
parent 8162118e6d
commit 6122b521a8
2 changed files with 23 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/superpowers/specs/2026-04-26-skill-normalized-result-and-dashboard-local-reader-design.md
View File

@@ -2,7 +2,9 @@
Date: 2026-04-26
Status: Proposed design for implementation
Status: Historical design archive; the in-repo `normalized_writer` design described here was later migrated out of `claw-new`
Historical note (2026-05-06): this document records the pre-extraction design that originally placed `normalized_writer` inside `claw-new`. The canonical implementation now lives in `D:\data\ideaSpace\rust\sgClaw\normalized_writer`.
Related baseline designs:
@@ -40,14 +42,14 @@ The system must support:
This design is not about changing business detection logic.
It is about adding a stable result contract and a stable local read path for dashboard consumption.
## Non-Negotiable Architecture Constraints
## Historical Architecture Constraints
The implementation must preserve these boundaries:
The pre-extraction design required these boundaries:
1. `run-record.json` remains the raw runtime/audit artifact
2. dashboard must not directly consume `run-record.json`
3. normalized result files become the only supported dashboard-facing data contract
4. `claw-new` is responsible for producing normalized files
4. at the time, `claw-new` was responsible for producing normalized files
5. `digital-employee` is responsible for reading normalized files through a local API
6. dashboard is responsible only for rendering and polling the local API
7. first implementation uses HTTP polling, not websocket
@@ -738,9 +740,11 @@ The index must contain enough information for:
2. quick health/status summary
3. later detail-file lookup
## `claw-new` Normalizer Design
## Historical `claw-new` Normalizer Design
The normalizer must live as a first-class module, not ad hoc file-writing logic.
In the pre-extraction design, the normalizer was intended to live as a first-class module, not ad hoc file-writing logic.
Migration note: `normalized_writer` was later extracted into the standalone repository `D:\data\ideaSpace\rust\sgClaw\normalized_writer`. The structure below is the original in-repo design and is no longer the active `claw-new` layout.
Recommended structure: