arm101-cli 0.3.3__tar.gz → 0.5.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (96) hide show
  1. arm101_cli-0.5.0/.claude/skills/recall/SKILL.md +181 -0
  2. arm101_cli-0.5.0/.claude/skills/recall/scripts/recall.sh +141 -0
  3. arm101_cli-0.5.0/.claude/skills/remember/SKILL.md +118 -0
  4. arm101_cli-0.5.0/.claude/skills/remember/scripts/remember.sh +138 -0
  5. arm101_cli-0.5.0/.devague/current +1 -0
  6. arm101_cli-0.5.0/.devague/current_plan +1 -0
  7. arm101_cli-0.5.0/.devague/frames/arm101-cli-grows-its-first-hardware-verbs-arm101-f.json +362 -0
  8. arm101_cli-0.5.0/.devague/plans/arm101-cli-grows-its-first-hardware-verbs-arm101-f.json +301 -0
  9. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.gitignore +3 -0
  10. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.markdownlint-cli2.yaml +12 -1
  11. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/CHANGELOG.md +42 -0
  12. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/PKG-INFO +25 -1
  13. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/README.md +18 -0
  14. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/__init__.py +6 -0
  15. arm101_cli-0.5.0/arm101/cli/_commands/calibrate.py +181 -0
  16. arm101_cli-0.5.0/arm101/cli/_commands/find_port.py +108 -0
  17. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_commands/learn.py +12 -0
  18. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_commands/overview.py +3 -0
  19. arm101_cli-0.5.0/arm101/cli/_commands/setup_motors.py +177 -0
  20. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/explain/catalog.py +74 -0
  21. arm101_cli-0.5.0/arm101/hardware/__init__.py +21 -0
  22. arm101_cli-0.5.0/arm101/hardware/bus.py +426 -0
  23. arm101_cli-0.5.0/arm101/hardware/ports.py +100 -0
  24. arm101_cli-0.5.0/arm101/hardware/profiles.py +208 -0
  25. arm101_cli-0.5.0/docs/hardware-validation.md +298 -0
  26. arm101_cli-0.5.0/docs/plans/2026-06-26-arm101-cli-grows-its-first-hardware-verbs-arm101-f.md +83 -0
  27. arm101_cli-0.5.0/docs/specs/2026-06-26-arm101-cli-grows-its-first-hardware-verbs-arm101-f.md +63 -0
  28. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/pyproject.toml +10 -1
  29. arm101_cli-0.5.0/tests/test_bus.py +196 -0
  30. arm101_cli-0.5.0/tests/test_calibrate.py +269 -0
  31. arm101_cli-0.5.0/tests/test_find_port.py +300 -0
  32. arm101_cli-0.5.0/tests/test_hardware_verbs.py +446 -0
  33. arm101_cli-0.5.0/tests/test_ports.py +246 -0
  34. arm101_cli-0.5.0/tests/test_profiles.py +201 -0
  35. arm101_cli-0.5.0/tests/test_setup_motors.py +264 -0
  36. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/uv.lock +36 -1
  37. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/agent-config/SKILL.md +0 -0
  38. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/agent-config/data/backend-fingerprints.yaml +0 -0
  39. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/agent-config/scripts/show.sh +0 -0
  40. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/ask-colleague/SKILL.md +0 -0
  41. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/ask-colleague/prompts/explore.md +0 -0
  42. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/ask-colleague/prompts/review.md +0 -0
  43. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/ask-colleague/prompts/write.md +0 -0
  44. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/ask-colleague/scripts/ask-colleague.sh +0 -0
  45. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/assign-to-workforce/SKILL.md +0 -0
  46. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/assign-to-workforce/scripts/assign-to-workforce.sh +0 -0
  47. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/cicd/SKILL.md +0 -0
  48. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/cicd/scripts/_resolve-nick.sh +0 -0
  49. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/cicd/scripts/portability-lint.sh +0 -0
  50. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/cicd/scripts/pr-reply.sh +0 -0
  51. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/cicd/scripts/pr-status.sh +0 -0
  52. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/cicd/scripts/workflow.sh +0 -0
  53. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/communicate/SKILL.md +0 -0
  54. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/communicate/scripts/fetch-issues.sh +0 -0
  55. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/communicate/scripts/mesh-message.sh +0 -0
  56. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/communicate/scripts/post-comment.sh +0 -0
  57. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/communicate/scripts/post-issue.sh +0 -0
  58. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/communicate/scripts/templates/skill-new-brief.md +0 -0
  59. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/communicate/scripts/templates/skill-update-brief.md +0 -0
  60. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/doc-test-alignment/SKILL.md +0 -0
  61. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/doc-test-alignment/scripts/check.sh +0 -0
  62. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/pypi-maintainer/SKILL.md +0 -0
  63. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/pypi-maintainer/scripts/switch-source.sh +0 -0
  64. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/run-tests/SKILL.md +0 -0
  65. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/run-tests/scripts/test.sh +0 -0
  66. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/sonarclaude/SKILL.md +0 -0
  67. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/sonarclaude/scripts/sonar.sh +0 -0
  68. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/spec-to-plan/SKILL.md +0 -0
  69. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/spec-to-plan/scripts/spec-to-plan.sh +0 -0
  70. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/think/SKILL.md +0 -0
  71. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/think/scripts/think.sh +0 -0
  72. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/version-bump/SKILL.md +0 -0
  73. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills/version-bump/scripts/bump.py +0 -0
  74. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.claude/skills.local.yaml.example +0 -0
  75. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.flake8 +0 -0
  76. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.github/workflows/publish.yml +0 -0
  77. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/.github/workflows/tests.yml +0 -0
  78. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/AGENTS.colleague.md +0 -0
  79. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/CLAUDE.md +0 -0
  80. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/LICENSE +0 -0
  81. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/__init__.py +0 -0
  82. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/__main__.py +0 -0
  83. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_commands/__init__.py +0 -0
  84. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_commands/cli.py +0 -0
  85. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_commands/doctor.py +0 -0
  86. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_commands/explain.py +0 -0
  87. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_commands/whoami.py +0 -0
  88. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_errors.py +0 -0
  89. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/cli/_output.py +0 -0
  90. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/arm101/explain/__init__.py +0 -0
  91. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/culture.yaml +0 -0
  92. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/docs/skill-sources.md +0 -0
  93. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/sonar-project.properties +0 -0
  94. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/tests/__init__.py +0 -0
  95. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/tests/test_cli.py +0 -0
  96. {arm101_cli-0.3.3 → arm101_cli-0.5.0}/tests/test_cli_introspection.py +0 -0
