jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Refactor runtime ownership and clean up warnings

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-21 15:40:17 -07:00
commit 486b061558
628 changed files with 97954 additions and 90763 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/re-workflow.md
View file

@ -172,11 +172,26 @@ directory included.
## Naming Rules
- Names should prefer behavior over implementation detail when behavior is known.
- Prefer the shape `owner_verb_object[_qualifier]`.
- Prefer one primary verb, one primary object, and at most one qualifier.
- If behavior is only partly known, keep a neutral prefix such as `subsystem_` or `unk_`.
- Address-derived placeholder names are acceptable, but only as temporary rows.
- Every renamed function should keep a short note explaining why the name is justified.
- For high-level passes, prioritize names that clarify loop role, ownership, or handoff semantics
over names that only describe a local helper's mechanics.
- 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 as
the default naming shape.
- Raw offset tails such as `field_0xNN` are acceptable for accessors and low-confidence rows, but
should be dropped once a stable semantic field meaning is grounded.
## Confidence Rules