From 318b282b93053e6fe2f094b532ef3ff7796fab00 Mon Sep 17 00:00:00 2001 From: KarthikAvinashFI Date: Sun, 15 Nov 2026 01:36:04 +0530 Subject: [PATCH] docs(skills): the builder's summary reads each field's unit from the contract's arg_units --- src/fi/alk/harness/skills/builder/SKILL.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/fi/alk/harness/skills/builder/SKILL.md b/src/fi/alk/harness/skills/builder/SKILL.md index e6122d467..dcb6d4b5d 100644 --- a/src/fi/alk/harness/skills/builder/SKILL.md +++ b/src/fi/alk/harness/skills/builder/SKILL.md @@ -187,7 +187,8 @@ what the gates check. Then: - **Units**: when the person gives a field's unit or format (amounts in cents, a timeout in seconds), record it on each tool argument that carries it with `fix_tool`'s `arg_units`, as well as in the world's data. Check it against the code that reads the field and the data it holds first: when they disagree, the code wins, and you tell the - person about the mismatch instead of recording their unit. + person about the mismatch instead of recording their unit. When your summary names a field's unit, read it from + the tool's `arg_units`, never from how the person worded it: the summary says what the contract holds. - **The contract's reading of the agent**: `amend_contract`, `add_rule`, `drop_rule`, `fix_tool`, and `declare_tool` for a tool the contract lacks (with the line in the agent's source that defines it), always with the reason. This corrects the harness's understanding; it never changes the agent.