@@ -0,0 +1,181 @@
1
+ ---
2
+ name: recall
3
+ type: command
4
+ description: >
5
+ Search the shared eidetic memory store and get back ranked, provenanced
6
+ records. Drives `eidetic recall` with four search modes — exact (verbatim
7
+ substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid
8
+ (a weighted blend of vector+keyword, the default) — each hit carrying its
9
+ text, full metadata, a relevance `score`, and a freshness `signal`. Recall
10
+ passively reinforces matched records (bumps last_recall + recall_count).
11
+ Shadowed and archived records are excluded by default; use
12
+ --include-shadowed / --include-archived to retrieve them. The store lives at
13
+ ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper
14
+ defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope arm101-cli
15
+ --visibility private`, suffix read from culture.yaml) — matching where
16
+ /remember writes — so a no-flag recall returns this agent's own private records
17
+ plus the shared public pool, and Claude and the colleague backend recall each
18
+ other's memories because both resolve the same suffix via this skill. Use
19
+ when the user says "recall", "what do we know about X", "search memory",
20
+ "have we seen X before", "look it up in memory", "eidetic recall", or before
21
+ answering from scratch when prior context may already be stored. Pairs with
22
+ the sibling /remember skill.
23
+ ---
24
+
25
+ # recall — search the shared eidetic memory
26
+
27
+ `recall` drives **`eidetic recall`**: given a query, it returns the top-k stored
28
+ records ranked by relevance, each with its `text`, full `metadata` (provenance),
29
+ a numeric `score`, and a freshness `signal`. It is the read half of the memory
30
+ surface; the write half is the sibling **/remember** skill.
31
+
32
+ The point of a *shared* store is that memory is a **team faculty**, not a
33
+ per-agent silo: a record Claude wrote is recallable by the colleague backend
34
+ (and vice versa), because both resolve the same `~/.eidetic/memory` path.
35
+
36
+ ## How to run
37
+
38
+ ```bash
39
+ bash .claude/skills/recall/scripts/recall.sh "<query>" [flags...]
40
+ ```
41
+
42
+ The wrapper resolves the CLI portably (installed `eidetic` on `PATH`, else
43
+ `uv run eidetic` from the checkout) and forwards every flag verbatim, so it is
44
+ exactly `eidetic recall …`. Run it from anywhere; the store is the same.
45
+
46
+ ## Search modes (`--mode`, default `hybrid`)
47
+
48
+ | Mode | What it matches | Needs embed server? |
49
+ |------|-----------------|---------------------|
50
+ | `exact` | case-insensitive verbatim substring (`--case-sensitive` to tighten) | no — offline-safe |
51
+ | `approximate` | vector cosine / semantic similarity | yes (falls back offline) |
52
+ | `keyword` | BM25 lexical; only records sharing a query term | no — offline-safe |
53
+ | `hybrid` | `alpha*approximate + (1-alpha)*keyword` (`--alpha`, default 0.5) | uses it when up |
54
+
55
+ `hybrid` is the default because the two signals cover each other's blind spots:
56
+ vector catches paraphrases, keyword catches exact ids/quotes. When the embed
57
+ server is unreachable, `hybrid` collapses to keyword-only (it never fuses
58
+ meaningless offline-fallback cosine).
59
+
60
+ ## Output fields
61
+
62
+ Each hit in `--json` output includes:
63
+
64
+ | Field | Notes |
65
+ |-------|-------|
66
+ | `id` | stable record identity |
67
+ | `text` | the stored chunk |
68
+ | `type` | record type |
69
+ | `metadata` | full provenance, round-tripped verbatim from ingest |
70
+ | `score` | relevance score from the chosen search mode (freshness-blended) |
71
+ | `signal` | freshness strength in [0, 1]; computed at recall time from age, recall frequency, and staleness |
72
+ | `created` | ISO-8601 ingest date (may be DATE_UNKNOWN for legacy records) |
73
+ | `last_recall` | ISO-8601 timestamp of the most recent recall hit (null if never recalled) |
74
+ | `recall_count` | number of times this record has been recalled (passive reinforcement counter) |
75
+ | `lifecycle` | `active`, `shadowed`, or `archived` |
76
+ | `links` | list of related-memory ids |
77
+
78
+ ## Freshness signal
79
+
80
+ Every `recall` hit carries a `signal` field (float in `[0, 1]`). The signal
81
+ blends **multiplicatively** into the lexical/vector score so recently-created
82
+ and frequently-recalled records surface ahead of stale ones. The formula:
83
+
84
+ ```
85
+ access_bonus = min(0.5, recall_count * 0.05)
86
+ age_factor = 1 / (1 + days_since_creation * 0.01)
87
+ staleness = days_since_last_recall * 0.01
88
+ signal = clamp((0.5 - staleness + access_bonus) * age_factor, 0, 1)
89
+ blended_score = score * (1 + 0.25 * (signal - 0.5))
90
+ ```
91
+
92
+ Records with no temporal data (legacy, undated) are an exact no-op — the blend
93
+ is skipped for them so pre-existing fixture scores are unchanged.
94
+
95
+ Each `recall` call is also **passive reinforcement**: it bumps `last_recall` and
96
+ `recall_count` on every matched record, so frequently-recalled memories organically
97
+ gain signal strength over time.
98
+
99
+ ## Lifecycle flags
100
+
101
+ By default, `recall` returns only `active` records. Use these flags to retrieve
102
+ non-active records:
103
+
104
+ - `--include-shadowed` — include records whose `lifecycle == "shadowed"` (records
105
+ superseded within their scope by a newer record). Shadowed records are preserved
106
+ and still searchable; they are just hidden from the default result set.
107
+ - `--include-archived` — include records whose `lifecycle == "archived"` (records
108
+ older than ~1 year or below the signal threshold). Archived records are fully
109
+ preserved; the flag makes them retrievable again.
110
+
111
+ Both flags can be combined. Neither affects ranking — shadowed/archived records
112
+ compete on score/signal just like active ones when included.
113
+
114
+ ## Common flags (forwarded to `eidetic recall`)
115
+
116
+ - `--mode exact|approximate|keyword|hybrid` — default `hybrid`.
117
+ - `--top-k N` — max results (default 5).
118
+ - `--alpha F` — hybrid blend weight in `[0,1]` (default 0.5).
119
+ - `--case-sensitive` — for `--mode exact`.
120
+ - `--filter KEY=VALUE` — metadata facet filter (repeatable): e.g. `--filter source=docs`.
121
+ - `--scope NAME` / `--visibility public|private` — scope isolation (no private
122
+ leak). **The wrapper defaults this to the agent's PERSONAL, PRIVATE scope**
123
+ (`--scope arm101-cli --visibility private`, suffix read from `culture.yaml`),
124
+ matching where `/remember` writes — so a no-flag recall returns this agent's
125
+ own private records **plus** the shared public pool, while those private records
126
+ stay invisible to a `default`/other-scope recall. Pass `--scope`/`--visibility`
127
+ to query elsewhere; a wheel install with no `culture.yaml` falls back to the
128
+ CLI default `default`/`public`.
129
+ - `--backend files|mongo|neo4j` — default `files` (the shared home-dir store).
130
+ - `--include-shadowed` — include shadowed records in results (excluded by default).
131
+ - `--include-archived` — include archived records in results (excluded by default).
132
+ - `--json` — structured list to stdout (use this when an agent parses the result).
133
+
134
+ ## Examples
135
+
136
+ ```bash
137
+ # Default hybrid recall, JSON for an agent to parse:
138
+ bash .claude/skills/recall/scripts/recall.sh "jetson nano power draw" --json
139
+
140
+ # Find the exact message that mentions a phrase:
141
+ bash .claude/skills/recall/scripts/recall.sh "Orin Nano" --mode exact
142
+
143
+ # Keyword search, offline-safe, narrowed to a source:
144
+ bash .claude/skills/recall/scripts/recall.sh "thermal throttle" --mode keyword \
145
+ --filter source=discord --top-k 10
146
+
147
+ # Retrieve a record that was recently shadowed (its superseding record is now active):
148
+ bash .claude/skills/recall/scripts/recall.sh "old topic" --include-shadowed --json
149
+
150
+ # Retrieve all records including archived (to audit stale memories):
151
+ bash .claude/skills/recall/scripts/recall.sh "power" --include-archived --include-shadowed --json
152
+ ```
153
+
154
+ ## Notes
155
+
156
+ - **Provenance is mandatory** on every hit — recall is for *cited* answers.
157
+ - The embed endpoint defaults to the local model-gear embed gear
158
+ (`http://localhost:8002/v1`, model `Qwen/Qwen3-Embedding-0.6B`); override with
159
+ `EIDETIC_EMBED_URL` / `EIDETIC_EMBED_MODEL`. `exact`/`keyword` ignore it.
160
+ - **Use the wrapper, not a bare `eidetic`.** The console script may not be on
161
+ `PATH` (in a dev checkout it isn't) — the wrapper resolves it for you (`PATH`
162
+ first, else `uv run eidetic`). For the docs, run `eidetic explain recall` if
163
+ installed, otherwise `uv run --project <eidetic-cli checkout> eidetic explain
164
+ recall`. (`explain` is an **`eidetic`** verb — a sibling tool like `devex`
165
+ won't know it.)
166
+ - **Reading scores:** `exact`, `keyword`, and `hybrid` drop non-matching records
167
+ (hybrid drops any record with a `0.0` blended score), so their hits are real
168
+ matches. `approximate` keeps every candidate ranked by raw cosine, so it can
169
+ return low/near-zero scores when the store is small — lower `--top-k` to trim.
170
+ A `--min-score` threshold is a tracked follow-up.
171
+ - **Sharing scope = one OS user.** The default store is `~/.eidetic/memory`, so
172
+ every agent/process running as the *same* OS user shares it (that is the point —
173
+ Claude + colleague). It is not isolated between OS users by anything but file
174
+ permissions; keep genuinely private data in a `--visibility private` scope and
175
+ treat the host as the trust boundary.
176
+
177
+ ## Provenance
178
+
179
+ First-party to **eidetic-cli** — eidetic owns its memory surface. Cite, don't
180
+ import: downstream repos copy this skill, they don't symlink it. See
181
+ [`docs/skill-sources.md`](../../../docs/skill-sources.md).
@@ -0,0 +1,141 @@
1
+ #!/usr/bin/env bash
2
+ # recall.sh — search the shared eidetic memory store (the /recall skill).
3
+ #
4
+ # Thin, portable wrapper around `eidetic recall`. It resolves the CLI, points
5
+ # the embedding modes at the local model-gear embed gear (overridable), and
6
+ # forwards every flag verbatim — so `recall.sh "<query>" --mode hybrid --json`
7
+ # is exactly `eidetic recall "<query>" --mode hybrid --json`.
8
+ #
9
+ # The store is the files backend at ~/.eidetic/memory by default — a home-dir
10
+ # path OUTSIDE any git worktree, so Claude and the colleague backend (which runs
11
+ # in throwaway worktrees) read the SAME memories. Set EIDETIC_DATA_DIR to opt out
12
+ # of sharing; set EIDETIC_MONGO_URI / NEO4J_URI + --backend for a server store.
13
+
14
+ set -euo pipefail
15
+
16
+ # ── resolve the eidetic CLI (installed tool first, then dev checkout) ────────
17
+ EIDETIC=()
18
+ resolve_eidetic() {
19
+ if command -v eidetic >/dev/null 2>&1; then
20
+ EIDETIC=(eidetic) # installed console script — the normal case
21
+ return 0
22
+ fi
23
+ # Dev fallback: inside the eidetic-cli checkout, run via uv.
24
+ local dir
25
+ dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
26
+ while [ -n "$dir" ] && [ "$dir" != "/" ]; do
27
+ if [ -f "$dir/pyproject.toml" ] \
28
+ && grep -q '^name = "eidetic-cli"' "$dir/pyproject.toml" 2>/dev/null; then
29
+ if command -v uv >/dev/null 2>&1; then
30
+ EIDETIC=(uv run --project "$dir" eidetic)
31
+ return 0
32
+ fi
33
+ break
34
+ fi
35
+ dir=$(dirname "$dir")
36
+ done
37
+ cat >&2 <<'EOF'
38
+ error: eidetic CLI not found.
39
+ hint: install it with `uv tool install eidetic-cli` (or `pipx install eidetic-cli`),
40
+ or run from inside the eidetic-cli checkout with `uv` available.
41
+ The console script is `eidetic` (dist name: eidetic-cli).
42
+ EOF
43
+ return 1
44
+ }
45
+
46
+ usage() {
47
+ cat <<'EOF'
48
+ recall.sh — search the shared eidetic memory store (the /recall skill).
49
+
50
+ Usage:
51
+ recall.sh "<query>" [--mode exact|approximate|keyword|hybrid] [--top-k N] \
52
+ [--alpha F] [--case-sensitive] [--filter KEY=VALUE]... \
53
+ [--backend files|mongo|neo4j] [--scope NAME] [--visibility public|private] \
54
+ [--json]
55
+
56
+ Modes (default: hybrid):
57
+ exact case-insensitive verbatim substring (--case-sensitive to tighten); offline-safe
58
+ approximate vector cosine / semantic similarity (uses the embed server)
59
+ keyword BM25 lexical; only records sharing a query term; offline-safe
60
+ hybrid alpha*approximate + (1-alpha)*keyword (--alpha, default 0.5);
61
+ degrades to keyword-only when the embed server is offline
62
+
63
+ Every flag is forwarded verbatim to `eidetic recall`. See `eidetic explain recall`.
64
+ EOF
65
+ }
66
+
67
+ case "${1:-}" in
68
+ -h | --help | help | "")
69
+ usage
70
+ exit 0
71
+ ;;
72
+ esac
73
+
74
+ resolve_eidetic || exit 2
75
+
76
+ # ── default to this agent's PERSONAL, PRIVATE scope (culture.yaml `suffix`) ──
77
+ # Query this agent's OWN personal scope by default, matching where /remember
78
+ # writes, instead of the global `default` scope shared by every project on this
79
+ # host. We read the `suffix` from the nearest culture.yaml (walking up from this
80
+ # script), so the scope follows the repo identity rather than being hard-coded —
81
+ # a downstream cite-don't-import copy adapts to its own suffix, and the colleague
82
+ # backend (running in a worktree of this same repo) resolves the same suffix,
83
+ # keeping the Claude↔colleague shared-memory story intact.
84
+ #
85
+ # The personal scope is PRIVATE by default to match /remember: in eidetic's model
86
+ # a private record is served only to a recall in the SAME scope (`can_serve`), so
87
+ # querying with --scope <suffix> --visibility private is what retrieves those
88
+ # isolated records (a public/default recall can't see them). Scope and visibility
89
+ # are paired — the private default applies only when we inject the resolved scope,
90
+ # and only if the caller didn't pass --visibility (so an explicit
91
+ # `--visibility public` still wins). An explicit --scope on the command line takes
92
+ # over steering entirely; a wheel install with no culture.yaml falls back to the
93
+ # plain CLI default (`default`/`public`).
94
+ resolve_scope() {
95
+ local dir suffix=""
96
+ dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
97
+ while [ -n "$dir" ] && [ "$dir" != "/" ]; do
98
+ if [ -f "$dir/culture.yaml" ]; then
99
+ # Capture only the first non-space token after `suffix:` (so an
100
+ # inline `# comment` or trailing space can't bleed into the scope),
101
+ # then strip surrounding quotes only — matching the canonical parser
102
+ # in .claude/skills/cicd/scripts/_resolve-nick.sh.
103
+ suffix=$(sed -n \
104
+ 's/^[[:space:]]*-\{0,1\}[[:space:]]*suffix:[[:space:]]*\([^[:space:]]*\).*/\1/p' \
105
+ "$dir/culture.yaml" | head -n1 | tr -d "\"'")
106
+ break
107
+ fi
108
+ dir=$(dirname "$dir")
109
+ done
110
+ printf '%s' "$suffix"
111
+ }
112
+
113
+ has_flag() {
114
+ local needle=$1
115
+ shift
116
+ local a
117
+ for a in "$@"; do
118
+ case "$a" in
119
+ "$needle" | "$needle"=*) return 0 ;;
120
+ esac
121
+ done
122
+ return 1
123
+ }
124
+
125
+ SCOPE_ARGS=()
126
+ if ! has_flag --scope "$@"; then
127
+ EIDETIC_SCOPE=$(resolve_scope)
128
+ if [ -n "$EIDETIC_SCOPE" ]; then
129
+ SCOPE_ARGS+=(--scope "$EIDETIC_SCOPE")
130
+ has_flag --visibility "$@" || SCOPE_ARGS+=(--visibility private)
131
+ fi
132
+ fi
133
+
134
+ # Default the embedding endpoint to the local model-gear embed gear. eidetic
135
+ # falls back to a deterministic offline embedding if it's unreachable, so this
136
+ # is safe even when the gear is down. Override by exporting these yourself.
137
+ : "${EIDETIC_EMBED_URL:=http://localhost:8002/v1}"
138
+ : "${EIDETIC_EMBED_MODEL:=Qwen/Qwen3-Embedding-0.6B}"
139
+ export EIDETIC_EMBED_URL EIDETIC_EMBED_MODEL
140
+
141
+ exec "${EIDETIC[@]}" recall "${SCOPE_ARGS[@]}" "$@"
@@ -0,0 +1,118 @@
1
+ ---
2
+ name: remember
3
+ type: command
4
+ description: >
5
+ Ingest records into the shared eidetic memory store so they can be recalled
6
+ later. Drives `eidetic remember`: accepts one record as a JSON object, or a
7
+ batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and
8
+ dedups by content hash) — re-remembering updates in place, never duplicates.
9
+ Stamps a `created` date on every record at ingest time. Accepts `supersedes`
10
+ (id of the record this one replaces, for within-scope shadowing via `sweep`)
11
+ and `links` (list of related-memory ids). The store lives at
12
+ ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper
13
+ defaults records to this agent's PERSONAL, PRIVATE scope (`--scope arm101-cli
14
+ --visibility private`, suffix read from culture.yaml) so they don't leak to a
15
+ default/other-scope recall — Claude and the colleague backend still share them
16
+ because both resolve the same suffix via this skill. Pass `--visibility public`
17
+ to contribute to the shared public pool instead. Use when the user says
18
+ "remember this", "store this", "save to memory", "index these", "eidetic
19
+ remember", or when something learned this session should outlive it. Pairs with
20
+ the sibling /recall skill.
21
+ ---
22
+
23
+ # remember — write to the shared eidetic memory
24
+
25
+ `remember` drives **`eidetic remember`**, the write half of the memory surface
26
+ (the read half is the sibling **/recall** skill). Records you store here are
27
+ recallable later by *any* agent on this machine — Claude or the colleague
28
+ backend — because the default store is one shared `~/.eidetic/memory` path.
29
+
30
+ ## How to run
31
+
32
+ ```bash
33
+ # One record (JSON object as the argument):
34
+ bash .claude/skills/remember/scripts/remember.sh \
35
+ '{"id":"d1","text":"Orin Nano draws 7-15W","type":"docs","metadata":{"source":"docs","permalink":"https://..."}}' --json
36
+
37
+ # Batch (NDJSON on stdin, one record per line) — for bulk re-index:
38
+ cat records.ndjson | bash .claude/skills/remember/scripts/remember.sh --json
39
+
40
+ # Record that supersedes an older one (same scope required for sweep to shadow):
41
+ bash .claude/skills/remember/scripts/remember.sh \
42
+ '{"id":"r2","text":"Updated Orin Nano draw: 10-20W","type":"note","supersedes":"r1","links":["r3"]}' --json
43
+ ```
44
+
45
+ The wrapper resolves the CLI portably (installed `eidetic` on `PATH`, else
46
+ `uv run eidetic` from the checkout) and forwards every flag verbatim.
47
+
48
+ ## Record shape
49
+
50
+ | Field | Required? | Notes |
51
+ |-------|-----------|-------|
52
+ | `id` | yes | stable identity; the upsert key |
53
+ | `text` | yes | the chunk being remembered |
54
+ | `type` | yes | e.g. `note`, `docs`, `discord`, a research object type |
55
+ | `hash` | optional | content hash for dedup; derived from `text` when omitted |
56
+ | `metadata` | recommended | provenance + facets; **round-trips verbatim** on recall |
57
+ | `created` | auto-stamped | ISO-8601 UTC date; stamped at ingest if absent; drives freshness signal age-decay |
58
+ | `supersedes` | optional | id of an earlier same-scope record this one replaces; `sweep` auto-shadows the target |
59
+ | `links` | optional | list of related-memory ids; persisted for future corroboration scoring |
60
+
61
+ `score` and `signal` are recall-only and are ignored on ingest. **Mind the
62
+ scope:** the default personal scope is **private** (`--scope arm101-cli
63
+ --visibility private`), so personal/role-gated notes stay isolated to this
64
+ agent's recall and are safe to store. Only when you deliberately write to a
65
+ **public** scope (`--visibility public`) does the record enter the shared pool
66
+ visible to every scope — keep public-scope records to public data only.
67
+
68
+ ## Idempotency
69
+
70
+ Re-submitting a record with the same `id` overwrites the previous value; a record
71
+ with a matching content `hash` is de-duplicated. So re-running an ingest (e.g. a
72
+ periodic re-scan) is safe and will not create duplicates.
73
+
74
+ ## Lifecycle — supersedes and sweep
75
+
76
+ Setting `supersedes` on a record declares that this record replaces an earlier one
77
+ **within the same scope**. The actual lifecycle transition (marking the older record
78
+ as `shadowed`) is applied by `eidetic sweep`, not by `remember` itself. Cross-scope
79
+ `supersedes` links are recorded but never auto-shadow (preserving the
80
+ public/private no-leak invariant).
81
+
82
+ To apply pending transitions after ingesting superseding records:
83
+
84
+ ```bash
85
+ eidetic sweep --dry-run # preview what would change
86
+ eidetic sweep # apply transitions
87
+ ```
88
+
89
+ ## Flags (forwarded to `eidetic remember`)
90
+
91
+ - `--json` — structured result (`{"upserted": N, "ids": [...]}`) to stdout.
92
+ - `--scope NAME` / `--visibility public|private` — record scope. **The wrapper
93
+ defaults this to the agent's PERSONAL, PRIVATE scope** — `--scope <suffix>
94
+ --visibility private`, where `<suffix>` is read from the nearest `culture.yaml`
95
+ (here, `arm101-cli`). Private records are served only to a recall in the same
96
+ scope, so they don't leak to a `default`/other-scope query. Pass `--scope` to
97
+ steer to a different scope (which then uses the plain CLI default visibility),
98
+ or `--visibility public` to keep the personal scope but make it shared. A wheel
99
+ install with no `culture.yaml` falls back to the CLI default `default`/`public`.
100
+ - `--backend files|mongo|neo4j` — default `files` (the shared home-dir store);
101
+ use `mongo`/`neo4j` (with `EIDETIC_MONGO_URI` / `NEO4J_URI`) for a server store.
102
+
103
+ ## Notes
104
+
105
+ - The embed endpoint defaults to the local model-gear embed gear
106
+ (`http://localhost:8002/v1`); override with `EIDETIC_EMBED_URL` /
107
+ `EIDETIC_EMBED_MODEL`. Ingest still works offline (embeddings are recomputed at
108
+ recall time).
109
+ - **Use the wrapper, not a bare `eidetic`.** The console script may not be on
110
+ `PATH` (in a dev checkout it isn't); the wrapper resolves it (`PATH` first, else
111
+ `uv run eidetic`). For the docs, run `eidetic explain remember` if installed,
112
+ otherwise `uv run --project <eidetic-cli checkout> eidetic explain remember`.
113
+
114
+ ## Provenance
115
+
116
+ First-party to **eidetic-cli** — eidetic owns its memory surface. Cite, don't
117
+ import: downstream repos copy this skill, they don't symlink it. See
118
+ [`docs/skill-sources.md`](../../../docs/skill-sources.md).
@@ -0,0 +1,138 @@
1
+ #!/usr/bin/env bash
2
+ # remember.sh — ingest records into the shared eidetic memory store (the /remember skill).
3
+ #
4
+ # Thin, portable wrapper around `eidetic remember`. It resolves the CLI, points
5
+ # the embedding endpoint at the local model-gear embed gear (overridable), and
6
+ # forwards every argument verbatim. Accepts ONE record as a JSON object argument,
7
+ # or a BATCH as NDJSON on stdin (one JSON object per line) for bulk ingest.
8
+ #
9
+ # remember.sh '{"id":"d1","text":"...","type":"docs","metadata":{...}}' --json
10
+ # cat records.ndjson | remember.sh --json
11
+ #
12
+ # Upsert is idempotent by id (and dedups by content hash): re-remembering the
13
+ # same record updates it in place, never duplicates.
14
+ #
15
+ # The store is the files backend at ~/.eidetic/memory by default — a home-dir
16
+ # path OUTSIDE any git worktree, so a record Claude remembers is recallable by
17
+ # the colleague backend (which runs in throwaway worktrees), and vice versa.
18
+ # Set EIDETIC_DATA_DIR to opt out of sharing; use --backend mongo|neo4j (with
19
+ # EIDETIC_MONGO_URI / NEO4J_URI) for a server-backed shared store.
20
+
21
+ set -euo pipefail
22
+
23
+ # ── resolve the eidetic CLI (installed tool first, then dev checkout) ────────
24
+ EIDETIC=()
25
+ resolve_eidetic() {
26
+ if command -v eidetic >/dev/null 2>&1; then
27
+ EIDETIC=(eidetic)
28
+ return 0
29
+ fi
30
+ local dir
31
+ dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
32
+ while [ -n "$dir" ] && [ "$dir" != "/" ]; do
33
+ if [ -f "$dir/pyproject.toml" ] \
34
+ && grep -q '^name = "eidetic-cli"' "$dir/pyproject.toml" 2>/dev/null; then
35
+ if command -v uv >/dev/null 2>&1; then
36
+ EIDETIC=(uv run --project "$dir" eidetic)
37
+ return 0
38
+ fi
39
+ break
40
+ fi
41
+ dir=$(dirname "$dir")
42
+ done
43
+ cat >&2 <<'EOF'
44
+ error: eidetic CLI not found.
45
+ hint: install it with `uv tool install eidetic-cli` (or `pipx install eidetic-cli`),
46
+ or run from inside the eidetic-cli checkout with `uv` available.
47
+ The console script is `eidetic` (dist name: eidetic-cli).
48
+ EOF
49
+ return 1
50
+ }
51
+
52
+ usage() {
53
+ cat <<'EOF'
54
+ remember.sh — ingest records into the shared eidetic memory store (the /remember skill).
55
+
56
+ Usage:
57
+ remember.sh '<json-object>' [--json] [--backend files|mongo|neo4j] \
58
+ [--scope NAME] [--visibility public|private]
59
+ cat records.ndjson | remember.sh [--json] ...
60
+
61
+ A record needs `id`, `text`, and `type`; `hash` and `metadata` are recommended
62
+ (hash is derived from text when omitted). Upsert is idempotent by id.
63
+ Public data only. Every flag is forwarded verbatim to `eidetic remember`.
64
+ See `eidetic explain remember`.
65
+ EOF
66
+ }
67
+
68
+ case "${1:-}" in
69
+ -h | --help | help)
70
+ usage
71
+ exit 0
72
+ ;;
73
+ esac
74
+
75
+ resolve_eidetic || exit 2
76
+
77
+ # ── default to this agent's PERSONAL, PRIVATE scope (culture.yaml `suffix`) ──
78
+ # A record this agent remembers should land in its OWN personal scope, not the
79
+ # global `default` scope shared by every project on this host. We read the
80
+ # `suffix` from the nearest culture.yaml (walking up from this script), so the
81
+ # scope follows the repo identity rather than being hard-coded — a downstream
82
+ # cite-don't-import copy adapts to its own suffix, and the colleague backend
83
+ # (running in a worktree of this same repo) resolves the same suffix, keeping
84
+ # the Claude↔colleague shared-memory story intact.
85
+ #
86
+ # The personal scope is PRIVATE by default: in eidetic's model only a private
87
+ # record is isolated to its scope (`can_serve`), so private is what actually
88
+ # keeps these records from leaking to a default/other-scope recall. Scope and
89
+ # visibility are paired — the private default applies only when we inject the
90
+ # resolved scope, and only if the caller didn't pass --visibility (so an
91
+ # explicit `--visibility public` still wins). An explicit --scope on the command
92
+ # line takes over steering entirely; a wheel install with no culture.yaml falls
93
+ # back to the plain CLI default (`default`/`public`).
94
+ resolve_scope() {
95
+ local dir suffix=""
96
+ dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
97
+ while [ -n "$dir" ] && [ "$dir" != "/" ]; do
98
+ if [ -f "$dir/culture.yaml" ]; then
99
+ # Capture only the first non-space token after `suffix:` (so an
100
+ # inline `# comment` or trailing space can't bleed into the scope),
101
+ # then strip surrounding quotes only — matching the canonical parser
102
+ # in .claude/skills/cicd/scripts/_resolve-nick.sh.
103
+ suffix=$(sed -n \
104
+ 's/^[[:space:]]*-\{0,1\}[[:space:]]*suffix:[[:space:]]*\([^[:space:]]*\).*/\1/p' \
105
+ "$dir/culture.yaml" | head -n1 | tr -d "\"'")
106
+ break
107
+ fi
108
+ dir=$(dirname "$dir")
109
+ done
110
+ printf '%s' "$suffix"
111
+ }
112
+
113
+ has_flag() {
114
+ local needle=$1
115
+ shift
116
+ local a
117
+ for a in "$@"; do
118
+ case "$a" in
119
+ "$needle" | "$needle"=*) return 0 ;;
120
+ esac
121
+ done
122
+ return 1
123
+ }
124
+
125
+ SCOPE_ARGS=()
126
+ if ! has_flag --scope "$@"; then
127
+ EIDETIC_SCOPE=$(resolve_scope)
128
+ if [ -n "$EIDETIC_SCOPE" ]; then
129
+ SCOPE_ARGS+=(--scope "$EIDETIC_SCOPE")
130
+ has_flag --visibility "$@" || SCOPE_ARGS+=(--visibility private)
131
+ fi
132
+ fi
133
+
134
+ : "${EIDETIC_EMBED_URL:=http://localhost:8002/v1}"
135
+ : "${EIDETIC_EMBED_MODEL:=Qwen/Qwen3-Embedding-0.6B}"
136
+ export EIDETIC_EMBED_URL EIDETIC_EMBED_MODEL
137
+
138
+ exec "${EIDETIC[@]}" remember "${SCOPE_ARGS[@]}" "$@"
@@ -0,0 +1 @@
1
+ arm101-cli-grows-its-first-hardware-verbs-arm101-f
@@ -0,0 +1 @@
1
+ arm101-cli-grows-its-first-hardware-verbs-arm101-f