Execution-Credit Asymmetry

I. The records the company already owns

An accounting analyst tells the audit-committee hotline that revenue recognition on a major contract looks wrong. The report enters the company's case-management system. Compliance scopes the file. HR joins the chronology. The analyst is moved off the engagement during the inquiry to protect the investigation. Six months later, after a reorganization, the role is eliminated. The termination memo references performance concerns documented over the prior year. The hotline file, the audit-committee minutes, the HR investigation chronology, the manager emails, the access logs, and the performance file all sit in systems the company runs.

The company has policy, hotline procedure, training records, an audit-committee charter, a non-retaliation clause, a code of conduct, and — where the issuer is subject to Sarbanes-Oxley § 404 attestation — an external auditor's attestation that internal control over financial reporting is effective. Every one of those papers is legible to a regulator, a board, an investor, or a court before any dispute is named.

The analyst has Section 806 of Sarbanes-Oxley. To make that paper run, the analyst must establish protected activity, employer knowledge, adverse action, and contribution. Much of the contested proof runs through records the company controls. The analyst has 180 days from the violation to file with OSHA. If OSHA does not issue a final decision within 180 days of filing, the analyst may exit OSHA and bring the case in federal court. Two clocks, same number, different events. Both run while the company holds the file.

After Murray v. UBS Securities, the analyst no longer has to prove retaliatory animus. Protected activity need only be a contributing factor. The employer then carries a clear-and-convincing burden to show it would have taken the same action absent the protected activity. The doctrinal direction is favorable to the worker. The trace burden is not. To activate any of the doctrinal moves, the analyst needs the company's records first — emails, meeting notes, scoping decisions, the hotline closure note, the performance-history timeline that produced the termination memo.

The OSHA whistleblower table for fiscal year 2023 lists 114 completed SOX cases: two merit findings, four positive settlements, thirteen other settlements, seventy-three dismissals, twelve kick-outs, ten withdrawals. The OSHA merit determination is rare. Some strong cases likely settle before OSHA writes a finding or leave OSHA at the 180-day mark for federal court; weak cases dominate what remains in the table. The selection is built into the disposition mix.

The pattern is simple: the side that controls the record channel gets credit before the side protected by the rule gets proof. Call it Execution-Credit Asymmetry. The mechanism that produces it is Legibility Capture — one side designs the channel through which its compliance becomes visible; the other side is rendered legible by an adversarial system. The repair is Execution Parity: credit follows trace; trace burden follows control. The repair does not execute itself. It requires discovery power, publication power, sanction power, or automatic consequence.

II. Execution credit and trace burden

The channel divides credit from proof. Two terms make the routing visible.

Execution credit is institutional recognition that a formal object has done its job. Trace burden is the obligation to prove the formal object reached the world. Execution-Credit Asymmetry occurs when execution credit follows institutional position rather than audit-channel strength, evidence control, or actual execution. Trace burden follows the actor who depends on the channel rather than the actor who controls it.

The law already names a burden-shifting answer in places. McDonnell Douglas, Reeves v. Sanderson Plumbing, Faragher/Ellerth, and Murray v. UBS all build machinery for moving burdens once the dispute reaches the right stage. Doctrine names the answer late. Execution-Credit Asymmetry starts earlier. It asks what happens before that machinery matters, while the employer's compliance paper is already legible and the claimant is still trying to extract the records that would let the doctrinal burden bite.

In supervisor hostile-environment cases where no tangible employment action has been taken, the Faragher/Ellerth affirmative defense runs the asymmetry through doctrine itself. An employer with a published anti-harassment policy, a complaint procedure, and a record of training can present those compliance artifacts as evidence that it exercised reasonable care; the employee must then explain why they did not use the procedure, or why using it was unreasonable. The policy is the institution's. The procedure is the institution's. The training records are the institution's. The employee's failure-to-use becomes a fact the employee must explain.

The recurring pattern: a formal object is invoked, the institution's compliance paper runs immediately, and the claimant's paper runs only after procedural proof through records the institution controls.

Nominal Execution names the broader failure in which a formal object substitutes for the path that would carry it into the world. Execution-Credit Asymmetry is one shape inside that failure — not "the paper does not run," but the asymmetric routing of credit when both sides have paper.

III. How the channel is captured

The asymmetry has a structural cause. The institution designs the channel through which its own compliance becomes visible. The institution does not happen to own its records. The institution constructed the system that produces them in the format the regulator, auditor, or court will recognize. Compliance objects are paper produced by the apparatus the rule was supposed to discipline, in a format chosen by the same apparatus, transmitted through interfaces the apparatus designed.

