aming-claw-hn-demo-before-worklisted

## REQUIRED FIRST READ Before any response that uses this skill, in this exact order: ListMcpResourcesTool() ReadMcpResourceTool(uri="aming-claw://current-context") ReadMcpResourceTool(uri="aming-claw://skill") ReadMcpResourceTool(uri="aming-claw://graph-first") current-context anchors project_id, governance URLs, and 3 guardrails. skill is the operating contract (Start Sequence, Observer Operating Modes). graph-first has copy-pasteable graph_query payload examples. Common failures when these are skipped: - Bootstrapping the wrong project (workspace_match auto-detected aming-claw) - Calling task_create dev/pm (V1 default is observer-led mf_parallel.v1) - Using Grep on the aming-claw codebase instead of graph_query - Fabricating trace_id strings (audit ledger is server-resolvable, will fail) - Running Execution Supervisor mode by default (Design Alignment is default) # HN Demo: Before Work Show how Aming Claw turns "the AI will grep blindly and duplicate work" into a bounded, auditable start condition. ## Fear AI does not understand the project structure, misses existing modules, and creates duplicate work. ## Evidence To Collect - Graph discovery: node, file, function, or neighbor evidence for the target area before reading broad source files. - Backlog duplicate/overlap probe: real `backlog_list` or governance API response for the proposed work title/files before `backlog_upsert`, recorded exactly with `count`, `bugs`, and `request_id`. - Backlog cont