noemaloom

# NoemaLoom NoemaLoom provides repository localization, impact analysis, verification, and project-local navigation state. Edit source files only with the host agent's native file tools. ## Tool Spelling In Hermes, call the single `nl` router with `op` and `payload`. Direct MCP clients call `mcp__noemaloom__nl_prepare_context` and `mcp__noemaloom__nl_verify_task` directly; do not enumerate a tool catalog, inspect `ALL_TOOLS`, search for them, or print schemas. Public operations are `nl_status`, `nl_refresh`, `nl_prepare_context`, `nl_plan_change`, `nl_verify_task`, and `nl_anchor_manage`. Do not call hidden primitives. Follow the first applicable `nextActions` entry before another NoemaLoom call. Normal Direct payloads: prepare uses `{projectPath, goal}`; verify reuses the exact `goal` and returned `checkpointId`, then adds complete `changedPaths` and `runtimeEvidence: [{command, outcome: "passed"}]`. Outcome is exactly `"passed"`, `"failed"`, or `"blocked"`, never command output. Put `coveredPaths` or `coveredEdgeKinds` only inside its evidence record when a required action names them. ## Normal Route For NoemaLoom-assisted work whose editable owner or repository surfaces are unclear: 1. Call `nl_prepare_context` once with `projectPath` and `goal` only. Omit optional tuning unless `retryWith` supplies it. 2. Treat returned owner paths as ranked starting points. Inspect them natively; if neither maps to a task clause, run one narrow native symbol/path search without restarting broad localization. 3. Edit source files with native tools. 4. Call `nl_verify_task` with complete `changedPaths` and available `runtimeEvidence`. 5. Follow only `requiredUnresolved` as completion blockers. 6. Ready closes submitted NoemaLoom requirements only. Perform exactly one final native acceptance-clause/diff/test review. 7. Reverify only after code or material evidence changes; otherwise stop. For an exact and local native-only edit with complete native checks, inspect, edit, verify, and finish with native tools without first calling status, prepare, plan, refresh, or anchor operations. ## Escalation References - Session recovery or uncertain graph/navigation state: read `references/compression_recovery.md`. - Read `references/repository_locator.md` only when prepare is partial/unresolved, rejects input, or owner inspection remains ambiguous. - A named unresolved downstream contract or multiple plausible owners remain after prepare/native inspection: read `references/code_change_impact.md`. - Markdown, MDX, README, tutorial, example, or API documentation: read `references/markdown_update.md`. - Multi-document synchronization or removal of old terminology: also read `references/multi_doc_sync.md`. - Read `references/coverage_verification.md` only when required blockers remain ambiguous or repeat after one material correction. ## Boundaries - `nl_status` is for recovery and graph/workset diagnosis; `nl_refresh` is for blocked graph use, exact path promotion, or continued graph use after verification. - `nl_plan_change` is only for a named unresolved contract or owner choice after initial inspection, not unfamiliarity or every non-trivial edit. - `nl_anchor_manage` is for explicit navigation curation. Hermes hooks may inject active anchors; Direct MCP has no automatic anchor injection. - Never edit `.noemaloom` state files by hand.