update claude settings and wip DAG with SlotMap
This commit is contained in:
5
.claude/memory/MEMORY.md
Normal file
5
.claude/memory/MEMORY.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# Memory Index
|
||||
|
||||
- [No constant leaf in RcCircuit](feedback_dag_no_const_leaf.md) — coefficients live in Poly; don't suggest a Const variant for RcCircuit
|
||||
- [Always ask before changing settings](feedback_settings_approval.md) — describe proposed settings changes and wait for approval before editing any settings file
|
||||
- [Use cargo add for dependencies](feedback_cargo_add.md) — never edit Cargo.toml directly; use `cargo add <dep>` instead
|
||||
11
.claude/memory/feedback_dag_no_const_leaf.md
Normal file
11
.claude/memory/feedback_dag_no_const_leaf.md
Normal file
@@ -0,0 +1,11 @@
|
||||
---
|
||||
name: No constant leaf in RcCircuit
|
||||
description: User does not want a Const leaf variant in RcCircuit — coefficients belong in Poly, not in the circuit DAG
|
||||
type: feedback
|
||||
originSessionId: 4c73b3be-dd4d-4cc5-ae2c-da7af42d444b
|
||||
---
|
||||
Do not suggest adding a `Const` (or constant) leaf variant to `RcCircuit` in `src/circuit/dag.rs`.
|
||||
|
||||
**Why:** Coefficients are handled at the `Poly` layer. The circuit DAG only encodes structural/symbolic relationships between variables.
|
||||
|
||||
**How to apply:** When reviewing or extending `RcCircuit`, treat the absence of a constant leaf as intentional design, not a gap.
|
||||
11
.claude/memory/feedback_settings_approval.md
Normal file
11
.claude/memory/feedback_settings_approval.md
Normal file
@@ -0,0 +1,11 @@
|
||||
---
|
||||
name: Always ask before changing settings
|
||||
description: Never modify any Claude settings files without explicit user approval first
|
||||
type: feedback
|
||||
originSessionId: 4c73b3be-dd4d-4cc5-ae2c-da7af42d444b
|
||||
---
|
||||
Always ask the user for approval before modifying any settings file (`~/.claude/settings.json`, `.claude/settings.json`, `.claude/settings.local.json`).
|
||||
|
||||
**Why:** The user wants full control over their Claude configuration and does not want settings changed autonomously.
|
||||
|
||||
**How to apply:** Before any settings change, explicitly describe what you intend to change and wait for the user to confirm. This applies even when the user's request implies a settings change — describe the proposed edit first, then wait.
|
||||
Reference in New Issue
Block a user