zam-core 0.3.5 → 0.3.6
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.
|
@@ -21,7 +21,7 @@ All knowledge management is done through the `zam` CLI:
|
|
|
21
21
|
zam init
|
|
22
22
|
|
|
23
23
|
# Token management
|
|
24
|
-
zam token register --slug <slug> --concept "<one sentence>" --domain <d> --bloom <1-5>
|
|
24
|
+
zam token register --slug <slug> --concept "<one sentence>" --domain <d> --bloom <1-5> [--source-link <link>]
|
|
25
25
|
zam token find --query "<keywords>"
|
|
26
26
|
zam token list [--domain <d>]
|
|
27
27
|
zam token prereq --token <child> --requires <parent>
|
|
@@ -164,6 +164,20 @@ zam session start --user <username> --task "<description>" --context shell
|
|
|
164
164
|
|
|
165
165
|
### STEP 4 — Hand off, observe, rate
|
|
166
166
|
|
|
167
|
+
> **Spoiler-free console option:** For pure conceptual recall, you can hand the
|
|
168
|
+
> whole review off to the standalone console harness instead of probing card by
|
|
169
|
+
> card here:
|
|
170
|
+
> > "Let's do your reviews in the dedicated console — run `zam learn` and rate
|
|
171
|
+
> > yourself. I'll wait."
|
|
172
|
+
>
|
|
173
|
+
> `zam learn` shows a concept-free cue, captures the answer, and only then
|
|
174
|
+
> reveals the stored answer (concept + context + resolved `source_link`) before a
|
|
175
|
+
> single 1–4 self-rating — all in-process. This sidesteps agent-CLI autocomplete
|
|
176
|
+
> that would otherwise ghost the answer, and the per-subcommand permission
|
|
177
|
+
> prompts from chained `card update` / `session log` calls. Use the verbal
|
|
178
|
+
> probing below when you want to drive the discussion yourself or add depth a
|
|
179
|
+
> stored answer can't (that richer mode will later be backed by an LLM).
|
|
180
|
+
|
|
167
181
|
**For executable tasks (observation mode):**
|
|
168
182
|
|
|
169
183
|
Hand off to the user:
|
|
@@ -242,11 +256,27 @@ For each due token, ask a conceptual question at the right Bloom level:
|
|
|
242
256
|
| 4 Analyze | "Why X over Y?" | "Why is == more efficient than contains?" |
|
|
243
257
|
| 5 Synthesize | "Design a..." | "Build the full query from scratch" |
|
|
244
258
|
|
|
245
|
-
|
|
259
|
+
**CRITICAL: Stop and WAIT for the user to provide their answer. Do not ask for the rating until the user has attempted to answer the conceptual question.**
|
|
260
|
+
|
|
261
|
+
After the user answers, ask:
|
|
246
262
|
> "How did that feel? 1 = drew a blank, 2 = hard recall, 3 = knew it, 4 = instant"
|
|
247
263
|
|
|
264
|
+
**WAIT for the user to provide a rating (1-4).**
|
|
265
|
+
|
|
248
266
|
Submit the rating and log the step.
|
|
249
267
|
|
|
268
|
+
#### Leveraging Source Links for AI Agent Context
|
|
269
|
+
When a token has a `source_link`, `zam bridge get-review` resolves it for you and returns a `resolvedContext` object alongside `prompt` — you no longer need to fetch the file or URL yourself. Its shape:
|
|
270
|
+
|
|
271
|
+
- `sourceType: "local" | "remote_web"` → `content` is the literal file/page text, already line-sliced when the link carried a `#L10-L25` anchor. Ground your question and verification directly in it.
|
|
272
|
+
- `sourceType: "dynamic_search"` → `content` is a `QUERY_DIRECTIVE: Run web search for "..."`. Run that web search yourself, then ground the review in the results.
|
|
273
|
+
- `truncated: true` → the content was capped; fetch the full `filePath`/`url` only if you need more.
|
|
274
|
+
- `resolvedContext: null` → no link, or resolution was disabled (`--no-resolve`); fall back to the one-sentence concept, or inspect the path yourself.
|
|
275
|
+
|
|
276
|
+
Use it to:
|
|
277
|
+
1. **Formulate Contextual Questions**: Instead of asking generic questions based strictly on the one-sentence concept text, use the resolved code or documentation to ask targeted, realistic, deep conceptual questions (e.g., at Bloom level 2, 3, or 4).
|
|
278
|
+
2. **Verify Responses Precisely**: Reference the resolved material to verify the user's answers, addressing specific edge cases, syntax, or trade-offs present in the actual codebase or documentation.
|
|
279
|
+
|
|
250
280
|
### STEP 5 — End session
|
|
251
281
|
```bash
|
|
252
282
|
zam session end --session <id>
|