A claimant has no such instrument. The claimant files on standard forms, runs to clerk-administered deadlines, accepts agency-controlled dispositions, narrates under cross-examination, and produces evidence subject to rules the claimant did not design. Where the institution produces visibility, the claimant is produced as visible.

Scott's account of state legibility runs in one direction: the state sees subjects through forms it designs. The institutional layer inverts that. Some actors design the forms they are seen through. Others are seen through forms designed by adversaries. Call it Legibility Capture — not a new theory of legibility but a routing observation about who controls the channel.

A small political economy stabilizes the asymmetry. Form producers — legislators, advocates, academics, policy shops — earn credit from producing the form. Form validators — auditors, lawyers, consultants, certifiers — earn rent from navigating it. Form shelters — agencies, firms, institutional defendants — earn immunity from satisfying it. The reward routes upward through the form, not through the trace it claims.

IV. The same shape in four fields

In tax, GDPR, modern-slavery disclosure, and SOX, the record owner gets the first legible paper.

Tax — high-wealth complexity vs. EITC correspondence

The IRS's audit capacity for partnership returns, large-corporate filings, and high-net-worth taxpayers requires scarce specialists, multi-year examination horizons, and contested-issue litigation budgets. Historically, complexity and resource scarcity have made high-income and complex filings harder to examine than highly legible correspondence-audit populations. The Earned Income Tax Credit is the inverse case: claims are processed through automated mismatch detection, refund freezes, and correspondence audits run by clerks. The recipient's records — pay stubs, child-residency documentation, custody agreements — must be produced into a system designed by the IRS. Compliance complexity protects the high-wealth filing because the trace would have to be reconstructed by an examiner the IRS does not have. EITC simplicity exposes the low-income claim because the trace runs through standard documents on the agency's clock.

The Treasury Inspector General for Tax Administration's July 2025 report on the IRS's high-income initiative documents the system attempting to re-route. The fiscal year 2024 plan increased high-income examinations while holding audit rates flat for taxpayers below $400,000. The IRS recognized the asymmetry at the operating-plan level. Whether the re-routing holds across appropriations cycles and administrations is a future question. The recognition itself is part of the finding: the directional asymmetry was visible enough at the agency level to write a counter-program into the plan.

GDPR — controller compliance artifact vs. data-subject complaint

A data controller produces a privacy notice, a record of processing activities, a data protection impact assessment for high-risk processing, a designated data protection officer, a consent-management workflow, and a documented breach-response procedure. These artifacts are filed in formats supervisory authorities recognize. The artifacts exist before any complaint is filed.

A data subject has access, erasure, objection, portability, and complaint rights under the regulation. Each right runs through the controller's interface first, then through a national data protection authority's complaint process. noyb's 2025 analysis of European Data Protection Board statistics from 2018 to 2023 reports that an average of 1.3% of cases before data protection authorities result in a fine, with country variation from 0.03% (the Netherlands) to 6.84% (Slovakia). The denominator is cases before DPAs, combining complaints and own-initiative investigations. The number does not measure complaint success; it measures how often the regulator's machinery produces a sanction-visible outcome. Article 24 places accountability on the controller, and the artifacts above are how that accountability is demonstrated to a supervisory authority. The data subject's complaint runs only through staged proof inside an interface the controller chose and a regulator the controller files with.

Modern Slavery Act § 54 — supplier statement vs. victim recognition

Section 54 of the United Kingdom's Modern Slavery Act 2015 requires commercial organisations carrying on business in the UK and meeting a turnover threshold to publish an annual slavery and human trafficking statement. The statement must be approved by the board and signed by a director. Government guidance is explicit: organisations are not expected to guarantee slavery-free supply chains, and an organisation that has taken no steps may comply by publishing a statement saying so. As of June 2026, the Home Office registry showed 31,695 organisations self-declaring that they were required to produce a statement for the 2026 registry year.

The other side of the same statutory program runs through the National Referral Mechanism. The 2024 end-of-year summary reports 19,125 potential victims referred — the highest annual figure since the NRM began — 20,090 reasonable-grounds decisions of which 53% were positive, and 17,304 conclusive-grounds decisions of which 56% were positive. At year end, 17,168 cases with positive reasonable-grounds decisions were still awaiting conclusive-grounds determination.

Statement compliance and victim recognition are not the same legal object. The supplier statement is a transparency obligation; victim recognition is a multi-stage administrative process with criminal-justice and immigration consequences. The asymmetry is not that the two pieces of paper should run the same way. The asymmetry is that the corporate paper executes on a clean disclosure track — filed, signed, published, registered — while the victim's paper enters staged proof, backlog, and adjudication. The same Act produces a one-step path for the entity required to publish, and a many-step path for the person the Act was named to protect.

