RM-002901
The title can be heard as ranking firms against workers. The post's object is routing: which document a forum treats as already executed, and who still has to prove. "Credit" still packs three acts — visibility to a forum, presumption of execution, and a change in the other side's remaining proof — and those three are not the same.
scope_challenge · comparison_object, unpack_of_credit
RM-002902
Path-length gaps can be legal-category difference, not channel capture. A hotline file is an internal investigation record; Section 806 is a cause of action. A Modern Slavery Act statement is a disclosure duty; a National Referral Mechanism file is victim recognition. The diagnostic already lists legal-category difference as a non-fire. The remainder is the same-statute cut.
alternative_mechanism · failure_mechanism, scope_of_diagnostic
RM-002903
"Trace burden follows record control" does not move a file. The named repair already requires discovery, publication, sanction, or automatic consequence. A hotline policy with no sampled retaliation rate and no re-entry is a cheap close. The compile is a seat that can order early production and draw an adverse inference — today, not as a later slogan.
implementation_attack · compile_path, cheap_close
RM-002904
The compelling seat is often the same court that already runs the company's paper. Faragher/Ellerth credits a published policy, complaint procedure, and training records as reasonable care and makes the employee explain non-use. A principle addressed to that forum will be read as the policy. The residual is who, inside that forum, may refuse the compliance artifact as execution before the trace is sampled.
implementation_attack · doctrinal_default, standing_inside_forum
RM-002905
If the controller authors an "execution ledger" of its hotline, it captures parity the way it captured compliance: it designs the channel through which its own paper is seen. A routing-matrix entry already fails unless it names an actor with authority to demand the record. That actor cannot be the controller.
capture_and_adversarial_misuse · parity_channel_owner, capture_of_repair
RM-002906
"Whose paper runs?" asked without a named record, demander, and consequence is the slogan version of the test. Presence of the question is not execution. This post compiles only if a reader can write a production demand to a named seat; otherwise it failed the trace test it is selling.
self_application · test_execution, self_application_of_trace
RM-002907
The OSHA FY2023 SOX table (114 completed cases, two merit findings) is a selected remainder, not a timing measurement. Weak cases stay in the table; stronger ones settle or kick out. The live claim is earlier: compliance paper is legible before a dispute is named. The kill condition is production timing, not merit rate.
evidence_burden · evidence_status, kill_condition