@tangle-network/agent-runtime 0.348.1 → 0.349.0

package/skills/graph-designer/SKILL.md

@@ -10,6 +10,8 @@ that does the work, run it under your granted permissions, and record what happe
 Every execution is fully traced like any graph run — the registry plus the run's journal
 is the knowledge.
 
+Production designs: search [Factory’s design catalog](https://github.com/tangle-network/factory/blob/main/README.md) before authoring; record a delivered Factory run through `recordGraphRun` like any graph.
+
 ## The loop (every input)
 
 1. Compute the task shape: the durable description you will look this kind of work up by
@@ -41,6 +43,10 @@ one axis at a time so the next record attributes the difference. When an optimiz
 (agent-eval) is available, feed it the losing graph's journal; otherwise your reasoned
 mutation IS the search step.
 
+When the registry promotes a winning topology for a task type, retain a case under
+`skills/agent-graphs/cases/` citing the run and its measured outcome. The cited record
+provides the evidence; a descriptive ranking alone does not establish a win.
+
 ## Profiles improve the same way graphs do
 
 A worker profile is named and content-addressed; when a mutation rewrites a node's

package/skills/profile-authoring/SKILL.md

@@ -13,7 +13,7 @@ Do not constrain agents with prohibitions: change what is rewarded and who is in
 ## A profile that starts
 
 A refused profile fails before its first model turn, and it fails the same way on every retry.
-On 2026-10-10 Discovery lost 20 driver attempts to unpublished tool names and 3 spawns to a missing subscription source.
+Discovery lost 20 driver attempts to unpublished tool names and 3 spawns to a missing subscription source.
 Start from a profile that already ran (in a Discovery play, `inputs/profile-examples/<family>.json`) and change only `name`, `description` and `prompt.instructions`.
 
 | Field | Rule |