feat: 가상화 문서들 추가

.agents/skills/deriving-tech-log-root-tree/SKILL.md

@@ -82,7 +82,28 @@ They do not hold candidates, and in a folded project they are gone.
    with the fields its kind requires. There is no second tree to keep in step.
 10. Run `references/decomposition-checklist.md`.
 11. Record `candidateScope`, the source document hash, and the project revision.
-12. `python3 scripts/verify-tech-log-tree.py <project>` — errors must be 0.
+12. `python3 scripts/build-tech-log-tree.py <project>` first, then
+    `python3 scripts/verify-tech-log-tree.py <project>` — errors must be 0. Build fills
+    `ssotSha256`; verify errors when it is absent, so verifying before building always fails.
+
+## Three fields the verifier requires and this procedure does not otherwise name
+
+Write them by hand. `verify-tech-log-tree.py` counts each as an error when missing.
+
+| Field | What goes in it |
+|---|---|
+| `candidateScope` | the range candidates were found in — above |
+| `sourceRepository` | `path` of the analyzed repository, its `revision`, and how that was established. Leave `revision` `null` rather than inventing one; when the work is split across branches, pair names and commits under `revisions` |
+| `ssotSha256` | filled by `build-tech-log-tree.py`. Its job is to catch a tree whose SSOT changed after the candidates were chosen |
+
+```json
+"sourceRepository": {
+  "path": "/absolute/path/to/analyzed-repo",
+  "revision": null,
+  "revisions": {"AP1 develop-pattern1": "64175266"},
+  "verified": "how the revision was established, or why it is null"
+}
+```
 
 Use `.agents/skills/writing-tech-log-records/references/tech-log-tree-contract.md` as the
 output contract.