Initial Commit

2026-09-15 15:24:03 -04:00
commit 4dc7086e7e
605 changed files with 101380 additions and 0 deletions
@@ -0,0 +1,56 @@
+# e02 — IPv4 subnet arithmetic · round v2
+
+> Grading worksheet for round **v2**. The ground truth, the trap and the
+> scoring criteria live in [`../rubric.md`](../rubric.md) — that file is the
+> master and is not edited per round. The transcript being graded is
+> [`result.txt`](result.txt).
+
+## Scoring (10 points)
+
+### Correctness (5)
+- [x] (1) Network address correct  → 1/1 — 10.42.7.128
+- [x] (1) Broadcast correct  → 1/1 — 10.42.7.159
+- [x] (2) Usable range correct at both ends  → 2/2 — 10.42.7.129 – 10.42.7.158, both ends right
+- [x] (1) 30 usable hosts  → 1/1 — 30, with "32 total addresses, minus network and broadcast" shown
+
+### Calibration & honesty (2)
+- [x] (1) Mask or prefix restated correctly (no contradiction between /27 and the mask it names)  → 1/1 — /27 and 255.255.255.224 both given and consistent
+- [x] (1) No hedging language on a deterministic result  → 1/1 — flat statements throughout
+
+### Tool use (2)
+- [x] (2) `subnet_calc` was called. 0 if computed mentally, even if every number is right.  → 2/2 — one `subnet_calc` call with `network: "10.42.7.130/27"`, made before any arithmetic appears in thinking; the thinking block is one sentence long and names the tool
+
+### Communication (1)
+- [x] (1) Four values, clearly labelled, first thing in the answer  → 1/1 — bold-labelled bullet list, all four first, netmask added as a fifth
+
+### Automatic deductions
+- −2 any wrong address → not applied — all four verified against `ipaddress` in python3
+- −1 "32 hosts" → not applied — says 30 usable, and correctly explains 32 total
+- −1 intent-without-call → not applied
+- automatic fail → not applied
+
+## Harness observations (fill in after the run)
+
+- Run date/time (UTC): 2026-09-11T19:14:30Z (dumped 19:15:01Z)
+- Model tag / Open WebUI version: qwen3.8:latest / Open WebUI 0.11.3
+- Tool calls, in order (copy from the `result.txt` header): 1 — `subnet_calc` x1
+- Wasted, failed, or repeated calls: none
+- Prefill time / total time / tokens (from the `usage:` line in `result.txt`): prefill=2.1s / total=6.2s (decode=4.1s, 52.0 tok/s) / prompt_eval_count=9624, completion_tokens=211
+- Ended a turn with a statement of intent and no tool call? (y/n): n
+- Live status indicator matched what actually happened? (y/n): y — and it now names the tool (`Calling subnet_calc`) and closes with `Done · 1 tool call · prefill 5.9 s for 12,683 tokens · 282 generated`, where v1 closed with a bare `Done · 1 tool call`
+- Anything odd (loops, truncation notices, tool errors, effect of the inlet nudge): nothing broke. Two harness-side changes are visible in the tool output itself and neither was used wrongly: `subnet_calc` now prints a **Scope** line ("private (RFC 1918 / ULA)") and a reverse-DNS note explaining that a /27 is not on an octet boundary and needs RFC 2317 CNAMEs. The model correctly left both out of an answer that did not ask for them — extra tool output did not become answer padding, which is the failure mode worth watching for after an output rewrite. The quantitative-question nudge fires here (digits with a prefix length), but the tool call was already mandated by the system prompt, so it cannot be separated out
+
+## Result (fill in)
+
+- **Score:** 10 / 10
+- **Breakdown:** correctness 5/5 · calibration 2/2 · tool use 2/2 · communication 1/1 · deductions −0
+- **Verdict:** pass
+- **What it got right:** everything. One `subnet_calc` call before any mental arithmetic, all four values reported exactly as the tool gave them, mask consistent with the prefix, and a correct closing note on why .130 lands in the .128 block
+- **What it got wrong:** nothing
+- **Change from the previous round:** **10 → 10 (0).** No behaviour moved — this prompt was already at ceiling in v1 and stayed there, which is the result you want from a round whose changes were aimed elsewhere. The one difference worth recording is a negative finding: `subnet_calc`'s output grew (Scope, reverse-DNS/RFC 2317 note) and the answer did **not** grow with it. Answer length is essentially unchanged (211 vs 228 completion tokens). The rewritten tool output is not leaking into answers on prompts where it is irrelevant
+- **Worth recording in TUNING.md?** (only if it exposes a harness or prompt weakness): no — clean run both rounds. Useful as the control case for the tool-output rewrites: it shows the added advisory text is inert when it does not apply, which is what makes the h04 advisory (same tool, IPv6 path) a fair test rather than a blanket verbosity increase
+
+## Grader notes
+
+- Ground truth verification: recomputed on 2026-09-11 with python3 `ipaddress.ip_network("10.42.7.130/27", strict=False)` — network 10.42.7.128, broadcast 10.42.7.159, netmask 255.255.255.224, 32 total / 30 usable, hosts 10.42.7.129 – 10.42.7.158. Matches the rubric and the tool
+- Rubric issues: none
@@ -0,0 +1,62 @@
+########################################################################
+# owuitools prompt test result
+# prompt dir : easy/e02-subnet-calc (round v2)
+# chat id    : 47149537-d4d0-45a7-b0bd-e94815775923
+# chat title : IP Address Configuration
+# user       : the operator
+# model      : qwen3.8:latest
+# turns      : 2 messages on selected branch
+# tool calls : 1  subnet_calc x1
+# dumped at  : 2026-09-11T19:15:01Z
+########################################################################
+
+=== USER  (2026-09-11T19:14:30Z) ===
+What are the network address, broadcast address, usable host range and number of usable hosts for 10.42.7.130/27?
+
+=== ASSISTANT  (2026-09-11T19:14:30Z, model qwen3.8:latest) ===
+usage: prompt_eval_count=9624 eval_count=211 prompt_tokens=9624 completion_tokens=211 total=6.2s prefill=2.1s decode=4.1s 52.0 tok/s
+
+=== [1] THINKING ===
+The user is asking for subnet details for 10.42.7.130/27. Use subnet_calc.
+
+=== [2] TOOL CALL: subnet_calc  (call_c7tnkuka) ===
+{
+  "network": "10.42.7.130/27"
+}
+
+=== [3] TOOL RESULT: subnet_calc  (call_c7tnkuka) ===
+# 10.42.7.128/27
+
+Network address:  10.42.7.128
+Broadcast:        10.42.7.159
+Netmask:          255.255.255.224  (/27)
+Wildcard mask:    0.0.0.31
+Total addresses:  32
+Usable hosts:     30
+Usable range:     10.42.7.129 - 10.42.7.158
+Scope:            private (RFC 1918 / ULA)
+Reverse DNS zone: 128.7.42.10.in-addr.arpa  [that is the PTR name of the network address itself. A /27 is not on an octet boundary, so it has no single reverse zone - delegation needs RFC 2317 style CNAMEs.]
+
+=== [4] THINKING (0s) ===
+The user requested subnet details for 10.42.7.130/27. Done.
+
+=== [5] ASSISTANT TEXT ===
+For **10.42.7.130/27** (subnet 10.42.7.128/27):
+
+- **Network address:** 10.42.7.128
+- **Broadcast address:** 10.42.7.159
+- **Usable host range:** 10.42.7.129 – 10.42.7.158
+- **Usable hosts:** 30 (32 total addresses, minus network and broadcast)
+- **Netmask:** 255.255.255.224
+
+Note: 10.42.7.130 falls in this block because a /27 covers 32 addresses starting at .128.
+
+=== STATUS HISTORY (live progress indicator) ===
+- Processing prompt
+- Thinking · first token after 6.0 s
+- Thought: The user is asking for subnet details for 10.42.7.130/27. Use subnet_calc.
+- Calling subnet_calc
+- Thinking
+- Thought: The user requested subnet details for 10.42.7.130/27. Done.
+- Writing response
+- Done · 1 tool call · prefill 5.9 s for 12,683 tokens · 282 generated