SOX — the cold-open specimen, finished

The cold-open analyst belongs in this series. The compliance apparatus is publicly described in proxy statements, audit-committee charters, internal-control attestations (for accelerated filers), and hotline disclosures. The § 806 worker's protection is operationally an evidence problem the worker must solve through records the company controls. The OSHA disposition statistics characterize the channel; the legal standard, post-Murray, is friendlier than it used to be; the trace burden is unchanged.

V. What counter-evidence does and does not say

Execution-Credit Asymmetry does not claim that powerful actors never face consequences. It is a claim about timing — when formal artifacts receive execution credit before the execution trace is shown.

The Securities and Exchange Commission's fiscal year 2025 enforcement results report 119 officer-and-director bars and individual charges in about two-thirds of standalone actions. The Environmental Protection Agency's fiscal year 2025 enforcement results report 156 defendants charged and 65 years of incarceration imposed. BP pleaded guilty to felony manslaughter, environmental crimes, and obstruction following Deepwater Horizon; the Department of Justice indicted BP supervisors Robert Kaluza and Donald Vidrine individually. Volkswagen executives Martin Winterkorn and Rupert Stadler were prosecuted individually in the diesel-emissions matter.

These cases show consequence after investigation. They do not answer whether the compliance artifacts received front-end credit before the investigated trace was produced. KPMG's 2005 tax-shelter deferred-prosecution agreement is not the anchor specimen for SOX execution credit, because KPMG admitted wrongdoing, paid $456 million, was placed under monitorship, faced a Public Company Accounting Oversight Board statement, and DOJ prosecuted named former partners. The DPA pattern belongs to Brandon Garrett's work on corporate criminal resolution. Execution-Credit Asymmetry fires elsewhere in the same statutory neighborhood, at the credit-without-trace moment inside the compliance apparatus before the investigation that produced KPMG's outcome had begun.

VI. When this is not asymmetry

Execution-Credit Asymmetry does not fire when:

1. Both sides' paper receives the same initial evidentiary status.
2. The favored actor bears strong audit-channel consequence proportionate to the credit received.
3. The burden tracks evidence access rather than status: the actor best positioned to produce the relevant records actually bears the burden.
4. Formal compliance triggers automatic independent testing.
5. The favored actor is sanctioned individually at rates comparable to others charged with equivalent violations.
6. Legal-category difference, evidentiary complexity, or institutional capacity explains the asymmetry better than control of the legibility channel.

A criminal-environmental case where both individual operators and corporate operators are prosecuted is not Execution-Credit Asymmetry; the trace runs both ways. A pension-disability claim where the records the claimant needs sit with a third-party medical provider rather than the agency or the employer is administrability, not asymmetry of control. A consumer-product-recall regime where post-market injury data triggers automatic re-evaluation of premarket clearance is structurally close to parity even when the original clearance ran one way: the channel feeds back. These boundaries keep the diagnostic attached to record control.

VII. The failed inversion test

Faction rotation was the natural conjecture: progressive-institutional beneficiaries in some statutes, corporate-institutional beneficiaries in others. The document record did not produce a clean rotation pair.

Five inversion pairs were tested at document level: DEI and Title VII institutional compliance against individual disparate-impact proof burden; university Office of Civil Rights resolution agreements against individual respondent process under Title IX; ESG ratings and disclosure against FTC greenwashing enforcement; Modern Slavery Act § 54 statement filing against trafficking-victim recognition; and NLRB enforcement against corporate union-avoidance compliance. None survived.

The DEI/Title VII direction failed because the institutional compliance side did not receive paper-only credit: OFCCP affirmative-action programs required problem-area analysis, personnel-activity review, compensation review, and measurable results; the fiscal year 2024 program found discrimination in roughly 3% of supply-and-service evaluations, with multi-year median durations to enforcement referral. The historical regime was further disrupted by Executive Order 14173 in January 2025, which revoked Executive Order 11246. The university-OCR direction failed because resolution agreements impose monitored compliance plans rather than credit; the Title IX rule landscape is a pendulum, not a stable asymmetry. The ESG/greenwashing direction failed because the FTC and SEC do pursue institutional ESG actors. The NLRB direction failed because the corporate notice-posting compliance object did not survive NAM v. NLRB. The Modern Slavery Act direction is a clean specimen of execution-credit asymmetry but a corporate-beneficiary one, not a coalition inverse.

