Refactor runtime ownership and clean up warnings

docs/function-map.md

@@ -34,9 +34,24 @@ Field meanings:
 ## Update Rules
 
 - New rows must always include `address`, `name`, `subsystem`, `source_tool`, and `confidence`.
+- Prefer names in the shape `owner_verb_object[_qualifier]`.
+- Prefer one primary verb, one primary object, and at most one qualifier.
 - If a rename is speculative, state that directly in `notes`.
 - When two tools disagree on function boundaries, preserve the ambiguity in `notes` instead of hiding it.
 - Prefer one row per concrete function, not per guessed feature.
+- Prefer `try_` for best-effort helpers that may fall through without mutation or publication.
+- Prefer `apply_` when a helper commits one selected policy or state transition.
+- Reserve `evaluate_` for read-heavy helpers that classify or score state without committing the later action themselves.
+- Prefer one stable family noun once a transient runtime structure is grounded.
+- Use `queue_node` for transient linked-list allocations, and reserve `record` for persisted rows or document-style payloads.
+- Prefer `startup_company` over `company_start` when the object is the newly started company.
+- Prefer participial qualifiers such as `_ignoring_territories` over `_with_*_ignored` once the side condition is grounded.
+- Drop filler tails such as `_lanes` once a broader owner is grounded well enough to carry the family directly.
+- Prefer `_and_optionally_` over `_with_optional_` when a helper may take one secondary path but the main owner is still singular.
+- Treat `_and_`, `_with_`, `_if_`, and `_via_` as fallback tools for still-uncertain seams, not the
+  default naming style.
+- Raw offset tails such as `field_0xNN` are acceptable for direct accessors and low-confidence rows,
+  but should be replaced once a grounded semantic field name exists.
 
 ## Starter Subsystems