Wrench

1. Purpose of This Ordination

The new Rell split is a candidate map. It is not yet a new application layout, not a controller generator, and not a commitment to final ownership. The useful thing at this stage is to name each case pool according to the system slice it most likely belongs to. That lets the next human pass choose candidates with the right mental model.

The old Tell controller was a toolbox that grew by necessity. It accepted command values, interpreted them, touched files, shaped redirects, staged messages, assembled uploads, handled commerce, pushed print intent, and consulted gates. Rell is the recovery of that toolbox into named utility surfaces.

2. Selection Rule

The selection rule is simple:

Assign by identity grammar, not by adjacency.

A case that writes to /Work/Mms may be print, messaging, or both, depending on whether the payload is Prt_ print intent or an SMS/MMS message. A case that mentions xact may look like commerce, but it may really belong to the old photography/event-commerce knot. A case that returns a page may not be UI at all; it may be a route translator.

3. Application Slice Vocabulary

4. Rell Case Pool Atlas

The following table is the working candidate-selection map. It is intentionally opinionated, but not final. “Application slice” means the best current home for reasoning and future segregation; it does not require that the code be moved there immediately.

5. High-Risk Knots

Photography / Xact / Commerce

The most dangerous knot remains the xact/tack/photog/hotel/session area. These cases look like commerce because they display products, save orders, compute totals, and prepare purchase routes. But they also carry the older photography event system. That means they should not be split only by nouns such as “product” or “order.” Until the new assembly proves otherwise, keep the photography-session gravity visible.

Messaging / Gating

Message text can become gate control. The allow, refuse, and team-setting patterns may arrive as SMS body content and then call gate behavior. This does not mean the MessagingController should own all gating. It means Messaging is one source of gating commands. The proper future shape is likely a Messaging intake that delegates to a Gating service.

Upload / Diagnostics Checker

checker appears diagnostic, but in practice it also polls for next server directive in an upload/intake style. For candidate selection, duplicate ownership is acceptable: let UploadSession keep the operational checker while Diagnostics keeps the concept of server-condition verification.

Static Types

Extension cases should be treated as retirement candidates. IIS should own plain static delivery unless the file response is guarded, transformed, logged, generated, or otherwise meaningful as application behavior.

6. Brancher Clue

Brancher matters here because it demonstrates how Wrench should behave: it should not flatten the system into a generic summary. It should preserve full bodies, named slices, and portable doctrine. The same principle applies to Rell case selection. The goal is not to make the split look neat. The goal is to preserve enough meaning that the next conversation or next operator can pick up the work without losing the original grain.

7. Candidate-Selection Workflow

1. Review one candidate pool.
2. Confirm or adjust its application slice.
3. Mark cross-slice dependencies.
4. Avoid moving code until the owning slice is stable.
5. Keep LocateController_Remnant as a temporary delegating shell.
6. Retire Misc only after every held case has a named reason and owner.

8. Wrench Doctrine After Rell Split

Rell confirms that Wrench is not just a place for helper functions. Wrench is the working bench where unclassified tools become named instruments. Some tools will graduate into their own Pens or application slices. Others will remain in Wrench because their purpose is to help every slice: filesystem truth, WorkZone resolution, ordination, diagnostics, template expansion, and compatibility routing.

The LocateController split is therefore not a cleanup story. It is a recognition story. The system already contained Route, Send, Merch, Print, Fence, Upload, Transfer, Media, Conduit, and Wrench. The split merely makes those identities visible enough to choose.

9. Immediate Next Human Pass

The best next review is not to edit code. It is to walk the table and mark each pool as one of:

• accepted owner
• split required
• duplicate candidate
• hold in remnant
• retire to static/IIS

That will make the eventual migration mechanical instead of interpretive.

10. Body-Carried Styling for PenPals Absorption

This ordination shifts Wrench into the same body-carried styling contract used by Route and the corrected Door delivery. The essential style for this Pen is no longer dependent on the document head. It travels inside the body with the donated content so PenPals Gather, Brancher extraction, or any later full-body union keeps Wrench readable without special casing.

The rule is practical: if a Pen expects to survive as a gathered body, its essential ink, spacing, cards, tables, tags, and code styling must be present inside that body. External or head-level styling may still exist in live pages, but gathered survival cannot depend on it.