Field 17 and securities law
Decision Accounting
Field 17 and securities law: discoverability, admissions, and the welfare-disclosure safe harbor
core-claim
Core claim
Field 17 is needed because Hollow Wins cannot be seen from bilateral payoffs
The paper’s starting point is the Hollow Win: the (0,1,1) result where both bargaining parties gain while system welfare falls. Field 17 is the DA field that records the missing C dimension, so it is necessary for governance and risky in litigation.
- The Missing System Theorem says system welfare W cannot be expressed as a function of the bargaining parties’ payoffs.
- Field 17 records SYSTEM WELFARE, the only DA field not derivable from the bilateral payoff space.
- The same features that make Field 17 useful internally, including standardization, quantification, and auditability, make it useful to securities plaintiffs.
discovery-problem
Discovery problem
A quantified Field 17 can become the complaint’s best exhibit
The paper’s manufacturing hypothetical shows the danger: a firm records expected groundwater harm, keeps it out of SEC filings, then faces EPA enforcement and a shareholder suit after a stock-price drop.
- The Field 17 entry estimates $12-15 million in annual system-welfare destruction from groundwater contamination risk.
- It also records a 65% probability of regulatory intervention within three years.
- Two years later, EPA enforcement is followed by a 30% stock drop and a Rule 10b-5 class action.
scienter-materiality
Scienter and materiality
Plaintiffs can frame Field 17 as knowledge of an investor-relevant risk
The paper distinguishes system welfare from shareholder welfare, but calls that distinction legally fragile. Environmental, regulatory, reputational, and liability risks can convert a system-welfare record into evidence about the firm’s financial condition.
- Under Ernst & Ernst v. Hochfelder, plaintiffs need scienter, and internal records help show what officers knew and when they knew it.
- Under Basic v. Levinson, materiality turns on whether a reasonable investor would consider the fact important.
- A Field 17 record can be argued to show both system harm and foreseeable financial risk from cleanup costs, penalties, litigation, or backlash.
missing-system-trap
Missing system trap
Current securities law rewards firms that do not measure system-welfare harm
The paper identifies a trap: once a firm measures system-welfare harm, it creates a record that may support disclosure claims. A firm that stays ignorant creates no comparable record.
- Disclosure duties are triggered by risks to the firm-investor relationship, not by externalities as such.
- A firm has no duty to disclose system-welfare destruction unless it creates a material risk to the firm’s financial condition.
- Field 17 is meant to make measurement routine, but securities exposure may deter adoption of the DA framework.
pslra
PSLRA limits
The PSLRA safe harbor likely misses Field 17 on every key element
The paper rejects the PSLRA forward-looking safe harbor as a real shield for Field 17. Field 17 is an internal governance record, usually about current or past system-welfare impact, not an investor-facing projection.
- 15 U.S.C. § 78u-5 protects forward-looking statements identified as such and paired with meaningful cautionary language, or statements not made with actual knowledge of falsity.
- The statute lists projections of revenues, income, earnings per share, capital expenditures, dividends, capital structure, and other financial items.
- System-welfare impact is not treated as a statutory financial item, and an ordinary Field 17 entry is not accompanied by PSLRA cautionary language.
proposed-safe-harbor
Welfare-disclosure safe harbor
The proposed safe harbor protects the record, not lies built on top of it
The paper proposes a statutory safe harbor for welfare-disclosure records. The protection would bar use of a completed Field 17 as evidence of scienter or materiality in private securities actions if the firm follows specified conditions.
- Condition 1: the record is prepared in the ordinary course as part of a structured decision-making protocol.
- Condition 2: the firm does not make a public statement that contradicts the Field 17 content.
- Condition 3: the firm has a written policy requiring Field 17 for all decisions that may produce a Hollow Win.
- Condition 4: the firm does not use the record to justify a public claim that the activity has no material risk.
safe-harbor-limits
Safe harbor limits
The safe harbor cannot perfectly separate good-faith records from bad-faith use
The paper ties the proposal to the Safe Harbor Intractability Theorem: no governance mechanism can distinguish good faith from a Hollow Win after the fact. The safe harbor is therefore a litigation-risk allocation device, not a perfect screen.
- The safe harbor addresses honest Field 17 completion, not every possible abuse of Field 17.
- It accepts that some bad-faith actors may be protected and some good-faith actors may remain exposed.
- The intended effect is to reduce the incentive to avoid measurement or destroy records.
privilege
Privilege
Routing Field 17 through counsel does not make the business record privileged
The paper says attorney-client privilege depends on purpose. Legal advice about disclosure obligations may be protected, but the Field 17 record used to decide whether to proceed with a transaction remains vulnerable as a business record.
- United States v. United Shoe Machinery Corp. protects communications that are primarily or predominantly legal in character.
- A Field 17 entry made to approve a transaction, allocate resources, or manage operations is not privileged just because counsel saw it.
- The same document can have legal and business purposes, creating costly privilege uncertainty.
work-product-waiver
Work product and waiver
Routine DA records do not fit work-product doctrine cleanly
Work-product protection is also narrow. The DA framework creates Field 17 records for routine decisions that may produce Hollow Wins, while work product protects documents prepared because of litigation.
- Hickman v. Taylor and Rule 26(b)(3) protect documents prepared in anticipation of litigation.
- A Field 17 completed for routine decision-making is prepared in the ordinary course of business.
- Even protected work product can be obtained on substantial need and undue hardship, and privilege can be waived through disclosure to regulators, auditors, or other third parties.
half-truth
Macquarie
Macquarie helps with silence but not contradictions
Macquarie Infrastructure v. Moab Partners limits Rule 10b-5(b) liability for pure omissions. A firm that completes Field 17 but says nothing publicly about system-welfare impact does not create omission liability from the record alone.
- The Supreme Court held that a pure omission is not actionable unless it makes an affirmative statement misleading.
- The danger is a public statement such as no material system-welfare risks have been identified when Field 17 says significant risk identified.
- SEC v. Texas Gulf Sulphur supplies the half-truth rule: a literally true statement can mislead if omitted facts are needed to make it accurate.
disclosure-protocol
Disclosure protocol
Before public risk statements, the disclosure committee must check Field 17
The paper’s protocol turns Field 17 into a consistency check for public disclosures. It does not force disclosure in every case, but it bars blanket denials that conflict with internal records.
- All Field 17 records are kept in a secure database with access controls.
- Before public statements about system-welfare risk, the disclosure committee reviews relevant Field 17 records.
- If Field 17 shows material system-welfare impact, the public statement must disclose the impact or be qualified to avoid contradiction.
- The committee documents the review, creating evidence relevant to scienter.
resolution
Resolution architecture
The paper separates the business record, the legal review, and the link between them
The proposed architecture keeps Field 17 useful without pretending the whole record is privileged. It creates three layers so the decision record can be produced without automatically producing legal advice.
- Layer 1: the business unit completes the 17-field DA decision record, including quantitative system-welfare impact, probability assessment, and basis for assessment.
- Layer 2: legal counsel separately reviews disclosure duties, litigation risk, whether to proceed, and public-disclosure recommendations.
- Layer 3: an access-controlled index links the decision record and legal review across separate databases for authorized users only.
falsification
Falsification
The shield claim fails if courts treat compliant Field 17 records as naked admissions
The paper makes its legal claim testable. If courts systematically use a privilege-architected, safe-harbor-conditioned Field 17 as evidence of scienter or materiality despite the protocol, the proposed shield does not work.
- The strong falsification condition is a federal district court treating a compliant Field 17 as admissible evidence of scienter or materiality despite the architecture and safe harbor.
- A weaker condition is multiple courts holding that the privilege overlay does not protect the legal-review layer from discovery.
- An empirical condition is firms adopting DA facing a statistically significant increase in securities fraud litigation.
- All results are proposed and not yet peer-reviewed.