The verified variable was not coalition identity but channel control. The pairs that survived document audit sorted by control of records, reporting channels, evidentiary architecture, and audit cost. Execution-Credit Asymmetry is theoretically reversible; the verified mechanism appears wherever one actor owns the channel that makes execution legible and the other must prove through it.

Post-EO 14173 contractor certification — under which federal contractors certify they do not operate unlawful DEI programs, with compliance treated as material to payment — may become a future inversion specimen if enforcement records accumulate. The records do not yet exist.

VIII. Execution Parity

The repair principle is compact:

Credit follows trace. Trace burden follows control.

Operationally:

1. The actor that controls the execution channel bears the trace burden.
2. Execution credit cannot exceed audit-channel strength.
3. A claimant does not bear proof burdens for records controlled by the institution.
4. Compliance artifacts count as execution only when sampled against target variables.
5. If the formal object is invoked as defense, the defender must show the execution path.

Execution Parity is not self-executing. The principles above do not move records out of the institution's control. They require discovery power, publication power, sanction power, or automatic consequence. Without one of these, credit follows trace is a sentence, not a repair.

The implementation teeth that turn the principle into repair:

• Early mandatory production of the records the favored actor controls — before the claimant must prove what those records would show.
• Adverse inference when required channel records are missing, incomplete, or destroyed.
• Fee shifting for materially incomplete compliance-defense records.
• Interim reinstatement or front-pay leverage where the statute permits, so channel pressure runs while the proceedings run.
• Sampling of compliance systems — hotlines, investigation files, audit-committee minutes, training records — against the outcomes the systems are supposed to prevent or detect.

These are familiar evidentiary moves. The frame's contribution is routing: the moves above are the trace burden following control. They are what Execution Parity means in practice.

Where an independent oversight body is needed to run discovery or publish a ledger, the institutional architecture is The Fourth Branch. Where parity correction fails and a trace gap remains, the owner is named in Corrective Closure Ownership. The canonical format for the execution-trace record is the Implementation Ledger. The moment the parity record acquires institutional consequence is The Record Gate.

IX. The routing matrix

Each entry turns the diagnosis into a record demand. The form is the same in every case: name the records, name the credit, name the trace, write the demand that moves the trace burden to the actor who controls the records.

"We have compliance."

Records controlled by the company. Credit received by the company. Trace burden borne by the claimant or regulator.

Parity correction. Regulator, auditor, or court demands prior hotline complaints by category, substantiation rate, correction rate, time from report to closure, retaliation complaints among reporters, and training-to-incident correlation. Adverse inference attaches if records are missing.

"I am protected." (§ 806, Title VII, state whistleblower)

Records controlled by the employer. Credit received by no one yet. Trace burden borne by the worker.

Parity correction. Worker's counsel demands the hotline log, investigation file, decisionmaker emails, performance documentation history, comparator discipline records, and preservation history. Adverse inference rule attached.

"We enforce."

Records controlled by the agency. Credit received by the agency. Trace burden borne by the beneficiary or the public.

Parity correction. Inspector general, congressional committee, or FOIA requester demands per-channel intake, time-to-disposition, disposition mix, and sampled outcome against the target variable (recidivism among supervised parolees; injury rates inside inspected workplaces; medication-error rates inside surveyed facilities). The agency's enforcement claim gets credit only against target-variable samples, not intake totals or action counts. Published by default.

"We are GDPR-compliant."

Records controlled by the controller. Credit received by the controller. Trace burden borne by the data subject.

Parity correction. Supervisory authority or procurement counterparty demands the DSAR response-time distribution, rectification-execution log, erasure-confirmation trace, and complaint-resolution disposition. Filed alongside the Record of Processing Activities, not in place of it.

"Our § 54 statement is filed."

Records controlled by the supplier or parent company. Credit received by the supplier or parent company. Trace burden borne by the worker, the victim, the NGO, or the procurement officer.

Parity correction. Statement credit is limited to disclosure. Substantive anti-slavery credit requires sampled remediation outcomes, registry-flagged status (non-filing / no-steps statement / stale statement), and procurement-linked cooperation with NRM referral and remediation processes — not private victim adjudication.

An entry passes only where it names an actor with authority to demand the record.

X. The trace test that does not become another piece of paper

The slogan version of Execution Parity, like the slogan version of Nominal Execution, can become another token. A discovery-demand template filed without enforcement is paper. An execution ledger that publishes nothing the regulator could not have already published is paper. A procurement clause signed but never audited is paper.

The deployable artifact in § IX is the test. If the matrix moves no records, the diagnostic has named a pattern without changing it.

Takeaways