/pro — house register

A repeatable pass converting plainly-written internal prose into the house register: maximum signal per line for readers who already share the context.

The register exists because internal readers are context-rich and time-poor. Density is the point — but density is also the failure mode, so most of this skill is about which compressions pay and which ones quietly cost content, credibility, or the one reader you most needed to convince.

Invocation

Run only when called. /pro on its own applies P2. /pro 1 and /pro 3 select depth explicitly.

The gate matters because the three depths differ in which readers they lose, not just in how dense they are — and that's the author's call, not a default. Auto-applying this register to a doc heading for sign-off or external circulation makes it worse, confidently. If the target audience is unclear from context and there's any sign the document leaves the team, ask for a depth before writing rather than assuming P2.

The pass

Work in this order. Ordering matters: compressing before inventorying is how content disappears.

1. Inventory before compressing

List every load-bearing claim in the source before writing a word of output. Compression feels like editing but behaves like deletion — an item never logged is an item you won't notice missing. Check the finished draft against the list.