UCLA CRO PRE-REPORT RESPONSE SYSTEM

Comprehensive V2 Synthesis, Fulfillment Audit, and Operational Guide

Integrated review of the original production assignment, V1 audit, V2 continuation, final continuation response, all attached thread exports, and every member of the sealed 25-file V2 archive

Prepared for: Cooper Beaman

Prepared: July 26, 2026 (PDT)

Final V2 ZIP: CRO_PRE_REPORT_RESPONSE_SYSTEM_FINAL_V2_2026-07-23.zip

ZIP SHA-256: 94B5A900E00667CCA5A38B36B0847FBD11BE839362717FD5243040359244AAEC

ZIP size: 1,097,473 bytes

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

This document is an integrated internal reference. It is not a substitute for the actual CRO report, current UCLA confirmation, or qualified legal advice.

Document Map

1. Executive determination and practical bottom line
2. Scope, corpus, methodology, and explicit limitations
3. End-to-end task evolution: V4 assignment → V1 → audit → V2 → final continuation
4. Section-by-section evaluation of the final continuation response
5. Cumulative fulfillment audit of every requested deliverable and workflow gate
6. Integrated operational synthesis: report receipt, deadlines, route logic, evidence, DGE/CDP, hearing, remedies, preservation, and counsel triggers
7. Artifact-by-artifact guide to all twenty primary artifacts and five controls
8. Detailed section/sheet digest of every file inside the V2 ZIP
9. Attached thread-export audit and execution-history synthesis
10. Risk register, limitations, and prioritized action plan
11. Appendix A: verified 25-member archive inventory and checksum hierarchy
12. Appendix B: complete atomic-requirement status index (1,550 rows)
13. Appendix C: full section/sheet structural index

Navigation note: Word’s Navigation Pane can jump directly among the numbered headings. The appendices are landscape-oriented for dense tables.

1. Executive Determination and Practical Bottom Line

• Final package integrity: 25 members; 1,097,473 bytes; sealed ZIP SHA-256 94B5A900E00667CCA5A38B36B0847FBD11BE839362717FD5243040359244AAEC.
• Primary deliverables: all 20 requested artifacts are present. Eighteen changed from V1; Artifacts 11 and 16 remained byte-identical because the targeted audit found no content defect requiring alteration.
• Requirement fulfillment: 1,550 atomic rows reconcile to 1,497 PASS, 0 PARTIAL, 0 FAIL, 3 REPORT-DEPENDENT, 1 UCLA-CONFIRMATION-DEPENDENT, 1 COUNSEL-DEPENDENT, and 48 NOT APPLICABLE.
• Final QA: 17/17 route checks; 21/21 probability checks; 34/34 deadline samples; 9/9 workbooks and 40/40 sheets with persisted panes; 167/167 citation/source-fidelity sample; zero unexplained epistemic-language failures; exact 25/25 manifest and ZIP checks.
• Operational priority: when the report arrives, activate Artifact 05 first, preserve the native transmission, verify completeness, calculate both counting assumptions, and do not make a final hearing-versus-comments election from an uncured incomplete transmission.

2. Scope, Corpus, Methodology, and Explicit Limitations

2.1 Corpus reviewed

2.2 Method

• Archive integrity: extracted the ZIP, enumerated all members, recomputed SHA-256 for the ZIP and each member, compared the root checksum ledger, and reconciled the 25-row output manifest.
• Markdown: indexed every heading, line range, word count, preview passage, and table header across all 13 Markdown members, then produced a section-by-section digest.
• Workbooks: opened all nine XLSX files, inventoried all 40 sheets, dimensions, formulas, merges, freeze panes, first/last populated rows, tables, and key operational controls.
• Requirements: read all 1,550 rows from the final Atomic Requirements sheet and incorporated a complete status/artifact/locator index in Appendix B.
• Execution history: parsed all 18 attached thread exports for metadata, task roles, prompt/response chunks, actions, created/edited files, final messages, and truncation markers.
• Fulfillment: compared the original V4 assignment, the V1 defect audit, the V2 continuation prompt, the final resume/finalization request, the final response, and the actual sealed files.

2.3 Limits of “every word/token” review

3. End-to-End Evolution of the Task

4. Section-by-Section Evaluation of the Final Continuation Response

Opening completion and package-seal statement

Response content: Accurately states that V2 preserves V1, cures all confirmed presently completable defects, and creates an exact 25-member release. The reported ZIP size and SHA-256 independently match the uploaded archive.

Evaluation: Fully supported.

V1-to-V2 defect disposition

Response content: Concise 15-row closure table accurately connects each reproduced V1 defect to its V2 cure. It appropriately keeps V2-R008 and V2-R014 as only “partially confirmed” at the V1-baseline level while reporting the V2 cure as PASS.

Evaluation: Supported by the repair ledger, final audit, and QA report.

Twenty repaired primary artifacts

Response content: Provides the complete required artifact list in the correct numbering and naming scheme. All 20 are present in the archive.

Evaluation: Fully supported.

V2 control and verification files

Response content: Lists all five required controls. The checksum-hierarchy explanation is correct: the root ledger hashes every other member, and the sealed ZIP hash authenticates that ledger.

Evaluation: Fully supported.

Final validation results

Response content: Summarizes deterministic, structural, sampled, and visual tests. Counts reconcile with the QA files and workbooks. The response correctly differentiates the 167-claim source sample from full semantic proof of every historical assertion.

Evaluation: Strongly supported; QA is technical/compliance validation, not a legal merits adjudication.

Completion ledger

Response content: Reports 1,497 PASS, no presently completable PARTIAL/FAIL/BLOCKED rows, and five genuine dependency rows plus 48 N/A controls. This is the appropriate non-overclaiming classification.

Evaluation: Fully supported by Artifact 00 and Artifact 19.

5. Cumulative Fulfillment Audit

5.1 Original V4 workflow and production standard

5.2 V2 continuation phases

5.3 Final resume/finalization instructions

5.4 Deliverable-by-deliverable fulfillment

6. Integrated Operational Synthesis

6.1 Current posture

• The actual CRO report and transmittal remain the principal future facts. The current package is designed to be populated rapidly when they arrive.
• The system is route-neutral until the transmission is preserved, complete/readable, and allegation/evidence mapping is performed.
• CRO findings, DGE mitigation, Bailey record integrity, remedy authority, and external/counsel questions are kept analytically separate so one adverse conclusion does not erase useful factual or procedural material elsewhere.

6.2 Report-receipt sequence

6.3 Deadline framework

Critical cautions: The 15-Day comments and 20-Day finalization periods are concurrent, not sequential. Observed holidays are not automatically full-campus closures. Reasonable extensions may be granted for good cause, and the procedure states no numerical cap. A corrected or incomplete transmission requires preservation and written clarification rather than an assumed final anchor.

6.4 Corrected forecast

6.5 Evidence and actor architecture

• Eight formally scoped actions are evaluated separately across the named respondent groupings rather than treated as one all-or-nothing case.
• Outside-formal-scope people or events remain relevant only for bounded functions such as chronology, notice, comparator context, witness leads, or DGE mitigation—not as automatic proof of the scoped allegations.
• Every proposition must retain its epistemic label: source-established procedural fact, allegation, respondent/program position, primary account, witness/evidence proffer, user-authored synthesis, prior-AI hypothesis, unknown/source silence, or report-dependent fact.
• Artifact 08 is the central accounting device for whether an item was addressed, discounted, omitted, contradicted, or merely not cited. Artifact 10 is the central bridge from authenticated facts to DGE mitigation.

6.6 Hearing versus comments

• Hard stop first: an incomplete, unreadable, internally inconsistent, or materially redacted transmission cannot support a final merits-route election unless the earliest plausible deadline requires a protective step.
• After completeness, use hard triggers and the weighted scorecard: disputed material facts, credibility, cross-examination need, witness value, material omission, new rationale, record correction, remedy feasibility, cost/time, and preservation needs.
• A hearing route is generally more relevant where live credibility, disputed facts, unavailable witnesses, or cross-examination are material. A comments route is generally more relevant where the record is complete, disputes are documentary, and concise correction/remedy submissions are sufficient.
• The choice remains Cooper’s; this package supplies decision support and protective drafting, not an automatic election.

6.7 DGE/CDP and Bailey

• DGE mitigation is not identical to a CRO policy-violation finding. A report can be formally adverse yet contain authenticated facts that are substantively relevant to academic performance, disability circumstances, accommodation process, timing, stress, support, or procedural fairness.
• The Standards describe DGE abeyance and “Investigation Materials,” but do not clearly define whether completion includes a hearing or subsequent appeal. Preserve the ambiguity and request UCLA confirmation when it becomes material.
• Bailey’s acknowledged simultaneous-service problem is a record-integrity circumstance. The strongest argument is concrete lost opportunity or prejudice, supported by the prejudice table, not an assertion that any procedural error automatically creates an unlimited rebuttal right.
• Requested remedies must be routed by authority: express CRO/Procedure authority, plausible corrective step, referral, negotiation, UCLA confirmation, or counsel-dependent relief.

6.8 Preservation and counsel triggers

• Preserve native messages, full headers, original attachments, portal state, timestamps/time zones, hashes, immutable originals, working copies, redactions, submission receipts, and every corrected version.
• Counsel consultation is triggered by concrete observable events: waiver/exhaustion/finality ambiguity, denial of a timely hearing, missed deadlines without a verified extension, undisclosed extra-record material, irreversible academic consequences, source-silent DGE sequencing, substantive mitigation denial, or a new fact-supported retaliation event.
• Consultation and preservation are distinct from filing. No external claim, agency jurisdiction, constitutional theory, deadline, or entitlement should be treated as settled without qualified review.

7. Artifact-by-Artifact Guide

7.1 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx

Primary role: Master compliance ledger

What it contains: Maps 1,550 atomic instructions to acceptance criteria, final artifacts, exact evidence, verification methods, statuses, and V1 defect history.

How to use it: Use it to answer “Was this requirement actually completed, where, and how was it verified?” Filter by status, source, artifact, or defect.

Boundary / limitation: It proves package compliance, not the truth of future CRO findings.

Integrity: 423,976 bytes; SHA-256 DB4E4918599AF5350370EF748284C62D66C8062AB792AB414CB531C7496DA7C9.

7.2 01_SOURCE_COVERAGE_AND_RELIABILITY_LEDGER.xlsx

Primary role: Source-control and epistemic ledger

What it contains: Inventories the authorized package, distinguishes control files from evidentiary tiers, and records traversal, passage verification, and page-image review separately.

How to use it: Consult before relying on any source; preserve the distinction between allegation, party position, proffer, synthesis, and established procedural text.

Boundary / limitation: Full traversal is not equated with human-equivalent semantic review of every source token.

Integrity: 19,181 bytes; SHA-256 C193718EBEDE1866EB2778F68D7F5EA4FAB80A58A49BD94FF3194C80FBC54105.

7.3 02_STAGE_A_INTEGRATION_AND_PROCEDURAL_ARCHITECTURE.md

Primary role: Procedural architecture

What it contains: Consolidates verified Procedure 230.2, Attachment B, DGE/CDP, policy-version, deadline-counting, source-silence, and sequencing rules.

How to use it: Use as the governing procedural reference before calculating dates or choosing a route.

Boundary / limitation: Several points remain expressly source-silent and require UCLA confirmation.

Integrity: 26,163 bytes; SHA-256 90C3453707A1C04E37C9C869E03FB6FD88657ECB63500C6CB97B0481024BAB1A.

7.4 03_DEADLINE_CALCULATOR_AND_SEQUENCING_MATRIX.xlsx

Primary role: Deadline engine

What it contains: Implements Assumptions A and B, closure sensitivity, no-hearing and hearing sequences, strategic internal targets, and independent QA samples.

How to use it: Enter the actual complete-transmission facts; preserve both counting conventions and use the earlier plausible protective date until confirmed.

Boundary / limitation: Hypothetical dates are not actual deadlines; closures, extensions, and corrected transmissions can change them.

Integrity: 94,445 bytes; SHA-256 A8443FD1E95171435D46B020A173ADFEBAF4D2C91BC7D177A9D84EE73B54E07A.

7.5 04_CORRECTED_FORECAST_AND_REPORT_ARCHITECTURE.md

Primary role: Structured forecast

What it contains: Separates delivery timing, conditional merits, and nonexclusive operational overlays; includes factor ledgers, sensitivities, allegation-level judgments, report architecture, confirmers, and falsifiers.

How to use it: Use only for planning and resource allocation; update by recording the new fact and exact reallocation.

Boundary / limitation: Weights are subjective planning judgments, not empirical probabilities.

Integrity: 54,381 bytes; SHA-256 86AEFE0F595AE3BADD7BECF941B8DD509C1C1980693A8D30D0E89B03C8186601.

7.6 05_REPORT_RECEIPT_WAR_ROOM.md

Primary role: Immediate receipt protocol

What it contains: Provides roles, folder structure, first-15-minute, first-hour, first-day, completeness, preservation, and escalation checklists.

How to use it: This is the first artifact to activate when any report or issuance message arrives.

Boundary / limitation: Do not let analysis or reply drafting precede native preservation and completeness verification.

Integrity: 17,003 bytes; SHA-256 2371D6428F8E5D464644515097B5463BF11B5CF23807B8559BF8EA35F8B81820.

7.7 06_HEARING_VS_COMMENTS_DECISION_SYSTEM.xlsx

Primary role: Route decision system

What it contains: Contains the corrected completeness gate, hard triggers, weighted scorecard, decision tree, worked examples, and machine-checkable route assertions.

How to use it: Use after the report is complete/readable and the allegation/evidence map is populated; record assumptions and preserve rights.

Boundary / limitation: Do not make a final merits-route election from an uncured incomplete transmission unless a protective filing is required.

Integrity: 22,904 bytes; SHA-256 743E47F64E648ACD17B56E7DD7B8BCF521554B923090B61F1EFD24E76133CE93.

7.8 07_EIGHT_COMPLETE_SCENARIO_PLAYBOOKS.md

Primary role: Eight modular response playbooks

What it contains: Operationalizes eight possible delivery/merits/record states with 20 fields each, including triggers, tasks, evidence, route implications, DGE actions, templates, escalation, and exit criteria.

How to use it: Select one or combine compatible modules after classifying the actual report; they are not one probability universe.

Boundary / limitation: Actual facts control; modules require authentication and report-specific insertion.

Integrity: 52,283 bytes; SHA-256 35222D4D17B891D34CE2C46BEFB7CEE631C52AA13472FF3BC2EC22417813754D.

7.9 08_EXPECTED_RECORD_OMISSION_CONTRADICTION_MATRIX.xlsx

Primary role: Record-accounting matrix

What it contains: Tracks scoped actions, outside-scope items, witnesses, documents, DGE integrity issues, Stage A rules, unavailable exhibits, omission status, contradiction type, materiality, and cure.

How to use it: Use to distinguish true omission from noncitation, summarize contradictions, and produce item-specific cure requests.

Boundary / limitation: The blank operational log must be populated from the actual report; noncitation alone is not nonconsideration.

Integrity: 31,777 bytes; SHA-256 921FBED36D04B561E033DA9D782859F7798562F5A4BABB652632649618E7E381.

7.10 09_DGE_CDP_MITIGATION_PACKAGE.md

Primary role: DGE/CDP strategy package

What it contains: Separates the CRO violation question from DGE mitigation, maps possible report outcomes to requested DGE actions, and addresses sequencing, abeyance, substantive mitigation, and CDP referral.

How to use it: Use even if CRO finds no formal violation; extract authenticated facts that may be substantively relevant to academic performance.

Boundary / limitation: DGE completion and referral mechanics remain partly source-silent.

Integrity: 72,574 bytes; SHA-256 8A2B95089CCB0C5867C0BC42A61D029931AF918FAECAE09B8751868BEA5EEC22.

7.11 10_DGE_CDP_MITIGATION_CROSSWALK.xlsx

Primary role: Mitigation crosswalk

What it contains: Provides baseline and future-report rows linking facts, CRO treatment, disability circumstances, accommodation/process issues, academic effects, source, DGE relevance, and requested handling.

How to use it: Populate the future-report copy allegation by allegation and fact by fact.

Boundary / limitation: Do not collapse disability circumstances, accommodation-process defects, and formal policy findings into one category.

Integrity: 17,698 bytes; SHA-256 DAD90B82A3668B4522BC2840C2B1AD59C3210B081A38455BD4EF1024A40F12FE.

7.12 11_BAILEY_RECORD_INTEGRITY_MEMORANDUM.md

Primary role: Bailey service/record memorandum

What it contains: Analyzes the simultaneous-service defect, DGE acknowledgement, record integrity, source silence, prejudice pathways, and bounded corrective requests.

How to use it: Use as the narrative explanation supporting a narrow record-integrity correction or sequencing request.

Boundary / limitation: The service defect does not automatically establish an unlimited sur-rebuttal right or constitutional violation.

Integrity: 49,015 bytes; SHA-256 891A1DC32BC3ECE45963277A81E187F9B83BCF1FD6CFE16EDD0EEFC02761EE42.

7.13 12_BAILEY_PREJUDICE_TABLE.xlsx

Primary role: Bailey prejudice proof table

What it contains: Organizes each alleged defect, timing, affected opportunity, prejudice theory, counterargument, proof, cure, and deployment trigger.

How to use it: Use to show concrete prejudice rather than relying on procedural error in the abstract.

Boundary / limitation: Each prejudice proposition still requires exact authenticated facts.

Integrity: 13,326 bytes; SHA-256 7E116720E9FA3C2D21B4EEB576BA8ED1B2DA16F41F055B4B3400B66AE2110421.

7.14 13_REMEDY_AUTHORITY_MAP.xlsx

Primary role: Remedy-authority map

What it contains: Separates express authority, plausible corrective steps, referral, negotiation, UCLA confirmation, and counsel-dependent relief by decisionmaker and source.

How to use it: Use to route each requested remedy to the correct office and to avoid asking CRO for relief it cannot clearly grant.

Boundary / limitation: Possible outcomes are not entitlements; authority and feasibility must be verified.

Integrity: 14,755 bytes; SHA-256 750645D2B2EFFFBD53E570AAF07E6DD9798A9B79A41A5E1BBAD732648D9BA7F9.

7.15 14_READY_TO_DEPLOY_TEMPLATE_SUITE.md

Primary role: Template suite

What it contains: Contains 24 minimal and 24 substantive drafts for completeness, extensions, route preservation, comments, hearing, DGE/CDP, record correction, remedies, counsel, and follow-up.

How to use it: Choose the narrowest suitable template, populate bracketed facts and exact citations, then review before any sending.

Boundary / limitation: Templates are drafts; no recipient, address, legal conclusion, or deadline should be assumed.

Integrity: 126,962 bytes; SHA-256 28CC76795FF1B4210250A31EEE9843540812B10F19AF59F1F6D7A0811C35B1FA.

7.16 15_HEARING_AND_POST_HEARING_PACKAGE.md

Primary role: Hearing package

What it contains: Provides request modules, representative disclosure, issue framing, proof plan, witness/exhibit map, opening/closing outlines, cross-examination, post-hearing comments, appeal preservation, and source ledger.

How to use it: Use only after a hearing is chosen or protectively requested; build from authenticated exhibits and the actual report.

Boundary / limitation: Hearing Officer procedure and relevance control remain case-specific.

Integrity: 31,186 bytes; SHA-256 3A1C0F9D12F6010119D45E78A555E0A5A906DB99C19880E8C5B6818EE34607A9.

7.17 16_ADMINISTRATIVE_RECORD_PRESERVATION_PROTOCOL.md

Primary role: Record-preservation protocol

What it contains: Defines native capture, immutable originals, hashing, versioning, metadata, screenshot, redaction, submission-proof, and chain-of-custody practices.

How to use it: Use throughout receipt, drafting, submission, correction, and appeal stages.

Boundary / limitation: Preservation must not alter original evidence or imply access to unavailable records.

Integrity: 13,677 bytes; SHA-256 F0D0A1E538E1961ED00133501DBD632A122C84A1E0A38D102117C30F589BF843.

7.18 17_EXTERNAL_REVIEW_AND_COUNSEL_TRIGGER_MATRIX.xlsx

Primary role: Counsel/external-review triggers

What it contains: Pairs observable events with proof, timing, consultation scope, purpose, and caution for administrative, disability, agency, judicial, interim-relief, negotiation, and retaliation issues.

How to use it: Use to decide when specialized advice is warranted—not to trigger automatic filing.

Boundary / limitation: Consultation/preservation is distinct from filing; legal characterization is reserved for counsel.

Integrity: 12,129 bytes; SHA-256 80D726DC50B2D24BEE9D598D4A63394137EADC8F68B18CD48498865B9F5A5259.

7.19 18_TWO_PAGE_EXECUTIVE_COMMAND_SHEET.md

Primary role: Executive command sheet

What it contains: Condenses immediate rules, deadlines, ranked planning scenarios, route hard stop, DGE actions, evidence priorities, templates, and escalation triggers.

How to use it: Use as the rapid command view during report receipt and first-day triage.

Boundary / limitation: It is a summary; consult the underlying artifacts for detail and evidence.

Integrity: 11,854 bytes; SHA-256 7CB19B2A9AF92B2C1023C8FEF66C2F8CF598F33CE40012AB4F7D593A436A0BAD.

7.20 19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md

Primary role: Final compliance audit

What it contains: Reports methodology, status counts, defect dispositions, V1 historical failures, dependencies, completion ledger, and the full 1,550-row evidence appendix.

How to use it: Use to verify what the package claims, what remains future-dependent, and where exact evidence resides.

Boundary / limitation: It audits fulfillment, not the ultimate merits of the UCLA dispute.

Integrity: 2,602,025 bytes; SHA-256 DF4F5149FE9A39C869E1F2FA5752B782D841C107FF786F55943E744C7305AD1C.

7.21 V2_REPAIR_LEDGER.md

Primary role: Repair ledger

What it contains: Records V1 preservation, each V2 defect, cure, final status, artifact-by-artifact changes, validation results, and residual dependencies.

How to use it: Use to understand exactly what changed from V1 and why.

Boundary / limitation: Two V1 artifacts remained byte-identical because no targeted content defect was established.

Integrity: 16,808 bytes; SHA-256 9517446321436A28941972663701ACE3555144E2D17DE511CF7E0870EBB904FB.

7.22 V2_INDEPENDENT_QA_REPORT.md

Primary role: Independent QA report

What it contains: Consolidates baseline, workbook, route, forecast, deadline, requirement, citation, epistemic, deployment, visual, manifest, and ZIP tests plus exact commands.

How to use it: Use as the technical validation record and reproducibility guide.

Boundary / limitation: QA includes deterministic and sampled checks; it is not an independent legal merits adjudication.

Integrity: 16,952 bytes; SHA-256 3255AA35FB20C83775306C4686EC3A97F0A0D484B28881EFD44213231CF01ECB.

7.23 INPUT_PACKAGE_MANIFEST.csv

Primary role: Input manifest

What it contains: Byte-for-byte copy of the controlling input-package inventory.

How to use it: Use to confirm authorized source scope and provenance.

Boundary / limitation: It inventories sources; it does not prove their substantive assertions.

Integrity: 5,741 bytes; SHA-256 7C067C0668A5D86E6B200DFFCAF641613E036427112188BD2852160170D073BC.

7.24 FINAL_OUTPUT_MANIFEST_V2.csv

Primary role: Output manifest

What it contains: Lists each of the 25 final members with size, SHA-256, generator/source, validation, change status, report-dependent fields, and residual risks.

How to use it: Use for release inventory, exact-member verification, and future integrity checks.

Boundary / limitation: The ZIP hash is the final archive-level seal.

Integrity: 14,199 bytes; SHA-256 22A57D58D14D07A6E6BC9D7F858285D7C9DABAC1B8BD9AB7FE5681BC56E10965.

7.25 FINAL_OUTPUT_SHA256SUMS_V2.txt

Primary role: Root checksum ledger

What it contains: Hashes every archive member except itself.

How to use it: Recompute hashes after transfer and compare exactly.

Boundary / limitation: The ledger authenticates members; the sealed ZIP hash authenticates the ledger itself.

Integrity: 2,801 bytes; SHA-256 6799744CCDEC7943885EA5617C9B7702AA8B9B0F83FFDFA0AB62F9FE02E4D469.

8. Detailed Section and Sheet Digest of Every V2 Member

This chapter follows the native organization of every Markdown artifact and every workbook sheet. It is deliberately structural and exhaustive: each heading/sheet is represented, with its function, content type, and key operational information.

02_STAGE_A_INTEGRATION_AND_PROCEDURAL_ARCHITECTURE.md

390 lines; 3,558 words; 27 indexed headings/sections.

Stage A Integration and Procedural Architecture

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Fixed reference date: July 22, 2026 PDT Current posture: No CRO investigation report or transmittal exists. Every date below is a rule, calculation convention, hypothetical example, or internal target; none is an actual case deadline.

Source lines 1–9; approximately 51 words.

1. Executive operating findings

1. Source-established procedural fact. Attachment B defines “issuance” as the date of transmission. The operational anchor must therefore be derived from the actual native transmittal, not the date printed on a report. 2. Unknown / source silence. Neither Procedure 230.2 nor Attachment B says whether the transmission date is day zero or day one. The deadline system preserves both Assumption A (anchor excluded) and Assumption B (anchor

Source lines 10–56; approximately 357 words.

2. Policy and version control

| Source | Verified identity and date fields | Operational treatment | Unresolved issue | | UCLA Procedure 230.2 | Attached PDF is byte-for-byte identical to the current official PDF. PDF face/history: effective Sept. 26, 2016. Live APP record: Oct. 4, 2016. | Use the verified PDF text and preserve the official date discrepancy. | The official site does not state which effective-date display has priority. | | Attachment B | Guidance completed Dec. 12, 2016; current standalone file reflects the Jan. 24, 2017 technical build and matches bundled pp. 12–16 in text and rendering. | Use its express definition of issuance and its guidance, while recording any tension with the main procedure. | It prints no separate effective date or superseded version. | | Standards and Procedures for Graduate Study at UCLA | Cover states “Updated and Effective September 2025.” Attached/current official PDFs a…

Source lines 57–69; approximately 260 words. Tables/matrices: | Source | Verified identity and date fields | Operational treatment | Unresolved issue |

3. Procedure 230.2 — no-hearing route

Structural heading introducing subordinate content.

Source lines 70–71; approximately 0 words.

3.1 Receipt and issuance control

On receipt, preserve the native email and all attachments; record the first verified complete transmission timestamp; compare the printed report date with the native transmission; confirm every attachment and appendix; and place both counting assumptions into the deadline workbook. If the transmission is incomplete, corrupted, missing an attachment, or later corrected, preserve each version and request written clarification of the operative issuance

Source lines 72–82; approximately 75 words.

3.2 Route

1. Within the 10-Day hearing-request period, decide whether Cooper disagrees with findings and whether a hearing request is warranted. Preserve the earliest plausible A/B endpoint as the internal hard stop unless UCLA confirms otherwise. 2. If no hearing is requested within the permitted time, the Grievant and Subject each have 15 Days from issuance to submit written comments.

Source lines 83–99; approximately 130 words.

3.3 “Acceptance” textual tension

The operative main-procedure text applies the no-hearing comments route when the Grievant “does not request a formal hearing within the time permitted.” Attachment B Step 2B and the procedure summary add that the Grievant “accepts the findings and recommendations” and does not request a hearing. Stage A found no definition of accepts, no required acceptance act or form, and no recipient or date for an affirmative acceptance. Therefore:

Source lines 100–120; approximately 144 words.

4. Procedure 230.2 — hearing route

Structural heading introducing subordinate content.

Source lines 121–122; approximately 0 words.

4.1 Request and representation

The main procedure provides that a Grievant who disagrees with findings may request a formal grievance hearing within 10 Days of report issuance. The procedure summary and Attachment B rights list refer to written notice. The request should therefore be in writing, identify whether Cooper will be assisted, name the representative if known, state whether the representative is an attorney, and preserve the ability to supplement detailed grounds.

Source lines 123–131; approximately 68 words.

4.2 Hearing timing

The hearing is scheduled on a mutually agreeable date. - It must be completed within 60 Days of investigation-report issuance. - The parties receive at least 10 Days’ written notice of time and place. - The Hearing Officer requests relevant material and intended-witness identities at least 5 Days before the hearing under operative §VI.B.3. The procedure summary adds “to the extent feasible”; that qualification does not

Source lines 132–146; approximately 104 words.

4.3 Hearing mechanics and report

Procedure 230.2 supplies the Hearing Officer with responsibility for procedural and evidentiary rulings and uses relevance and noncumulative value as practical organizing principles. The hearing package should connect each requested witness and exhibit to a disputed finding, a credibility issue, a causal link, a harm issue, or a remedy question, and should explain why the proof is not cumulative.

Source lines 147–160; approximately 110 words.

5. Post-hearing and appeal route

1. Parties may submit written comments to the Vice Chancellor through the Grievance Coordinator within 5 Days of hearing-report issuance. 2. The Vice Chancellor issues a written decision within 15 Days of that same hearing-report issuance. The decision includes findings and remedial action but not discipline. 3. An appeal may be filed within 5 Days following issuance of the Vice

Source lines 161–180; approximately 152 words.

6. DGE/CDP route and the unresolved interlock

Structural heading introducing subordinate content.

Source lines 181–182; approximately 0 words.

6.1 Controlling mitigation standard

The Standards direct DGE to determine whether the Investigation Materials reflect: > “substantive mitigating circumstances that could have affected a > disqualified student’s academic performance” Source: *Standards and Procedures for Graduate Study at UCLA*, printed p. 33, PDF file p. 34; Stage A PROCEDURAL_TEXT_EXTRACT.md, “Investigation

Source lines 183–198; approximately 79 words.

6.2 Abeyance

The Standards state that DGE will hold the appeal decision in abeyance while an investigatory office is processing allegations and until that process has completed. Academic disqualification remains in place during abeyance. Stage A did not identify the completion milestone. The system therefore uses the following neutral sequence: 1. Notify DGE promptly after the report is received, without asserting that

Source lines 199–220; approximately 161 words.

6.3 DGE decision branches

If the Investigation Materials do not reflect possible substantive mitigating circumstances, the Standards say the disqualification will stand and DGE will notify the individual within 30 calendar days of DGE’s receipt of the materials. - If the materials do reflect possible substantive mitigating circumstances, the Dean will refer the written appeal and Investigation Materials to CDP

Source lines 221–240; approximately 140 words.

7. Deadline counting architecture

Structural heading introducing subordinate content.

Source lines 241–242; approximately 0 words.

7.1 Assumptions

| Convention | Rule implemented | Why preserved | | Assumption A — anchor excluded | Transmission/anchor date is day zero; next qualifying business day is day one. | Common calculation convention, but not stated by the source. | | Assumption B — anchor counted | If the anchor is Monday–Friday and not an excluded closure, it is day one; otherwise the next qualifying day is day one. | Plausible alternative not excluded by the source. | Backward notice/disclosure calculations apply the same A/B conventions in reverse. The actual operational approach is to work to the earlier plausible endpoint unless UCLA confirms the convention in writing.

Source lines 243–253; approximately 96 words. Tables/matrices: | Convention | Rule implemented | Why preserved |

7.2 Closure and holiday treatment

| Category | Primary calculation | Sensitivity calculation | Statement permitted | | Saturdays/Sundays | Excluded | Excluded | Source-established exclusion. | | Confirmed full-campus closure | Excluded if officially confirmed | Excluded | None confirmed for the target period as of July 22, 2026. | | UCLA-observed holiday | Not automatically excluded | Excluded in sensitivity | Observed holiday; not established here as a full-campus closure. | | Dec. 28–30, 2026 | Not excluded | Excluded in possible-curtailment sensitivity | Uncertain possible curtailment weekdays; no 2026–27 designation located. | Sensitivity dates include Sept. 7; Nov. 11, 26, and 27; Dec. 24, 25, 28, 29,

Source lines 254–266; approximately 110 words. Tables/matrices: | Category | Primary calculation | Sensitivity calculation | Statement permitted |

7.3 Hypothetical July 31 illustration

If, and only if, a complete report were transmitted on Friday, July 31, 2026, the Stage A primary calculation produced: | Event | Assumption A | Assumption B | | 10-Day hearing-request endpoint | Aug. 14, 2026 | Aug. 13, 2026 | | 15-Day no-hearing comment endpoint | Aug. 21, 2026 | Aug. 20, 2026 | | 20-Day no-hearing finalization endpoint | Aug. 28, 2026 | Aug. 27, 2026 |

Source lines 267–282; approximately 94 words. Tables/matrices: | Event | Assumption A | Assumption B |

8. Primary versus sensitivity and internal targets

The operational workbook maintains three distinct date classes: 1. Primary A/B dates: weekends plus only confirmed campus closures. 2. Sensitivity A/B dates: observed holidays and possible curtailment dates excluded for stress testing, visibly labeled unconfirmed. 3. Internal targets: decision, draft-completion, and proposed submission dates set earlier than the earliest plausible external date. The recommended

Source lines 283–297; approximately 91 words.

9. Unextended versus extendable sequence

The calculator can place each stated period at its outer endpoint to show the longest unextended sequence under a selected assumption. That output is not an absolute maximum because §VI.D permits reasonable good-cause extensions for any time limit and states no numerical cap. Every timeline display must carry the extension warning, record any written request and decision, and preserve the pre-extension endpoint.

Source lines 298–306; approximately 63 words.

10. Prior-response correction table

| Prior treatment | Final treatment | Action | | Treated downstream dates as settled | Preserve A/B assumptions and actual-transmittal dependency | Reject certainty; calculate both. | | Treated named holidays as confirmed closure days | Separate observed-holiday and possible-curtailment sensitivities from confirmed closures | Correct. | | Described a “maximum-duration” chain | Describe only an outer-limit unextended sequence | Qualify because extensions have no stated cap. | | Implied 60 Days ran from hearing request | Anchor hearing completion to investigation-report issuance | Correct. | | Added sequential no-hearing periods | Run 15-Day comments and 20-Day finalization concurrently | Correct. |

Source lines 307–320; approximately 144 words. Tables/matrices: | Prior treatment | Final treatment | Action |

11. Official-source-silence register

| Question | Status | Operational response | | Is transmission day day zero or day one? | Unknown | Calculate A and B; work to earlier date. | | What time and time zone control transmission or receipt? | Unknown | Preserve native metadata; request confirmation. | | Does incomplete or corrected transmission constitute issuance? | Unknown | Preserve versions and request an operative-date statement. | | Which calendar identifies campus closure for Procedure 230.2? | Unknown | Exclude only confirmed closures in primary scenario. | | Do observed holidays necessarily equal campus closure? | Not established | Sensitivity only. |

Source lines 321–337; approximately 207 words. Tables/matrices: | Question | Status | Operational response |

12. Questions to confirm immediately upon report receipt

1. What native timestamp and transmission event does UCLA treat as issuance? 2. Is the transmission complete, and are all attachments, appendices, evidence lists, redaction pages, and referenced materials included? 3. Which A/B counting convention will UCLA use, and what time of day and time zone control? 4. Which announced dates, if any, are “days on which the campus is closed” for

Source lines 338–358; approximately 166 words.

13. Authority and caution

This architecture is decision support, not legal advice and not a finding that any right has been waived, exhausted, or preserved. Questions about waiver, exhaustion, constitutional claims, external filing periods, judicial review, or interim relief require qualified counsel. No UCLA contact or filing has been made.

Source lines 359–366; approximately 46 words.

14. V2 pinpoint authority index

This index supplies the smallest controlling location for the load-bearing rules used above. Stage A remains the interpretation baseline where the underlying texts differ or are silent. | ID | Proposition controlled | Exact source path and pinpoint | Verification treatment | | SA-01 | “Issuance” is the date of transmission. | 01_CASE_RECORD/05_UCLA_Procedure_230.2.pdf, Attachment B opening paragraph, bundled file p. 12; reproduced in 02_STAGE_A_POLICY_VERIFICATION/PROCEDURAL_TEXT_EXTRACT.md, “Issuance and transmission.” | Source-established procedural fact. | | SA-02 | Capitalized Days excludes Saturdays, Sundays, and campus-closed days. | 01_CASE_RECORD/05_UCLA_Procedure_230.2.pdf, §II, printed/file p. 2; Stage A extract, “Days.” | Source-established procedural fact. |

Source lines 367–390; approximately 573 words. Tables/matrices: | ID | Proposition controlled | Exact source path and pinpoint | Verification treatment |

04_CORRECTED_FORECAST_AND_REPORT_ARCHITECTURE.md

388 lines; 6,730 words; 29 indexed headings/sections.

Corrected Forecast and Report Architecture

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION V2 repair reference date: July 23, 2026 (PDT); the closed case-record cutoff remains July 22, 2026 Forecast objects: (A) the delivery state at the stated expected date, (B) the merits outcome conditional on a usable report, and (C) nonexclusive operational overlays Decision boundary: structured preparation only; this document does not predict what any identified person will do, establish a fact not in the record, or advise Cooper to elect a procedural route.

Source lines 1–8; approximately 88 words.

1. Executive judgment

The existing record supports preparing first for a mixed or factually nuanced report, not assuming either broad vindication or categorical rejection. The most useful pre-report posture is therefore route-neutral: preserve the native transmission, verify what was actually issued, protect the earliest plausible deadline under both counting assumptions, extract favorable factual findings even if the formal outcome is adverse, and keep DGE mitigation separate from the CRO policy-violation question. The weights below are structured subjective planning weights, not measured base rates, frequencies, or statistical confidence estimates. No comparable-case sample was available or used. The model begins from disclosed, deliberately non-equal starting judgments and then reallocates percentage points using stated evidence factors. The reallocations make the judgment auditable; they do not make it e…

Source lines 9–14; approximately 137 words.

2. Three-layer forecast architecture

The former eight-scenario table mixed timing, delivery quality, merits, and record-quality conditions in a single denominator. V2 separates those questions. Layer A and Layer B are different probability families and each independently sums to 100%. Layer C is nonexclusive and must not be added. The eight playbooks in Artifact 07 remain operational response modules, not a single probability universe.

Source lines 15–18; approximately 59 words.

Layer A — delivery/timing state

Denominator and classification moment: the next material CRO status at or through the close of July 31, 2026, using the case-record cutoff. If an unusable transmission arrives, classify A4 even if a merits label is visible; if no transmission arrives but a further extension is expressly communicated by then, classify A2; if neither a transmission nor a further extension is verified by then, classify A3. | ID | Mutually exclusive delivery state | Base structured weight | Observable classification fact | | A1 | Usable report issued on or before the stated expected date | 62% | Complete, readable, internally consistent transmission permits allegation-level merits review. | | A2 | Further expressly authorized extension | 20% | A verified communication invokes or states additional time before a usable report arrives. | | A3 | Late/no report without a further extension | 10% | No usable or un…

Source lines 19–52; approximately 493 words. Tables/matrices: | ID | Mutually exclusive delivery state | Base structured weight | Observable classification fact |; | Step | A1 usable by date | A2 extension | A3 late/no extension | A4 unusable | Reason |; | Delivery sensitivity set | A1 | A2 | A3 | A4 | Total |

Layer B — merits outcome conditional on a usable report

Denominator: only cases in which a usable report exists. These weights do not include delay, extension, corruption, redaction, or missing-material events. They therefore do not combine with Layer A weights. | ID | Mutually exclusive conditional merits outcome | Base structured weight | Low/base/high interpretation | | B1 | Broadly favorable | 12% | Multiple findings materially credit Cooper’s position or substantiate broad parts of the scoped case. | | B2 | Mixed/partial substantiation | 32% | Differentiated findings across the eight separable alleged actions. | | B3 | Factual concessions or mitigation-relevant findings without formal violation | 22% | Useful authenticated facts or process concerns, but no formal policy violation. | | B4 | Detailed adverse merits outcome | 15% | Complete allegation-level adverse reasoning and material rejection of Cooper’s account or nexus theory. |

Source lines 53–91; approximately 568 words. Tables/matrices: | ID | Mutually exclusive conditional merits outcome | Base structured weight | Low/base/high interpretation |; | Step/factor | B1 | B2 | B3 | B4 | B5 | B6 | Directional logic |; | Prior/result set | B1 | B2 | B3 | B4 | B5 | B6 | Total |

Layer C — nonexclusive operational overlays

These overlays may coexist with any Layer A or Layer B state and do not sum to 100%. They are structured planning weights or current-state flags, not a third mutually exclusive distribution. | Overlay | Structured weight / status | Planning use | First fact that changes the assessment | | Material omission | 34% | Prepare an item-specific omission/consideration log; never equate noncitation with nonconsideration. | Complete allegation/evidence mapping shows a material item addressed, discounted, or truly absent. | | Material redaction affecting review | 12% | Preserve redaction notice and identify the exact blocked function. | Redaction key, corrected copy, or confirmation that review remains possible. | | Incomplete evidence/interview list | 22% | Compare the stated list to proven submissions and expected sources. | A complete list or written clarification. | | Deadline ambiguity | 45%…

Source lines 92–108; approximately 262 words. Tables/matrices: | Overlay | Structured weight / status | Planning use | First fact that changes the assessment |

3. Evidence model by allegation and respondent

The exact allegation descriptions below are controlled by 01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 1 (allegations 1 and 2(a)) and p. 2 (allegations 2(b)(i)–(iii), 3(a), and 3(b)(i)–(ii)). “Program position” entries are positions shown in 01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, especially pp. 5–9, and are not adopted as established fact.

Source lines 109–112; approximately 54 words.

A1 — James Bisley / NEURO M203 midterm accommodation

Scope and element: formally scoped allegation that Bisley failed to accommodate Cooper’s disability when Cooper asked to take the NEURO M203 midterm later. Source-established procedural fact. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 1, allegation 1.) - Direct case evidence: the actual messages, timing, course arrangements, and any CAE documentation identified in the case compilations; the program response says the request came after the examination began and that a later sitting was allowed. That is a respondent/program position, not a resolved fact. (01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, pp. 7–8, section 3.2 and the August 14 response.) - Cooper’s account: disability-related executive-function effects and a request for flexibility were material to the course event. Complainant account. - Upward factors: contemporaneous message timing; any…

Source lines 113–127; approximately 321 words.

A2 — Carrie Bearden / declined primary mentorship

Scope and element: formally scoped allegation that Bearden discriminated by declining to become Cooper’s primary mentor. Source-established procedural fact. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 1, allegation 2(a).) - Direct/circumstantial evidence: rotation communications, expectations, work product, timing, comparator or standard-practice evidence, and the reason Bearden gave. - Cooper’s account: the decision was affected by disability-linked expectations or unsupported barriers. Complainant account. - Program/respondent position: mentor selection is individualized and performance/fit based; the DGE response disputes discriminatory causation. Respondent/program position. (01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, pp. 6–8, responses concerning the fifth rotation, primary mentorship, and overall degree progress.) - Upward factors: contempor…

Source lines 128–142; approximately 260 words.

A3 — Carrie Bearden / highlighted unmet expectations and missing skills

Scope and element: formally scoped harassment allegation concerning statements that Cooper had not met expectations or lacked required skills. Source-established procedural fact. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 2, allegation 2(b)(i).) - Evidence function: exact words, audience, repetition, context, relation to academic evaluation, and disability nexus are load-bearing. A transcript proves what Cooper said in interview, not necessarily what occurred. - Upward factors: repeated disability-linked disparagement, humiliating context, corroborating recipients, departure from ordinary feedback, or effect on access. - Strongest defense / downward factors: accurate and neutrally delivered academic feedback; isolated communication; no disability nexus; legitimate evaluative context. - Evidentiary gap: the exact words, recipients, frequency, surrounding academic c…

Source lines 143–154; approximately 175 words.

A4 — Carrie Bearden / denial that she had considered serving as primary mentor

Scope and element: formally scoped harassment allegation that Bearden denied she had considered serving as Cooper’s primary faculty mentor toward the end of his fifth rotation. Source-established procedural fact. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 2, allegation 2(b)(ii).) - Evidence: rotation terms, mentor availability, timing, communications, reason for denial, practice for other students, and any disability-linked language. - Program position: Cooper had already received an exceptional fifth rotation and still had insufficient degree progress. Respondent/program position. (01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, p. 8, response concerning five rotations and insufficient degree progress.) - Strongest defense / downward factors: documented neutral rotation or mentor requirements, consistent treatment, and a stable nondiscriminatory expl…

Source lines 155–166; approximately 205 words.

A5 — Carrie Bearden / email to Felix Schweizer

Scope and element: formally scoped harassment allegation concerning the email phrase reproduced in the NOI: “I assume you’re not talking about [ideas] that would allow [Cooper] to stay in NSIDP?” Source-established allegation text, not a finding. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 2, allegation 2(b)(iii); program-response context at 01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, pp. 5–6.) - Upward factors: authentic email, disability-linked surrounding context, evidence of exclusionary intent, and material effect. - Strongest defense / downward factors: legitimate discussion of academic options; ambiguous context; lack of disability nexus; no actionable effect. - Evidentiary gap: the full native email chain, surrounding discussion, intended referent, and any concrete decision effect have not been established in this pre-report record. - Likel…

Source lines 167–176; approximately 166 words.

A6 — Felix Schweizer / recommendation of academic disqualification

Scope and element: formally scoped allegation that Schweizer discriminated by recommending academic disqualification. Source-established procedural fact. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 2, allegation 3(a).) - Direct evidence: recommendation, academic-plan record, stated reasons, timing, accommodation record, mentor/rotation/course facts, and evidence of consistency or pretext. - Strongest defense / program position: insufficient overall degree progress and failure to satisfy personalized benchmarks, including failure to secure a mentor, supported the recommendation; it was not solely based on five rotations. Respondent/program position. (01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, pp. 5 and 8, responses concerning the Academic Plan, mentor requirement, and overall degree progress.) - Upward factors: material inaccuracies, inconsistent r…

Source lines 177–189; approximately 235 words.

A7 — Felix Schweizer / Ophoff statement

Scope and element: formally scoped harassment allegation that Schweizer relayed Roel Ophoff’s opinion that Cooper was not capable of completing a Ph.D. Source-established procedural fact. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 2, allegation 3(b)(i).) - Evidence: exact words, source, audience, purpose, repetition, accuracy, disability nexus, and effect. - Upward factors: corroboration; disability-linked or stigmatizing context; use in decision-making; unnecessary repetition. - Strongest defense / downward factors: legitimate academic feedback; accurate relay for advising; no disability nexus; one communication. - Evidentiary gap: the original speaker’s exact words, Schweizer’s precise wording, the audience, purpose, repetition, and any decision use remain unresolved. - DGE mitigation utility: medium if it shaped placement or evaluation; greater if connected to…

Source lines 190–199; approximately 127 words.

A8 — Felix Schweizer / “internalized self-loathing” article remark

Scope and element: formally scoped harassment allegation concerning Schweizer’s remark about an article on “internalized self-loathing.” Source-established procedural fact. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 2, allegation 3(b)(ii).) - Evidence: exact remark, article, setting, relationship to disability, audience, and effect. - Upward factors: direct protected-status linkage, corroboration, repeated conduct, or material exclusion. - Strongest defense / downward factors: ambiguous or unrelated academic discussion, no disability nexus, isolated comment. - Evidentiary gap: the exact remark, article, setting, audience, repetition, and relationship—if any—to disability or an academic decision remain report-dependent or disputed. - DGE mitigation utility: lower than the disqualification and mentor issues unless the report connects it to climate or performance.

Source lines 200–209; approximately 122 words.

4. Outside-formal-scope actor and theory map

The NOI records several matters outside formal scope, including conduct attributed to Leanna Hernandez, Roel Ophoff, Addison Wightman, Jenny Lee, and Patty Violi. This is a scope determination, not a merits finding. (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, pp. 2–3, “Allegations Not Under Investigation.”) CRO’s April 20 response states that evidence, witnesses, and theories presented would be taken into consideration and the ultimate report would reflect this; it does not promise a separate finding on every item. (01_CASE_RECORD/04_CRO_NOI_Objections_and_2026-04-20_Response.md, April 20 CRO response, lines 332–334.) | Actor/item | Formal status | Proper use on receipt | Improper inference to avoid | | Hernandez mentor decision/personality concern | Outside scope / untimeliness per NOI | Check whether used as chronology, comparator context, or background and whether…

Source lines 210–221; approximately 273 words. Tables/matrices: | Actor/item | Formal status | Proper use on receipt | Improper inference to avoid |

5. Conditional element-level forecasts

These are structured subjective weights conditional on receipt of a complete, usable report. They are nonexclusive, need not sum to 100%, are not measured base rates, and must not be added to Layer B or Layer C. “Low” and “High” are reasonable sensitivity judgments, not statistical confidence limits. Each row starts from a qualitative judgment about how central and documentable the issue is, then moves up for the listed supporting factors and down for the listed

Source lines 222–266; approximately 1,767 words. Tables/matrices: | Required element-level estimate | Starting judgment and adjustment logic | Low | Base | High | Upward / supporting factors | Downward / contrary factors | Confirmers / falsifiers |

6. Likely report architecture

Verify the actual headings rather than forcing this structure onto the report. 1. Authority, policy version, and standard of proof. Check the exact version and conduct-date analysis; do not assume the current UC policy automatically governs earlier conduct. 2. Procedural history and scope. Compare to every NOI allegation, respondent, exclusion, and April 20 statement. 3. Methodology and evidence reviewed. Inventory interviewees, documents, unavailable materials, redactions, and limitations. 4. Chronology/background. Separate established dates from party accounts. 5. Allegation-specific evidence summaries. Track complainant account, respondent explanation, witness/evidence material, and disputed facts.

Source lines 267–281; approximately 162 words.

7. Anticipated wording patterns — paraphrases only

The following are planning paraphrases, not quotations from the future report: - “The evidence is insufficient to establish the required nexus, even though the communication could have been handled more effectively.” - “The investigator credits parts of each account but finds the contemporaneous record more persuasive on the stated academic reason.” - “The program had legitimate academic concerns, but the accommodation dialogue was incomplete or delayed.” - “The matter is outside formal scope but is considered as background or context.” - “A witness or document was cumulative, unavailable, or not necessary to resolve the allegation.”

Source lines 282–295; approximately 137 words.

8. Credibility, causation, harm, and remedy treatment to audit

Structural heading introducing subordinate content.

Source lines 296–297; approximately 0 words.

Credibility

Check whether the report applies consistent criteria to all accounts; distinguishes lack of recollection from contradiction; addresses contemporaneous documentation; explains treatment of corroboration; and avoids equating academic rank with credibility. A disagreement is not itself bias. A credibility objection should identify the exact statement, competing source, and why the difference was material.

Source lines 298–301; approximately 52 words.

Causation

For each finding, isolate the causal formulation actually used. Academic difficulty following disability notice does not alone establish discrimination; a legitimate academic reason does not alone disprove a contributing discriminatory factor. Preserve any authenticated chronology, shifting rationale, comparator evidence, or decisionmaker knowledge.

Source lines 302–305; approximately 42 words.

Harm

Separate formal-policy harm from DGE mitigation. Potential effects include course performance, rotation completion, ability to secure a mentor, M203 timing, funding, placement, program status, and alternative-degree pathways. State each only to the extent supported by a cited source or the future report.

Source lines 306–309; approximately 42 words.

Remedy

Separate: (1) what CRO may recommend; (2) what DGE, Graduate Dean, CDP, the program, CAE, or another office may implement; and (3) what may only be requested as a referral or negotiated resolution. The report’s silence on a remedy is not proof that another authorized office lacks power.

Source lines 310–313; approximately 48 words.

9. High-value favorable facts under adverse outcomes

Even if no allegation is substantiated, immediately extract whether the report confirms: 1. disability status or University notice; 2. requests for accommodation or flexibility; 3. timing and content of the M203 request and response; 4. rotation expectations, fifth-rotation permission, and mentor-search chronology; 5. decisionmakers’ knowledge of disability-related circumstances;

Source lines 314–332; approximately 119 words.

10. DGE utility across the eight operational playbook modules

The S1–S8 labels below are deployment modules from Artifact 07. They are not one probability denominator: S1–S6 map primarily to Layer B, S7 to Layer A4, and S8 to Layer A3. | Scenario | DGE use | | S1 broad favorable | Lead with exact findings linking disability, notice, University response, and academic effects; request the DGE completion/clock status in writing. | | S2 mixed partial | Crosswalk each substantiated and nonsubstantiated factual finding; explain why mitigation does not require every allegation to be substantiated. | | S3 concessions / no violation | Use authenticated facts and process weaknesses; explicitly separate the broader DGE mitigation test from the policy-violation result. | | S4 detailed adverse | Identify any undisputed disability, notice, timing, or academic-effect facts; answer adverse findings narrowly and preserve record objections. |

Source lines 333–347; approximately 203 words. Tables/matrices: | Scenario | DGE use |

11. Unsupported propositions rejected

Unsupported proposition rejected: senior review, delay, or extension proves the report will be favorable or adverse. - Unsupported proposition rejected: senior review proves intentional institutional manipulation or any person’s motive. - Unsupported proposition rejected: an upload index proves CRO reviewed every underlying exhibit. - Unsupported proposition rejected: a witness/evidence proffer proves the witness was interviewed or testified as anticipated. - Unsupported proposition rejected: noncitation proves nonconsideration. - Unsupported proposition rejected: every factual inconsistency is a credibility failure or policy violation.

Source lines 348–361; approximately 155 words.

12. Receipt-time confirmers and falsifiers

Within the first four hours, update the forecast using only observable data: - exact disposition of every NOI allegation; - policy version and causation test; - complete evidence/interview list; - whether the report separately addresses scoped and contextual material; - credibility findings and cited support;

Source lines 362–378; approximately 117 words.

13. Citation key

NOI allegation map: 01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, p. 1 (allegations 1 and 2(a)); p. 2 (2(b)(i)–(iii), 3(a), 3(b)(i)–(ii)); pp. 2–3 (“Allegations Not Under Investigation”). - CRO scope response: 01_CASE_RECORD/04_CRO_NOI_Objections_and_2026-04-20_Response.md, April 20 CRO response, lines 332–334. - Extension: 01_CASE_RECORD/02_CRO_Extension_Notice_2026-06-24_to_2026-06-25.pdf, p. 2. - Program response record: 01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, p. 5 (Academic Plan, mentor, and overall-progress response); pp. 5–7 (Bearden rotation/email and mentor-response context); pp. 7–8 (M203 timing and response); p. 8 (five-rotation and overall-progress response). - DGE/Bailey correspondence: 01_CASE_RECORD/10_DGE_Update_2026-04-24_to_2026-05-04.pdf, p. 2. - DGE standard: 01_CASE_RECORD/06_UCLA_Standards_and_Procedures_for_Graduate_Study.pdf, p…

Source lines 379–388; approximately 182 words.

05_REPORT_RECEIPT_WAR_ROOM.md

319 lines; 1,864 words; 25 indexed headings/sections.

Report-Receipt War Room

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Activation event: receipt of any email, portal notice, link, report, appendix, corrective transmission, or message stating that the CRO investigation report has issued. Non-action boundary: this is an internal checklist. Do not send, submit, acknowledge, download from a private account, or alter any external record unless Cooper separately chooses and authorizes that action.

Source lines 1–7; approximately 69 words.

Roles

| Placeholder | Responsibility | | [COOPER] | Owns route and submission decisions; confirms factual accuracy. | | [INTAKE_LEAD] | Preserves the transmission and creates immutable originals. | | [DEADLINE_LEAD] | Records the exact transmittal facts and runs both counting assumptions. | | [REPORT_LEAD] | Decomposes findings, evidence, omissions, and contradictions. | | [DGE_LEAD] | Builds the mitigation crosswalk and tracks the unresolved interlock. |

Source lines 8–21; approximately 93 words. Tables/matrices: | Placeholder | Responsibility |

Required intake folder

Create a new case-event folder without modifying the received material: [YYYYMMDD]_[HHMMSS-PDT]_CRO_REPORT_RECEIPT/ 00_NATIVE_TRANSMISSION/ 01_IMMUTABLE_ORIGINALS/ 02_HASHES_AND_METADATA/

Source lines 22–39; approximately 25 words.

First 15 minutes

| Minute | Owner | Exact task | Named output | | 0–2 | [INTAKE_LEAD] | Record the device-displayed receipt time, time zone, sender display, subject, account, and delivery channel. Do not rely on memory. | 02_HASHES_AND_METADATA/00_RECEIPT_EVENT_LOG.md | | 0–5 | [INTAKE_LEAD] | Preserve the native email/message, including full headers where available, plus original attachments and linked-file notices. Save originals without opening and resaving them. | 00_NATIVE_TRANSMISSION/[native export]; 01_IMMUTABLE_ORIGINALS/ | | 3–7 | [INTAKE_LEAD] | Capture a full-screen screenshot showing the transmittal, timestamp, attachment list, and account/channel; capture the portal page if applicable without changing status fields. | 00_NATIVE_TRANSMISSION/TRANSMITTAL_SCREEN_001.png | | 5–10 | [SECOND_CHECKER] | Hash every native file with SHA-256; record filename, bytes, hash, source, and acquisition tim…

Source lines 40–55; approximately 270 words. Tables/matrices: | Minute | Owner | Exact task | Named output |

First hour

Structural heading introducing subordinate content.

Source lines 56–57; approximately 0 words.

Transmission and completeness verification

1. Compare the transmittal subject/body, attachment names, file count, report title page, footer, pagination, appendices, evidence list, and redaction notice. 2. Record whether the report states an issuance date and whether that matches the transmission date. Attachment B defines issuance as the date of transmission; the sources do not resolve incomplete transmission or anchor-day counting. 3. Check continuous pagination, blank pages, missing appendices, broken bookmarks, clipped OCR, signatures, and version identifiers. 4. Render representative pages—title, findings, recommendations, appendices, redactions—and compare to extracted text. 5. Preserve any later corrected transmission as a new event. Never overwrite the first transmission. Outputs:

Source lines 58–71; approximately 111 words.

Rights and deadline verification

[DEADLINE_LEAD] records: - exact transmittal date/time/time zone; - any stated issuance date; - exact quoted hearing/comments language; - stated recipient/method—without inventing an address or portal; - any stated extension;

Source lines 72–94; approximately 77 words.

First-pass disposition map

Create one row for every NOI allegation and one row for every formal-scope exclusion: | Field | Required entry | | NOI allegation/respondent | Exact NOI language | | Report disposition | Exact finding, [REPORT_PAGE], and short quotation | | Factual findings | Favorable, adverse, neutral, unresolved | | Policy version/test | Exact report text |

Source lines 95–112; approximately 77 words. Tables/matrices: | Field | Required entry |

First four hours

Structural heading introducing subordinate content.

Source lines 113–114; approximately 0 words.

Report decomposition

[REPORT_LEAD] creates: - 04_REPORT_DECOMPOSITION/01_REPORT_SECTION_OUTLINE.md - 04_REPORT_DECOMPOSITION/02_EXACT_FINDINGS_EXTRACT.md - 04_REPORT_DECOMPOSITION/03_FAVORABLE_FACTS_LEDGER.xlsx - 04_REPORT_DECOMPOSITION/04_ADVERSE_FINDINGS_LEDGER.xlsx - 04_REPORT_DECOMPOSITION/05_CREDIBILITY_CAUSATION_HARM_MAP.xlsx

Source lines 115–143; approximately 190 words. Tables/matrices: | Report page | Section | Allegation | Asserted fact | Finding | Evidence cited | Evidence credited | Evidence discounted | Credibility determination | Policy element | Causation analysis | Harm analysis | Omitted evide…

Expected-record comparison

Copy Artifact 08 into the receipt folder and code each baseline item as: - mentioned; - considered but not cited; - expressly discounted; - out of scope; - cumulative;

Source lines 144–165; approximately 84 words.

Preliminary route screen

Run Artifact 06 with verified report facts. Record: - any hard hearing trigger; - whether written comments can preserve the issue; - new fact or credibility dispute; - need for live testimony or cross-examination; - favorable findings that should not be placed at risk unnecessarily;

Source lines 166–183; approximately 71 words.

First 24 hours

Structural heading introducing subordinate content.

Source lines 184–185; approximately 0 words.

Independent second read

[SECOND_CHECKER] independently: 1. verifies hashes and page count; 2. checks every NOI allegation against the report; 3. recomputes the earliest plausible deadline under Assumptions A and B; 4. checks that sensitivity dates are not treated as confirmed closures; 5. samples every load-bearing quotation against the page image;

Source lines 186–198; approximately 61 words.

Draft the route-neutral preservation set

Prepare, but do not send: - 08_DRAFT_SUBMISSIONS/01_REPORT_RECEIPT_ACKNOWLEDGMENT_MINIMAL.md - 08_DRAFT_SUBMISSIONS/02_MISSING_MATERIALS_OR_CLARIFICATION_REQUEST.md - 08_DRAFT_SUBMISSIONS/03_ISSUANCE_AND_DEADLINE_CONFIRMATION_REQUEST.md - 08_DRAFT_SUBMISSIONS/04_GOOD_CAUSE_EXTENSION_REQUEST.md if an observable trigger exists - 08_DRAFT_SUBMISSIONS/05_MINIMAL_HEARING_REQUEST.md

Source lines 199–212; approximately 58 words.

DGE/CDP sequence

[DGE_LEAD]: 1. records whether DGE received “Investigation Materials,” if known; 2. preserves source silence about when the investigatory process is “completed”; 3. prepares a notice that does not concede the trigger; 4. populates Artifact 10 with exact report facts; 5. separates formal substantiation from the Standards test: “substantive mitigating circumstances that could have affected academic performance”;

Source lines 213–231; approximately 91 words.

Counsel-review packet

If an Artifact 17 trigger is met, prepare: - 07_COUNSEL_REVIEW/00_COUNSEL_HANDOFF_MEMORANDUM.md - native transmittal and hash inventory; - report and evidence index; - deadline worksheet; - route scorecard;

Source lines 232–247; approximately 54 words.

Days two through five

Structural heading introducing subordinate content.

Source lines 248–249; approximately 0 words.

Day two

Complete allegation-by-allegation source checking. - Resolve every apparent report quotation against page images. - Classify every expected-record item without equating silence with nonconsideration. - Populate both hearing and comments drafts far enough to compare them. - Obtain Cooper’s factual corrections. - Send nothing merely because a draft exists.

Source lines 250–264; approximately 54 words.

Day three

Convene the internal route review using Artifact 06. - Record hard triggers, score, nonquantifiable factors, and counsel questions. - Choose a provisional route only after checking the actual transmittal method and deadline. - Finalize the DGE crosswalk and separate report-dependent facts from contested Cooper assertions. Named outputs: - 05_DEADLINES_AND_ROUTE/05_ROUTE_DECISION_RECORD.md

Source lines 265–276; approximately 50 words.

Day four

Red-team the chosen route against the strongest University response. - Check whether a narrow correction, comments submission, hearing request, or combined protective sequence is actually supported by the text. - Confirm the requested remedy is directed to an office with authority or expressly framed as a referral/negotiation request. - Freeze a candidate submission and create a redline from the approved prior version. Named outputs: - 08_DRAFT_SUBMISSIONS/10_RED_TEAM_AND_COUNTERARGUMENT_LOG.md

Source lines 277–289; approximately 74 words.

Day five or earlier internal cutoff

Perform final citation, confidentiality, privilege, accessibility, attachment, and deadline checks. - Recompute the due date from the preserved transmittal. - Confirm the submission target is at least one University business day before the earliest plausible date unless a documented reason prevents it. - Have [SECOND_CHECKER] verify the recipient/method from the actual transmittal. - Cooper alone approves whether and what to submit. Named outputs:

Source lines 290–303; approximately 80 words.

Decision controls

Structural heading introducing subordinate content.

Source lines 304–305; approximately 0 words.

Never do

Do not edit or overwrite the native email, report, appendix, or first hash list. - Do not call the report date an actual deadline without verifying the transmittal. - Do not count observed holidays as confirmed campus closures. - Do not describe an unextended sequence as an absolute maximum. - Do not state that DGE “completion” occurs at any particular milestone absent confirmation. - Do not invent recipient addresses, portal names, report quotations, witness testimony, or missing-evidence conclusions.

Source lines 306–316; approximately 116 words.

Completion definition for the war room

The receipt response is operationally complete when: native transmission and originals are preserved; hashes and metadata are independently verified; the report opens and its completeness status is recorded; every NOI allegation is mapped; primary A/B dates and sensitivity dates are separated; favorable/adverse/omission/contradiction/new-evidence logs exist; a route decision record states its factual basis and uncertainties; DGE sequencing is preserved without inventing the completion trigger; counsel triggers are assessed; and any authorized submission has its own immutable sent-item and receipt record.

Source lines 317–319; approximately 84 words.

07_EIGHT_COMPLETE_SCENARIO_PLAYBOOKS.md

600 lines; 6,916 words; 171 indexed headings/sections.

Eight Complete Scenario Playbooks

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION V2 repair reference date: July 23, 2026 (PDT); the closed case-record cutoff remains July 22, 2026 Use: select the operational module that matches the verified event and, where needed, pair it with a nonexclusive Layer C overlay from Artifact 04. Verify the actual report/transmittal before using any route or draft. These playbooks are decision support and drafts for Cooper’s review; nothing is sent or submitted.

Source lines 1–7; approximately 82 words.

Classification rule

These eight scenarios are operational response modules, not one homogeneous probability universe. Artifact 04 controls the denominators: Layer A covers mutually exclusive delivery/timing states; Layer B covers mutually exclusive merits outcomes conditional on a usable report; Layer C covers nonexclusive operational overlays. Scenarios 1–6 map principally to Layer B only after a report is complete and usable. Scenario 7 maps to Layer A4 when a transmission defect prevents reliable merits analysis. Scenario 8 maps to Layer A3 only when the verified record contains neither a report nor a further extension after July 31. A material omission in an otherwise usable adverse report may invoke Scenario 5 and a Layer C omission overlay; a defect that makes merits review unreliable invokes Scenar… > INCOMPLETE-TRANSMISSION HARD STOP: Do not make a final merits-route election from an incomplete, un…

Source lines 8–13; approximately 201 words.

Scenario 1 — Broad favorable report

Structural heading introducing subordinate content.

Source lines 14–15; approximately 0 words.

1. Expected characteristics

The report substantiates several or most formally scoped allegations, credits material parts of Cooper’s account, identifies a disability nexus or accommodation failure, and may recommend corrective action. It may still reject particular allegations, limit scope, or reserve implementation to another office.

Source lines 16–18; approximately 41 words.

2. First verification

Confirm every allegation-specific disposition, the policy version and standard, exact factual findings, credibility findings, remedy language, appendices, redactions, and whether the transmittal makes any hearing/comments deadline run. A favorable overall label never substitutes for page-by-page verification.

Source lines 19–21; approximately 37 words.

3. Principal objective

Preserve favorable findings, translate them into implementable academic and protective relief, and avoid unnecessarily reopening settled facts while correcting any material omission that limits DGE/CDP use.

Source lines 22–24; approximately 27 words.

4. What not to contest unnecessarily

Do not contest harmless wording merely to obtain a perfect narrative. Do not demand discipline or relief from CRO that only an academic or personnel office can implement. Do not assume that broad substantiation automatically reverses disqualification.

Source lines 25–27; approximately 37 words.

5. Favorable findings to preserve

Create an exact-quotation schedule for each substantiated allegation; disability/notice facts; accommodation or interactive-process weaknesses; decisionmaker knowledge; causation; academic effects; credibility findings; and any recommendation. Mark page, element, DGE use, and implementation office.

Source lines 28–30; approximately 33 words.

6. Damaging findings to address

Identify any unsubstantiated allegation, adverse credibility language, academic-performance finding, scope exclusion, mitigation limitation, or remedy reservation. Answer only what affects route, DGE, remedy, or future record integrity.

Source lines 31–33; approximately 27 words.

7. Hearing/comments presumptive route

Presumptive written comments or narrow clarification if the report is complete and the dispute is documentary. A hearing remains available for a material adverse credibility or factual error, but favorable findings should be placed at risk only after route-specific counsel analysis.

Source lines 34–36; approximately 41 words.

8. Exact route-changing triggers

Shift toward hearing if an adverse conclusion material to relief turns on disputed credibility, a scoped allegation is omitted, a necessary witness was materially ignored, or the report introduces a new adverse fact that written comments cannot fairly resolve. Shift toward comments if favorable findings are robust and remaining disputes are textual.

Source lines 37–39; approximately 52 words.

9. Evidence and witness priorities

Prioritize the native report, exact findings, evidence/interview list, M203 messages, rotation/mentor communications, Bearden email, academic-plan/disqualification record, and authenticated program responses. Confirm anticipated witness testimony before listing it.

Source lines 40–42; approximately 30 words.

10. CRO response strategy

Acknowledge receipt only if Cooper approves; preserve favorable findings expressly; provide a narrow page-cited correction/omission table; ask the proper office to identify implementation and any deadline ambiguity. Do not dilute strong findings with peripheral objections.

Source lines 43–45; approximately 36 words.

11. DGE notification strategy

Give DGE a rights-preserving notice that identifies the report/transmittal without conceding which event completes the investigatory process. Ask what Investigation Materials DGE received and what date, and request written confirmation before any clock is treated as running.

Source lines 46–48; approximately 38 words.

12. DGE mitigation framing

Lead with exact favorable findings and map each to the exact standard: substantive mitigating circumstances that could have affected academic performance. Show notice, timing, and effects on M203, rotations, mentor placement, overall progress, funding, and alternatives; formal substantiation is powerful but not the only relevant material.

Source lines 49–51; approximately 46 words.

13. CDP strategy

Request referral if DGE determines possible substantive mitigation, preserve the written-request right to a personal appearance, and present a viable academic remedy with safeguards. Do not assume the public sources answer appearance mechanics or CDP timing.

Source lines 52–54; approximately 36 words.

14. Remedy ladder

First: corrected academic review and status protection. Second: accommodated reinstatement or a viable supervised path. Third: course/rotation/mentor relief, future safeguards, funding/insurance bridge, and record correction. Alternatives: cognate master’s, facilitated transfer, or negotiated nonmonetary resolution.

Source lines 55–57; approximately 37 words.

15. Risks and tradeoffs

A hearing can delay implementation or reopen credibility; an overbroad remedy demand can obscure a strong record; DGE may still emphasize academic judgment; a favorable CRO report may not identify the office empowered to deliver relief.

Source lines 58–60; approximately 36 words.

16. External-review trigger

Trigger counsel review for remedy authority, any settlement/release, imminent status/funding loss, contested finality, or a need to preserve an external deadline. Consultation is not a filing.

Source lines 61–63; approximately 28 words.

17. First-day actions

Preserve native transmission and hashes; run both deadline assumptions; extract every favorable and adverse finding; verify completeness; populate Artifacts 08, 10, and 13; prepare a narrow receipt acknowledgment and DGE sequencing notice.

Source lines 64–66; approximately 32 words.

18. First-week actions

Complete source checking; choose comments/hearing route; finalize DGE crosswalk; obtain counsel review if triggered; develop an authority-matched remedy package; create immutable final drafts and second-check deadlines before Cooper decides whether to submit.

Source lines 67–69; approximately 33 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Receipt of CRO investigation report — rights and implementation reserved I acknowledge receipt on [TRANSMITTAL_TIMESTAMP] of the CRO investigation report dated [REPORT_DATE]. I am reviewing the complete transmission, including its findings, recommendations, attachments, and stated deadlines. I preserve the favorable findings at [REPORT_PAGES] and reserve the ability to identify any material correction, omission, or implementation question after that review. This acknowledgment does not concede a deadline computation, the completeness of the transmission, or the event that completes the investigatory process for the separate DGE appeal. Please confirm, if not already stated in the transmittal, the operative issuance date, submission method, and materials transmitted to DGE. No response beyond confirmation is requested at this time.

Source lines 70–78; approximately 121 words.

20. Complete full-submission architecture

Caption and preservation statement; verified transmittal facts; concise disposition summary; schedule of exact favorable findings; narrow correction/omission table; route election and textual basis; DGE mitigation crosswalk; authority-matched remedy request; attachments/index; certification that quoted report text was checked against page images; reservations limited to identified source silence. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 79–86; approximately 103 words.

Scenario 2 — Mixed partial-substantiation report

Structural heading introducing subordinate content.

Source lines 87–88; approximately 0 words.

1. Expected characteristics

The report substantiates one or more allegations, rejects others, and may credit overlapping facts while reaching different policy-element conclusions. Credibility and causation findings may vary by respondent and event.

Source lines 89–91; approximately 29 words.

2. First verification

Build a separate finding card for all eight discrete formally scoped alleged actions and every sub-incident. Check whether a single fact is being reused across allegations, whether partial substantiation is allegation- or element-specific, and whether remedy language matches the actual finding.

Source lines 92–94; approximately 41 words.

3. Principal objective

Protect substantiated findings and high-value factual concessions while correcting material adverse errors and presenting a coherent DGE theory that does not depend on winning every CRO allegation.

Source lines 95–97; approximately 27 words.

4. What not to contest unnecessarily

Do not treat the report as globally favorable or adverse. Do not contest accurate adverse details that are immaterial to relief. Do not imply that a mixed result is internally inconsistent merely because different elements were decided differently.

Source lines 98–100; approximately 38 words.

5. Favorable findings to preserve

Preserve each substantiated element, authenticated communication, notice finding, timeline, credibility determination, and process weakness. Record how every favorable fact supports academic mitigation even if attached to an unsubstantiated allegation.

Source lines 101–103; approximately 29 words.

6. Damaging findings to address

Answer only adverse credibility, causation, academic-performance, comparator, scope, or evidence-weight findings that affect a requested remedy, hearing trigger, or DGE use. State the strongest program response before replying.

Source lines 104–106; approximately 28 words.

7. Hearing/comments presumptive route

Use Artifact 06. Written comments are presumptive where objections are documentary and favorable findings should remain stable; hearing analysis becomes strong where an adverse credibility determination or missing witness controls a major allegation.

Source lines 107–109; approximately 33 words.

8. Exact route-changing triggers

Hearing triggers include a material credibility split, reliance on a new rationale, or a scoped allegation with no reasoned disposition. Comments triggers include separable documentary errors, legal/textual disagreement, and no identified live-evidence value.

Source lines 110–112; approximately 34 words.

9. Evidence and witness priorities

Prioritize the report’s cited sources, contrary sources for each adverse finding, authentic messages, academic-plan documents, M203 timing, rotation benchmarks, mentor communications, program response pages 5–9, and witnesses whose noncumulative value can be confirmed.

Source lines 113–115; approximately 34 words.

10. CRO response strategy

Use a two-column approach: findings accepted and preserved; findings or analysis disputed with exact source and requested cure. Avoid asking CRO to revisit an uncontested favorable section.

Source lines 116–118; approximately 27 words.

11. DGE notification strategy

Notify DGE of the mixed outcome, state that the crosswalk will use report-authenticated facts from both substantiated and unsubstantiated allegations, and reserve the unresolved completion/clock question.

Source lines 119–121; approximately 27 words.

12. DGE mitigation framing

Explain that DGE’s possible-and-substantive mitigation standard is not coextensive with CRO’s violation elements. Map favorable facts, including those below a policy threshold, to specific academic components and address each contrary finding.

Source lines 122–124; approximately 31 words.

13. CDP strategy

Present a balanced record: exact favorable findings, adverse findings conceded or answered, and a feasible academic path. Request personal appearance in writing after referral and seek procedural confirmation without inventing mechanics.

Source lines 125–127; approximately 31 words.

14. Remedy ladder

Use modular relief: corrected review; targeted M203/rotation/mentor reassessment; neutral supervision; future accommodation safeguards; status/funding protection; alternative degree path if reinstatement is not feasible.

Source lines 128–130; approximately 26 words.

15. Risks and tradeoffs

Overreaching can make accurate partial findings look disputed; failure to answer a central adverse credibility finding can weaken DGE use; hearing could change favorable portions; comments may be inadequate for a genuinely testimonial dispute.

Source lines 131–133; approximately 34 words.

16. External-review trigger

Counsel review is triggered by waiver/finality uncertainty, a material new fact, serious version error, imminent status loss, or settlement terms. External-agency analysis remains held unless a live trigger is verified.

Source lines 134–136; approximately 31 words.

17. First-day actions

Preserve and hash; run deadlines; map all allegation outcomes; extract favorable/adverse facts; mark report pages; compare evidence list; populate scorecard; prepare DGE notice without conceding completion.

Source lines 137–139; approximately 27 words.

18. First-week actions

Complete a split-route memorandum, witness necessity analysis, comments and hearing alternatives, DGE crosswalk, remedy map, and counsel packet if needed. Freeze the approved candidate at least one business day before the earliest plausible date.

Source lines 140–142; approximately 34 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Receipt and review of mixed CRO findings I acknowledge receipt of the investigation report transmitted on [TRANSMITTAL_TIMESTAMP]. I preserve the findings at [FAVORABLE_REPORT_PAGES] and am reviewing the separate adverse findings and supporting record at [ADVERSE_REPORT_PAGES]. I will identify any material, page-specific correction or procedural election through the method stated in the transmittal. This message does not accept an unstated deadline computation or concede when the separate DGE investigatory process is complete. Please confirm any missing attachment, the operative submission method, and the date and contents of any Investigation Materials transmitted to DGE.

Source lines 143–151; approximately 100 words.

20. Complete full-submission architecture

Verified receipt/completeness; allegation-by-allegation outcomes; favorable-findings preservation; disputed-findings table; credibility/causation response; route rationale; DGE distinct-standard section; requested narrow and alternative relief; attachments; reservations. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 152–159; approximately 79 words.

Scenario 3 — Factual concessions / no formal violation

Structural heading introducing subordinate content.

Source lines 160–161; approximately 0 words.

1. Expected characteristics

The report does not substantiate a policy violation but authenticates useful facts: disability or notice, accommodation requests, program communications, timing, academic effects, or process weaknesses. It may describe conduct as concerning yet below the policy threshold.

Source lines 162–164; approximately 36 words.

2. First verification

Separate formal conclusions from factual findings and investigator observations. Confirm which facts are genuinely findings rather than recitations of Cooper’s account or a program position.

Source lines 165–167; approximately 25 words.

3. Principal objective

Preserve authenticated facts, correct any material analytical error, and reposition the report as mitigation evidence under DGE’s distinct standard without relitigating every CRO element.

Source lines 168–170; approximately 24 words.

4. What not to contest unnecessarily

Do not call a factual concession a substantiated violation. Do not claim that concerning conduct necessarily satisfies policy. Do not discard the report merely because the formal result is no violation.

Source lines 171–173; approximately 31 words.

5. Favorable findings to preserve

Extract every authenticated notice, request, timeline, quote, decision rationale, academic consequence, and process concern. Mark whether CRO adopted it, found it undisputed, or merely summarized it.

Source lines 174–176; approximately 26 words.

6. Damaging findings to address

Address adverse nexus, severity, causation, reasonableness, comparator, and credibility findings only to the extent they undermine the factual record or DGE theory.

Source lines 177–179; approximately 22 words.

7. Hearing/comments presumptive route

Presumptive written comments if the principal disagreement is how established facts satisfy policy text. Hearing analysis is warranted only if a material factual/credibility rejection could be changed by specific live evidence.

Source lines 180–182; approximately 32 words.

8. Exact route-changing triggers

Move toward hearing for an outcome-controlling credibility determination, demonstrable report error, missing scoped allegation, or material new adverse evidence. Stay with comments when facts are largely established and the disagreement is element weighting.

Source lines 183–185; approximately 33 words.

9. Evidence and witness priorities

Focus on primary communications and report-authenticated facts. Use the transcript only as Cooper’s recorded account, proffers only as anticipated evidence, and the upload index only to verify listed submission activity.

Source lines 186–188; approximately 30 words.

10. CRO response strategy

Preserve accepted facts, identify the smallest number of outcome-changing analytical errors, and request precise correction or clarification rather than a wholesale rewrite.

Source lines 189–191; approximately 22 words.

11. DGE notification strategy

Transmit a draft notice for Cooper’s approval explaining that no-violation does not answer whether substantive mitigating circumstances could have affected performance. Ask DGE to confirm receipt, materials, and clock without defining completion.

Source lines 192–194; approximately 32 words.

12. DGE mitigation framing

The core argument is distinct standards: DGE asks possibility and substantive academic effect, not whether every discrimination/harassment element was proven by a preponderance. Show how authenticated facts could have affected M203, rotations, mentor placement, progress, funding, or alternative pathways.

Source lines 195–197; approximately 40 words.

13. CDP strategy

Give CDP a candid no-violation result plus the favorable factual record, contrary evidence, and a feasible remedy. Avoid asking CDP to overturn CRO.

Source lines 198–200; approximately 23 words.

14. Remedy ladder

Prioritize corrected academic review using authenticated circumstances, prospective safeguards, neutral reassessment, and a viable degree path. Use referral language for remedies outside DGE authority.

Source lines 201–203; approximately 24 words.

15. Risks and tradeoffs

DGE may treat no violation as no mitigation unless the distinction is made precisely; aggressive CRO objections can obscure useful concessions; speculative causation can weaken a strong possible-effect argument.

Source lines 204–206; approximately 29 words.

16. External-review trigger

Seek counsel if the no-violation result rests on a policy-version question, disputed accommodation law, or creates a live filing deadline. Consultation remains distinct from an external filing.

Source lines 207–209; approximately 27 words.

17. First-day actions

Preserve, hash, verify no-violation findings allegation by allegation, extract concessions, run deadline assumptions, code source labels, and prepare the DGE distinct-standard notice.

Source lines 210–212; approximately 22 words.

18. First-week actions

Finalize concise comments if chosen; build the full mitigation crosswalk; present strongest contrary evidence and reply; develop corrected-review and alternative-degree remedies; complete counsel screen.

Source lines 213–215; approximately 24 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Preservation of report-established facts and DGE sequencing I acknowledge the report transmitted on [TRANSMITTAL_TIMESTAMP]. Although the report concludes [EXACT_FORMAL_RESULT], I preserve the report-established facts at [REPORT_PAGES], including [EXACT_FACTUAL_FINDINGS]. I am reviewing whether a page-specific written response is appropriate. For the separate academic appeal, those facts must be assessed under the Standards question whether substantive mitigating circumstances could have affected academic performance. Please confirm what Investigation Materials DGE received and the date DGE treats any applicable clock as beginning, without prejudice to the unresolved meaning of completion.

Source lines 216–224; approximately 94 words.

20. Complete full-submission architecture

Exact formal result; report-established facts versus party accounts; targeted analytical objections; favorable-fact preservation; DGE distinct standard and component-by-component crosswalk; contrary evidence/reply; requested corrected academic review; fallback relief; attachments and reservations. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 225–232; approximately 86 words.

Scenario 4 — Detailed adverse merits report

Structural heading introducing subordinate content.

Source lines 233–234; approximately 0 words.

1. Expected characteristics

The report rejects the formal allegations with developed credibility, causation, academic-judgment, accommodation, or comparator analysis and may adopt substantial parts of respondents’ explanations.

Source lines 235–237; approximately 23 words.

2. First verification

Check every adverse quotation against page images; identify the precise policy version, burden, credibility criteria, evidence list, contrary evidence treatment, and whether each formal allegation received a separate disposition.

Source lines 238–240; approximately 29 words.

3. Principal objective

Prevent demonstrable factual or methodological error from hardening into the record, preserve any undisputed mitigation facts, and make a disciplined route choice based on whether live evidence can materially improve the record.

Source lines 241–243; approximately 32 words.

4. What not to contest unnecessarily

Do not answer every unfavorable sentence. Do not accuse investigators or senior reviewers of motive. Do not treat disagreement as proof of bias. Do not list witnesses without confirmed testimony and noncumulative value.

Source lines 244–246; approximately 33 words.

5. Favorable findings to preserve

Even an adverse report may authenticate disability, notice, communications, M203 timing, fifth rotation, mentor search, academic reasons, and consequences. Extract these without relabeling rejected allegations as facts.

Source lines 247–249; approximately 27 words.

6. Damaging findings to address

Prioritize adverse credibility determinations, findings of complete accommodation, legitimate academic reasons, lack of comparator evidence, unmet benchmarks, and no disability nexus. For each, state exact source, contrary proof, materiality, and cure.

Source lines 250–252; approximately 31 words.

7. Hearing/comments presumptive route

Hearing analysis is strong where a material adverse result depends on testimony, credibility, a missing witness, or new evidence. Written comments remain appropriate for textual, documentary, or policy-version disputes with no live-evidence value.

Source lines 253–255; approximately 33 words.

8. Exact route-changing triggers

Hard triggers: misquotation, mistaken timeline, material new rationale, omitted scoped allegation, or a credibility finding that a confirmed witness could test. Comments presumption: complete documentary record and disputes about weight or legal standard.

Source lines 256–258; approximately 33 words.

9. Evidence and witness priorities

Use the smallest primary passages: native messages, academic plan, recommendation/decision, M203 timing, rotation benchmarks/work product, mentor communications, complete program response, and exact report citations. Treat Cooper’s syntheses as Tier 2.

Source lines 259–261; approximately 32 words.

10. CRO response strategy

Prepare a concise statement of errors, not a second case narrative. Each ground must identify finding, page, primary source, why material, requested hearing issue or correction, and favorable finding preserved.

Source lines 262–264; approximately 30 words.

11. DGE notification strategy

Notify DGE of the adverse outcome while reserving CRO route rights and the completion trigger. Ask DGE to identify received materials and avoid treating adverse merits as dispositive of its different mitigation standard.

Source lines 265–267; approximately 33 words.

12. DGE mitigation framing

Use authenticated undisputed facts and show possible substantive effects. Answer the strongest program grounds—academic plan, mentor, fifth rotation, M203, comparators, and accommodation—without asking DGE to reject legitimate standards wholesale.

Source lines 268–270; approximately 31 words.

13. CDP strategy

If referred, present a feasible, bounded path with safeguards and candidly address adverse credibility/academic findings. The presentation should demonstrate why mitigation remains possible and substantive, not reargue discrimination.

Source lines 271–273; approximately 29 words.

14. Remedy ladder

First seek a corrected/neutral academic review if a material error exists. Otherwise propose tailored status protection, alternative supervised path, course/rotation remedy, or cognate master’s/transfer support. Use negotiated resolution only with counsel review.

Source lines 274–276; approximately 35 words.

15. Risks and tradeoffs

A weak hearing can reinforce adverse credibility; a broad submission can obscure strong errors; DGE may give the report substantial weight; delay can affect status/funding; external deadlines may run independently.

Source lines 277–279; approximately 31 words.

16. External-review trigger

Immediate counsel trigger for material credibility hearing, version/retroactivity issue, imminent status loss, external deadline, or potential judicial/administrative preservation. No filing is authorized.

Source lines 280–282; approximately 24 words.

17. First-day actions

Preserve and hash; map allegations; identify hard triggers; run deadline A/B; extract undisputed mitigation facts; confirm witnesses; prepare minimal hearing and comments alternatives; build counsel issue list.

Source lines 283–285; approximately 28 words.

18. First-week actions

Finish grounds addendum, witness/exhibit necessity, comments fallback, DGE crosswalk, Bailey issue only if triggered, remedy options, red-team, and second-checker QA before Cooper chooses.

Source lines 286–288; approximately 24 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Receipt of CRO report and reservation of procedural election I acknowledge receipt of the report transmitted on [TRANSMITTAL_TIMESTAMP]. I am reviewing the adverse findings at [REPORT_PAGES], the evidence and credibility analysis, the completeness of the transmission, and the procedural options stated in the transmittal. I preserve all applicable rights and do not concede a deadline computation, completeness, or DGE completion milestone by this acknowledgment. Please confirm the operative issuance date and submission method if they are not explicit, and identify any attachment or evidence list that was intended to accompany the report.

Source lines 289–297; approximately 100 words.

20. Complete full-submission architecture

Receipt and timeliness; exact findings challenged; allegation-specific grounds; material factual errors; credibility and missing-witness grounds; policy/version grounds; evidence and witness necessity; favorable/undisputed facts preserved; remedy; DGE distinct-standard appendix; complete exhibit index; reservations. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 298–305; approximately 89 words.

Scenario 5 — Narrow or materially omissive adverse report

Structural heading introducing subordinate content.

Source lines 306–307; approximately 0 words.

1. Expected characteristics

The report is adverse but unusually narrow, does not visibly address a scoped allegation or material theory, compresses contrary evidence, or treats contextual actors/evidence without explaining their function.

Source lines 308–310; approximately 29 words.

2. First verification

Distinguish a genuinely omitted scoped allegation from concise treatment, cumulative evidence, an out-of-scope item, an item not actually submitted, or an unavailable underlying exhibit. Search the full report and appendices and obtain a second check.

Source lines 311–313; approximately 35 words.

3. Principal objective

Create a precise record of what is missing or contradicted, seek the narrowest timely cure, and preserve hearing/comments and DGE rights without asserting that silence proves nonconsideration.

Source lines 314–316; approximately 28 words.

4. What not to contest unnecessarily

Do not label every uncited exhibit an omission. Do not assert intentional narrowing. Do not demand findings on conduct the NOI expressly excluded. Do not allow a clarification request to consume the protective deadline.

Source lines 317–319; approximately 34 words.

5. Favorable findings to preserve

Preserve any express scope statement, evidence-list entry, authenticated fact, and finding that shows CRO had the item or considered the theory. These may support a focused clarification without alleging motive.

Source lines 320–322; approximately 30 words.

6. Damaging findings to address

Identify each adverse conclusion whose reasoning cannot be followed, each scoped allegation without a disposition, each material contrary source not addressed, and each new rationale. Code treatment using Artifact 08’s definitions.

Source lines 323–325; approximately 31 words.

7. Hearing/comments presumptive route

First seek missing materials/clarification and a good-cause extension if warranted; simultaneously protect the earliest plausible route deadline. Hearing becomes more likely if cure is denied and the omission affects a material factual/credibility issue.

Source lines 326–328; approximately 35 words.

8. Exact route-changing triggers

Hard trigger: no identifiable disposition of a scoped allegation after complete review. Other triggers: evidence list/report mismatch, broken appendix, material new basis, or inability to understand an outcome. Comments may suffice for a narrow documentary omission cured by addendum.

Source lines 329–331; approximately 40 words.

9. Evidence and witness priorities

NOI allegation map, April 20 CRO response, complete report search log, evidence/upload inventories, underlying submitted exhibits where actually available, transmittal, page/appendix inventory, and primary contrary sources.

Source lines 332–334; approximately 28 words.

10. CRO response strategy

Use an itemized table: expected item; actual report treatment; status code; source proving submission; materiality; narrow requested action. Ask whether the item was considered and request correction/clarification without presuming the answer.

Source lines 335–337; approximately 32 words.

11. DGE notification strategy

Tell DGE the transmission is under a documented completeness/clarification review; ask what DGE received and whether any clock is considered running; do not assert that an incomplete report cannot be Investigation Materials absent source text.

Source lines 338–340; approximately 36 words.

12. DGE mitigation framing

Provide authenticated existing facts and mark omitted/report-dependent fields. Explain that DGE should not infer no mitigation from report silence and should confirm the complete materials it will review.

Source lines 341–343; approximately 29 words.

13. CDP strategy

If referral proceeds, include the omission-status table and request that party positions remain labeled. Use the personal appearance to explain material missing context, not to enlarge CRO scope.

Source lines 344–346; approximately 28 words.

14. Remedy ladder

Narrow cure first: complete transmission, addendum, allegation disposition, corrected evidence list, or clarified rationale. Broader fallback: hearing, corrected academic review, or record annotation if material reliance persists.

Source lines 347–349; approximately 27 words.

15. Risks and tradeoffs

Overclaiming omission can damage credibility; waiting for cure can endanger a deadline; broad demands may provoke a finality dispute; unavailable exhibits cannot be represented as reviewed.

Source lines 350–352; approximately 26 words.

16. External-review trigger

Counsel trigger when cure is denied, deadline continues despite material incompleteness, or a scoped allegation reaches finality without disposition. Consultation/preservation only.

Source lines 353–355; approximately 22 words.

17. First-day actions

Preserve transmission; verify pages/attachments; run both date assumptions; conduct full search and manual pass; code expected-record rows; draft missing-material, deadline-confirmation, extension, and minimal route forms.

Source lines 356–358; approximately 26 words.

18. First-week actions

Obtain/record cure response; update hashes as a new transmission; decide route; finalize omission matrix and DGE notice; prepare counsel packet if hard trigger remains; second-check every absence claim.

Source lines 359–361; approximately 29 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Material completeness and clarification request concerning CRO transmission I received the transmission on [TRANSMITTAL_TIMESTAMP]. My preservation review identifies the following specific issue: [MISSING_OR_UNCLEAR_ITEM], expected from [SOURCE_OR_NOI_PROVISION] and material because [MATERIALITY]. I do not assume that noncitation means nonconsideration; I ask whether this item was considered, whether an attachment or section was omitted, and whether a corrected or complete transmission will issue. Please also confirm the operative issuance date and the effect, if any, of this cure request on the stated procedural deadline. I preserve both counting assumptions and all route rights.

Source lines 362–370; approximately 99 words.

20. Complete full-submission architecture

Native transmission facts; completeness method; NOI-to-report disposition table; expected-record status table; specific missing/unclear items; proof of actual submission/availability; materiality; requested narrow cure; deadline/extension request; protective route statement; DGE notice; attachments and search certification. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 371–378; approximately 91 words.

Scenario 6 — Procedural or ambiguous disposition

Structural heading introducing subordinate content.

Source lines 379–380; approximately 0 words.

1. Expected characteristics

The transmission does not present a conventional merits report, uses unclear finality or acceptance language, applies an uncertain policy/version, or leaves the operative hearing/comments path difficult to identify.

Source lines 381–383; approximately 30 words.

2. First verification

Capture exact title, decision language, stated authority, policy version, issuance/transmission dates, rights notice, finality terms, attachments, and whether every NOI allegation has a disposition. Do not classify the document by label alone.

Source lines 384–386; approximately 33 words.

3. Principal objective

Obtain a narrow written clarification of status, authority, route, and deadline while preserving every plausible option and avoiding a concession about finality or DGE completion.

Source lines 387–389; approximately 25 words.

4. What not to contest unnecessarily

Do not invent the procedural effect. Do not call ambiguity a denial. Do not assume a document labeled final is appealable under a particular provision without text. Do not wait silently while a stated date runs.

Source lines 390–392; approximately 36 words.

5. Favorable findings to preserve

Preserve any merits facts, acknowledgment of uncertainty, nonfinal language, reserved issue, or commitment to a corrected/complete document.

Source lines 393–395; approximately 18 words.

6. Damaging findings to address

Identify any adverse outcome, purported finality, ambiguous acceptance requirement, unclear route notice, or policy-version mismatch. Record exact text without legal characterization.

Source lines 396–398; approximately 21 words.

7. Hearing/comments presumptive route

Clarification and, where supported, good-cause extension are primary. Prepare both minimal hearing and comments forms so Cooper can protect the earliest plausible date after focused counsel review.

Source lines 399–401; approximately 27 words.

8. Exact route-changing triggers

Counsel trigger for finality, waiver, exhaustion, scope, or version questions. Hearing trigger only if the clarified disposition creates a material factual/credibility issue. Comments trigger if the ambiguity resolves into a documentary/textual dispute.

Source lines 402–404; approximately 34 words.

9. Evidence and witness priorities

Native transmittal and headers, Procedure/Attachment B exact text, Stage A ambiguity table, NOI, report/disposition, any official correction, and confirmed case-specific instructions.

Source lines 405–407; approximately 23 words.

10. CRO response strategy

Ask closed, answerable questions: what document issued; date of transmission; whether complete; applicable route; deadline/method; policy version; and whether/what was sent to DGE. State no proposed answer.

Source lines 408–410; approximately 29 words.

11. DGE notification strategy

Advise DGE that the CRO document’s procedural status is being clarified; ask DGE not to infer a conceded completion milestone and to identify materials/clock status.

Source lines 411–413; approximately 26 words.

12. DGE mitigation framing

If merits facts exist, crosswalk them with explicit uncertainty labels. If none exist, preserve the baseline crosswalk and state what is report-dependent.

Source lines 414–416; approximately 22 words.

13. CDP strategy

Do not request substantive CDP treatment until DGE identifies a referral basis, but keep the referral and written appearance requests ready. Ask for procedures once referral occurs.

Source lines 417–419; approximately 27 words.

14. Remedy ladder

Immediate relief is procedural: clarification, complete transmission, reasonable extension, and status preservation. Merits remedies follow the clarified record and proper decisionmaker.

Source lines 420–422; approximately 21 words.

15. Risks and tradeoffs

Silence can be treated as acquiescence; an overconfident interpretation can forfeit an option; DGE may start a clock based on its own receipt; extensions are discretionary and not automatic.

Source lines 423–425; approximately 29 words.

16. External-review trigger

Focused administrative/disability counsel review is appropriate when ambiguity affects finality or a live deadline. No court/agency filing should be initiated without separate authority.

Source lines 426–428; approximately 25 words.

17. First-day actions

Preserve; hash; quote status language; run primary A/B dates as protective scenarios; draft closed questions, extension request, and minimal route forms; notify DGE in neutral terms.

Source lines 429–431; approximately 27 words.

18. First-week actions

Record clarification; reclassify scenario; update deadline workbook; choose route; complete DGE crosswalk if facts exist; archive all versions and responses.

Source lines 432–434; approximately 20 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Clarification of status, issuance, and procedural options I received [DOCUMENT_TITLE] on [TRANSMITTAL_TIMESTAMP]. To preserve an accurate record, please confirm: (1) whether this is the complete investigation report contemplated by the NOI; (2) the date of transmission treated as issuance; (3) the available hearing and/or comments procedure and submission method; (4) the date UCLA treats as applicable under each instruction; and (5) what Investigation Materials were sent to DGE. I request a reasonable good-cause extension if clarification cannot be provided with adequate review time. This request does not concede finality, acceptance, a counting method, or the DGE completion milestone.

Source lines 435–443; approximately 107 words.

20. Complete full-submission architecture

Exact document/transmittal description; unanswered procedural questions; governing text side-by-side; protective date calculations A/B; completeness and scope map; conditional route election; extension grounds; DGE status notice; requested written clarification; rights reservation. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 444–451; approximately 87 words.

Scenario 7 — Incomplete or materially redacted transmission

Structural heading introducing subordinate content.

Source lines 452–453; approximately 0 words.

1. Expected characteristics

The email or portal indicates a report issued, but a file, appendix, evidence list, page, password, link, or necessary portion is missing, corrupt, inaccessible, or materially redacted so the findings cannot be evaluated reliably.

Source lines 454–456; approximately 34 words.

2. First verification

Preserve the native event; inventory every promised and received item; hash readable files; record page count, gaps, redactions, passwords, broken links, and screenshots; compare title page, table of contents, pagination, and transmittal list.

Source lines 457–459; approximately 33 words.

3. Principal objective

Obtain a complete usable transmission and written deadline treatment while preserving both counting assumptions and avoiding any premature merits election.

Source lines 460–462; approximately 20 words.

4. What not to contest unnecessarily

Do not modify the original file, bypass access controls, speculate about redacted content, or state that issuance failed as a settled rule. The official sources do not define incomplete transmission.

Source lines 463–465; approximately 30 words.

5. Favorable findings to preserve

Preserve any readable rights notice, partial findings, attachment list, redaction legend, and statement promising later material. Do not build a final merits strategy from a fragment.

Source lines 466–468; approximately 26 words.

6. Damaging findings to address

Record each defect objectively: exact missing item, expected source, page gap, error message, or redaction that blocks allegation/credibility/remedy review. Avoid adjectives about intent.

Source lines 469–471; approximately 25 words.

7. Hearing/comments presumptive route

Missing-materials, issuance/deadline confirmation, and reasonable extension requests are presumptive. Keep protective minimal hearing/comments drafts ready because the effect of incompleteness is source-silent. Do not rely on a final Artifact 06 merits score until the defect is cured, UCLA confirms the operative record/date, or the earliest plausible deadline requires a protective election.

Source lines 472–474; approximately 54 words.

8. Exact route-changing triggers

Hard trigger if UCLA refuses timely cure while treating a route deadline as running, or if a scoped allegation cannot be assessed because of the defect. If the earliest plausible date will arrive before cure or confirmation, prepare the narrow protective filing that preserves all completeness and issuance objections without making an unnecessary final merits concession. Reclassify only after a cured transmission is preserved and hashed.

Source lines 475–477; approximately 66 words.

9. Evidence and witness priorities

Native email/export, headers, screenshots, file inventory/hashes, open/error log, report table of contents, expected appendices, redaction notice, and any correction transmission.

Source lines 478–480; approximately 23 words.

10. CRO response strategy

Request the specific file/page/access cure, ask whether the received set is complete, confirm issuance/deadline treatment, and request an extension adequate for review. Do not argue merits before access.

Source lines 481–483; approximately 31 words.

11. DGE notification strategy

Ask DGE what materials it received, whether it considers them Investigation Materials, and what clock status it uses. State that Cooper cannot yet provide a final crosswalk.

Source lines 484–486; approximately 27 words.

12. DGE mitigation framing

Use only verified readable facts; preserve explicit placeholders for missing report data in the working copy; do not send a placeholder-filled merits submission.

Source lines 487–489; approximately 23 words.

13. CDP strategy

Hold substantive CDP presentation until DGE referral and a complete record; preserve the appearance request template and ask for procedures if a referral occurs.

Source lines 490–492; approximately 24 words.

14. Remedy ladder

Complete transmission and reasonable review time first; alternate accessible format if needed; corrected version hash/version record; protective status measures if delay creates concrete harm.

Source lines 493–495; approximately 25 words.

15. Risks and tradeoffs

A deadline may be asserted despite incompleteness; correction may change the record; repeated downloads can obscure provenance; redactions may be lawful even if inconvenient.

Source lines 496–498; approximately 24 words.

16. External-review trigger

Counsel review if cure is denied, deadline runs, material redaction blocks a route, or imminent harm occurs. Consultation does not authorize filing.

Source lines 499–501; approximately 22 words.

17. First-day actions

Preserve native event; hash; inventory; screenshot; log defects; run protective A/B dates without conceding completeness or issuance; draft cure, deadline-confirmation, extension, and minimal route forms; notify DGE neutrally; suspend final merits scoring unless the protective-deadline exception applies.

Source lines 502–504; approximately 38 words.

18. First-week actions

Track cure; preserve each version; compare hashes/redline; re-run completeness and deadline checks; reclassify scenario; only then finalize merits, route, and DGE packages.

Source lines 505–507; approximately 23 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Request for complete and accessible CRO transmission I received the transmission on [TRANSMITTAL_TIMESTAMP], but the following specifically identified material is unavailable or unusable: [MISSING_CORRUPT_REDACTED_ITEM]. The defect prevents review of [AFFECTED_ALLEGATION_OR_RIGHT]. Please provide the intended complete accessible material, confirm whether UCLA treats the current transmission as complete issuance, and state the operative procedural date and method. Because the official materials do not resolve the effect of an incomplete transmission, I also request a reasonable good-cause extension sufficient to review the cured materials. I preserve all procedural options and do not concede a counting method.

Source lines 508–516; approximately 101 words.

20. Complete full-submission architecture

Transmission inventory; defect log with screenshots/hashes; expected-versus-received table; affected review functions; exact cure requested; accessible-format request if applicable; issuance/deadline questions; extension request; protective route statement; DGE materials/clock question; version-control protocol. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 517–524; approximately 88 words.

Scenario 8 — No report by July 31 without a further extension

Structural heading introducing subordinate content.

Source lines 525–526; approximately 0 words.

1. Expected characteristics

No CRO report and no further extension or status communication appears in the preserved case record by the end of July 31, 2026. The June 25 communication described July 31 as an expected on-or-before date, not an adjudicated deadline or default consequence.

Source lines 527–529; approximately 42 words.

2. First verification

Confirm across the authorized account/channel only if Cooper chooses to check it; record no external search or private access by this system. Verify the June 25 wording, time zone, and whether any later communication exists before using this scenario.

Source lines 530–532; approximately 40 words.

3. Principal objective

Preserve the missed expectation objectively, request status and a revised good-cause explanation/timeline if Cooper approves, and protect DGE/status interests without claiming default victory or an absolute maximum.

Source lines 533–535; approximately 29 words.

4. What not to contest unnecessarily

Do not state UCLA violated a hard deadline solely because July 31 passed. Do not infer report valence, manipulation, or bad faith. Do not contact UCLA from this environment.

Source lines 536–538; approximately 29 words.

5. Favorable findings to preserve

Preserve the direct June 25 statements: nineteen-business-day extension, additional senior review time, no further contribution needed then, and expected issuance on or before July 31 with efforts to issue sooner.

Source lines 539–541; approximately 30 words.

6. Damaging findings to address

The absence of a report prolongs uncertainty and may affect status, funding, insurance, placement, and DGE abeyance, but each practical consequence must be verified rather than assumed.

Source lines 542–544; approximately 27 words.

7. Hearing/comments presumptive route

No merits hearing/comments route exists until an operative report/transmittal. Prepare a status/extension-confirmation draft and continue preserving all pre-report materials.

Source lines 545–547; approximately 22 words.

8. Exact route-changing triggers

Escalate for counsel review if a concrete status/funding/insurance consequence becomes imminent, DGE acts without Investigation Materials, or UCLA states a new procedural position affecting rights. Reclassify on any report or extension.

Source lines 548–550; approximately 33 words.

9. Evidence and witness priorities

June 25 native correspondence, receipt logs, absence/status record, DGE abeyance text, any verified consequence notice, and all later communications preserved as new events.

Source lines 551–553; approximately 24 words.

10. CRO response strategy

A draft status request should quote the expected-date language accurately, ask whether good cause is being invoked again and for a revised expected transmission date, and avoid accusations or invented deadlines.

Source lines 554–556; approximately 31 words.

11. DGE notification strategy

If a concrete need exists, prepare a neutral continuing-abeyance/status notice stating that no report has been received and asking DGE to confirm no adverse clock/action is occurring. Preserve source silence about completion.

Source lines 557–559; approximately 34 words.

12. DGE mitigation framing

Do not submit speculative report findings. Maintain the baseline mitigation crosswalk and identify which entries await report authentication.

Source lines 560–562; approximately 18 words.

13. CDP strategy

No CDP referral request should claim that the report stage is complete. Keep the referral and appearance drafts ready for the later DGE determination.

Source lines 563–565; approximately 24 words.

14. Remedy ladder

Immediate requests, if Cooper approves, are procedural status, continued protection against irreversible implementation, and a reliable revised timeline. Substantive remedies await the record.

Source lines 566–568; approximately 23 words.

15. Risks and tradeoffs

Overstating July 31 can undermine credibility; silence may continue; extensions have no numerical cap; DGE interlock remains undefined; external deadlines may not toll automatically.

Source lines 569–571; approximately 24 words.

16. External-review trigger

Counsel consultation is triggered only by an observable deadline, concrete harm, DGE action, or legal-preservation need—not delay alone. No filing is authorized.

Source lines 572–574; approximately 23 words.

17. First-day actions

Create an internal no-receipt record after the date passes; verify the June 25 source; identify concrete consequences; prepare status and DGE drafts for Cooper’s review; do not send.

Source lines 575–577; approximately 28 words.

18. First-week actions

Update the record daily only through authorized user-reviewed information; preserve any response; reassess counsel triggers; continue keeping receipt war-room and deadline tools ready.

Source lines 578–580; approximately 23 words.

19. Complete short-form communication

Draft — do not send without Cooper’s approval Subject: Status request concerning expected CRO report The June 25, 2026 communication stated that the report was expected on or before July 31, 2026 and that efforts would be made to issue it sooner. As of [VERIFIED_DATE_TIME], I have not received the report or a further extension communication in the preserved record. Please confirm the current status, whether a further good-cause extension is being invoked, the reason and expected transmission date, and whether any action or clock is occurring in the related DGE appeal. This request does not assert a default merits outcome or waive any right.

Source lines 581–589; approximately 104 words.

20. Complete full-submission architecture

Verified no-receipt statement; June 25 exact language; chronology of extensions; Procedure extension text and no-cap caution; concrete consequences; narrow status questions; continuing DGE-abeyance request; preservation of report-stage rights; counsel trigger screen; attachment of only necessary correspondence. Every section must use exact report pages and epistemic labels; every attachment must appear in an index with filename, date, source, and purpose. The final package should include a one-page executive request, verified deadline statement, table of contents, and signature/approval block appropriate to the actual submission method. Remove all unused placeholders before any submission.

Source lines 590–597; approximately 91 words.

Universal pre-submission gate

For every scenario: preserve native originals and hashes; verify the actual recipient and submission method; compute both primary counting assumptions; keep observed holidays and possible curtailment dates in sensitivity only; do not call an unextended sequence an absolute maximum; distinguish report findings from party accounts and proffers; confirm witness testimony; scan for unfilled placeholders; obtain Cooper’s approval; and apply any qualified-counsel advice triggered by Artifact 17. If the transmission is incomplete, unreadable, internally inconsistent, or materially redacted, apply the incomplete-transmission hard stop before any final merits-route election.

Source lines 598–600; approximately 87 words.

09_DGE_CDP_MITIGATION_PACKAGE.md

657 lines; 9,638 words; 40 indexed headings/sections.

DGE / CDP Mitigation Package

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Prepared for: Cooper Beaman Fixed reference date: July 22, 2026 (PDT) Status: The CRO investigation report and transmittal do not yet exist. Nothing in this package has been sent. Purpose: A source-bounded, ready-to-review package for the Division of Graduate Education (DGE) and, if DGE refers the appeal, the Graduate Council’s Committee on Degree Programs (CDP).

Source lines 1–9; approximately 71 words.

1. Deployment rules

1. Replace every bracketed report field only from the native CRO transmittal, the report itself, or a written UCLA confirmation. Keep the original source beside the working copy. 2. Do not submit this entire strategy file. Select the argument and draft that match the actual report and procedural posture. 3. Attach the populated 10_DGE_CDP_MITIGATION_CROSSWALK.xlsx; cite exact report pages and distinguish findings from background, party accounts, and source silence. 4. Do not argue that a CRO policy violation is required for DGE mitigation. Do not argue that a CRO violation automatically compels reversal. 5. Do not concede that initial report issuance, report finalization, hearing completion, a Vice Chancellor decision, or a later appeal is the event that completes the investigatory process. The reviewed official sources do not answer that question. 6. Do not describe a report omission a…

Source lines 10–20; approximately 215 words.

2. Controlling DGE / CDP framework

Structural heading introducing subordinate content.

Source lines 21–22; approximately 0 words.

2.1 Exact standard

The controlling S\&P standard is: > “substantive mitigating circumstances that could have affected academic performance” The full operative sentence states that, after the investigatory office completes its process and provides appropriately redacted written investigation materials, DGE determines whether the report reflects “substantive mitigating circumstances that could have affected a disqualified student’s academic performance.” The next branch uses the formulation “possible substantive mitigating circumstances.” [S1] This is a distinct inquiry from whether CRO proves a policy violation by a preponderance of the evidence. DGE’s question is whether the Investigation Materials reflect a circumstance that is both: - possible: supported enough by the Investigation Materials to be a genuine, non-speculative contributor; and - substantive: materially connected to one or more academic-perf…

Source lines 23–37; approximately 147 words.

2.2 Express branch architecture

Source-established procedural facts: - While an investigatory office processes the allegations, DGE holds the appeal decision in abeyance “until that process has completed”; while the appeal decision is in abeyance, the academic disqualification remains in place. [S1] - After the investigatory office completes its process, it notifies DGE of the outcome and provides appropriately redacted versions of any written investigation report, defined as “Investigation Materials.” [S1] - If the Investigation Materials do not reflect possible substantive mitigating circumstances, DGE notifies the individual in writing within 30 calendar days of DGE’s receipt of the materials that the appeal is denied; the Graduate Dean retains final authority, and the decision is final with no further appeal. [S1] - If the Investigation Materials do reflect possible substantive mitigating circumstances, the Dean o…

Source lines 38–48; approximately 214 words.

2.3 Source silence that must be preserved

Unknown / source silence: - The Standards do not define when the investigatory office’s “process has completed.” - They do not say whether that milestone is initial report issuance, expiration of the hearing-request period, no-hearing finalization, hearing completion, a post-hearing decision, or completion of a later appeal. - They do not say whether an incomplete or materially redacted transmission is effective. - They do not define whether the receipt date is included in a 30-calendar-day period, when receipt occurs, the deadline time or time zone, or whether a weekend or holiday endpoint shifts. - They do not publish the referenced CDP-approved personal-appearance procedures. No reviewed public source supplies the request deadline or method, notice period, duration, representation rules, witness or document rules, recording practice, accommodation procedure, quorum, recusal rules, or…

Source lines 49–60; approximately 142 words.

2.4 Current case posture

Established or source-established facts: - The April 8, 2026 NOI opened a Procedure 230.2 investigation concerning allegations against James Bisley, Carrie Bearden, and Felix Schweizer. The scoped allegations concern the NEURO M203 later-exam request, Bearden’s refusal to serve as primary mentor and alleged harassment, and Schweizer’s recommendation for academic disqualification and alleged harassment. The NOI expressly said it had made no determination about accuracy or violation. [C1] - CRO declined to amend the NOI on April 20, 2026 but stated that it would consider the evidence, witnesses, and theories Cooper presented and that the ultimate report would reflect them. That statement does not convert every theory into a formal allegation or guarantee that every item will be cited. [C2] - DGE told Cooper on July 21, 2025 that his procedural-error and nondiscrimination appeals would be…

Source lines 61–71; approximately 241 words.

2.5 Baseline academic-performance map

Use this map only as a pre-report index. Replace or confirm every report-dependent point with exact report language and pages. | Component | Source-grounded baseline | Epistemic treatment | Future-report deployment | | Primary mentor | The November 19, 2024 Academic Plan required confirmation by March 14, 2025 that the fifth-rotation mentor would serve as primary mentor. The April 28, 2025 recommendation identified failure to secure a mentor as the basis for insufficient progress. [C5] | Established administrative record | Cite any report finding about Bearden’s mentor decision, notice, disability nexus, comparative treatment, or independent academic reasons. | | Fifth rotation | The Academic Plan authorized a fifth rotation. Bearden provided written expectations. The program later relied on an Unsatisfactory grade and said multiple expectations were not met; Cooper argued an external E…

Source lines 72–84; approximately 476 words. Tables/matrices: | Component | Source-grounded baseline | Epistemic treatment | Future-report deployment |

3. Common mitigation proof structure

Use the following order in every DGE or CDP submission: 1. Report fact or finding: quote no more than needed and cite [REPORT_PAGE]. 2. Disability-related circumstance: identify the circumstance without converting an allegation into a fact. 3. University notice: state who knew what, when, and how the report establishes it. 4. Accommodation or interactive-process issue: distinguish a request, a response, a provided accommodation, a disputed modification, and source silence. 5. Temporal connection: link the circumstance to the precise period of M203, the fifth rotation, mentor search, the Academic Plan, funding, or placement.

Source lines 85–99; approximately 173 words.

3.1 V2 crosswalk-field discipline

Each of the six outcome-specific arguments below must use three independent columns from 10_DGE_CDP_MITIGATION_CROSSWALK.xlsx: - Disability-related circumstance identifies the disability-related condition, functional limitation, barrier, or report-authenticated circumstance that could have affected performance. - University notice identifies who knew what, when, and through which report-authenticated communication or event. - Accommodation or interactive-process issue identifies the particular request, response, provided accommodation, disputed modification, individualized step, unresolved gap, N/A, or source silence. Do not duplicate one field into the others. A disability-related circumstance does not by itself prove University notice; notice does not by itself prove an accommodation or interactive-process defect; and an accommodation/process issue does not by itself establish causati…

Source lines 100–109; approximately 155 words.

4. Six complete outcome-specific DGE arguments

Structural heading introducing subordinate content.

Source lines 110–111; approximately 0 words.

4.1 Outcome 1 — Favorable CRO liability findings

Use when: CRO substantiates one or more violations concerning Bisley, Bearden, or Schweizer. Submission-ready argument The Investigation Materials reflect substantive mitigating circumstances that could have affected academic performance. CRO found at [REPORT_PAGE(S)] that [EXACT_VIOLATION_FINDING]. That finding concerns [M203 / FIFTH_ROTATION / PRIMARY_MENTOR / DISQUALIFICATION_RECOMMENDATION], an academic component later relied upon in the disqualification record. The material connection is concrete: [EXACT_CAUSAL_PATH_FROM_REPORT]. The relevant University notice is established at [REPORT_PAGE], where the report states [EXACT_NOTICE_FINDING]. The requested DGE determination is narrower than treating CRO liability as automatic reversal. The S\&P asks whether the Investigation Materials reflect substantive mitigating circumstances that could have affected academic performance. Here, the…

Source lines 112–127; approximately 406 words.

4.2 Outcome 2 — Mixed findings

Use when: CRO substantiates some allegations or material facts but rejects others. Submission-ready argument The mixed result should be disaggregated rather than averaged into a global “partial win” or “partial loss.” The relevant DGE question is whether any report-established circumstance is both substantive and capable of affecting an academic-performance component. At [REPORT_PAGE], CRO found [FAVORABLE_FINDING_OR_FACT]; at [REPORT_PAGE], it did not substantiate [ADVERSE_OR_REJECTED_ALLEGATION]. This submission accepts the latter finding for purposes of DGE review and does not ask DGE to relitigate CRO’s merits. The favorable matter is independently sufficient for the referral threshold because it bears on [ACADEMIC_COMPONENT] through [EXACT_CAUSAL_MECHANISM]. It is possible because the report itself authenticates [NOTICE / REQUEST / RESPONSE / EFFECT]. It is substantive because [ACA…

Source lines 128–143; approximately 338 words.

4.3 Outcome 3 — No violation, but substantial favorable facts

Use when: CRO finds no policy violation but authenticates material facts about disability, notice, requests, process, timing, barriers, or effects. Submission-ready argument CRO’s no-violation conclusion and DGE’s mitigation inquiry answer different questions. This submission does not ask DGE to disturb CRO’s conclusion that [EXACT_NO_VIOLATION_FINDING]. It asks DGE to apply the S\&P language to the report’s accepted factual findings. The report states at [REPORT_PAGE(S)] that [FAVORABLE_FACT_1], [FAVORABLE_FACT_2], and [FAVORABLE_FACT_3]. Those facts concern [M203 / ROTATION / MENTOR / NOTICE / ACCOMMODATION PROCESS]. They are possible mitigating circumstances because CRO accepted them as part of its factual account even though it concluded that the policy element or preponderance threshold was not met. They are substantive because the record links the same academic components to the di…

Source lines 144–161; approximately 394 words.

4.4 Outcome 4 — Adverse report with acknowledged disability-related circumstances

Use when: CRO substantially credits respondents or the program and finds no violation, but the report still acknowledges disability-related circumstances. Submission-ready argument This is not a request for DGE to reverse an adverse CRO report. The report concludes [EXACT_ADVERSE_CONCLUSION] and credits [RESPONDENT_OR_PROGRAM_POSITION] at [REPORT_PAGE]. Those conclusions must be presented accurately. The separate mitigation question is whether the report also reflects a substantive disability-related circumstance that could have affected academic performance. At [REPORT_PAGE], the report acknowledges [EXACT_DISABILITY_RELATED_CIRCUMSTANCE]; at [REPORT_PAGE], it places that circumstance during [ACADEMIC_PERIOD]; and at [REPORT_PAGE], it identifies [EFFECT_OR_LIMITATION]. The circumstance is possible because it is accepted in the report rather than inferred from advocacy. It is substantiv…

Source lines 162–179; approximately 364 words.

4.5 Outcome 5 — Narrow report with missing mitigation evidence

Use when: the report is materially narrow, omissive, incomplete, or redacted in a way that prevents reliable mitigation review. Submission-ready argument The transmitted materials do not yet permit a reliable application of the S\&P standard. This is not based solely on noncitation. The specific problem is [MISSING_REPORT_SECTION / MISSING_APPENDIX / UNEXPLAINED_REDACTION / OMITTED_SCOPE_TREATMENT / CORRUPT_OR_INCOMPLETE_ATTACHMENT], documented at [TRANSMITTAL_OR_REPORT_PAGE]. The missing item matters because it bears directly on [NOTICE / ACCOMMODATION / M203 / ROTATION / MENTOR / CAUSATION], which in turn bears on an academic benchmark used in the disqualification record. CRO stated on April 20, 2026 that it would take the evidence, witnesses, and theories Cooper presented into consideration and that the ultimate report would reflect them. [C2] That statement does not require citation…

Source lines 180–197; approximately 391 words.

4.6 Outcome 6 — Hearing requested and CRO process not yet confirmed final

Use when: Cooper timely requests a Procedure 230.2 hearing and UCLA has not answered whether the DGE abeyance continues through the hearing or any later appeal. Submission-ready argument Cooper timely requested a Procedure 230.2 hearing on [HEARING_REQUEST_DATE] concerning the report issued on [REPORT_ISSUANCE_DATE]. The request does not itself establish whether the investigatory office’s process remains incomplete for S\&P purposes. The Standards use “until that process has completed” but do not define the milestone or say whether it includes a timely hearing, post-hearing decision, or later appeal. [S2] Because the governing source is silent, Cooper does not assert that DGE is legally required to wait through every later stage, and he does not concede that report issuance started DGE’s 30-calendar-day period. He requests a written administrative determination before any irreversible DG…

Source lines 198–215; approximately 372 words.

5. Sequencing controls

Structural heading introducing subordinate content.

Source lines 216–217; approximately 0 words.

5.1 Risk to avoid

Immediate transmission of an initial report to DGE may create parallel clocks while the Procedure 230.2 hearing or comments route remains open. The Standards do not resolve the interlock. The operational response is to preserve both routes: meet the earliest plausible CRO deadline, notify DGE promptly but neutrally, and request written clock and completion confirmation.

Source lines 218–221; approximately 56 words.

5.2 Information that must be confirmed in writing

The neutral notice is designed to obtain an express answer to each original control question: what DGE received; the date received; whether it considers the CRO process complete; when its thirty-calendar-day clock began; whether it will await finality of any timely hearing or appeal; what documents it treats as Investigation Materials; whether the student may provide a mitigation crosswalk; and whether the admitted prior service defect will be preserved in the record. - exact documents DGE received; - DGE’s actual receipt date and timestamp; - whether DGE treats the CRO process as complete; - the event DGE uses as the completion event; - whether DGE considers its 30-calendar-day period to have begun and, if so, the date it uses;

Source lines 222–236; approximately 175 words.

6. Complete sequencing notice

Use: Send promptly after report receipt if DGE may have received the report directly. This notice preserves the interlock question without asserting an answer. To: [CONFIRMED_DGE_CASE_CONTACT_OR_CHANNEL] Subject: Notice of CRO report issuance and request for sequencing confirmation — Cooper Beaman, UID 105692562, [CURRENT_DGE_SERVICE_REQUEST] Dear [DGE_CONTACT_NAME_OR_TITLE], I am writing to provide notice that UCLA’s Civil Rights Office transmitted an investigation report to me on [TRANSMITTAL_DATE] at [TRANSMITTAL_TIME_AND_TIME_ZONE] concerning the disability-related allegations underlying my active academic-disqualification appeal. I am preserving all rights and deadlines under UCLA Procedure 230.2. My current CRO route is [NO_HEARING_COMMENTS_ROUTE / HEARING_REQUESTED_ON_DATE / ROUTE_DECISION_PENDING_WITHIN_ACTIVE_PERIOD]. I do not intend this notice to concede what event constitute…

Source lines 237–273; approximately 400 words.

7. Complete continuing-abeyance request

Use: When a CRO route remains active or UCLA has not confirmed that the process is complete. To: [CONFIRMED_DGE_CASE_CONTACT_OR_CHANNEL] Subject: Request to continue abeyance pending written completion and record confirmation — Cooper Beaman Dear [DGE_CONTACT_NAME_OR_TITLE], I respectfully request written confirmation that DGE will continue to hold the decision on my active nondiscrimination-based academic-disqualification appeal in abeyance unless and until UCLA determines that the investigatory office’s process has completed and identifies the complete Investigation Materials and the date DGE received them. The CRO report was transmitted on [REPORT_TRANSMITTAL_DATE]. My Procedure 230.2 posture is [DESCRIBE_ACTIVE_ROUTE]. On [DATE], I [REQUESTED_A_HEARING / SUBMITTED_COMMENTS / REQUESTED_CORRECTION_OR_COMPLETE_MATERIALS]. The next identified event is [NEXT_CONFIRMED_EVENT_OR_UNKNOWN].

Source lines 274–305; approximately 293 words.

8. Complete Investigation Materials and clock-confirmation request

Use: When DGE confirms receipt or when the record suggests DGE may already be reviewing materials. To: [CONFIRMED_DGE_CASE_CONTACT_OR_CHANNEL] Subject: Investigation Materials, receipt date, and DGE clock confirmation — Cooper Beaman Dear [DGE_CONTACT_NAME_OR_TITLE], Thank you for confirming that DGE received materials from CRO concerning my active nondiscrimination-based academic-disqualification appeal. To ensure an accurate administrative record and a focused mitigation submission, please provide or confirm the following: 1. Materials received. The exact title, date, version, page count, and attachment or appendix status of every item DGE received from CRO.

Source lines 306–345; approximately 401 words.

9. Complete mitigation-crosswalk cover memorandum

To: Dean of Graduate Education, through [CONFIRMED_DGE_CHANNEL] From: Cooper M. Beaman, UID 105692562 Re: Application of the S\&P mitigation standard to CRO Investigation Materials Date: [SUBMISSION_DATE]

Source lines 346–352; approximately 27 words.

Requested determination

I respectfully request that DGE determine that the Investigation Materials reflect possible substantive mitigating circumstances that could have affected my academic performance and refer my written appeal and the Investigation Materials to CDP.

Source lines 353–356; approximately 33 words.

Standard and scope of request

The S\&P standard is not whether DGE independently finds a CRO policy violation. It is whether the Investigation Materials reflect substantive mitigating circumstances that could have affected academic performance. This memorandum accepts the report’s conclusions as written and maps only report-established facts or clearly labeled report accounts to the academic components used in my disqualification decision.

Source lines 357–360; approximately 57 words.

Report-grounded mitigation

1. [ACADEMIC_COMPONENT_1]. The report states [EXACT_FINDING_OR_FACT] at [REPORT_PAGE]. The University notice finding is [EXACT_NOTICE] at [REPORT_PAGE]. This could have affected performance by [CAUSAL_MECHANISM]. It is substantive because [LINK_TO_DISQUALIFICATION_BENCHMARK]. 2. [ACADEMIC_COMPONENT_2]. The report states [EXACT_FINDING_OR_FACT] at [REPORT_PAGE]. The temporal link is [DATE_OR_PERIOD]. The effect is [CAUSAL_MECHANISM]. It is substantive because [LINK_TO_BENCHMARK]. 3. [ACADEMIC_COMPONENT_3]. The report states [EXACT_FINDING_OR_FACT] at [REPORT_PAGE]. The circumstance is possible because [REPORT_SUPPORT] and substantive because [MATERIALITY]. The attached crosswalk supplies the complete mapping, strongest contrary evidence, and responses.

Source lines 361–368; approximately 80 words.

Contrary evidence

The report and academic record also reflect [STRONGEST_PROGRAM_OR_RESPONDENT_POSITION]. I do not ask DGE to disregard it. The November 2024 plan established benchmarks, and the program has asserted independent academic reasons concerning mentor placement, rotation performance, and M203. [C5] The requested referral permits CDP to evaluate those academic reasons with the report-established mitigation given its proper weight.

Source lines 369–372; approximately 56 words.

Requested action

Please: 1. confirm the complete Investigation Materials and DGE receipt date; 2. find that the materials reflect possible substantive mitigating circumstances; 3. refer my written appeal and the complete Investigation Materials to CDP within the applicable confirmed period; 4. include the attached crosswalk and this memorandum in the referral packet; 5. provide the CDP-approved personal-appearance procedures and the deadline and channel for requesting an appearance; and

Source lines 373–388; approximately 84 words.

10. Complete CDP referral request

Use: When the report supports possible substantive mitigation or DGE has not acted within the confirmed branch period. To: Dean of Graduate Education, through [CONFIRMED_DGE_CHANNEL] Subject: Request for CDP referral under the S\&P possible-substantive-mitigation branch — Cooper Beaman Dear Dean [NAME], I respectfully request referral of my written nondiscrimination-based academic-disqualification appeal and the complete Investigation Materials to the Graduate Council’s Committee on Degree Programs. The report reflects possible substantive mitigating circumstances that could have affected academic performance:

Source lines 389–424; approximately 307 words.

11. Complete CDP personal-appearance request

Use: Submit in writing through the confirmed channel immediately after referral or earlier if DGE instructs. To: [CONFIRMED_CDP_OR_DGE_CHANNEL] Subject: Written request for personal appearance before CDP — Cooper Beaman, UID 105692562 Dear [CDP_CONTACT_NAME_OR_TITLE], Under the *Standards and Procedures for Graduate Study at UCLA*, I respectfully request a personal appearance before the Graduate Council’s Committee on Degree Programs in connection with the referral of my academic-disqualification appeal. My appearance will focus on the report-established mitigation and its relationship to the academic benchmarks used in the disqualification decision. I will not ask CDP to conduct a new CRO investigation. I expect to address:

Source lines 425–463; approximately 309 words.

12. Complete five-minute CDP presentation

Preparation note — not spoken: Replace bracketed fields from the report and the populated crosswalk. At an average 140–150 words per minute, this script is approximately five minutes. If CDP supplies a shorter limit, preserve the opening, standard, three causal links, counterargument, and request. Spoken script Good [morning/afternoon], and thank you for allowing me to appear. My request is focused. I ask the Committee to recommend a disposition that gives real effect to the Investigation Materials’ substantive mitigating circumstances while preserving legitimate academic standards. The governing question is whether the Investigation Materials reflect substantive mitigating circumstances that could have affected academic performance. It is not limited to whether CRO found every alleged policy violation, and it does not require the circumstance to be the only cause of an academic result.…

Source lines 464–497; approximately 641 words.

13. Complete ten-minute CDP presentation

Preparation note — not spoken: Replace only report-dependent bracketed fields. At approximately 140–150 words per minute, this script is designed for ten minutes. Bring a one-page exhibit containing the three-component causal map and remedy ladder. Spoken script Good [morning/afternoon], Chair and members of the Committee. Thank you for reviewing my appeal and for allowing me to appear. I will make four points. First, the S\&P mitigation standard is distinct from CRO’s liability determination. Second, the Investigation Materials connect disability-related circumstances to the academic components used in my disqualification. Third, the principal academic counterarguments can be respected without making the mitigation meaningless. Fourth, there is a proportionate disposition that protects academic standards and gives the Investigation Materials practical effect. The controlling question is…

Source lines 498–579; approximately 1,515 words.

14. Remedy ladder for the DGE / CDP submission

Select a primary request and no more than two fallbacks. Tie each request to report findings and confirmed authority. 1. Corrected individualized academic review. Ask CDP to recommend and the Dean to adopt a review that separates report-affected inputs from independent academic judgments. 2. Accommodated NSIDP continuation or reinstatement. Request only if the report and academic record support feasibility. Supply objective benchmarks, responsible reviewers, timing, and an interactive-process step. Do not demand assignment to an unwilling faculty mentor. 3. Neutral reassessment of a course, rotation, or benchmark. Request if a report finding directly bears on that component; identify the academic office or faculty process that must implement it. 4. Facilitated major/classification change. Ask DGE to coordinate a fair review by a consenting program. Do not represent transfer as automatic…

Source lines 580–591; approximately 216 words.

15. Attachment and filing checklist

Before any DGE submission: - [ ] Preserve the native CRO transmittal and attachments. - [ ] Record the transmittal timestamp, file names, page counts, and SHA-256 values. - [ ] Confirm that the report, appendices, evidence list, and attachments open and are complete. - [ ] Confirm the Procedure 230.2 route and meet the earliest plausible CRO deadline. - [ ] Obtain or request DGE’s list of Investigation Materials and receipt date.

Source lines 592–618; approximately 216 words.

16. Guardrails and propositions rejected

Unsupported proposition rejected: A favorable CRO report automatically reverses academic disqualification. - Unsupported proposition rejected: A no-violation CRO report automatically defeats DGE mitigation. - Unsupported proposition rejected: Initial report issuance necessarily completes the investigatory process for DGE. - Unsupported proposition rejected: A timely hearing or appeal necessarily extends DGE abeyance. - Unsupported proposition rejected: Noncitation proves CRO did not consider evidence. - Unsupported proposition rejected: General disability awareness proves notice of a specific requested modification.

Source lines 619–631; approximately 125 words.

17. Source key

Structural heading introducing subordinate content.

Source lines 632–633; approximately 0 words.

Tier 0 — verified policy/procedure baseline

[S1] 02_STAGE_A_POLICY_VERIFICATION/PROCEDURAL_TEXT_EXTRACT.md, “Graduate Standards and DGE/CDP process,” citing *Standards and Procedures for Graduate Study at UCLA*, printed pp. 31–34; PDF file pp. 32–35. It supplies the abeyance, Investigation Materials, mitigation, referral, appearance, recommendation, final-authority, and timing text. - [S2] 02_STAGE_A_POLICY_VERIFICATION/UNRESOLVED_AMBIGUITIES.md, “Meaning of completion,” “Calendar-day and business-day computation,” and “CDP timing.” It records the absence of a completion definition and the partially described personal-appearance procedure. - [S3] 02_STAGE_A_POLICY_VERIFICATION/POLICY_VERSION_MEMO.md, “Standards handbook and the current Senate manual.” The handbook states “Updated and Effective September 2025” without a day of month; the reviewed Senate amendment does not state that the handbook was reissued.

Source lines 634–639; approximately 106 words.

Tier 1A — primary case records

[C1] 01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, PDF file pp. 1–4. The NOI controls the scoped respondents, allegations, exclusions, no-determination caveat, and described report route. - [C2] 01_CASE_RECORD/04_CRO_NOI_Objections_and_2026-04-20_Response.md, April 20, 2026 email from Investigator Anwandter. CRO declined to amend the NOI but said it would consider the evidence, witnesses, and theories and that the ultimate report would reflect them. - [C3] 01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, PDF file pp. 2–3. DGE separated the procedural-error and nondiscrimination routes, held the latter in abeyance, and Dean Kite stated that the academic disqualification remained in place during investigation. - [C4] 01_CASE_RECORD/10_DGE_Update_2026-04-24_to_2026-05-04.pdf, PDF file p. 2. DGE confirmed the nondiscrimination appeal remained active, described re…

Source lines 640–647; approximately 187 words.

18. Final review record

Pre-submission reviewer: [NAME_OR_ROLE] Report/transmittal verified: [DATE_AND_TIME] DGE completion/clock confirmation received: [YES_OR_NO; DATE] Selected outcome argument: [1–6] Crosswalk version: [FILENAME_AND_SHA256] Counsel review required or obtained: [ASSESSMENT]

Source lines 648–657; approximately 37 words.

11_BAILEY_RECORD_INTEGRITY_MEMORANDUM.md

389 lines; 6,876 words; 39 indexed headings/sections.

Bailey Record-Integrity Memorandum

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Status: Complete pre-report preservation and decision-support memorandum Fixed reference date: July 22, 2026 (PDT) Use: For Cooper Beaman’s review; hold unless a deployment trigger below occurs Not legal advice: Any constitutional, judicial-review, waiver, exhaustion, or limitations issue should be reviewed by qualified counsel before it is asserted or relinquished.

Source lines 1–9; approximately 65 words.

1. Executive conclusion

The strongest present position is narrow and source-grounded: 1. Source-established procedural fact. The UCLA *Standards and Procedures for Graduate Study* says the program or department Chair “will” provide both the Division of Graduate Education (DGE) and the individual with a written response to the procedural-error appeal within fifteen business days. The printed page is 32; it is PDF page 33. The text requires service on both recipients within the same stated period. It does not use the word “simultaneously” and does not specify identical timestamps. [Case Record 06, printed p. 32 / PDF p. 33.] 2. Established record fact. On July 21, 2025, Thomas Bailey told Cooper that the Chair would provide a written response within fifteen business days and that Cooper would receive a copy. [Case Record 11, PDF p. 2.] 3. Established record fact. The NSIDP Chair’s response is dated August 7, 202…

Source lines 10–22; approximately 486 words.

2. Concise preservation paragraph

The Standards and Procedures required the program Chair to provide both DGE and me with the written program response within fifteen business days. DGE has since acknowledged that, because of a DGE miscommunication, the NSIDP Chair did not share the response with me at the same time it was submitted to DGE. I first received the August 7 response and August 14 addendum on August 26, 2025, together with the Dean’s final decision, even though the decision states that the Dean reviewed the Chair’s response. I do not claim that the Standards grant an unrestricted sur-rebuttal right, and I am not adding a new ground to my timely appeal. I preserve a narrower record-integrity objection: no decision should materially rely on a new or previously undisclosed program rationale, factual assertion, exhi…

Source lines 23–26; approximately 171 words.

3. Questions presented

1. What did the Standards require the Chair and DGE to do with the Chair’s written response? 2. What failure did DGE acknowledge, and what limitation did Bailey place on its significance? 3. Does the Standards text create an unrestricted right to submit a sur-rebuttal? 4. How should a request to correct or contextualize an item in the Chair’s response be distinguished from an impermissible new procedural-appeal ground? 5. Which assertions in the August 7 response and August 14 addendum could create case-specific prejudice if they were new, undisclosed, materially relied upon, and factually disputable? 6. What is the least disruptive institutional cure?

Source lines 27–36; approximately 119 words.

4. Source and proposition controls

| Proposition | Epistemic label | What the source establishes | What it does not establish | | Chair service obligation | Source-established procedural fact | The Chair “will” provide DGE and the individual with a written response within fifteen business days. [06, printed p. 32 / PDF p. 33.] | The text does not expressly say “same instant,” create a reply period, or prescribe a remedy. | | No-new-ground limitation | Source-established procedural fact | No additional information, including new alleged procedural errors, can be considered after the thirty-calendar-day deadline. [06, printed p. 32 / PDF p. 33.] | It does not expressly define a record correction, an objection to new program material, or a response confined to an already pleaded ground as a “new alleged procedural error.” | | July 21 assurance | Established record fact | Bailey said Cooper would receive a copy of the Chair’…

Source lines 37–49; approximately 338 words. Tables/matrices: | Proposition | Epistemic label | What the source establishes | What it does not establish |

5. Controlling text and the precise service issue

Structural heading introducing subordinate content.

Source lines 50–51; approximately 0 words.

5.1 Mandatory contemporaneous-service text

The operative sentence provides: > “The Chair of the program or department will then provide the Division of Graduate Education and the individual with a written response to the appeal within fifteen (15) business days.” [Case Record 06, printed p. 32 / PDF p. 33.] The best textual reading is that the Chair has a mandatory duty, expressed by “will,” to provide the same category of document - the written response - to two recipients within one service window. Calling this contemporaneous service is accurate if it means service on both recipients during that common window. The Standards do not expressly require identical transmission timestamps. Bailey nevertheless described the omitted same-time sharing as something “stipulated in the academic disqualification appeal procedures.” [Case Record 10, PDF p. 2.] The service obligation matters independently of whether a reply is authorized. Se…

Source lines 52–63; approximately 172 words.

5.2 No express unrestricted sur-rebuttal

The Standards say that the Dean reviews the departmental response and sends a decision within fifteen business days of that response. They do not insert a student-reply stage. They also say that no additional information, including new alleged procedural errors, can be considered after the thirty-calendar-day appeal deadline. [Case Record 06, printed pp. 32-33 / PDF pp. 33-34.] Accordingly: - Cooper should not assert that the Standards expressly guarantee a sur-rebuttal. - Cooper should not use late service as a vehicle to add a procedural-error ground that was not timely presented. - Cooper may preserve the distinct question whether a decision-maker should rely on a materially new or inaccurate program assertion without a bounded method to correct the record. - A requested correction should identify the exact Chair-response sentence, cite an item already in the timely appeal record whe…

Source lines 64–74; approximately 148 words.

5.3 Service and notice are not the same issue as appeal scope

Four concepts should remain separate: 1. Service/notice: whether the Chair provided the response to both DGE and Cooper within the prescribed window. 2. Appeal grounds: the procedural errors actually stated in the timely appeal. 3. Record objection: an objection that DGE considered an inaccurate, new, undisclosed, or extra-record assertion when deciding a timely ground. 4. New procedural allegation: an additional claimed defect in the underlying disqualification process first raised after the filing deadline. A narrow record objection can say, for example: “The Chair’s response characterizes the February 19 expectations document as a personalized aid requested by Cooper; the timely appeal already challenged the non-standard use of that document, and this correction addresses that same ground.” It should not say: “The late service creates a wholly new ground that must be adjudicated as p…

Source lines 75–85; approximately 145 words.

6. Complete factual chronology

| Date | Event | Epistemic label and source | Record-integrity significance | | Nov. 19, 2024 | The program and later the Dean identified an Academic Plan containing degree-progress benchmarks. | Respondent/program position in Chair response; Established record fact that the Dean referenced it. [11, PDF pp. 3, 5.] | Baseline for deciding whether later response language merely explained known benchmarks or added a rationale. | | Apr. 28, 2025 | Written recommendation for academic disqualification issued. Cooper characterized it as citing failure to identify a mentor; the Chair later disputed that the rationale shifted. | Complainant account and Respondent/program position reproduced in the Chair-response document. [11, PDF p. 5.] | Exact comparison with the April 28 document is necessary before calling later grounds “new.” | | May 23, 2025 | Cooper made an in-person program appeal, accor…

Source lines 86–103; approximately 599 words. Tables/matrices: | Date | Event | Epistemic label and source | Record-integrity significance |

7. Full record-integrity analysis

Structural heading introducing subordinate content.

Source lines 104–105; approximately 0 words.

7.1 The strongest preserved claim

The strongest claim is not “I had an express unlimited right to rebut.” It is: > The governing procedure required service on both DGE and the individual; DGE acknowledged that same-time sharing did not occur because of its own miscommunication; the decision states that the Dean reviewed the program response; and a bounded cure is warranted if that response introduced a materially new or inaccurate item that affected the decision. This position honors the no-new-ground limitation while preserving accuracy, transparency, and a reviewable administrative record.

Source lines 106–113; approximately 84 words.

7.2 Bailey’s acknowledgment and “courtesy only” interpretation

Bailey’s May 4 message is important for two different propositions: - Acknowledgment: DGE stated that a DGE miscommunication led the Chair not to share the program response with Cooper at the same time it was submitted to DGE, “as stipulated” in the procedures. - Institutional interpretation: DGE stated that student service was intended as a courtesy, not an opportunity to further contest the program’s account, and that the final decision would not reopen. The acknowledgment is strong evidence of the service failure. The “courtesy only” description is DGE’s interpretation, not language appearing in the quoted Standards provision. Conversely, the absence of “courtesy” from the Standards does not by itself create a reply right. The responsible use is to preserve the textual duty and seek a proportionate record cure, not to convert the omission into an automatic merits reversal.

Source lines 114–122; approximately 136 words.

7.3 Reliance on undisclosed rationales, assertions, exhibits, or extra-record material

Potential prejudice depends on a four-part test: 1. Novelty: Was the item absent from the April 28 notice, May 30 program disposition, timely DGE appeal, or materials Cooper had received? 2. Disputability: Is it a factual assertion, characterization, institutional-history claim, or exhibit that could be materially corrected or contextualized? 3. Reliance: Did the Dean actually rely on it, rather than merely receive it? 4. Materiality: Could the item have affected the analysis of a timely pleaded procedural-error ground? Items that merely repeat an already disclosed core rationale are less prejudicial. Items that add precise timestamps, undocumented institutional-history claims, consultation summaries, negative inferences from the absence of a formal request, or an addendum exhibit are more concerning if they were material and not otherwise available.

Source lines 123–135; approximately 167 words.

7.4 Prejudice and nonprejudice

Factors supporting possible prejudice - Cooper received the Chair response and final decision in the same August 26 transmittal. [11, PDF p. 1.] - The decision expressly says the Dean reviewed the Chair response. [11, PDF p. 3.] - The response and addendum contain detailed factual characterizations beyond a bare denial, including the purpose of personalized rotation expectations, precise M203 timing, an asserted first-ever fifth rotation, accommodation-request and consultation accounts, and a quotation attributed to a CAE official. [11, PDF pp. 6-9.] - Some items could bear on the timely raised grounds of shifting rationale, inconsistent rotation procedures, impossibility, disparate treatment, accommodation context, and communication. - If DGE accepted a material assertion as true without identifying its source or allowing correction of an error, the resulting record could be incomplete…

Source lines 136–156; approximately 258 words.

8. Line/item-specific prejudice table

This table is tied to the actual Chair response and addendum at Case Record 11, PDF pages 5-9. It cross-checks, but does not treat as authority, the production package’s Artifact 12 rows B-001 through B-015. | ID | Chair-response item | Item type and disclosure question | Potential prejudice if new and relied upon | Strongest nonprejudice answer | Bounded reply or cure | | B-001 | The Nov. 19 Academic Plan established unsatisfactory progress and specified requirements. [11, p. 5.] | Program characterization of a known document. Compare the exact plan and original notice. | Could affect whether benchmarks were conditions, independent grounds, or remediation measures. | Cooper had the plan; the Dean’s decision also referenced it. | Quote the operative plan text; correct only a material mischaracterization. | | B-002 | Failure to secure a mentor was sufficient; the IDP also considered over…

Source lines 157–178; approximately 1,105 words. Tables/matrices: | ID | Chair-response item | Item type and disclosure question | Potential prejudice if new and relied upon | Strongest nonprejudice answer | Bounded reply or cure |

9. Theory ladder: keep the levels distinct

Structural heading introducing subordinate content.

Source lines 179–180; approximately 0 words.

Level 1 - Mandatory-procedure theory

Strength: Textually strongest. Proposition: The Chair was required to provide the written response to both DGE and the individual within fifteen business days. Bailey later acknowledged that same-time sharing did not occur because of DGE miscommunication. Limit: The text supplies no express remedy and no unrestricted reply right.

Source lines 181–186; approximately 48 words.

Level 2 - Record-integrity theory

Strength: Strong if tied to an actual relied-on item. Proposition: A final decision should rest on an identifiable, accurate, and reviewable record. The simultaneous transmittal of the response and decision prevented pre-decision identification of a material error in the program submission. Limit: Must show novelty, disputability, reliance, and materiality; receipt alone is not prejudice.

Source lines 187–192; approximately 54 words.

Level 3 - Administrative-irregularity theory

Strength: Established as to the service sequence; conditional as to remedy. Proposition: DGE’s acknowledged miscommunication caused noncompliance with the stated service workflow. That irregularity supports preservation and a proportionate administrative cure. Limit: Administrative irregularity does not automatically invalidate an academic judgment or create authority to reopen a final decision.

Source lines 193–198; approximately 49 words.

Level 4 - Procedural-due-process-like fairness theory

Strength: Useful as a fairness analogy, not as a legal conclusion. Proposition: It is difficult to test the accuracy of decisive adverse material when it is disclosed only with the final decision. Notice, an opportunity to identify a material error, and a reasoned record are familiar fairness values. Limit: Use “due-process-like” or “fundamental fairness” unless counsel advises otherwise. The Standards text, not generalized rhetoric, should lead.

Source lines 199–204; approximately 66 words.

Level 5 - Constitutional theory

Strength: Reserved and unestablished on this record. Proposition: A constitutional procedural-due-process theory would require legal analysis of a protected interest, state action, what process was due, available procedures, prejudice, exhaustion/finality, and remedy. Limit: The current package does not establish those elements or a constitutional violation. Do not characterize Bailey’s acknowledgment as an admission of a constitutional violation. Obtain qualified counsel review before asserting this level.

Source lines 205–210; approximately 66 words.

10. Strongest DGE counterarguments and point-by-point replies

| DGE counterargument | Narrow reply | | The copy was a courtesy only. | “Courtesy” does not appear in the quoted Standards sentence; the text says the Chair “will” provide the response to DGE and the individual. The requested remedy is compliance and record accuracy, not an invented unlimited reply stage. | | There is no sur-rebuttal right. | Agree that no unrestricted sur-rebuttal is express. Distinguish a bounded correction of a material assertion from an additional merits round. | | No new alleged procedural errors or additional information may be considered after thirty days. | Do not add a new ground. Tie each correction to a timely pleaded ground and, where feasible, to material already in the appeal record. Ask DGE to identify whether it considers a proposed correction prohibited and why. | | The Dean’s decision is final and no further appeal is available. | Do not label the req…

Source lines 211–227; approximately 450 words. Tables/matrices: | DGE counterargument | Narrow reply |

11. Institutional cure

Structural heading introducing subordinate content.

Source lines 228–229; approximately 0 words.

11.1 Narrow cure - preferred first request

Request that DGE: 1. place Cooper’s concise preservation paragraph in the DGE administrative record; 2. preserve the native August 7 response, August 14 addendum, all attachments, submission metadata, the version provided to the Dean, and the August 26 transmittal; 3. identify or certify the materials the Dean actually considered; 4. state whether any item in B-001 through B-015 materially informed the decision; 5. accept a short, item-specific correction limited to a timely pleaded ground and existing evidence;

Source lines 230–244; approximately 146 words.

11.2 Broader alternative cure - use only if triggered

If DGE confirms material reliance on a new or inaccurate item and the narrow cure cannot remove its effect, request: 1. withdrawal or administrative vacatur of the August 26 procedural-appeal decision solely for a corrected review; 2. service of the complete program response, addendum, exhibits, and relied-on record; 3. a short fixed period for Cooper to submit an itemized correction confined to the original procedural grounds; 4. no new grounds and no unrelated new evidence; 5. a new review by an authorized decision-maker on the closed corrected record;

Source lines 245–257; approximately 144 words.

11.3 Cure proportionality

No material reliance: preservation notation and record certification. - Minor correctable error: append a correction and issue a clarification. - Material reliance, outcome unaffected after correction: reasoned harmlessness determination. - Material reliance, outcome potentially affected: limited reconsideration. - Systemic or repeated record failures: counsel review and process-improvement request, without inferring motive.

Source lines 258–265; approximately 47 words.

12. DGE, CDP, and CRO use

Structural heading introducing subordinate content.

Source lines 266–267; approximately 0 words.

12.1 DGE use

DGE is the primary forum for the service record and any administrative cure because it administered the procedural appeal, received the Chair response, issued the final decision, and acknowledged the miscommunication. The immediate DGE objective is record integrity, not a second unrestricted appeal. Bailey’s May 4 message also confirms that the separate non-discrimination appeal remained active and that DGE expected to review appropriately redacted investigation materials after CRO completed its process. [Case Record 10, PDF p. 2.] The Standards state that DGE will determine whether Investigation Materials reflect “substantive mitigating circumstances that could have affected” academic performance and, if possible substantive mitigating circumstances appear, refer the appeal and Investigation Materials to CDP. [Case Record 06, printed p. 33 / PDF p. 34.] The Standards do not resolve in…

Source lines 268–275; approximately 165 words.

12.2 CDP use

If DGE refers the non-discrimination appeal to CDP, use the Bailey issue for a limited purpose: - explain the reliability and completeness of the academic-disqualification record; - identify any materially disputed program assertion that overlaps the Investigation Materials; - ask CDP to distinguish established facts, program positions, and unresolved disputes; - connect only source-supported circumstances to academic-performance mitigation; and - request that any recommendation not treat an undisclosed program assertion as independently established.

Source lines 276–287; approximately 104 words.

12.3 CRO scope boundary

The Bailey service issue is principally a DGE academic-appeal record-integrity issue. It is not automatically a discrimination finding, retaliation finding, or Procedure 230.2 violation. Use it with CRO only if: - the actual report places the issue within formal scope; - CRO relies on the Chair response or related materials and record accuracy is material; - the issue is relevant to a formally investigated accommodation, discrimination, harassment, or retaliation theory; or - the report expressly invites a procedural correction or recommendation. Otherwise, preserve it outside the CRO merits submission. Do not infer motive, concealment, coordination, or intentional manipulation from the service sequence.

Source lines 288–298; approximately 99 words.

13. Hold-unless-triggered recommendation

Default: Hold this memorandum as private strategy work product. Preserve the concise paragraph and supporting records, but do not submit the full memorandum solely because the CRO report arrives. Deploy the narrow version if any of these observable triggers occurs: 1. DGE asks for an update, mitigation submission, or confirmation that the non-discrimination appeal may resume. 2. DGE or CDP cites the Chair response, addendum, or an item in B-001 through B-015. 3. The CRO report relies on a materially disputed program assertion from those pages. 4. The actual report omits or misstates an item whose correction affects a live hearing/comments or DGE mitigation decision.

Source lines 299–321; approximately 189 words.

14. Scenario and timing deployment table

| CRO/report scenario | Timing | Bailey deployment | Objective | Avoid | | 1. Broad favorable report | After preserving and verifying the report | Usually hold full memo; include concise preservation only if DGE record use is imminent. | Preserve favorable findings and prevent a disputed program assertion from diluting them. | Turning a favorable posture into a broad collateral dispute. | | 2. Mixed partial substantiation | During DGE mitigation crosswalk preparation | Use the narrow memo only for response items that conflict with verified CRO findings or material mitigation facts. | Clarify record weight and secure a bounded correction. | Claiming every noncitation or disagreement proves nonconsideration. | | 3. Factual concessions / no formal violation | Before DGE decides whether mitigation is possible | Tie favorable factual findings to the exact Chair-response item; request record…

Source lines 322–337; approximately 480 words. Tables/matrices: | CRO/report scenario | Timing | Bailey deployment | Objective | Avoid |

15. Deployment-ready record request

If a trigger occurs, the following bounded request can accompany the concise preservation paragraph: > Please identify the version of the NSIDP Chair’s response, addendum, attachments, and other materials that the decision-maker actually considered; preserve the native submissions and metadata; and state whether any disputed item identified in my attached table materially informed the decision. I do not seek to add a new procedural-error ground or an unrestricted sur-rebuttal. I request permission to submit a short record correction limited to an existing timely ground and the specific item relied upon. If no disputed item was material, please place this preservation notice in the record. If a material item was inaccurate or materially incomplete, please provide the narrowest available administrative cure and confirm the effect, if any, on the separate non-discrimination appeal and DGE/…

Source lines 338–343; approximately 134 words.

16. Record package to preserve

Keep these together in the private administrative-record folder: 1. Native July 21 and July 31, 2025 DGE service-request messages. 2. Cooper’s timely procedural appeal and the exact evidence package uploaded to DGE, with upload metadata. 3. NSIDP’s August 7 response in native/original PDF form. 4. NSIDP’s August 14 addendum and each attachment in native/original form. 5. DGE’s August 26 transmittal with full headers.

Source lines 344–360; approximately 147 words.

17. Validation and residual questions

Structural heading introducing subordinate content.

Source lines 361–362; approximately 0 words.

Completed validation

The mandatory service sentence and no-new-information sentence were text-extracted from Case Record 06 and visually checked on printed page 32/PDF page 33. - The July 21 workflow statement, August 26 transmittal, Dean decision, August 7 response, and August 14 addendum were checked in Case Record 11. - Bailey’s May 4 acknowledgment, apology, “courtesy only” interpretation, no-further-contest position, and no-reopening position were checked in Case Record 10. - Every B-001 through B-015 row is tied to Case Record 11, PDF pages 5-9, or expressly labeled as a comparison category. - This memorandum rejects an express unrestricted-sur-rebuttal proposition and does not claim a constitutional violation.

Source lines 363–370; approximately 100 words.

Matters requiring UCLA confirmation or counsel review

1. The exact native submission timestamps for the August 7 response, August 14 addendum, and each attachment. 2. The exact version and materials Dean Kite actually reviewed. 3. Whether any B-001 through B-015 item materially affected the decision. 4. Whether DGE has authority to correct, reconsider, vacate, or reissue a final procedural-appeal decision for an acknowledged service irregularity. 5. Whether a bounded record correction is “additional information” under DGE’s interpretation when it addresses a timely ground and a program assertion added after filing. 6. What materials DGE will receive from CRO and when DGE considers the investigatory process “completed.”

Source lines 371–381; approximately 123 words.

18. Source notes

Case Record 06: 01_CASE_RECORD/06_UCLA_Standards_and_Procedures_for_Graduate_Study.pdf, especially printed pp. 32-33 / PDF pp. 33-34. - Case Record 10: 01_CASE_RECORD/10_DGE_Update_2026-04-24_to_2026-05-04.pdf, PDF pp. 1-2. - Case Record 11: 01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, PDF pp. 1-12, especially pp. 1-10. - Cross-check only: 12_BAILEY_PREJUDICE_TABLE.xlsx, rows B-001 through B-015. This derivative table is not treated as primary evidence. > PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 382–389; approximately 67 words.

14_READY_TO_DEPLOY_TEMPLATE_SUITE.md

2,019 lines; 15,590 words; 175 indexed headings/sections.

Ready-to-Deploy Template Suite

\<!– markdownlint-disable MD013 MD024 MD036 --> > PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Fixed reference date: July 22, 2026 (PDT) Prepared for: Cooper Beaman Status: Internal drafts only. No CRO investigation report or transmittal exists in the record. Nothing in this suite has been sent or submitted.

Source lines 1–10; approximately 54 words.

Deployment controls

1. Preserve the warning above in every detached template. 2. Replace bracketed fields only from the native transmittal, the actual report, an identified UCLA instruction, or a decision Cooper has made after review. 3. Verify the recipient and submission method from the current transmittal or a current written UCLA instruction. No address or portal is supplied here. 4. Preserve the original transmission, attachments, metadata, and SHA-256 hashes before editing a working copy. 5. Treat “issuance” as the date of transmission, but calculate both counting conventions because the official sources do not state whether the anchor date is day zero or day one. 6. Work to the earlier plausible date unless UCLA confirms the counting rule in writing. Observed holidays and possible curtailment dates are sensitivity scenarios, not established campus closures.

Source lines 11–25; approximately 282 words.

Common future-dependent fields

[REPORT_DATE], [REPORT_TITLE], [REPORT_FILENAME], [REPORT_PAGE] - [TRANSMITTAL_TIMESTAMP], [TRANSMITTAL_TIME_ZONE], [TRANSMITTAL_CHANNEL] - [CONFIRMED_RECIPIENT], [CONFIRMED_SUBMISSION_METHOD] - [EXACT_FINDING], [EXACT_QUOTATION], [EXACT_TRANSMITTAL_LANGUAGE] - [MISSING_ITEM], [CORRUPTION_OR_ACCESS_PROBLEM], [REDACTION_ISSUE] - [ASSUMPTION_A_DATE], [ASSUMPTION_B_DATE], [EARLIEST_PLAUSIBLE_DATE]

Source lines 26–38; approximately 24 words.

1. Report receipt acknowledgment

Structural heading introducing subordinate content.

Source lines 39–40; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Acknowledgment of receipt — CRO investigation report Dear [CONFIRMED_RECIPIENT], I acknowledge receipt of the CRO investigation report and accompanying materials transmitted on [TRANSMITTAL_TIMESTAMP] [TRANSMITTAL_TIME_ZONE] through [TRANSMITTAL_CHANNEL]. I am preserving the transmission and reviewing the materials. This acknowledgment does not state that the transmission is complete and does not waive any right or position concerning a hearing, written comments, completeness, correction, redaction, issuance, deadline calculation, finality, DGE sequencing, or other downstream use. Sincerely,

Source lines 41–55; approximately 90 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Acknowledgment and inventory of CRO investigation-report transmission Dear [CONFIRMED_RECIPIENT], Thank you for the transmission received on [TRANSMITTAL_TIMESTAMP] [TRANSMITTAL_TIME_ZONE] through [TRANSMITTAL_CHANNEL]. The materials presently received are: - [REPORT_FILENAME] — [PAGE_COUNT] pages; - [ATTACHMENT_OR_APPENDIX_1] — [PAGE_COUNT_OR_FILE_DESCRIPTION];

Source lines 56–81; approximately 184 words.

2. Missing-materials request

Structural heading introducing subordinate content.

Source lines 82–83; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Request for complete CRO report transmission and missing materials Dear [CONFIRMED_RECIPIENT], The transmission received on [TRANSMITTAL_TIMESTAMP] appears incomplete or inaccessible because [MISSING_ITEM_OR_ACCESS_PROBLEM]. Please provide the complete native report and the missing or readable version of [MISSING_ITEM], together with all referenced appendices, attachments, evidence lists, and redaction explanations. Please also confirm in writing whether UCLA regards the incomplete transmission or the completed transmission as the operative issuance event and identify the resulting hearing, comments, and finalization dates. I am continuing to preserve the earliest plausible deadline while awaiting clarification. Sincerely,

Source lines 84–98; approximately 108 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Completeness and access request — CRO investigation report transmitted [TRANSMITTAL_TIMESTAMP] Dear [CONFIRMED_RECIPIENT], I am writing promptly after receiving the CRO transmission on [TRANSMITTAL_TIMESTAMP] [TRANSMITTAL_TIME_ZONE]. My preservation and opening review identified the following objective completeness or access issues: 1. Missing item: [MISSING_ITEM]. The report or transmittal refers to it at [REPORT_PAGE_OR_TRANSMITTAL_LOCATION], but it was not included. 2. File problem: [CORRUPTION_OR_ACCESS_PROBLEM]. The affected file is [AFFECTED_FILENAME].

Source lines 99–140; approximately 307 words.

3. Issuance and deadline confirmation request

Structural heading introducing subordinate content.

Source lines 141–142; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Request to confirm issuance event and Procedure 230.2 dates Dear [CONFIRMED_RECIPIENT], Please confirm the date, time, and time zone UCLA treats as issuance of the report transmitted on [TRANSMITTAL_TIMESTAMP]. Please also confirm the controlling dates for the 10-Day hearing request, the 15-Day no-hearing comments period, and the 20-Day no-hearing finalization period, and state whether UCLA counts the transmission date itself as Day 1. Pending confirmation, I am preserving both counting assumptions and working to the earlier plausible date, [EARLIEST_PLAUSIBLE_DATE]. Sincerely,

Source lines 143–157; approximately 100 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Written confirmation requested — report issuance, counting convention, and controlling dates Dear [CONFIRMED_RECIPIENT], The CRO materials were transmitted on [TRANSMITTAL_TIMESTAMP] [TRANSMITTAL_TIME_ZONE] through [TRANSMITTAL_CHANNEL]. The report itself displays [REPORT_DATE], and the transmittal states: “[EXACT_TRANSMITTAL_LANGUAGE].” Attachment B to UCLA Procedure 230.2 defines “issuance” as the date of transmission. Procedure 230.2 defines capitalized “Days” as University business days excluding Saturdays, Sundays, and days on which the campus is closed. The reviewed text does not specify whether the transmission date is excluded as day zero or counted as Day 1 when it is a qualifying University business day. My current calculations therefore preser…

Source lines 158–193; approximately 276 words.

4. Good-cause extension request

Structural heading introducing subordinate content.

Source lines 194–195; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Good-cause request for reasonable extension under Procedure 230.2 Dear [CONFIRMED_RECIPIENT], I respectfully request a reasonable extension of [REQUESTED_EXTENSION], through [REQUESTED_NEW_DATE], for the [HEARING_REQUEST / COMMENTS / OTHER_IDENTIFIED] period. Good cause exists because [CONCISE_OBJECTIVE_REASON]. I am acting diligently, will continue preparing while this request is pending, and do not treat the request as automatically tolling the current period. Please confirm the decision and any revised date in writing. Sincerely,

Source lines 196–210; approximately 86 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Written good-cause extension request — [REPORT_TITLE_OR_CASE_IDENTIFIER] Dear [CONFIRMED_RECIPIENT], Under § VI.D of UCLA Procedure 230.2, I respectfully request a reasonable extension of [REQUESTED_EXTENSION], making [REQUESTED_NEW_DATE] the requested date for [SPECIFIC_PROCEDURAL_ACT]. The request is based on the following documented circumstances: 1. [OBJECTIVE_CIRCUMSTANCE_1];

Source lines 211–255; approximately 256 words.

5. Minimal hearing request

Structural heading introducing subordinate content.

Source lines 256–257; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Timely request for formal grievance hearing under UCLA Procedure 230.2 Dear [CONFIRMED_RECIPIENT], I disagree with findings in the investigation report issued by transmission on [TRANSMITTAL_DATE] and timely request a formal grievance hearing under UCLA Procedure 230.2. Choose and retain one complete statement: I WILL NOT BE ASSISTED BY A REPRESENTATIVE. / I WILL BE ASSISTED BY [REPRESENTATIVE_NAME]. THE REPRESENTATIVE’S ATTORNEY STATUS IS [ATTORNEY / NOT AN ATTORNEY]. Please confirm receipt, the operative request date, and the next scheduling and disclosure steps. I respectfully request permission to provide a focused grounds addendum after confirming the complete record and hearing schedule.

Source lines 258–274; approximately 119 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Formal grievance-hearing request — CRO report transmitted [TRANSMITTAL_DATE] Dear [CONFIRMED_RECIPIENT], I disagree with the following findings or material components of the investigation report transmitted on [TRANSMITTAL_TIMESTAMP]: 1. [DISPUTED_FINDING_OR_CONCLUSION_1] at [REPORT_PAGE]; 2. [DISPUTED_FINDING_OR_CONCLUSION_2] at [REPORT_PAGE]; and

Source lines 275–311; approximately 284 words.

6. Full hearing grounds memorandum

Structural heading introducing subordinate content.

Source lines 312–313; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Memorandum To: [CONFIRMED_RECIPIENT] From: Cooper Beaman Date: [SUBMISSION_DATE] Re: Preliminary grounds supporting timely hearing request

Source lines 314–329; approximately 128 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Memorandum To: [CONFIRMED_RECIPIENT] From: Cooper Beaman Date: [SUBMISSION_DATE] Re: Grounds supporting request for formal grievance hearing regarding [REPORT_TITLE]

Source lines 330–339; approximately 34 words.

I. Request and procedural posture

The CRO transmitted the investigation report on [TRANSMITTAL_TIMESTAMP]. I submitted a written hearing request on [HEARING_REQUEST_TIMESTAMP]. My request stated [REPRESENTATION_STATEMENT]. This memorandum identifies the material disputes for which a hearing is warranted and the focused proof needed to resolve them. I do not seek to relitigate favorable or immaterial findings. I request review of the specific findings below because they affect the report’s conclusions concerning disability discrimination, failure to accommodate, harassment, retaliation, causation, harm, or remedy, and may also affect the separate DGE/CDP mitigation analysis.

Source lines 340–345; approximately 86 words.

II. Findings preserved

I do not challenge the following findings except to the extent the report later uses them inconsistently: 1. [FAVORABLE_OR_UNDISPUTED_FINDING_1] at [REPORT_PAGE]; 2. [FAVORABLE_OR_UNDISPUTED_FINDING_2] at [REPORT_PAGE]; and 3. [FAVORABLE_OR_UNDISPUTED_FINDING_3] at [REPORT_PAGE]. Preserving these findings narrows the hearing and avoids unnecessary proof.

Source lines 346–355; approximately 40 words.

III. Material factual disputes

Structural heading introducing subordinate content.

Source lines 356–357; approximately 0 words.

A. Respondent 1 — NEURO M203 accommodation

The NOI investigated whether Dr. James Bisley failed to accommodate my disability when I requested to take the NEURO M203 midterm on a later date. The report finds [EXACT_FINDING] at [REPORT_PAGE]. I dispute the finding because [REPORT-SPECIFIC_REASON]. The relevant proof is [EXHIBIT], [EXHIBIT], and anticipated testimony requiring confirmation from [WITNESS] concerning [NARROW_PROPOSITION]. This proof is material to notice, the requested modification, the response, and any asserted academic or administrative justification. It is not cumulative because [NONCUMULATIVE_VALUE].

Source lines 358–363; approximately 76 words.

B. Respondent 2 — mentor decision and alleged harassment

The NOI investigated whether Dr. Carrie Bearden declined to serve as my primary faculty mentor on a discriminatory basis and whether specified statements constituted disability-based harassment. The report finds [EXACT_FINDING] at [REPORT_PAGE]. I dispute [SPECIFIC_COMPONENT] because [REPORT-SPECIFIC_REASON]. The focused proof is [EXHIBIT] and anticipated testimony requiring confirmation from [WITNESS] concerning [NARROW_PROPOSITION]. If the report relies on the fifth-rotation evaluation or ENIGMA-related timing, the hearing should distinguish my reported completion of the submission from the later external acknowledgment and determine what the decision-maker knew and relied upon.

Source lines 364–369; approximately 86 words.

C. Respondent 3 — academic-disqualification recommendation and alleged harassment

The NOI investigated whether Dr. Felix Schweizer’s recommendation for academic disqualification was discriminatory and whether two identified statements constituted harassment. The report finds [EXACT_FINDING] at [REPORT_PAGE]. I dispute [SPECIFIC_COMPONENT] because [REPORT-SPECIFIC_REASON]. The focused proof is [EXHIBIT] and anticipated testimony requiring confirmation from [WITNESS] concerning [NARROW_PROPOSITION]. The hearing should distinguish the program’s stated academic rationale from the separate questions of disability-related circumstances, notice, accommodation efforts, timing, and causation.

Source lines 370–375; approximately 67 words.

IV. Credibility and methodology issues

The report credits [PERSON_OR_SOURCE] over [PERSON_OR_SOURCE] on [DISPUTED_PROPOSITION] at [REPORT_PAGE]. The stated basis is [EXACT_REPORT_BASIS]. I request live examination because [MATERIAL_REASON_LIVE_TESTIMONY_IS_NEEDED]. The following methodology questions are narrow and outcome-relevant: 1. What evidence did the investigator use to resolve [CONTRADICTION]? 2. Was [IDENTIFIED_EVIDENCE] obtained and considered, and if so, for what proposition? 3. Was [PROFFERED_WITNESS] interviewed? If not, what evidentiary gap remained? 4. How did the report distinguish a party account, a witness proffer, an authenticated record, and an independently corroborated fact?

Source lines 376–389; approximately 118 words.

V. Scope, omission, and completeness

On April 20, 2026, CRO stated that the NOI would not be amended but that the evidence, witnesses, and theories presented would be considered and that the ultimate report would reflect them. The report’s treatment of [IDENTIFIED_CONTEXT_OR_EVIDENCE] is [EXACT_REPORT_TREATMENT_OR_SOURCE_SILENCE]. The issue is material because [CONNECTION_TO_FORMAL_ALLEGATION_OR_CONTEXT]. The requested cure is limited: [CLARIFICATION / ADMISSION_OF_EVIDENCE / TESTIMONY / CORRECTED_RECORD_ENTRY]. I do not contend that every out-of-scope actor became a respondent or that noncitation alone proves nonconsideration.

Source lines 390–395; approximately 71 words.

VI. Policy, causation, harm, and remedy

The report applies [POLICY_VERSION_OR_STANDARD] and concludes [EXACT_CONCLUSION] at [REPORT_PAGE]. I request review of [SPECIFIC_ELEMENT] because [ELEMENT-SPECIFIC_REASON]. The hearing should separately determine: - what conduct occurred; - what each decision-maker knew and when; - whether a requested accommodation or interactive-process issue was material; - whether disability was a causal factor under the governing standard;

Source lines 396–410; approximately 102 words.

VII. Proposed evidence and witnesses

I propose the exhibits listed in [PROPOSED_EXHIBIT_LIST_FILENAME]. For each exhibit, the list states its source, authentication basis, disputed issue, and noncumulative value. I propose the following witnesses only to the extent the Hearing Officer finds their testimony relevant and noncumulative: 1. Cooper Beaman — first-hand account of [NARROW_TOPICS]; 2. the investigator/report author — methodology and record treatment; 3. [RESPONDENT_OR_DECISION-MAKER] — basis, knowledge, and timing of [MATERIAL_DECISION]; and 4. [CORROBORATING_OR_COMPARATOR_WITNESS] — anticipated testimony requiring confirmation concerning [NARROW_PROPOSITION].

Source lines 411–423; approximately 96 words.

VIII. Requested hearing management

I respectfully request: 1. confirmation of the hearing date and the independently anchored 60-Day completion calculation; 2. at least 10 Days’ written notice; 3. a written disclosure date consistent with § VI.B.3; 4. a reasonable process to address a good-cause Hearing Officer challenge, if one arises; 5. identification of the complete record supplied to the Hearing Officer;

Source lines 424–435; approximately 85 words.

IX. Requested outcome

I ask the Hearing Officer to make independent findings on the disputed issues, correct any unsupported adverse finding, preserve supported favorable findings, and recommend relief within the authority provided by Procedure 230.2. Requested implementation by another office should be identified as a recommendation, referral, or negotiated option rather than attributed to an office lacking authority. Respectfully submitted, Cooper Beaman

Source lines 436–444; approximately 60 words.

7. Written comments submission

Structural heading introducing subordinate content.

Source lines 445–446; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Written comments on CRO investigation report Dear [CONFIRMED_RECIPIENT], I submit these written comments under § VI.A.4 of UCLA Procedure 230.2 concerning the report transmitted on [TRANSMITTAL_DATE]. I preserve [FAVORABLE_FINDING] but disagree with [DISPUTED_FINDING] at [REPORT_PAGE] because [CONCISE_REASON]. I have not requested a hearing within the permitted period. Without conceding that use of the comments route constitutes acceptance of every finding, I request that these comments be attached to the report as an appendix and included in any downstream transmission. Sincerely,

Source lines 447–461; approximately 101 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 462–465; approximately 16 words.

Written Comments of Cooper Beaman on the CRO Investigation Report

Report transmitted: [TRANSMITTAL_TIMESTAMP] Comments submitted: [SUBMISSION_TIMESTAMP] Procedure: UCLA Procedure 230.2, §§ VI.A.4–5

Source lines 466–471; approximately 15 words.

Introduction and route

I submit these comments for the University’s consideration and for attachment to the report. I have not requested a formal hearing within the permitted period. The operative procedure permits comments when no timely hearing is requested; Attachment B and the summary language also refer to “acceptance,” but the reviewed sources do not define an affirmative act of acceptance. Accordingly, these comments identify the findings I preserve and those I dispute without conceding an unstated waiver or acceptance of every finding.

Source lines 472–475; approximately 80 words.

Executive summary

The report concludes [OVERALL_DISPOSITION]. I agree that the record establishes [FAVORABLE_OR_UNDISPUTED_POINT]. I disagree with [CENTRAL_DISPUTED_POINT] because [CONCISE_REASON]. I also request clarification or correction concerning [MATERIAL_OMISSION_OR_ERROR]. My comments do not treat an allegation as an established fact merely because it was reported, do not treat a proffer as confirmed testimony, and do not infer nonconsideration from noncitation. They distinguish the report’s findings from my account and from the separate DGE mitigation standard.

Source lines 476–481; approximately 71 words.

Findings preserved

I ask the University to preserve the following findings in the final report and every transmitted copy: 1. [EXACT_FAVORABLE_FINDING_OR_PARAPHRASE_LABELLED_AS_SUCH], [REPORT_PAGE]; 2. [EXACT_FAVORABLE_FINDING_OR_PARAPHRASE_LABELLED_AS_SUCH], [REPORT_PAGE]; and 3. [EXACT_FAVORABLE_FINDING_OR_PARAPHRASE_LABELLED_AS_SUCH], [REPORT_PAGE]. These findings are material to [CRO_ELEMENT / HARM / REMEDY / DGE_MITIGATION].

Source lines 482–491; approximately 36 words.

Disputed findings and corrections

Structural heading introducing subordinate content.

Source lines 492–493; approximately 0 words.

Respondent 1 — NEURO M203 accommodation

The report states: “[EXACT_QUOTATION]” at [REPORT_PAGE]. I disagree with [SPECIFIC_FINDING_OR_REASONING]. The smallest record passage supporting my correction is [SOURCE_AND_PINPOINT], which shows [NARROW_PROPOSITION]. I request that the report be corrected or clarified to state [PRECISE_REQUESTED_WORDING_OR_ACTION].

Source lines 494–497; approximately 34 words.

Respondent 2 — mentor decision and specified statements

The report states: “[EXACT_QUOTATION]” at [REPORT_PAGE]. I agree with [UNCONTESTED_COMPONENT] but dispute [CONTESTED_COMPONENT]. The relevant record is [SOURCE_AND_PINPOINT]. If the report relies on fifth-rotation work or external collaborator timing, the final record should distinguish [DATE_OF_STUDENT_ACTION] from [DATE_OF_EXTERNAL_ACKNOWLEDGMENT].

Source lines 498–501; approximately 37 words.

Respondent 3 — disqualification recommendation and specified statements

The report states: “[EXACT_QUOTATION]” at [REPORT_PAGE]. I disagree with [SPECIFIC_COMPONENT] because [SOURCE-GROUNDED_REASON]. The final record should distinguish the program’s stated academic grounds from the separate questions of disability-related circumstances, notice, accommodation efforts, timing, and causation.

Source lines 502–505; approximately 35 words.

Material omissions and indeterminate treatment

The report does not mention [ITEM], or its treatment is indeterminate. I do not infer from noncitation that the item was not considered. I request confirmation whether it was: - considered but not cited; - expressly discounted; - treated as out of scope; - treated as cumulative; - not actually received;

Source lines 506–521; approximately 121 words.

Credibility, causation, and harm

The report credits [SOURCE] concerning [PROPOSITION] at [REPORT_PAGE]. My response is [SOURCE-GROUNDED_RESPONSE]. The report’s causation analysis should also account for [MATERIAL_TIMING_OR_KNOWLEDGE_FACT], while preserving [CONTRARY_EVIDENCE]. The report’s harm analysis states [EXACT_OR_PARAPHRASED_TREATMENT]. I request clarification concerning [ACADEMIC / HEALTH / FUNDING / STATUS / PLACEMENT_EFFECT] because [RECORD_SUPPORT].

Source lines 522–527; approximately 41 words.

DGE/CDP relevance

The DGE/CDP inquiry is not identical to the CRO liability determination. Under the Standards, DGE determines whether the Investigation Materials reflect “substantive mitigating circumstances that could have affected academic performance.” The following authenticated findings remain relevant to that question even if the report does not substantiate every alleged policy violation: 1. [REPORT_FINDING_ABOUT_DISABILITY_OR_FUNCTIONAL_LIMITATION]; 2. [REPORT_FINDING_ABOUT_UNIVERSITY_NOTICE]; 3. [REPORT_FINDING_ABOUT_ACCOMMODATION_OR_INTERACTIVE_PROCESS]; 4. [REPORT_FINDING_ABOUT_ROTATION_MENTOR_M203_FUNDING_OR_PLACEMENT]; and 5. [REPORT_FINDING_ABOUT_TEMPORAL_OR_ACADEMIC_EFFECT].

Source lines 528–539; approximately 89 words.

Requested action

I respectfully request that the University: 1. attach these comments to the report under § VI.A.5; 2. preserve the favorable findings identified above; 3. correct the objectively verifiable errors identified in [CORRECTION_TABLE_FILENAME]; 4. clarify the treatment of the indeterminate items without equating noncitation with nonconsideration; 5. identify any item the University did not receive or could not review;

Source lines 540–556; approximately 93 words.

8. Correction and omission table cover message

Structural heading introducing subordinate content.

Source lines 557–558; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Report correction and omission table for attachment to the record Dear [CONFIRMED_RECIPIENT], Attached is [CORRECTION_OMISSION_TABLE_FILENAME], keyed to the report’s pages. It separates objective corrections, disputed interpretations, and items whose treatment is indeterminate. It does not infer that noncitation means nonconsideration. Please append the table to my written comments and preserve it with the final report record. Sincerely,

Source lines 559–573; approximately 76 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Cover message — page-specific correction, omission, and record-treatment table Dear [CONFIRMED_RECIPIENT], I submit the attached [CORRECTION_OMISSION_TABLE_FILENAME] as a structured companion to my written comments on the report transmitted on [TRANSMITTAL_DATE]. The table uses separate categories so that different issues are not collapsed: - objective correction — a date, name, quotation, document description, or other verifiable entry appears inaccurate;

Source lines 574–616; approximately 318 words.

9. DGE notice of report receipt and continuing Procedure 230.2 rights

Structural heading introducing subordinate content.

Source lines 617–618; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Notice of CRO report receipt and continuing Procedure 230.2 rights Dear [CONFIRMED_DGE_RECIPIENT], I received a CRO investigation-report transmission on [TRANSMITTAL_TIMESTAMP]. I am preserving and reviewing the report and may timely exercise rights under Procedure 230.2, including [HEARING / COMMENTS / POST-HEARING_OR_APPEAL_RIGHTS_AS_APPLICABLE]. Please do not treat this notice as my agreement that the investigatory process has “completed.” Please confirm what DGE has received and whether DGE will preserve the abeyance while the applicable Procedure 230.2 route is clarified or completed. Sincerely,

Source lines 619–633; approximately 100 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Protective notice to DGE — CRO report receipt, continuing rights, and sequencing Dear [CONFIRMED_DGE_RECIPIENT], I am providing prompt notice that CRO transmitted an investigation report on [TRANSMITTAL_TIMESTAMP] [TRANSMITTAL_TIME_ZONE]. The transmitted materials presently consist of [RECEIVED_MATERIALS]. My current Procedure 230.2 posture is [CURRENT_PROCEDURE_POSTURE]; the event date, if applicable, is [POSTURE_EVENT_DATE]. The Standards state that DGE holds the nondiscrimination-based academic-disqualification appeal in abeyance while the investigatory office is processing the allegations and until that process has completed. The Standards do not define the completion milestone. This notice therefore does not concede that initial report issuance, no-…

Source lines 634–664; approximately 302 words.

10. DGE continuing-abeyance request

Structural heading introducing subordinate content.

Source lines 665–666; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Request to continue DGE abeyance pending confirmed completion Dear [CONFIRMED_DGE_RECIPIENT], I respectfully request confirmation that DGE will continue the abeyance of my nondiscrimination-based academic-disqualification appeal while [TIMELY_PROCEDURE_230_2_ROUTE] remains pending. The Standards do not define when the investigatory process has completed. This request preserves that uncertainty and asks DGE to identify its completion milestone before acting. Sincerely,

Source lines 667–681; approximately 75 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Continuing-abeyance request — nondiscrimination-based academic-disqualification appeal Dear [CONFIRMED_DGE_RECIPIENT], The Standards provide that, while an investigatory office is processing the allegations, DGE will hold the appeal decision in abeyance until that process has completed. DGE confirmed on May 4, 2026 that my nondiscrimination-based appeal remained active and that the DGE Dean would review appropriately redacted investigated materials produced by CRO. CRO transmitted [REPORT_TITLE] on [TRANSMITTAL_TIMESTAMP]. I have [REQUESTED A HEARING / ELECTED WRITTEN COMMENTS / RECEIVED A HEARING REPORT / RECEIVED A VICE CHANCELLOR DECISION / FILED AN APPEAL], and the following step remains pending: [PENDING_STEP]. Because the Standards do not define “c…

Source lines 682–711; approximately 274 words.

11. DGE Investigation Materials and clock-confirmation request

Structural heading introducing subordinate content.

Source lines 712–713; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Request to identify DGE Investigation Materials and receipt date Dear [CONFIRMED_DGE_RECIPIENT], Please identify every Investigation Material DGE has received, the date and time of receipt, and the date DGE regards as the start of any 30-calendar-day period. Please also state whether the materials are complete and whether later Procedure 230.2 comments, hearing materials, or decisions will be added. This request does not concede that the investigatory process has completed. Sincerely,

Source lines 714–728; approximately 90 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Investigation Materials inventory, completion milestone, and 30-calendar-day clock Dear [CONFIRMED_DGE_RECIPIENT], The Standards use “Investigation Materials” to refer to appropriately redacted versions of any written investigation report provided after the investigatory office completes its process. They direct DGE, within 30 calendar days of receipt of the Investigation Materials, either to notify the individual that the appeal is denied when the materials do not reflect possible substantive mitigating circumstances or to refer the appeal and materials to CDP when they do. To create an accurate record, please confirm: 1. Inventory: Has DGE received the CRO report, transmittal email, appendices, evidence list, redaction notice, written comments, hearing…

Source lines 729–765; approximately 323 words. Tables/matrices: | Item | Version/date | Received by Cooper | Known DGE status |

12. DGE mitigation-crosswalk cover memorandum

Structural heading introducing subordinate content.

Source lines 766–767; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Memorandum To: [CONFIRMED_DGE_RECIPIENT] From: Cooper Beaman Date: [SUBMISSION_DATE] Re: Investigation Materials and substantive mitigating circumstances

Source lines 768–781; approximately 87 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Memorandum To: [CONFIRMED_DGE_RECIPIENT] From: Cooper Beaman Date: [SUBMISSION_DATE] Re: Report-to-record crosswalk under the DGE substantive-mitigation standard

Source lines 782–791; approximately 32 words.

Question presented

Do the Investigation Materials reflect possible “substantive mitigating circumstances that could have affected academic performance” within the meaning of the Standards and Procedures for Graduate Study at UCLA?

Source lines 792–795; approximately 28 words.

Short answer

Yes. The attached crosswalk identifies [NUMBER] source-grounded circumstances linking disability-related functional limitations, University notice, accommodation or interactive-process issues, and the timing of academic events to the rotation, faculty-mentor, NEURO M203, funding, placement, or alternative-program issues that preceded academic disqualification. This conclusion does not depend on treating every CRO allegation as substantiated.

Source lines 796–799; approximately 51 words.

Distinct standards

CRO determines whether specified conduct violated the governing nondiscrimination policy under its applicable elements and burden of proof. DGE asks a different and broader academic-review question: whether the Investigation Materials reflect possible substantive mitigating circumstances that could have affected academic performance. A fact can be relevant to mitigation even when CRO finds that it does not establish discriminatory causation, severity, harm, or formal liability.

Source lines 800–803; approximately 64 words.

Crosswalk method

Each row in [MITIGATION_CROSSWALK_FILENAME] identifies: - the exact report fact or conclusion and page; - the epistemic status of the entry; - the disability-related circumstance; - University notice; - any accommodation or interactive-process issue;

Source lines 804–823; approximately 97 words.

Principal circumstances

Structural heading introducing subordinate content.

Source lines 824–825; approximately 0 words.

1. Disability-related functional limitations and notice

The report states [EXACT_REPORT_FINDING_OR_PARAPHRASE] at [REPORT_PAGE]. The University record also documents [SOURCE-ESTABLISHED_NOTICE_FACT]. Together, these materials bear on whether functional limitations were present and known during [ACADEMIC_PERIOD_OR_EVENT].

Source lines 826–829; approximately 26 words.

2. Accommodation and interactive-process context

The report states [EXACT_REPORT_TREATMENT] at [REPORT_PAGE]. The crosswalk identifies the request, response, timing, and any contrary institutional explanation. The mitigation question is not limited to whether CRO found a formal failure to accommodate; it includes whether the documented circumstances could have affected performance or the ability to meet program benchmarks.

Source lines 830–833; approximately 50 words.

3. Rotation and faculty-mentor effects

The academic-disqualification recommendation identified failure to secure a primary faculty mentor after five rotations as its stated basis. The report’s findings concerning [MENTOR_DECISION / ROTATION_EXPECTATIONS / PROGRAM_SUPPORT / DISABILITY_RELATED_FRICTION] are relevant to whether the mentor-search circumstances could have affected that outcome.

Source lines 834–837; approximately 38 words.

4. NEURO M203 and fifth-rotation effects

The crosswalk separately treats NEURO M203, the fifth-rotation evaluation, external collaborator timing, and the program’s later explanations. It preserves both the program position and Cooper’s account and asks DGE to determine their mitigation significance rather than assume that an academic label ends the inquiry.

Source lines 838–841; approximately 44 words.

5. Funding, placement, and alternative-program effects

The materials concerning funding responsibility, placement constraints, scholarship-supported executive-function coaching, and attempted major or classification change are mapped only to the extent supported by the record. They may inform feasible mitigation or disposition even if they do not establish CRO liability.

Source lines 842–845; approximately 41 words.

Requested action

I respectfully request that DGE: 1. accept the crosswalk into the administrative record; 2. identify the complete Investigation Materials and operative receipt date; 3. determine that the materials reflect possible substantive mitigating circumstances; 4. refer the written appeal and Investigation Materials to CDP within the applicable Standards process; 5. transmit the complete crosswalk to CDP;

Source lines 846–866; approximately 119 words.

13. CDP referral request

Structural heading introducing subordinate content.

Source lines 867–868; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Request for referral to the Committee on Degree Programs Dear [CONFIRMED_DGE_RECIPIENT], The Investigation Materials reflect possible substantive mitigating circumstances that could have affected my academic performance. I respectfully request referral of my written appeal and the Investigation Materials to the Graduate Council’s Committee on Degree Programs under the current Standards. Please confirm the referral date, the materials transmitted, and the procedure and deadline for requesting a personal appearance. Sincerely,

Source lines 869–883; approximately 88 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Request for CDP referral based on possible substantive mitigating circumstances Dear [CONFIRMED_DGE_RECIPIENT], I respectfully request that the Dean of Graduate Education refer my written academic-disqualification appeal and the complete Investigation Materials to the Graduate Council’s Committee on Degree Programs. The governing threshold is whether the Investigation Materials reflect possible “substantive mitigating circumstances that could have affected academic performance.” The materials satisfy that threshold for at least three independent, source-grounded reasons: 1. Disability, functional limitations, and University notice. The report finds or records [REPORT_FINDING] at [REPORT_PAGE], while the University record establishes [NOTICE_FACT]. This i…

Source lines 884–924; approximately 311 words.

14. CDP personal-appearance request

Structural heading introducing subordinate content.

Source lines 925–926; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Written request for personal appearance before CDP Dear [CONFIRMED_RECIPIENT], Because my appeal has been referred to CDP, I respectfully request a personal appearance before the Committee under the current Standards. Please confirm receipt and provide the CDP-approved procedures, scheduling process, format, time allocation, submission limits, accessibility process, and materials the Committee will review. Sincerely,

Source lines 927–941; approximately 73 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Personal-appearance request and procedural information — CDP referral [REFERRAL_IDENTIFIER] Dear [CONFIRMED_RECIPIENT], I understand that DGE referred my written appeal and Investigation Materials to the Graduate Council’s Committee on Degree Programs on [REFERRAL_DATE]. Under the Standards and Procedures for Graduate Study at UCLA, an individual is entitled, upon written request, to a personal appearance before the Committee. I hereby make that written request. My intended presentation will be focused on whether the Investigation Materials reflect substantive mitigating circumstances that could have affected academic performance, the relationship of those circumstances to the program’s stated academic grounds, and feasible disposition options within the…

Source lines 942–978; approximately 306 words.

15. Five-minute CDP presentation

Structural heading introducing subordinate content.

Source lines 979–980; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Five-minute script — concise version Thank you for the opportunity to appear. I understand that CDP is making a recommendation to the Dean of Graduate Education and that the Graduate Dean retains final authority. The question before the Committee is not whether every allegation in my CRO grievance was substantiated. The Standards ask whether the Investigation Materials reflect substantive mitigating circumstances that could have affected academic performance. The materials do. First, the record documents [DISABILITY_RELATED_CIRCUMSTANCE] and University notice by [DATE_OR_PERIOD]. The report states [PARAPHRASE_OF_REPORT_FINDING] at page [REPORT_PAGE]. I ask the Committee to treat that as a report finding, not as proof of any broader proposition. Second, the materi…

Source lines 981–1004; approximately 296 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Five-minute script — full version Opening — approximately 30 seconds Thank you for allowing me to appear. I understand that the Committee reviews my written appeal and the Investigation Materials, considers the information I provide today, and makes a recommendation to the Dean of Graduate Education, who retains final authority. I will focus on one question: do the Investigation Materials reflect substantive mitigating circumstances that could have affected my academic performance? The answer is yes, even if CRO did not substantiate every alleged policy violation. Disability, functional limitations, and notice — approximately 60 seconds

Source lines 1005–1052; approximately 504 words.

16. Ten-minute CDP presentation

Structural heading introducing subordinate content.

Source lines 1053–1054; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Ten-minute script — streamlined version Thank you for the opportunity to appear. I understand that CDP will review my written appeal and the Investigation Materials, consider this presentation, and recommend a disposition to the Dean of Graduate Education. I also understand that the Graduate Dean retains final authority. The governing question is whether the Investigation Materials reflect substantive mitigating circumstances that could have affected academic performance. That is a different question from whether CRO found that every respondent violated nondiscrimination policy. The academic-disqualification sequence is important. NSIDP’s April 28, 2025 letter identified insufficient degree progress based on failure to identify a primary faculty mentor after five…

Source lines 1055–1084; approximately 546 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Ten-minute script — full version 1. Opening and governing standard — approximately 60 seconds Thank you for the opportunity to appear. I understand the Committee’s role is to review my written appeal and the Investigation Materials, consider the information I provide today, and make a recommendation to the Dean of Graduate Education. I understand that the Graduate Dean retains final authority. My request is focused on the exact Standards language: whether the Investigation Materials reflect “substantive mitigating circumstances that could have affected academic performance.” That standard does not require the Committee to find that every allegation was substantiated or that every academic concern was invalid. It asks whether meaningful circumstances reflected in…

Source lines 1085–1178; approximately 1,085 words.

17. Bailey service-defect preservation note

Structural heading introducing subordinate content.

Source lines 1179–1180; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Preservation of admitted Chair-response service defect Dear [CONFIRMED_DGE_RECIPIENT], I preserve the record-integrity objection arising from DGE’s May 4, 2026 acknowledgment that, due to a DGE miscommunication, the NSIDP Chair’s response to my procedural-error appeal was not shared with me at the same time it was submitted to DGE, as stipulated in the academic-disqualification appeal procedures. I do not claim that the Standards expressly create an unrestricted sur-rebuttal right or that the defect automatically changes the decision. I request that the admission, DGE’s “courtesy only” interpretation, and any item-specific prejudice remain part of the administrative record. Sincerely,

Source lines 1181–1195; approximately 115 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Record-integrity preservation — contemporaneous service of NSIDP response Dear [CONFIRMED_DGE_RECIPIENT], I submit this note to preserve, accurately and narrowly, the Chair-response service issue in my academic-disqualification appeal record. The Standards state that the program or department Chair will provide DGE and the individual with a written response to the procedural-error appeal within fifteen business days. On July 21, 2025, DGE advised me that I would receive a copy of the Chair’s response. On August 26, 2025, DGE transmitted the Chair’s response together with the Dean’s completed procedural-error appeal decision. On May 4, 2026, DGE acknowledged that, due to a DGE miscommunication, the Chair failed to share the program response with me at the…

Source lines 1196–1227; approximately 377 words.

18. Narrow cure request for the DGE record defect

Structural heading introducing subordinate content.

Source lines 1228–1229; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Narrow request to cure and annotate Chair-response service defect Dear [CONFIRMED_DGE_RECIPIENT], I request that DGE annotate the appeal file to reflect its May 4, 2026 acknowledgment that the NSIDP Chair’s response was not shared with me at the same time it was submitted to DGE, as stipulated in the appeal procedures. Please preserve my objection, DGE’s “courtesy only” interpretation, and the affected documents in the administrative record. I do not request an unrestricted sur-rebuttal or assert automatic reopening through this narrow request. Sincerely,

Source lines 1230–1244; approximately 102 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Proposed narrow institutional cure — procedural-appeal record integrity Dear [CONFIRMED_DGE_RECIPIENT], I request a limited, administratively manageable cure for the admitted failure to provide the NSIDP Chair’s procedural-appeal response to me at the same time it was submitted to DGE. The relevant sequence is: 1. on July 21, 2025, DGE stated that I would receive a copy of the Chair’s response;

Source lines 1245–1290; approximately 398 words.

19. Scenario-specific remedy proposal

Structural heading introducing subordinate content.

Source lines 1291–1292; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Remedy proposal following [REPORT_SCENARIO] Dear [CONFIRMED_DECISION_MAKER_OR_REFERRAL_RECIPIENT], The report concludes [OVERALL_DISPOSITION] and finds [LOAD_BEARING_FINDING] at [REPORT_PAGE]. I respectfully request [REQUESTED_REMEDY] because it directly addresses [IDENTIFIED_HARM_OR_MITIGATING_CIRCUMSTANCE]. If your office lacks authority to implement that relief, please treat this as a request for referral or facilitated discussion with [IMPLEMENTATION_OFFICE]. My fallback request is [FALLBACK_REMEDY]. Sincerely,

Source lines 1293–1307; approximately 71 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Proportionate remedy proposal based on [REPORT_SCENARIO] Dear [CONFIRMED_DECISION_MAKER_OR_REFERRAL_RECIPIENT],

Source lines 1308–1315; approximately 25 words.

Report posture

The report transmitted on [TRANSMITTAL_DATE] concludes [OVERALL_DISPOSITION]. The findings most relevant to relief are: 1. [EXACT_FINDING_OR_ACCURATE_PARAPHRASE], [REPORT_PAGE]; 2. [EXACT_FINDING_OR_ACCURATE_PARAPHRASE], [REPORT_PAGE]; and 3. [EXACT_FINDING_OR_ACCURATE_PARAPHRASE], [REPORT_PAGE]. The report also contains the following adverse or limiting finding, which I do not omit: [ADVERSE_FINDING], [REPORT_PAGE].

Source lines 1316–1325; approximately 41 words.

Scenario framing

Use the paragraph matching the verified report: - Broad favorable report: The report substantiates material disability-discrimination, failure-to-accommodate, harassment, or retaliation allegations and identifies resulting harm. The requested relief should preserve those findings, prevent recurrence, remedy documented effects, and coordinate any academic implementation with the office that has authority. - Mixed partial-substantiation report: The report supports some allegations and rejects others. The requested relief is tied only to the substantiated findings and authenticated favorable facts, while preserving a separate DGE mitigation argument for facts that did not establish formal liability. - Factual concessions with no formal violation: Although the report does not find a policy violation, it confirms material facts concerning disability, notice, accommodation context, academic t…

Source lines 1326–1338; approximately 309 words.

Requested remedy ladder

Structural heading introducing subordinate content.

Source lines 1339–1340; approximately 0 words.

1. Immediate record and sequence relief

I request: - preservation of the native report, transmittal, comments, and correction table; - written confirmation of finality and any remaining Procedure 230.2 step; - continued DGE abeyance until the completion milestone is identified and the timely route is resolved; - notice before any action affecting student status, funding, health insurance, records, or access; and - correction of [OBJECTIVE_RECORD_ERROR].

Source lines 1341–1350; approximately 55 words.

2. CRO-related relief

To the extent within the Vice Chancellor’s, Chancellor’s, or other authorized office’s role, I request: - [RECURRENCE_PREVENTION_MEASURE]; - [REMEDY_FOR_DOCUMENTED_EFFECT]; - future accommodation and interactive-process safeguards; - no-retaliation measures; - appropriate training or policy clarification; and

Source lines 1351–1361; approximately 49 words.

3. DGE/CDP academic relief

Under the separate mitigation standard, I request [PRIMARY_DGE_CDP_DISPOSITION]. Appropriate safeguards could include [ACADEMIC_CONDITIONS]. If that disposition is not feasible, I request consideration of [FALLBACK_DGE_CDP_DISPOSITION], which may involve a corrected academic review, accommodated reinstatement, facilitated major or classification change, a cognate master’s or other agreed degree path, inter-UC transfer support, or a stipulated terminal degree, subject to the authority and requirements of the responsible offices.

Source lines 1362–1367; approximately 64 words.

4. Consequence and transition relief

Any approved disposition should expressly address: - student-status continuity or a defined transition date; - tuition and fee consequences; - stipend or employment consequences; - health-insurance continuity; - transcript and internal-record language;

Source lines 1368–1381; approximately 47 words.

5. Negotiated alternative

If no single office can implement the primary request, I ask that [RECIPIENT] convene or refer a facilitated discussion among the offices with actual authority. Participation would not waive any position absent a written, mutually executed agreement.

Source lines 1382–1385; approximately 37 words.

Authority alignment

I direct each request only to the extent of the recipient’s authority. A CRO decision-maker may determine findings and non-disciplinary remedial action or recommend a remedy; DGE and the Graduate Dean address academic disqualification and CDP referral; CDP recommends a disposition; the Academic Senate process may be required for a grade change; and program, registrar, funding, benefits, or receiving-program offices may be necessary for implementation. Where authority is uncertain, this proposal seeks referral or negotiation, not an unsupported order.

Source lines 1386–1389; approximately 79 words.

Requested response

Please state: 1. which requested items are granted, denied, referred, or under review; 2. the authority and implementation office for each granted item; 3. any condition, schedule, or further submission required; 4. the responsible contact role; and 5. how compliance will be documented.

Source lines 1390–1404; approximately 46 words.

20. Settlement or facilitated-resolution request

Structural heading introducing subordinate content.

Source lines 1405–1406; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Request to explore facilitated resolution Dear [CONFIRMED_RECIPIENT], If the University is willing, I am open to a facilitated discussion aimed at a practical, primarily nonmonetary resolution that preserves the administrative record and reduces further process burden. Participation would not waive any position, deadline, or review right absent a written agreement signed by the relevant parties. Please confirm whether an authorized facilitator and the necessary decision-making offices are available. Sincerely,

Source lines 1407–1421; approximately 88 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Subject: Without-prejudice request to explore facilitated academic and administrative resolution Dear [CONFIRMED_RECIPIENT], In light of [REPORT_SCENARIO_OR_CURRENT_POSTURE], I am willing to explore a structured resolution that addresses the documented academic and disability-related circumstances while reducing the burden and uncertainty of further proceedings. This is an invitation to discuss possible terms, not an acceptance of any existing finding, a waiver, or a binding offer. I will continue to preserve all applicable deadlines unless a written standstill or extension is confirmed. No waiver would occur unless embodied in a final written agreement signed by all parties with authority.

Source lines 1422–1433; approximately 111 words.

Proposed discussion objectives

1. preserve accurate favorable findings and correct agreed factual errors; 2. resolve the DGE/CRO sequencing issue without premature academic action; 3. identify a viable academic disposition; 4. address status, tuition, funding, employment, and health-insurance consequences; 5. establish prospective accommodation and no-retaliation safeguards; 6. assign implementation responsibility to offices with actual authority; and

Source lines 1434–1443; approximately 61 words.

Possible terms for discussion

Subject to authority, feasibility, and mutual agreement, discussion could address: - accommodated NSIDP reinstatement under a defined academic plan; - reconsideration or corrected review of academic disqualification; - a facilitated major or classification change; - transition to a cognate master’s program; - support for an inter-UC transfer or other academic transition;

Source lines 1444–1464; approximately 150 words.

Process protections

I request that any facilitated process: 1. identify the facilitator and each participant’s authority; 2. preserve confidentiality only to the extent lawfully and mutually agreed; 3. state whether communications are part of the administrative record; 4. confirm whether any procedural dates are extended or held in abeyance; 5. permit consultation with a representative or counsel;

Source lines 1465–1477; approximately 87 words.

Proposed initial agenda

I propose an initial session limited to: - the verified report posture and unresolved procedural sequence; - the academic disposition options that the participating offices can actually authorize; - interim protection against avoidable status or benefits harm; - record-correction items that are not genuinely disputed; and - the information needed for a complete term sheet.

Source lines 1478–1494; approximately 91 words.

21. Counsel handoff memorandum

Structural heading introducing subordinate content.

Source lines 1495–1496; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Counsel-review memorandum — privilege status to be confirmed by counsel Client: Cooper Beaman Date: [HANDOFF_DATE] Immediate response requested by: [COUNSEL_RESPONSE_TARGET]

Source lines 1497–1505; approximately 35 words.

Posture

CRO transmitted [REPORT_TITLE] on [TRANSMITTAL_TIMESTAMP]. The earliest plausible 10-Day hearing-request date is [EARLIEST_PLAUSIBLE_DATE]. The route presently under consideration is [HEARING / COMMENTS / CLARIFICATION_OR_EXTENSION_FIRST].

Source lines 1506–1509; approximately 22 words.

Immediate questions

1. Does the report create a hard hearing trigger or can written comments adequately preserve the material disputes? 2. Does the transmittal create a waiver, acceptance, exhaustion, or finality concern? 3. Should DGE be asked to maintain abeyance while [PENDING_STEP] remains pending? 4. Does the Bailey service issue show item-specific prejudice requiring a cure beyond record annotation? 5. Are any external limitation or preservation dates implicated?

Source lines 1510–1517; approximately 66 words.

Requested review

Please review [ATTACHMENT_LIST] and advise on the narrowest deadline-preserving submission. No filing or external contact is authorized through this memorandum.

Source lines 1518–1521; approximately 20 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 1522–1525; approximately 16 words.

Counsel Handoff Memorandum

Privilege/confidentiality: Prepared for potential legal consultation. Counsel should determine privilege treatment and handling instructions. Client: Cooper Beaman Prepared: [HANDOFF_TIMESTAMP] Requested advice by: [COUNSEL_RESPONSE_TARGET]

Source lines 1526–1532; approximately 24 words.

1. Executive posture

CRO opened a Procedure 230.2 investigation by an April 8, 2026 NOI naming Dr. James Bisley, Dr. Carrie Bearden, and Dr. Felix Schweizer as respondents. The formal allegations concern a NEURO M203 accommodation request, a mentor decision and specified statements by Dr. Bearden, and an academic-disqualification recommendation and specified statements by Dr. Schweizer. On April 20, 2026, CRO declined to amend the NOI but stated that the evidence, witnesses, and theories presented would be considered and that the ultimate report would reflect them. On June 25, 2026, CRO announced a 19-business-day good-cause extension and stated that Cooper would receive the report on or before July 31, 2026. CRO transmitted [REPORT_TITLE] on [TRANSMITTAL_TIMESTAMP]. The report’s top-level disposition is [REPORT_SCENARIO]. The most consequential finding is [EXACT_FINDING] at [REPORT_PAGE].

Source lines 1533–1540; approximately 127 words.

2. Current dates and route

Attachment B defines issuance as the date of transmission. Procedure 230.2 does not say whether the anchor is day zero or Day 1. Current calculations are: | Event | Assumption A | Assumption B | Internal target | | Hearing request, 10 Days | [DATE] | [DATE] | [DATE] | | No-hearing comments, 15 Days | [DATE] | [DATE] | [DATE] | | No-hearing finalization, 20 Days | [DATE] | [DATE] | [DATE] | | Hearing completion, 60 Days | [DATE] | [DATE] | [DATE_OR_NOT_APPLICABLE] |

Source lines 1541–1555; approximately 104 words. Tables/matrices: | Event | Assumption A | Assumption B | Internal target |

3. Report analysis

Structural heading introducing subordinate content.

Source lines 1556–1557; approximately 0 words.

Favorable findings

1. [FAVORABLE_FINDING], [REPORT_PAGE]; 2. [FAVORABLE_FINDING], [REPORT_PAGE]; and 3. [FAVORABLE_FINDING], [REPORT_PAGE].

Source lines 1558–1563; approximately 10 words.

Adverse findings

1. [ADVERSE_FINDING], [REPORT_PAGE]; 2. [ADVERSE_FINDING], [REPORT_PAGE]; and 3. [ADVERSE_FINDING], [REPORT_PAGE].

Source lines 1564–1569; approximately 10 words.

Material potential errors or omissions

1. [ISSUE] — status [NOT_MENTIONED / EXPRESSLY_DISCOUNTED / OUT_OF_SCOPE / INDETERMINATE]; significance [SIGNIFICANCE]. 2. [ISSUE] — status [STATUS]; significance [SIGNIFICANCE]. 3. [ISSUE] — status [STATUS]; significance [SIGNIFICANCE]. Noncitation has not been treated as proof of nonconsideration. Proffers have not been represented as confirmed testimony.

Source lines 1570–1577; approximately 38 words.

4. DGE/CDP interlock

DGE confirmed on May 4, 2026 that the nondiscrimination-based appeal remained active and that the Dean would review appropriately redacted investigated materials. The Standards hold the appeal in abeyance until the investigatory process has completed but do not define the milestone. DGE’s separate test is whether the Investigation Materials reflect “substantive mitigating circumstances that could have affected academic performance.” The strongest crosswalk items are: 1. [MITIGATION_ITEM]; 2. [MITIGATION_ITEM]; and 3. [MITIGATION_ITEM]. Advice is requested on whether to seek continued abeyance through [PROPOSED_MILESTONE] and how to preserve an objection if DGE acts earlier.

Source lines 1578–1589; approximately 92 words.

5. Bailey record-integrity issue

The Standards state that the program Chair will provide DGE and the individual with the procedural-appeal response within fifteen business days. DGE acknowledged on May 4, 2026 that, due to a DGE miscommunication, the Chair failed to share the response with Cooper at the same time it was submitted to DGE, as stipulated in the procedures. DGE characterized the requirement as a courtesy only and stated there was no opportunity to further contest the program’s version. The current position is deliberately narrow: no claim of an express unrestricted sur-rebuttal right; preservation of service/notice, any undisclosed rationale or exhibit, DGE’s admission and interpretation, and item-specific prejudice. The proposed cure is record annotation plus limited reconsideration only if a specific prejudicial item is identified.

Source lines 1590–1595; approximately 123 words.

6. Requested advice

Please advise: 1. whether a hearing request is necessary to preserve the material disputes; 2. whether comments create any acceptance, waiver, exhaustion, or downstream-use risk; 3. how to frame completeness, redaction, or correction issues; 4. whether to request an extension and whether the stated facts show good cause; 5. the proper DGE sequencing position given source silence;

Source lines 1596–1611; approximately 122 words.

7. Proposed immediate action

Unless counsel advises otherwise before [INTERNAL_CUTOFF], the proposed protective sequence is: 1. preserve the native transmission and hashes; 2. send [COMPLETENESS_OR_DEADLINE_CONFIRMATION_REQUEST] if needed; 3. submit [MINIMAL_HEARING_REQUEST / WRITTEN_COMMENTS] by [INTERNAL_SUBMISSION_TARGET]; 4. notify DGE without conceding the completion milestone; 5. preserve the Bailey issue through a narrow record note; and

Source lines 1612–1622; approximately 58 words.

8. Attachment index

1. Native CRO transmittal and hash inventory; 2. CRO report, appendices, and redaction notice; 3. deadline worksheet with both assumptions; 4. allegation-disposition map; 5. hearing-versus-comments scorecard; 6. proposed route document;

Source lines 1623–1639; approximately 70 words.

22. External-agency administrative-record synopsis held in reserve

Structural heading introducing subordinate content.

Source lines 1640–1641; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 1642–1645; approximately 16 words.

Held in reserve — not filed

Potential reviewing body: [AGENCY_OR_FORUM] Prepared: [DATE] UCLA CRO opened a Procedure 230.2 investigation on April 8, 2026 concerning specified disability-discrimination, accommodation, harassment, and retaliation allegations. CRO transmitted its report on [TRANSMITTAL_TIMESTAMP], concluding [OVERALL_DISPOSITION]. Cooper selected [INTERNAL_ROUTE] and submitted [SUBMISSION] on [DATE]. The preserved issues are [ISSUE_1], [ISSUE_2], and [ISSUE_3]. This synopsis distinguishes allegations, report findings, program positions, and unresolved source silence. It is maintained for consultation and deadline analysis only. No external filing is authorized.

Source lines 1646–1654; approximately 76 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 1655–1658; approximately 16 words.

Administrative-Record Synopsis

Status: Held in reserve; not filed or submitted Potential use: Consultation concerning [AGENCY_OR_FORUM] Prepared for: Cooper Beaman Date: [DATE]

Source lines 1659–1665; approximately 19 words.

1. Purpose and limits

This synopsis organizes the existing University administrative record for qualified review. It does not assert jurisdiction, timeliness, exhaustion, liability, or entitlement to relief. Any external submission requires separate verification of the proper forum, current limitations period, filing prerequisites, confidentiality rules, and strategic consequences.

Source lines 1666–1669; approximately 43 words.

2. Parties and academic context

Cooper Beaman was a doctoral student in UCLA’s Neuroscience Interdepartmental Graduate Program. NSIDP recommended academic disqualification effective Spring 2025 for insufficient degree progress based on failure to identify a primary faculty mentor after five rotations. The later program record also discussed the fifth-rotation evaluation and NEURO M203. Cooper has a documented disability and accommodation history. The extent to which particular disability-related circumstances affected academic performance, mentor placement, the fifth rotation, or NEURO M203 is addressed in the CRO record and remains subject to the epistemic labels and contrary evidence identified below.

Source lines 1670–1675; approximately 91 words.

3. CRO proceeding

On April 8, 2026, CRO issued an NOI under UCLA Procedure 230.2 naming: - Dr. James Bisley, concerning a request to take the NEURO M203 midterm on a later date; - Dr. Carrie Bearden, concerning a decision not to serve as primary faculty mentor and specified alleged statements; and - Dr. Felix Schweizer, concerning the recommendation for academic disqualification and specified alleged statements. The NOI treated additional allegations or actors as untimely, outside formal scope, or customer-service matters. Cooper objected. On April 20, 2026, CRO declined to amend the NOI but stated that the evidence, witnesses, and theories presented would be considered and that the ultimate report would reflect them. On June 25, 2026, CRO stated that good cause supported a 19-business-day extension and that the report would be received on or before July 31, 2026.

Source lines 1676–1689; approximately 143 words.

4. Report findings

Structural heading introducing subordinate content.

Source lines 1690–1691; approximately 0 words.

Established or source-established findings

1. [REPORT_FINDING], [REPORT_PAGE]; 2. [REPORT_FINDING], [REPORT_PAGE]; and 3. [REPORT_FINDING], [REPORT_PAGE].

Source lines 1692–1697; approximately 10 words.

Cooper’s disputed points

1. Complainant account: [DISPUTED_POINT]; report treatment [TREATMENT]. 2. Complainant account: [DISPUTED_POINT]; report treatment [TREATMENT]. 3. Unknown / source silence: [ISSUE].

Source lines 1698–1703; approximately 19 words.

Respondent or program positions

1. [POSITION], source [SOURCE]; 2. [POSITION], source [SOURCE]; and 3. [POSITION], source [SOURCE]. No witness proffer is represented as testimony actually given. No upload-index entry is represented as an independently reviewed exhibit unless the underlying exhibit was verified.

Source lines 1704–1711; approximately 38 words.

5. Procedure 230.2 response

The report was issued by transmission on [TRANSMITTAL_DATE]. The preserved A/B deadline calculations were [DATES]. Cooper [REQUESTED A HEARING / SUBMITTED COMMENTS / REQUESTED CLARIFICATION] on [DATE]. The principal preserved procedural issues are: - [COMPLETENESS_OR_REDACTION_ISSUE]; - [MATERIAL_OMISSION_OR_CREDIBILITY_ISSUE]; - [POLICY_VERSION_OR_STANDARD_ISSUE]; and - [FINALITY_OR_DEADLINE_ISSUE].

Source lines 1712–1724; approximately 58 words.

6. DGE/CDP proceeding

DGE’s nondiscrimination-based academic-disqualification review remained active as of May 4, 2026. The Standards use a separate test: whether Investigation Materials reflect “substantive mitigating circumstances that could have affected academic performance.” The Standards do not define when the investigatory process has completed. DGE’s receipt date and completion position are [DGE_POSITION_OR_UNKNOWN]. Cooper requested [ABEYANCE / CLOCK_CONFIRMATION / CDP_REFERRAL / PERSONAL_APPEARANCE] on [DATE]. The strongest mitigation items are [ITEMS]. The strongest contrary evidence is [CONTRARY_EVIDENCE].

Source lines 1725–1732; approximately 69 words.

7. Bailey service issue

DGE acknowledged on May 4, 2026 that, due to a DGE miscommunication, the NSIDP Chair’s procedural-appeal response was not shared with Cooper at the same time it was submitted to DGE, as stipulated in the appeal procedures. DGE characterized the requirement as a courtesy only and did not reopen the decision. Cooper’s preserved position does not assert an unrestricted sur-rebuttal right. It distinguishes service and notice from new appeal grounds and identifies item-specific prejudice in [PREJUDICE_TABLE_FILENAME].

Source lines 1733–1738; approximately 76 words.

8. Administrative record preserved

The preserved record includes: - native CRO and DGE communications with headers; - immutable report and attachment originals; - SHA-256 inventories; - NOI, objections, and April 20 response; - report, comments or hearing materials, and decisions;

Source lines 1739–1753; approximately 57 words.

9. Questions for qualified review

1. What forum, if any, has jurisdiction over the verified issues? 2. What limitation periods, exhaustion rules, notice requirements, or record restrictions apply? 3. Does the chosen internal route adequately preserve the issues? 4. Does any observable event support interim-relief analysis? 5. What relief is legally and practically available? 6. What confidential or educational records require special handling?

Source lines 1754–1766; approximately 71 words.

23. Internal evidence-preservation checklist

Structural heading introducing subordinate content.

Source lines 1767–1768; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Receipt event: [TRANSMITTAL_TIMESTAMP] Preservation lead: [PRESERVATION_ROLE] Second checker: [SECOND_CHECKER_ROLE] - [ ] Export the native transmittal with full headers and preserve the original delivery channel. - [ ] Save every original attachment without opening and resaving it.

Source lines 1769–1787; approximately 122 words.

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 1788–1791; approximately 16 words.

Evidence and Administrative-Record Preservation Checklist

Structural heading introducing subordinate content.

Source lines 1792–1793; approximately 0 words.

A. Intake and immutable originals

[ ] Record device-displayed receipt date, time, time zone, account, sender, subject, and channel in 00_RECEIPT_EVENT_LOG.md. - [ ] Export the native email or message with full headers where available. - [ ] Save original attachments and linked-file notices exactly as received. - [ ] Capture a full-screen image showing the transmittal timestamp and complete attachment list. - [ ] Copy received files into 01_IMMUTABLE_ORIGINALS; inspect only working copies. - [ ] Record whether each original is read-only and who created the preservation copy.

Source lines 1794–1802; approximately 68 words.

B. File inventory and hashing

[ ] Create RECEIVED_FILE_INVENTORY.csv with filename, extension, bytes, source, acquisition time, and version. - [ ] Compute a SHA-256 hash for every native file. - [ ] Have a second person or independent process recompute and compare the hashes. - [ ] Preserve the first hash list and create a new list for every corrected transmission. - [ ] Do not hash a working copy as though it were the received original.

Source lines 1803–1810; approximately 59 words.

C. Opening, rendering, OCR, and page stability

[ ] Test each working copy for password protection, corruption, missing fonts, clipping, and readability. - [ ] Record PDF page count, printed-page numbering, blank pages, appendices, bookmarks, and signatures. - [ ] Extract text but verify every load-bearing quotation against the page image. - [ ] Record OCR errors and manual corrections without modifying the immutable original. - [ ] Use stable page references: report PDF page plus printed page where they differ. - [ ] Preserve redacted and unredacted versions separately if lawfully received.

Source lines 1811–1819; approximately 69 words.

D. Folder and naming controls

[ ] Use [YYYYMMDD]_[HHMMSS-PDT]_CRO_REPORT_RECEIPT as the event folder. - [ ] Maintain separate subfolders for native transmission, immutable originals, hashes/metadata, working copies, report decomposition, deadlines/route, DGE/CDP, counsel review, draft submissions, and sent/receipts. - [ ] Name working files [YYYYMMDD]_[DOCUMENT_ROLE]_vNN_[DRAFT/REVIEW/APPROVED]. - [ ] Never overwrite a prior version; increment the version and preserve a redline. - [ ] Add APPROVED_BY_COOPER_[TIMESTAMP] only after actual approval.

Source lines 1820–1827; approximately 63 words.

E. Source-to-claim discipline

[ ] For every load-bearing statement, record source, page/section, exact quotation or accurate paraphrase, and epistemic label. - [ ] Distinguish report finding, complainant account, respondent/program position, witness or evidence proffer, inference, and source silence. - [ ] Do not treat a proffer as confirmed testimony. - [ ] Do not treat an upload index as proof that CRO reviewed the underlying exhibit. - [ ] Do not infer nonconsideration from noncitation. - [ ] Record contradictions without inferring motive.

Source lines 1828–1836; approximately 65 words.

F. Deadlines and decisions

[ ] Record the native transmission timestamp and any printed report date. - [ ] Calculate Assumption A and Assumption B. - [ ] Exclude only confirmed campus closures in the primary calculation. - [ ] Keep observed-holiday and possible-curtailment sensitivities separate. - [ ] Record every clarification or extension request and written decision. - [ ] Preserve the original unextended date after an extension.

Source lines 1837–1846; approximately 58 words.

G. Submission control

[ ] Verify the current recipient and method from the transmittal or written instruction. - [ ] Confirm final filenames, attachments, pagination, citations, and confidentiality markings. - [ ] Scan for unresolved placeholders and prohibited completion-language remnants. - [ ] Create a PDF or other required submission form without altering source citations. - [ ] Compute final-submission hashes. - [ ] Obtain Cooper’s written approval.

Source lines 1847–1857; approximately 73 words.

H. Confidentiality, privilege, and separation

[ ] Keep private strategy separate from submission files. - [ ] Keep potential counsel communications in a restricted folder; do not assume privilege without counsel guidance. - [ ] Do not place health, educational, or third-party information in a public or unnecessary distribution. - [ ] Maintain a redacted sharing set for any reviewer who does not require the complete record. - [ ] Record every disclosure copy, recipient role, date, and purpose.

Source lines 1858–1865; approximately 60 words.

I. Counsel handoff

[ ] Provide the native transmittal, hash inventory, report, deadline worksheet, route scorecard, source-to-claim table, DGE interlock memo, Bailey memorandum, and proposed filing. - [ ] Identify the earliest internal response target. - [ ] State which facts are established, disputed, or unknown. - [ ] Ask objective questions; do not present legal conclusions as settled. - [ ] Record counsel’s handling and confidentiality instructions.

Source lines 1866–1873; approximately 51 words.

Preservation completion sign-off

Primary checker: [NAME_OR_ROLE], [TIMESTAMP] - Second checker: [NAME_OR_ROLE], [TIMESTAMP] - Unresolved issue: [UNRESOLVED_PRESERVATION_ISSUE_OR_NONE] - Cooper approval: [APPROVAL_TIMESTAMP]

Source lines 1874–1882; approximately 14 words.

24. One-page decision command sheet

Structural heading introducing subordinate content.

Source lines 1883–1884; approximately 0 words.

Minimal deadline-preserving form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 1885–1888; approximately 16 words.

CRO Report Decision Command Sheet — Minimal

| Control | Verified entry | | Native receipt timestamp/time zone | [TRANSMITTAL_TIMESTAMP] | | Complete transmission? | [YES / NO / INDETERMINATE] | | Report scenario | [REPORT_SCENARIO] | | Assumption A 10-Day date | [ASSUMPTION_A_DATE] | | Assumption B 10-Day date | [ASSUMPTION_B_DATE] |

Source lines 1889–1909; approximately 92 words. Tables/matrices: | Control | Verified entry |

Substantive form

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 1910–1913; approximately 16 words.

CRO Report Decision Command Sheet — Full

Structural heading introducing subordinate content.

Source lines 1914–1915; approximately 0 words.

Current posture

Received: [TRANSMITTAL_TIMESTAMP] through [TRANSMITTAL_CHANNEL] - Scenario: [REPORT_SCENARIO] - Top-line outcome: [OVERALL_DISPOSITION] - Completeness: [COMPLETE / INCOMPLETE / INDETERMINATE] - Critical missing or access issue: [ISSUE_OR_NONE]

Source lines 1916–1923; approximately 19 words.

Dates

| Event | Assumption A | Assumption B | Internal target | | Hearing request — 10 Days | [DATE] | [DATE] | [DATE] | | Comments — 15 Days | [DATE] | [DATE] | [DATE] | | No-hearing finalization — 20 Days | [DATE] | [DATE] | [DATE] | | Hearing completion — 60 Days | [DATE] | [DATE] | [DATE] | Counting rule: Work to the earlier plausible date. Primary calculation excludes only weekends and confirmed campus closures. Extensions can change the sequence; no absolute maximum is stated.

Source lines 1924–1934; approximately 61 words. Tables/matrices: | Event | Assumption A | Assumption B | Internal target |

Decision screen

Favorable findings to preserve: [FINDINGS_AND_PAGES] - Material adverse findings: [FINDINGS_AND_PAGES] - Potential objective errors: [ERRORS_AND_PAGES] - Potential omissions: [ITEMS_AND_STATUS] - New credibility or live-testimony issue: [ISSUE_OR_NONE] - New evidence unavailable during investigation: [ITEM_OR_NONE]

Source lines 1935–1945; approximately 43 words.

Route command

Provisional route: [HEARING / COMMENTS / CLARIFICATION_OR_EXTENSION_FIRST] Why: [THREE_SENTENCE_REASON] Route-changing event: [OBSERVABLE_EVENT] Protective document: [MINIMAL_HEARING_REQUEST / WRITTEN_COMMENTS / COMPLETENESS_REQUEST / EXTENSION_REQUEST] Approved representative statement: [REPRESENTATION_STATEMENT]

Source lines 1946–1957; approximately 20 words.

DGE/CDP command

[ ] Notify DGE of report receipt without conceding completion. - [ ] Ask what Investigation Materials DGE received and when. - [ ] Request continued abeyance through [PROPOSED_MILESTONE]. - [ ] Populate the report-to-mitigation crosswalk. - [ ] Request CDP referral if the materials reflect possible substantive mitigation. - [ ] Request a personal appearance in writing if referred.

Source lines 1958–1966; approximately 43 words.

Counsel and external-review command

Counsel trigger: [OBSERVABLE_TRIGGER_OR_NONE] - Advice needed by: [DATE_AND_TIME] - External record synopsis: held in reserve; no filing authorized. - Bailey issue: [HOLD / PRESERVE / SEEK_NARROW_CURE] because [REASON]

Source lines 1967–1973; approximately 23 words.

Do not do

Do not overwrite native files or first hashes. - Do not call a printed report date the issuance date without checking transmission. - Do not count observed holidays as confirmed campus closures. - Do not infer nonconsideration from noncitation or motive from delay or senior review. - Do not state that DGE completion occurs at a particular milestone without confirmation. - Do not send to an unverified address or portal.

Source lines 1974–1984; approximately 84 words.

Final approval

Route approved by Cooper: [TIMESTAMP] - Final file verified by: [SECOND_CHECKER] - Recipient/method reverified: [TIMESTAMP] - Submission authorized: [YES / NO]

Source lines 1985–1993; approximately 18 words.

Source-control note

These drafts are grounded in the following package sources and must be refreshed against the actual report and current instructions before use: - 01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, especially pp. 1–4; - 01_CASE_RECORD/04_CRO_NOI_Objections_and_2026-04-20_Response.md, especially the April 20 CRO response; - 01_CASE_RECORD/02_CRO_Extension_Notice_2026-06-24_to_2026-06-25.pdf, especially the June 25 extension; - 01_CASE_RECORD/08_ADQ_Official_Documents.pdf, including the April 28, 2025 academic-disqualification recommendation; - 01_CASE_RECORD/10_DGE_Update_2026-04-24_to_2026-05-04.pdf, especially DGE’s May 4, 2026 response;

Source lines 1994–2019; approximately 228 words.

15_HEARING_AND_POST_HEARING_PACKAGE.md

403 lines; 3,820 words; 44 indexed headings/sections.

Hearing and Post-Hearing Package

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Status: complete pre-report drafts; all report-dependent fields must be replaced and every proposed witness must be confirmed before use. Boundary: Cooper decides whether to request a hearing. Qualified counsel should review waiver, exhaustion, finality, examination, evidentiary, constitutional, and appeal-preservation issues. > INCOMPLETE-TRANSMISSION HARD STOP: Do not make a final merits-route election from an incomplete, unreadable, internally inconsistent, or materially redacted transmission unless a protective filing is required by the earliest plausible deadline. Preserve all objections and state the assumptions used. A minimal request may be used protectively when the earliest plausible deadline requires it; that filing is not a completed merits election.

Source lines 1–9; approximately 117 words.

1. Minimal hearing request

Subject: Timely request for hearing concerning CRO investigation report I, Cooper Beaman, request a formal hearing concerning the CRO investigation report transmitted on [TRANSMITTAL_TIMESTAMP] and identified as [REPORT_TITLE]. I disagree with the findings and/or recommendations identified at [REPORT_PAGES_OR_SECTIONS]. This request is submitted by the protective date calculated from the verified transmission under the earliest plausible counting assumption. It does not concede the completeness of the transmission, a different deadline calculation, the applicability of an unstated acceptance requirement, or the event that completes the separate DGE investigatory process. The principal hearing issues are: 1. [MATERIAL_FACTUAL_OR_CREDIBILITY_ISSUE]; 2. [MATERIAL_OMISSION_NEW_EVIDENCE_OR_METHODOLOGY_ISSUE]; and

Source lines 10–29; approximately 164 words.

2. Detailed grounds addendum

Structural heading introducing subordinate content.

Source lines 30–31; approximately 0 words.

Caption and preservation

Matter: [REPORT_TITLE / CASE IDENTIFIER] Report transmitted: [TRANSMITTAL_TIMESTAMP] Protective deadline method: [ASSUMPTION_A_OR_B_AND_SOURCE] Requested hearing issues: limited to the material grounds below. Cooper preserves every favorable factual finding and recommendation listed in Schedule A. He requests review only of the identified adverse findings, omissions, credibility determinations, or methodological conclusions. Nothing in this addendum converts a complainant account, witness proffer, upload index, or program position into an established fact.

Source lines 32–40; approximately 66 words.

Ground 1 — Material factual error

The report states at [REPORT_PAGE]: [EXACT_QUOTATION]. The smallest primary source passage is [EXHIBIT_AND_PAGE], which shows [SOURCE-ESTABLISHED_PROPOSITION]. The difference is material because it affects [ALLEGATION / ELEMENT / CREDIBILITY / CAUSATION / HARM / REMEDY]. Requested hearing resolution: determine [PRECISE_FACT] after receiving [WITNESS_OR_EXHIBIT]; correct the finding; and reconsider the dependent conclusion. Cooper does not seek a hearing over immaterial wording.

Source lines 41–46; approximately 54 words.

Ground 2 — Outcome-controlling credibility determination

At [REPORT_PAGE], the report credits [ACCOUNT] over [ACCOUNT] based on [EXACT_STATED_REASON]. The determination affects [FINDING]. Live evidence has noncumulative value because [SPECIFIC_CONFLICT_NOT_RESOLVABLE_FROM_DOCUMENTS]. The proposed examination is limited to [TOPICS]. Requested resolution: assess the identified conflict using consistent credibility criteria, contemporaneous corroboration, and the complete primary record. No inference of bias is requested merely because the investigator disagreed with Cooper.

Source lines 47–52; approximately 59 words.

Ground 3 — Material scoped omission

The NOI formally scoped [EXACT_ALLEGATION]. After a full-text search, manual page review, appendix review, and second check, the report’s identifiable treatment is [TREATMENT_OR_NONE]. This submission does not equate noncitation with nonconsideration. The problem is [NO_DISPOSITION / NO_ELEMENT_ANALYSIS / CONTRADICTORY_DISPOSITION], which prevents meaningful review of [MATERIAL ISSUE]. Requested resolution: identify and decide the scoped allegation or explain where it was decided; receive only the evidence necessary for that issue; and issue a corrected/additional report if authorized.

Source lines 53–58; approximately 74 words.

Ground 4 — Material new fact, rationale, or undisclosed evidence

The report first relies on [NEW_MATTER] at [REPORT_PAGE]. The pre-report record available to Cooper shows [PRIOR_RECORD_STATUS]. The matter is material because [DEPENDENT_CONCLUSION], and Cooper’s focused response is [RESPONSE_WITH_PRIMARY_SOURCE]. Requested resolution: admit the response; determine whether the new matter is accurate and properly weighted; and reconsider the dependent finding. Any legal characterization of notice or procedural due process remains reserved for qualified review.

Source lines 59–64; approximately 62 words.

Ground 5 — Policy identity, version, or element application

The report identifies [POLICY_AND_VERSION] and applies [ELEMENT_OR_TEST] to conduct dated [DATE_RANGE]. Stage A records the following version issue: [EXACT_VERSION_DISCREPANCY_OR_SOURCE_SILENCE]. Cooper asks the hearing officer to identify the operative source and apply its actual elements. He does not ask the hearing officer to assume retroactive application of the current UC policy.

Source lines 65–68; approximately 50 words.

Ground 6 — Methodological weight or contrary evidence

The report discounts [ITEM] for [EXACT_REASON]. The item is not offered simply because it appears in an upload index or proffer. The underlying exhibit is [AVAILABLE / UNAVAILABLE], was submitted as shown by [NATIVE_RECEIPT], and is relevant because [PROPOSITION]. Its noncumulative value is [VALUE]. Requested resolution: determine the appropriate weight and explain treatment. If the underlying exhibit is unavailable, Cooper will not represent that CRO reviewed it.

Source lines 69–74; approximately 66 words.

3. Allegation-by-allegation hearing theory

Complete only the grounds actually supported by the report.

Source lines 75–78; approximately 9 words.

James Bisley — M203 accommodation

NOI issue: alleged failure to accommodate when Cooper asked to take the NEURO M203 midterm later. - Hearing proposition: determine exact request/notice timing, what adjustment was offered, whether it addressed the identified barrier, and what academic effect followed. - Primary proof: native request/response timestamps; course/CAE arrangement; later-exam record; grade/progress documents. - Program position to confront fairly: request allegedly arrived at 9:06 after the exam began, CAE arrangements existed, and Cooper was permitted a later examination. - Live-evidence threshold: testimony is warranted only if a material question of knowledge, oral communication, implementation, or reasonableness is not resolved by the documents. - Requested result: [EXACT_FINDING_OR_CORRECTION], with any academic remedy referred to the authorized office.

Source lines 79–87; approximately 112 words.

Carrie Bearden — declined primary mentorship

Hearing proposition: determine the actual reason, criteria, notice, context, and effect of the decision, without assuming that faculty mentor discretion establishes or defeats discriminatory causation. - Primary proof: rotation expectations/work product; mentor communications; disability notice; comparator evidence if genuinely similarly situated; decision chronology. - Strongest defense: academic fit, capacity, and performance reasons; lack of supported comparator. - Live-evidence threshold: direct testimony has value only if the reason or criteria are materially disputed and not documented.

Source lines 88–94; approximately 73 words.

Carrie Bearden — statements about unmet expectations or skills

Hearing proposition: establish exact words, setting, audience, repetition, disability nexus, evaluative context, and effect. - Primary proof: authentic communications and confirmed recipients. - Strongest defense: legitimate academic feedback, accurate content, no disability nexus, isolated communication. - Requested result: distinguish ordinary criticism from protected-status harassment under the policy version actually applied.

Source lines 95–101; approximately 47 words.

Carrie Bearden — denial that she had considered serving as primary mentor

Hearing proposition: determine whether and why Bearden denied that she had considered serving as Cooper’s primary faculty mentor toward the end of the fifth rotation, the complete context of that statement, and whether disability-related circumstances materially affected the mentor path. - Primary proof: written benchmarks, rotation result, mentor communications, program rule/practice, and decision chronology. - Strongest defense: fifth rotation was exceptional; benchmarks remained unmet; mentor was not secured.

Source lines 102–107; approximately 67 words.

Carrie Bearden — email to Felix Schweizer

Hearing proposition: authenticate and contextualize the email phrase reproduced in the NOI; determine its subject, surrounding thread, purpose, and any role in an academic decision. - Primary proof: complete native email thread, not an isolated excerpt. - Strongest defense: legitimate discussion of options, ambiguous language, no disability nexus.

Source lines 108–113; approximately 46 words.

Felix Schweizer — disqualification recommendation

Hearing proposition: identify every actual academic ground, its contemporaneous source, decisionmaker knowledge, accommodation context, consistency over time, and whether disability was a factor under the applied standard. - Primary proof: November 19, 2024 Academic Plan; progress communications; mentor/rotation/M203 records; recommendation and decision; complete program response. - Strongest defense: insufficient overall progress and unmet benchmarks, including failure to secure a mentor, supplied legitimate independent grounds. - Requested result: correct any demonstrable factual error and identify what the record does and does not establish. DGE—not the hearing alone—must apply its separate mitigation standard.

Source lines 114–120; approximately 92 words.

Felix Schweizer — relayed Ophoff capability opinion

Hearing proposition: determine exact words, original source, reason for relay, audience, disability nexus, decision use, and effect. - Scope control: Ophoff’s own conduct was outside formal scope; Schweizer’s alleged relay was scoped. Do not merge them.

Source lines 121–125; approximately 35 words.

Felix Schweizer — “internalized self-loathing” article remark

Hearing proposition: establish exact remark, article/context, protected-status nexus, audience, frequency, and impact. - Strongest defense: ambiguous or unrelated academic discussion, isolated comment, no disability nexus.

Source lines 126–130; approximately 25 words.

4. Proposed exhibit list

Every proposed exhibit requires final Bates/page numbers, a source custodian, authenticity basis, and a one-sentence relevance statement. | ID | Proposed exhibit | Purpose | Limitation | | EX-01 | Native CRO transmittal and report | Issuance, completeness, exact findings | Report-dependent | | EX-02 | April 8, 2026 NOI | Formal allegations, respondents, scope | Not merits proof | | EX-03 | April 20, 2026 CRO response | CRO’s stated treatment of broader evidence/theories | Does not expand each formal allegation | | EX-04 | M203 native request/response and course arrangement | Timing, notice, response, implementation | Authenticate complete thread |

Source lines 131–151; approximately 223 words. Tables/matrices: | ID | Proposed exhibit | Purpose | Limitation |

5. Witness priority and necessity

All testimony below is anticipated and requires confirmation. | Priority | Witness/role | Anticipated subject | Necessity and noncumulative value | Do not use if | | 1 | Report author/investigator | Scope, evidence treatment, methodology, credibility, findings | Necessary only for a material unexplained methodology or record issue permitted at hearing | The report/documentary record fully answers it or process bars the inquiry | | 1 | Cooper Beaman | Requests, notice, communications, effects, disputed statements | Firsthand account of material events and harm | Topic is fully documentary and testimony adds no value | | 1 | Respondent tied to controlling disputed event | Knowledge, reason, words, decision use | Firsthand account central to allegation/credibility | The issue is immaterial or cumulative | | 2 | Confirmed recipient/participant in disputed communication | Exact statement/con…

Source lines 152–167; approximately 221 words. Tables/matrices: | Priority | Witness/role | Anticipated subject | Necessity and noncumulative value | Do not use if |

6. Direct-examination objectives

Structural heading introducing subordinate content.

Source lines 168–169; approximately 0 words.

Cooper

1. Establish personal knowledge and a clean chronology. 2. Identify the exact disability-related request or circumstance without unnecessary medical detail. 3. Show what the University knew and when. 4. Authenticate communications Cooper sent or received. 5. Explain the specific academic component and effect. 6. Address the strongest contrary fact candidly.

Source lines 170–179; approximately 57 words.

Corroborating witness

1. Establish role and firsthand opportunity. 2. Elicit the exact event, words, document, or practice. 3. Explain why the testimony is independent and noncumulative. 4. Test memory, timing, and any relationship to Cooper. 5. Avoid asking the witness to decide policy or repeat unverified proffers.

Source lines 180–187; approximately 45 words.

Record/process witness

1. Authenticate record creation, service, version, and timing. 2. Identify what was before the decisionmaker. 3. Separate required procedure from office custom. 4. Explain missing/late material without assigning intent.

Source lines 188–194; approximately 30 words.

7. Cross-examination objectives

Structural heading introducing subordinate content.

Source lines 195–196; approximately 0 words.

Respondents/program witnesses

Identify the exact contemporaneous reason and every supporting document. - Test whether criteria were fixed before the decision and applied consistently. - Clarify decisionmaker knowledge of disability-related circumstances. - Separate academic judgment from accommodation/process response. - Compare present testimony to the complete contemporaneous record. - Ask about alternatives actually considered, including the Bearden email context.

Source lines 197–206; approximately 63 words.

Report author

Confirm the operative scope, policy version, standard, evidence list, interview list, and missing-material treatment. - Identify criteria used for credibility and causation. - Ask how material contrary evidence was handled. - Clarify whether an item was not mentioned, considered but not cited, discounted, cumulative, out of scope, unavailable, or not submitted. - Do not ask for privileged deliberations or infer nonconsideration from noncitation.

Source lines 207–214; approximately 59 words.

8. Respondent credibility issue checklist

Use only if the actual report makes credibility material: 1. contemporaneous versus later rationale; 2. internal consistency; 3. consistency with primary documents; 4. personal knowledge; 5. corroboration;

Source lines 215–229; approximately 65 words.

9. Report-author methodology questions

1. Which policy version and elements governed each conduct date? 2. Was every scoped allegation separately resolved, and where? 3. What documents and interviews were actually reviewed? 4. How were unavailable exhibits, proffers, and upload-index items treated? 5. What credibility criteria were used? 6. How was the program’s strongest academic explanation tested?

Source lines 230–244; approximately 112 words.

10. Anticipated University defenses and replies

| Defense | Focused reply | | Legitimate academic judgment and unmet benchmarks | Accept the legitimacy of standards; test factual accuracy, consistency, notice, accommodation context, and whether a protected factor contributed under the applied policy. | | Fifth rotation was exceptional | Treat as a program position unless authenticated; explain why exceptional opportunity does not alone resolve how circumstances affected its outcome. | | M203 adjustment was provided | Identify exact request, timing, relief, remaining barrier, and academic effect; concede relief actually provided. | | No similarly situated comparator | Do not invent one; rely only on supported comparator evidence or other causation proof. | | Feedback was ordinary academic criticism | Test exact language, context, protected-status nexus, severity, and effect; do not equate criticism with harassment. |

Source lines 245–259; approximately 210 words. Tables/matrices: | Defense | Focused reply |

11. Evidentiary and relevance arguments

Primary communication: offered to establish what was said, when, and to whom; complete thread supplied. - Academic plan/decision: offered for contemporaneous grounds and expectations, not for the truth of every embedded assertion. - Transcript: offered to show Cooper’s recorded intake account and consistency, not automatic truth. - Proffer: offered only to show notice of anticipated evidence unless the witness or underlying exhibit is confirmed. - Upload index: offered only to show listed submission activity; native receipt/underlying exhibit establishes actual delivery and content. - Comparator: admitted only with a supported similarity foundation and necessary confidentiality protections.

Source lines 260–271; approximately 136 words.

12. Opening outline

1. Identify the exact report and limited hearing issues. 2. State which favorable findings Cooper preserves. 3. Explain the outcome-changing error/credibility/omission in one sentence. 4. Preview the smallest primary evidence and confirmed witnesses. 5. Acknowledge legitimate academic standards and the strongest defense. 6. Explain why the requested correction follows without inferring motive.

Source lines 272–285; approximately 148 words.

13. Closing outline

1. Revisit burden and exact policy elements. 2. State findings supported by admitted proof. 3. Resolve the central credibility question using consistent criteria. 4. Address the strongest defense. 5. Identify preserved favorable findings. 6. Explain materiality.

Source lines 286–299; approximately 127 words.

14. Remedy presentation

The hearing request should prioritize: 1. corrected factual finding or allegation disposition; 2. corrected or supplemental report; 3. preservation of favorable findings; 4. recommendation/referral for corrected academic review; 5. specific accommodation/process safeguards;

Source lines 300–314; approximately 92 words.

15. Five-Day hearing-report comments

Subject: Comments on hearing report issued [HEARING_REPORT_TRANSMITTAL_TIMESTAMP] These comments are submitted within the protective five-Day period calculated from transmission under [ASSUMPTION]. They preserve the hearing report’s favorable findings at [PAGES] and identify only material corrections.

Source lines 315–320; approximately 35 words.

A. Findings preserved

1. [EXACT_FINDING_AND_PAGE] 2. [EXACT_FINDING_AND_PAGE]

Source lines 321–325; approximately 4 words.

B. Material correction

At [PAGE], the hearing report states [QUOTE]. Hearing exhibit [ID/PAGE] and testimony [TRANSCRIPT_PAGE] establish [PROPOSITION]. The correction matters to [CONCLUSION/REMEDY]. Requested correction: [TEXT_OR_ACTION].

Source lines 326–329; approximately 25 words.

C. Material omission

The hearing report does not identify a resolution of [ISSUE], which was admitted and material as shown at [CITATIONS]. This is not an inference that the issue was unconsidered. Please identify its treatment or supplement the report.

Source lines 330–333; approximately 37 words.

D. Recommendation

Please preserve [FAVORABLE_RECOMMENDATION], correct [ERROR], and transmit the complete hearing record and report to the proper decisionmaker. These comments do not concede the DGE completion milestone. Respectfully submitted, Cooper Beaman [DATE]

Source lines 334–341; approximately 31 words.

16. Five-Day appeal limited to permissible grounds

Subject: Appeal from Vice Chancellor decision issued [DECISION_TRANSMITTAL_TIMESTAMP] This appeal is submitted within the protective five-Day period calculated from transmission under [ASSUMPTION]. It is limited to the ground(s) permitted by the operative Procedure 230.2 text and identified in the actual decision/transmittal. Cooper does not use this appeal to relitigate every factual dispute.

Source lines 342–347; approximately 55 words.

Appeal ground `[PERMISSIBLE_GROUND]`

1. Decision challenged: [EXACT_DECISION_TEXT_AND_PAGE]. 2. Permissible basis: [EXACT_PROCEDURE_TEXT_AND_CITATION]. 3. Record support: [HEARING_REPORT / TRANSCRIPT / EXHIBIT PAGES]. 4. Materiality: [WHY THE ERROR COULD AFFECT THE DECISION]. 5. Requested disposition: [NARROW AUTHORIZED RELIEF]. 6. Favorable matters preserved: [EXACT FINDINGS/RECOMMENDATIONS].

Source lines 348–362; approximately 84 words.

17. Final hearing-package QA

Actual report/transmittal and deadline verified. - Both anchor-day assumptions recorded. - No observed holiday treated as confirmed closure. - Every ground tied to an exact report page and primary source. - Favorable findings expressly preserved. - Witnesses confirmed; testimony labeled anticipated until confirmation.

Source lines 363–380; approximately 108 words.

18. V2 hearing-source and authentication index

Every witness proposition below remains an anticipated proffer requiring confirmation. Every exhibit must be authenticated and compared with the actual report before use. | ID | Hearing proposition or item | Exact controlled source location | Epistemic / authentication rule | | H-01 | The eight formally scoped alleged actions and respondent assignments | 01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, pp. 1–2, “Summary of the Factual Allegations” | Scope/allegation text only; not proof or a finding. | | H-02 | Hernandez and Ophoff matters treated as untimely and outside scope | Same NOI, p. 2, “Allegations Not Under Investigation” | Source-established scope treatment; underlying conduct remains alleged. |

Source lines 381–403; approximately 437 words. Tables/matrices: | ID | Hearing proposition or item | Exact controlled source location | Epistemic / authentication rule |

16_ADMINISTRATIVE_RECORD_PRESERVATION_PROTOCOL.md

370 lines; 1,703 words; 21 indexed headings/sections.

Administrative-Record Preservation Protocol

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Purpose: preserve provenance, authenticity, chronology, confidentiality, and retrieval across the CRO, DGE, CDP, counsel-review, and possible external-review workstreams. Non-action boundary: this protocol does not authorize access to private accounts, alteration of external records, submission, or contact with UCLA.

Source lines 1–7; approximately 54 words.

1. Canonical folder structure

CRO_DGE_RECORD/ 00_CONTROL/ CASE_INDEX.xlsx HASH_REGISTER.csv EVENT_LOG.csv

Source lines 8–53; approximately 63 words.

2. Naming convention

Use: [YYYYMMDD]_[HHMMSS-TZ]_[SOURCE]_[DOCTYPE]_[SHORT-DESCRIPTION]_v[NN]_[STATUS].[ext] Examples:

Source lines 54–83; approximately 98 words.

3. Native-email export protocol

For every material received or sent message: 1. record account/channel, displayed sender/recipient, subject, displayed timestamp, time zone, and attachment list; 2. export the native message in the format the mail system supplies, preserving full headers; 3. save attachments using their delivered bytes and names; 4. capture a full-screen image showing the message context and attachment list; 5. calculate SHA-256 for the native message and every attachment;

Source lines 84–98; approximately 125 words.

4. Immutable-original protocol

An immutable-original event folder contains: - the original native message or portal capture; - every delivered attachment; - a file inventory with names and byte sizes; - a SHA-256 list; - acquisition/event log;

Source lines 99–113; approximately 83 words.

5. Hashing procedure

Use SHA-256. The hash register must contain: | Field | Meaning | | Record ID | Stable unique identifier | | Relative path | Path within canonical record | | Original filename | Exactly received/sent | | Bytes | Exact size |

Source lines 114–134; approximately 98 words. Tables/matrices: | Field | Meaning |

6. OCR and page-image verification

1. Hash and preserve the PDF before extraction. 2. Record extractor/version, OCR settings, language, date, and output path. 3. Preserve page boundaries in extracted text using stable file-page markers. 4. Render every load-bearing page to an image at readable resolution. 5. Compare exact quotations, dates, names, findings, footnotes, tables, and redactions to the page image. 6. Record blank, image-only, corrupted, rotated, clipped, duplicated, or nonextractable pages.

Source lines 135–145; approximately 101 words.

7. Page-number stability

Cite the immutable original’s PDF file page and printed page where available. - Never repaginate the original. - Add Bates labels only to a derivative; record the mapping. - If combining documents for counsel, create a manifest mapping compiled page to original filename/page/hash. - When a corrected report arrives, preserve it as a new version and create a page-by-page change map. - A quotation must cite the version and page from which it came.

Source lines 146–154; approximately 71 words.

8. Redline and version control

Each working document begins with: Document ID: Version: Status: Owner:

Source lines 155–180; approximately 86 words.

9. Source-to-claim table

Minimum columns: | Column | Required content | | Claim ID | Stable identifier | | Draft and section | Exact location | | Claim text | Sentence proposed for use | | Epistemic label | Established fact, source-established procedural fact, complainant account, program position, proffer, inference, conditional, unknown, or rejected |

Source lines 181–201; approximately 98 words. Tables/matrices: | Column | Required content |

10. Deadline log

For each event: - native transmittal timestamp/time zone; - stated issuance date; - rule and exact citation; - trigger event; - Assumption A date;

Source lines 202–224; approximately 85 words.

11. Submission-receipt log

| Field | Required value | | Submission ID | Unique | | Route/office | CRO, DGE, CDP, or other confirmed recipient | | Authority for recipient/method | Actual transmittal or confirmed instruction | | Approved by | Cooper | | Sent date/time/time zone | Exact |

Source lines 225–243; approximately 77 words. Tables/matrices: | Field | Required value |

12. Portal screenshot protocol

Before an authorized upload: 1. capture logged-in portal name and case identifier without exposing credentials; 2. capture submission instructions and deadline display; 3. capture selected filenames before submission; 4. verify each file hash against the candidate register; 5. after submission, capture confirmation number, timestamp, filenames, and status;

Source lines 244–257; approximately 75 words.

13. Sent-message header preservation

For email submissions, retain the native sent item, full message headers, recipient fields, subject, body, exact attachments, and delivery or bounce messages. A screenshot alone is insufficient. If the recipient replies, preserve the reply as a new native event and link it to the submission ID.

Source lines 258–261; approximately 46 words.

14. Document index

The master index contains: - Record ID; - event date/time; - document date; - exact title; - creator/sender;

Source lines 262–287; approximately 65 words.

15. Privilege and confidentiality separation

Use four labels: - CASE RECORD — NONPUBLIC - PRIVATE STRATEGY — NOT FOR SUBMISSION - COUNSEL COMMUNICATION — PRIVILEGE STATUS TO BE CONFIRMED - SUBMISSION CANDIDATE / SENT Do not assume that calling a document privileged makes it privileged. Counsel determines privilege/work-product treatment. Keep medical, disability, student, witness, and personnel information to the minimum necessary. Create redacted working/counsel-production copies as derivatives while preserving originals.

Source lines 288–298; approximately 59 words.

16. Private-strategy versus submission-file separation

Private strategy may contain: - forecasts and probability judgments; - hearing/comments scores; - settlement ranges or negotiation considerations; - internal critiques and red-team notes; - counsel questions;

Source lines 299–320; approximately 73 words.

17. Counsel handoff structure

COUNSEL_HANDOFF_[DATE]/ 00_READ_ME_AND_QUESTION_MEMO.pdf 01_DEADLINE_AND_EVENT_CHRONOLOGY.xlsx 02_NATIVE_TRANSMITTAL_AND_HASHES/ 03_OPERATIVE_REPORT_AND_DECISIONS/

Source lines 321–336; approximately 55 words.

18. Correction transmission protocol

When a corrected report or attachment arrives: 1. treat it as a new receipt event; 2. preserve and hash it separately; 3. never replace the prior version; 4. compare filename, bytes, hashes, pages, metadata, and visible content; 5. create a redline/change table;

Source lines 337–349; approximately 80 words.

19. Release and destruction hold

No original, sent item, receipt, hash register, decision, report version, or source-to-claim table is destroyed while an internal route, DGE/CDP process, counsel review, external deadline analysis, or record correction remains potentially active. Routine duplicates and temporary renders may be removed only under a documented retention decision after confirming they are not event-context records.

Source lines 350–353; approximately 54 words.

20. Monthly and event-based audit

Run at every major receipt/submission and monthly while active: - every indexed path opens; - hashes of immutable originals pass; - no privileged/private strategy appears in submission directories; - deadlines link to native transmittals; - sent items match recorded hashes;

Source lines 354–370; approximately 76 words.

18_TWO_PAGE_EXECUTIVE_COMMAND_SHEET.md

149 lines; 1,484 words; 16 indexed headings/sections.

Executive Command Sheet

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION V2 reference posture — July 23, 2026 PDT; closed case-record cutoff July 22 The April 8 NOI formally scopes eight alleged actions concerning James Bisley, Carrie Bearden, and Felix Schweizer (01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf, pp. 1–2). CRO’s June 25 correspondence says additional time was needed for Director and Assistant Vice Chancellor review and that the report was expected on or before July 31, 2026 (01_CASE_RECORD/02_CRO_Extension_Notice_2026-06-24_to_2026-06-25.pdf, p. 2). That statement does not predict outcome or establish an absolute deadline. The report and transmittal do not exist in the closed case record.

Source lines 1–8; approximately 107 words.

Page 1 — Act on receipt

Structural heading introducing subordinate content.

Source lines 9–10; approximately 0 words.

Expected next event

A native CRO email, portal notice, report, appendix, correction, or further extension. Treat the first event as evidence: preserve it before analyzing it.

Source lines 11–14; approximately 23 words.

Ranked top-three planning scenarios

These are readiness priorities, not one combined distribution; Layer A and Layer B use different denominators. | Rank | Planning scenario | Layer and current structured weight | First fact that materially reorders it | | 1 | Usable report on or before July 31 | Layer A delivery state; 62% of Layer A | A verified further extension, no transmission by the classification point, or an unusable transmission. | | 2 | Mixed/partial substantiation | Layer B merits; 32% conditional on a usable report | The allegation-by-allegation disposition is predominantly one-directional or nonmerits. | | 3 | Factual concessions / DGE-useful findings without formal violation | Layer B merits; 22% conditional on a usable report | The report substantiates material allegations, rejects the factual predicates, or provides no DGE-useful authenticated facts. | The weights are structured subjective planning weights…

Source lines 15–26; approximately 139 words. Tables/matrices: | Rank | Planning scenario | Layer and current structured weight | First fact that materially reorders it |

First actions

1. Record displayed transmittal timestamp and time zone. 2. Export native message/full headers; preserve delivered attachments. 3. Hash originals; create immutable copies; use working copies. 4. Verify file opens, page count, pagination, appendices, evidence list, redactions, and completeness. 5. Enter actual transmittal in Artifact 03 and run protective Assumptions A and B without conceding completeness or issuance. 6. If complete and usable: map every NOI allegation and scope exclusion; extract exact favorable/adverse findings, credibility, causation, harm, policy version, and recommendations; then run Artifact 06.

Source lines 27–41; approximately 187 words.

Earliest plausible deadline logic

Attachment B says issuance is the date of transmission (02_STAGE_A_POLICY_VERIFICATION/PROCEDURAL_TEXT_EXTRACT.md, “Issuance and transmission,” lines 50–54). - Procedure 230.2 defines capitalized Days as University business days excluding weekends and campus-closed days (02_STAGE_A_POLICY_VERIFICATION/PROCEDURAL_TEXT_EXTRACT.md, “Days,” lines 44–47). - The sources do not say whether transmission day is day zero or day one: retain A and B (02_STAGE_A_POLICY_VERIFICATION/UNRESOLVED_AMBIGUITIES.md, required-silence table, line 17). - Use primary calculations with no unconfirmed closures. - Keep observed holidays and possible December 28–30 curtailment in sensitivity only (02_STAGE_A_POLICY_VERIFICATION/UNRESOLVED_AMBIGUITIES.md, “Closure and holiday uncertainty,” lines 80–88). - Set internal decision and draft targets early; aim to submit at least one University business day before the ear…

Source lines 42–53; approximately 200 words.

Critical uncertainties

transmission day counted or excluded; - effect of incomplete/corrected transmission; - confirmed campus-closure dates; - actual report policy/version analysis; - meaning of DGE “process has completed”; - whether that includes a hearing, Vice Chancellor decision, or appeal;

Source lines 54–64; approximately 46 words.

Hearing/comments trigger summary

Strong hearing analysis: outcome-controlling credibility; material new evidence/rationale; missing scoped disposition; demonstrable material misquotation; confirmed noncumulative witness value. Presumptive comments: disputes are documentary/textual; no material credibility issue; favorable findings should be preserved; DGE needs a clean authenticated record. Clarify/extend first: missing/corrupt file, broken link, material redaction, inconsistent issuance date. The reviewed official sources do not define whether an incomplete transmission constitutes issuance (02_STAGE_A_POLICY_VERIFICATION/UNRESOLVED_AMBIGUITIES.md, line 18). The score is decision support, not a legal rule.

Source lines 65–74; approximately 80 words.

Page 2 — Route and command

Structural heading introducing subordinate content.

Source lines 75–76; approximately 0 words.

DGE sequencing warning

The Standards require DGE to hold the appeal decision in abeyance while the investigatory office processes allegations and until that process “has completed” (01_CASE_RECORD/06_UCLA_Standards_and_Procedures_for_Graduate_Study.pdf, printed pp. 33–34 / PDF file pp. 34–35). The official sources do not define that milestone (02_STAGE_A_POLICY_VERIFICATION/UNRESOLVED_AMBIGUITIES.md, “Meaning of completion,” lines 44–56). Do not concede that report issuance, report finalization, hearing completion, Vice Chancellor decision, or Chancellor appeal completion controls. Ask what Investigation Materials DGE received, the receipt date, and the clock/status in writing. DGE’s exact merits question is whether there are “substantive mitigating circumstances that could have affected academic performance” (01_CASE_RECORD/06_UCLA_Standards_and_Procedures_for_Graduate_Study.pdf, printed p. 33 / PDF file p.…

Source lines 77–82; approximately 125 words.

Eight operational-module index

These modules do not form one probability universe: 1–6 principally map to Layer B, 7 to Layer A4, and 8 to Layer A3. 1. Broad favorable — preserve findings; targeted comments/remedy. 2. Mixed partial — split favorable/adverse; route by material issue. 3. Factual concessions/no violation — leverage authenticated facts for DGE. 4. Detailed adverse — test credibility/live evidence; preserve mitigation. 5. Narrow/omissive adverse — itemized cure plus protective deadline.

Source lines 83–95; approximately 101 words.

Seven documents to keep ready

1. Artifact 03 deadline calculator. 2. Artifact 05 receipt war room. 3. Artifact 06 route scorecard. 4. Artifact 08 expected-record matrix. 5. Artifact 10 DGE crosswalk. 6. Artifact 14 template suite.

Source lines 96–105; approximately 37 words.

Priority checklist by horizon

| Horizon | Command | | Complete before report receipt | Keep all twenty artifacts, source/citation controls, templates, calculator, war room, route system, matrices, and preservation folders ready; only true report fields remain open. | | Complete on day of receipt | Preserve/hash the native transmission; verify completeness; run primary A/B dates; map all allegations; log favorable/adverse findings, omissions, contradictions, and new material; make only a preliminary route screen. | | Complete within twenty-four hours | Finish the independent second read, route-neutral preservation set, DGE sequence/crosswalk, counsel packet if triggered, and the evidence-backed hearing/comments recommendation for Cooper’s decision. | | Complete before the protective ten-Day deadline | Resolve or expressly preserve issuance/completeness disputes; finish the selected filing and source check; obtain req…

Source lines 106–116; approximately 183 words. Tables/matrices: | Horizon | Command |

Decision sequence

Preserve → verify completeness YES → timestamp/metadata → protective A/B → map allegations → extract facts → test hard triggers → choose route → crosswalk DGE → second-check → Cooper approves NO → preserve/hash defect → request cure/clarification → protective A/B without concession → consider extension → HARD STOP on final merits route unless protective filing is required

Source lines 117–126; approximately 49 words.

Do not do

Do not send or file from this system. - Do not infer outcome or motive from delay/senior review. - Do not invent report quotations, recipients, portals, witnesses, or deadlines. - Do not treat an allegation, proffer, transcript, upload index, or program position as an established fact. - Do not call noncitation proof of nonconsideration. - Do not apply the current UC policy retroactively without version analysis.

Source lines 127–139; approximately 103 words.

Internal command record

| Decision | Owner | Target | Status | | Receipt preservation | [INTAKE_LEAD] | first 15 minutes | [STATUS] | | Deadline second check | [DEADLINE_LEAD] / [SECOND_CHECKER] | first hour | [STATUS] | | Allegation map | [REPORT_LEAD] | first four hours | [STATUS] | | Route decision | Cooper after review | internal protective target | [STATUS] | | DGE package | [DGE_LEAD] | route-coordinated | [STATUS] |

Source lines 140–149; approximately 49 words. Tables/matrices: | Decision | Owner | Target | Status |

19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md

1,658 lines; 273,630 words; 14 indexed headings/sections.

Final Requirement Compliance Audit — V2

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Audit date: 2026-07-23 PDT Evidence dataset: qa_v2/requirement_evidence_rows_v2.json Overall present status: PASS — this audit does not claim all requirements pass.

Source lines 1–8; approximately 37 words.

Method and noncircular derivation

Artifact 19 is generated from 1,550 row-level evidence records. Substantive PASS evidence comes from direct Markdown line scans, workbook reimports through oai/artifact-tool, recomputed structural counts, or machine-observed QA/package results. Artifact 00 is not cited as proof that another artifact is substantively correct. Artifact 00 and this audit share the evidence dataset so their status counts reconcile, while the final independent QA remains a separate gate. Prohibited evidence is rejected: no PASS rests on “implemented in the mapped artifact,” “cross-checked in Artifact 19,” a generic acceptance sentence, or filename existence alone. Requirement-specific criteria include the requirement ID, exact locator, requested behavior/content, and observable acceptance condition.

Source lines 9–14; approximately 108 words.

Atomic requirement status summary

| Status | Count | Meaning | | PASS | 1497 | Direct evidence satisfies the presently completable requirement. | | PARTIAL | 0 | A presently completable final gate remains open. | | FAIL | 0 | Observed output contradicts or misses the requirement. | | REPORT-DEPENDENT | 3 | Requires the future report/transmittal fact. | | UCLA-CONFIRMATION-DEPENDENT | 1 | Requires UCLA or later controlling official text. |

Source lines 15–29; approximately 105 words. Tables/matrices: | Status | Count | Meaning |

V2 independent-audit defect disposition

| ID | Severity | Baseline disposition | V2 status | Exact evidence locator | Observed evidence | | V2-R001 | critical | Reproduced in Gate V2-0 | PASS | 06_HEARING_VS_COMMENTS_DECISION_SYSTEM.xlsx — ‘Decision Tree’!A3:E5; ‘Route Assertions’!A4:G9; downstream Artifacts 05, 07, 14, 15, 18 | Required YES/NO branch phrases and hard stop are present in the exported workbook; dependent Markdown hard stops were repaired. | | V2-R002 | high | Reproduced in Gate V2-0 | PASS | qa_v2/qa_v2_workbook_structure.json — final per-sheet pane coordinates and structural results | V1: 0/34 panes. Final V2: 9 workbooks, 40 sheets, 0 sheets without panes. | | V2-R003 | high | Reproduced in Gate V2-0 | PASS | 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx — ‘Historical V1 Failures’!A4:H9; 19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md — ## Historical V1 failures preserved | V1’s false frozen-header certificat…

Source lines 30–49; approximately 516 words. Tables/matrices: | ID | Severity | Baseline disposition | V2 status | Exact evidence locator | Observed evidence |

Historical V1 failures preserved

V1 freeze panes: FAIL. Direct XML inspection found nine workbooks, thirty-four sheets, and zero persisted pane definitions (qa_v2/v1_workbook_structure.json). V1 Artifact 19’s contrary frozen-row certification was false. - V1 requirement evidence: FAIL. V1 Artifact 00 used generic acceptance language, broad artifact locators, producer attestation, and circular reference to Artifact 19. - V1 final audit independence: FAIL. V1 Artifact 19 materially relied on Artifact 00/producer assertions and missed the reversed route branch and absent panes. - V1 forecast architecture: FAIL against the V2 acceptance test. Timing, delivery quality, merits, and record quality shared one denominator and began from an even allocation without alternate-prior analysis. Later V2 repair does not rewrite any V1 failure as a historical PASS.

Source lines 50–58; approximately 115 words.

Final V2 gates and observed status

| Gate | Present status | Exact observed evidence | | Post-export pane repair | PASS | qa_v2/qa_v2_workbook_structure.json | | Citation precision and source fidelity | PASS | qa_v2/citation_sampling.json and .csv | | Operationally separate final QA | PASS | V2_INDEPENDENT_QA_REPORT.md and named qa_v2 JSON results | | Self-verifying package | PASS | qa_v2/qa_v2_package_integrity.json and qa_v2/qa_v2_output_manifest.json | | Final user-facing handoff | NOT APPLICABLE | Interaction-level instruction verified after sealing; excluded from static package PASS/FAIL. |

Source lines 59–68; approximately 62 words. Tables/matrices: | Gate | Present status | Exact observed evidence |

Dependency register

Structural heading introducing subordinate content.

Source lines 69–70; approximately 0 words.

Report-dependent

Actual CRO report/transmittal timestamp, completeness, pages, findings, evidence/interview list, redactions, recommendations, route decision, and confirmed witness testimony remain future facts.

Source lines 71–74; approximately 22 words.

UCLA-confirmation-dependent

Transmission-day counting, incomplete/corrected-transmission effect, actual campus-closure designations, DGE completion milestone, and full CDP personal-appearance mechanics remain source-silent unless UCLA or later controlling official text resolves them.

Source lines 75–78; approximately 27 words.

Counsel-dependent

Waiver, exhaustion, finality, external-agency deadlines, mandamus/judicial-review preservation, interim relief, constitutional characterization, settlement/release language, and actual filing choices remain reserved for qualified counsel.

Source lines 79–82; approximately 24 words.

Completion ledger

DONE: V2 atomic extraction; requirement-specific direct-evidence mapping; noncircular Artifacts 00 and 19; corrected route logic; three-layer forecast; operational scenario classification; source-role/crosswalk/matrix/command-sheet repairs; pane repair; 167-claim citation check; deterministic QA; manifest/checksum controls; and the tested 25-member package structure. - PARTIAL: 0 presently completable atomic rows remain open. - FAIL: 0 atomic rows at this build. - NOT APPLICABLE: 48 metadata or interaction-level rows, including final-response-only instructions that cannot be circularly certified inside the package. - REPORT-DEPENDENT: 3 atomic rows. - UCLA-CONFIRMATION-DEPENDENT: 1 atomic rows.

Source lines 83–92; approximately 86 words.

Atomic requirement evidence appendix

| Requirement ID | Controlling instruction and source | Faithful requirement | Requirement-specific criterion | Exact final artifact and locator | Observed evidence | Verifier and method | Status | Defect/cure | Date | | V4-001 | 00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md:10 — UCLA CRO PRE-REPORT RESPONSE SYSTEM — FINAL PRODUCTION, REPAIR, VALIDATION, AND DEPLOYMENT PACKAGE | Status: The actual CRO investigation report and its transmittal email do not exist and will not be available during this run. | V4-001: record the prompt metadata verbatim at work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-0…

Source lines 93–1647; approximately 272,440 words. Tables/matrices: | Requirement ID | Controlling instruction and source | Faithful requirement | Requirement-specific criterion | Exact final artifact and locator | Observed evidence | Verifier and method | Status | Defect/cure | Date |; | V4-047 | 00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MA…; | V4-171 | 00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MA…; | V4-183 | 00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MA…

Open-row index

The following 0 rows are presently PARTIAL or FAIL. They are not converted to dependencies: | ID | Status | Exact locator | Required cure |

Source lines 1648–1655; approximately 21 words. Tables/matrices: | ID | Status | Exact locator | Required cure |

Dependency-row index

5 rows carry a report/UCLA/counsel dependency. Their exact fields remain in the atomic appendix; no dependency label substitutes for a presently completable repair.

Source lines 1656–1658; approximately 25 words.

V2_INDEPENDENT_QA_REPORT.md

192 lines; 1,879 words; 16 indexed headings/sections.

V2 Independent QA Report

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Verification date: July 23, 2026 (PDT) Scope: Final exported V2 files in outputs_v2/; no private connectors, external accounts, broad web research, messages, submissions, or external-record changes.

Source lines 1–7; approximately 42 words.

Executive result

Overall presently completable QA status: PASS. This report is based on fresh deterministic inspection of final exported files, not the V1 producer’s assertions. Dependency-labeled facts are not failures when they truly require the future CRO transmission, UCLA confirmation, later closure information, or qualified counsel. A presently repairable defect is not downgraded to a dependency. | Check | Status | Actual observed scope | Evidence | | Baseline/package reconstruction | PASS | All 20 V1 primary artifacts opened and hash-matched; original 20-case/6-Stage-A source boundary remained available. | qa_v2/baseline_integrity.json | | Authorized-input integrity | PASS | 35 manifest entries, 20 case files, and 6 Stage A artifacts independently hash/readability checked. | qa_v2/qa_v2_input_integrity.json | | Decision tree | PASS | Final exported Artifact 06 cells/formulas and dependent route l…

Source lines 8–29; approximately 332 words. Tables/matrices: | Check | Status | Actual observed scope | Evidence |

Independence and reproducibility

Producer files were exported first; fresh QA scripts reopened the actual XLSX/Markdown/ZIP bytes. - V1 workbook structure was read directly from OOXML, which reproduced the zero-pane defect despite V1 prose claiming frozen rows. - Final pane checks read each worksheet’s \<pane> element after all exports and after the narrow OOXML view patch. - Probability checks parse the final Artifact 04 tables and recompute sums; they do not trust displayed total rows. - Requirement checks resolve exact Markdown headings or workbook sheet/range locators and reject generic or circular evidence. - Citation sampling records the output proposition, exact source path/pinpoint, smallest source passage, epistemic label, correction, and final result.

Source lines 30–39; approximately 118 words.

Baseline defect reproduction

V1 ZIP SHA-256: B029504096CB18A16C99F076008B2AA0C55BFD0F670CC82D80C6CA497791EC35. - V1 artifacts verified: 20/20. - V1 workbook sheets with panes: 0; without panes: 34. - Defect classifications before repair: 13 CONFIRMED and 2 PARTIALLY CONFIRMED. No audit item was accepted blindly; exact contrary evidence was recorded for the partial classifications and for dependent-artifact nonreproductions.

Source lines 40–46; approximately 47 words.

Workbook structure and freeze coordinates

| Workbook | Sheet | Final freeze coordinate | Pane state | Formulas | Tables | Status | | 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx | README | B6 | frozen | 0 | 0 | PASS | | 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx | Status Summary | B6 | frozen | 0 | 0 | PASS | | 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx | Atomic Requirements | B5 | frozen | 0 | 1 | PASS | | 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx | V2 Defect Disposition | B5 | frozen | 0 | 1 | PASS | | 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx | Historical V1 Failures | B5 | frozen | 0 | 0 | PASS |

Source lines 47–95; approximately 423 words. Tables/matrices: | Workbook | Sheet | Final freeze coordinate | Pane state | Formulas | Tables | Status |

Decision-tree repair verification

YES branch: preserve transmission, capture native timestamp/metadata, calculate A/B protective dates, then map allegations. - NO branch: preserve/hash received material, log exact defect, request cure/clarification, calculate dates without conceding completeness/issuance, consider extension, and stop final merits scoring unless the earliest plausible date requires protection. - The exact INCOMPLETE-TRANSMISSION HARD STOP is checked in Artifact 06 and dependent Artifacts 04, 05, 07, 14, 15, and 18. - Final deterministic result: PASS.

Source lines 96–102; approximately 72 words.

Forecast and probability verification

Independently recomputed numeric families/checks: 15 families within 21 checks; final status PASS. - Layer A and Layer B base, starting, reallocated, alternate-prior, and low/base/high families are separately normalized. - Layer C overlays are expressly labeled nonexclusive and are not added. - Point weights are described as structured subjective planning weights, not empirical base rates or statistical confidence estimates.

Source lines 103–109; approximately 58 words.

Deadline and Stage A revalidation

Independent samples: 34; PASS: 34; FAIL: 0. - Samples include July 31 Assumptions A/B, concurrent no-hearing comments/finalization, the primary unextended hearing chain, and holiday/curtailment sensitivity rows. - The final workbook retains A/B uncertainty, treats observed holidays/possible curtailment as sensitivity only, and warns that good-cause extensions prevent an absolute maximum.

Source lines 110–115; approximately 52 words.

Requirement-evidence verification

Atomic rows inspected: 1550. - PASS rows inspected: 1497; workbook/JSON reconciled rows: 1550; workbook/JSON mismatches: 0. - Normalized duplicate-evidence groups: 194; independently reviewed/allowed: 194; unreviewed (fail-closed): 0. - Empty normalized evidence: 0; generic/circular evidence: 0; title-only evidence: 0; substantive semantic mismatches: 0. - Accepted statuses: PASS, PARTIAL, FAIL, REPORT-DEPENDENT, UCLA-CONFIRMATION-DEPENDENT, COUNSEL-DEPENDENT, and NOT APPLICABLE. - V1’s false pane certification remains in the historical defect record and is not retroactively rewritten as a V1 PASS.

Source lines 116–124; approximately 73 words.

Citation/source-fidelity verification

Deterministic sample size: 167. - Final PASS: 167; final FAIL: 0. - Selection method/seed: Candidates were generated from final exported V2 files, V2-repaired/newly pinpointed candidates were prioritized, and candidates within each stratum were ordered by SHA-256(seed|stable candidate key); fixed quotas were then selected.; 20260723. - Strata cover every scoped allegation, material outside-scope theories, Bailey propositions, DGE/CDP rules, deadlines/Stage A, high-weight forecast factors, remedy authority, hearing witnesses/exhibits, and source roles/version control. - A proffer is treated as proof of what was proffered, an upload-index entry as proof of indexing/submission description, and an allegation as a scope/account proposition—not as proof of underlying truth.

Source lines 125–132; approximately 108 words.

Prohibited-language and epistemic screen

Final status: PASS. - Files/cells/text blocks scanned: 20 files; unexplained critical occurrences: 0. - Faithful quotations of the controlling prompt’s prohibited phrases inside the requirement ledger/audit are allowed only when classified as control text, not deployed drafting. - No unsupported recipient address or portal may survive. Official addresses quoted in source text are not automatically deployment-authorized; templates use recipient/route placeholders unless the actual transmittal confirms them.

Source lines 133–139; approximately 67 words.

Deployment completeness

Primary artifacts: 20/20; workbooks: 9/9; sheets: 40; tables: 30; populated operational rows checked: 2721. - Empty table rows: 0; blank identifier rows: 0; missing strategy warnings: 0. - Template suite: 24 categories, 24 minimal forms, and 24 substantive forms. Scenario playbooks: 8 scenarios and 160 numbered fields. - Operational schema checks: 3; failures: 0. These inspect Artifact 08’s exact blank-log table/validation, Artifact 10’s independently populated process field, and Artifact 17’s nine distinct in-table observable triggers.

Source lines 140–146; approximately 75 words.

Visual inspection

Rendered workbooks: 9; sheets: 40; images: 50. - Every sheet has a representative top render; long sheets also have middle and lower renders. Contact sheets were inspected for readable headers, wrapped text, usable widths, visible input differentiation, and absence of clipped critical text. - Final visual status: PASS.

Source lines 147–152; approximately 46 words.

Manifest, checksum, and ZIP integrity

Output-manifest status: PASS; rows: 25; failures: 0. - Candidate package status at report assembly: PASS; members: 25; candidate-stage SHA-256: A9A5690A0D6BC6A48A06F1D1FC105B4B95E10178096859A0AC03F4881266E795. - The ZIP must contain the twenty primary artifacts plus five V2 controls exactly once, and must not include the V1 ZIP. - FINAL_OUTPUT_SHA256SUMS_V2.txt hashes every other member, including the actual bytes of FINAL_OUTPUT_MANIFEST_V2.csv. A file cannot contain its own final actual-byte hash; therefore the root ledger is authenticated by the externally reported final ZIP SHA-256. The manifest states this boundary rather than fabricating a self-hash. - After this report is embedded, the same package and manifest checks are rerun externally against the sealed final ZIP. That post-embedding result and archive SHA-256 are reported in the handoff; the embedded candidate-stage hash is…

Source lines 153–160; approximately 126 words.

Exact validation commands

The bundled workspace Python and Node runtimes were used with these reproducible checks: python work/v2_builders/qa_v2_baseline_integrity.py python work/v2_builders/qa_v2_input_integrity.py python work/v2_builders/finalize_workbook_freeze.py python work/v2_builders/qa_v2_workbook_structure.py

Source lines 161–184; approximately 99 words.

Dependency ledger

REPORT-DEPENDENT: actual report/transmittal facts, report pages, exact findings, quotations, attachments, evidence list, redactions, completeness, and route-changing facts. - UCLA-CONFIRMATION-DEPENDENT: counting anchor, completeness/issuance effect, later campus closures, DGE completion milestone, full CDP appearance practice, and source-silent office authority. - COUNSEL-DEPENDENT: waiver/exhaustion/finality, constitutional or mandamus analysis, external jurisdiction/deadlines, interim relief, settlement/releases, and contested remedy authority. - No report-dependent placeholder is a completed submission field. All must be replaced and reverified before use. > PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 185–192; approximately 89 words.

V2_REPAIR_LEDGER.md

84 lines; 1,690 words; 7 indexed headings/sections.

V2 Repair Ledger

PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION Repair date: July 23, 2026 (PDT) Boundary: Internal decision support only. No message was sent, no account was accessed, no external record was changed, and no legal or academic election was made.

Source lines 1–7; approximately 48 words.

Baseline and preservation

V1 archive: CRO_PRE_REPORT_RESPONSE_SYSTEM_FINAL_2026-07-22.zip - V1 SHA-256: B029504096CB18A16C99F076008B2AA0C55BFD0F670CC82D80C6CA497791EC35 - Baseline primary artifacts opened/hash-matched: 20/20. - V1 was treated as read-only. V2 uses the same twenty primary filenames only inside outputs_v2/. - Gate V2-0 reproduction record: repair_logs_v2/V2_BASELINE_DEFECT_REPRODUCTION.md.

Source lines 8–15; approximately 36 words.

Defect disposition

| ID | Severity | Baseline classification | V1 defect reproduced | V2 cure | Final status | Independent evidence | | V2-R001 | Critical | CONFIRMED | Artifact 06 first completeness branch reversed. | Decision Tree!C5:D5 corrected; exact hard stop at A3; Route Assertions sheet; downstream 05/07/14/15/18 aligned. | DONE — Observed QA PASS | qa_v2/qa_v2_decision_tree.json | | V2-R002 | High | CONFIRMED | All 34 V1 sheets lacked persisted panes. | Persistent pane added to every final V2 sheet; exact coordinates recorded and final XML reopened. | DONE — Observed QA PASS | qa_v2/qa_v2_workbook_structure.json | | V2-R003 | High | CONFIRMED | V1 Artifact 19 falsely certified frozen rows. | Historical failure retained; V2 reports only machine-observed coordinates. | DONE — Observed QA PASS | Artifact 19 §V2 historical defect record; qa_v2/qa_v2_workbook_structure.json | | V2-R004 | High | CONFIR…

Source lines 16–37; approximately 626 words. Tables/matrices: | ID | Severity | Baseline classification | V1 defect reproduced | V2 cure | Final status | Independent evidence |

Artifact-by-artifact change ledger

| Artifact | V1 SHA-256 | V2 SHA-256 | Changed | Exact section/sheet | Old behavior | New behavior / reason | Verification evidence | | 00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx | 7F51D857CA29AAD20B6E4359425283A49E36F4DE6567B6E07D5B9186D81D7D9B | DB4E4918599AF5350370EF748284C62D66C8062AB792AB414CB531C7496DA7C9 | Yes | Atomic Requirements; Evidence Catalog; V1 Defect History | Targeted audit defect or missing V2 control. | Replaced generic/circular evidence with exact requirement-specific evidence and honest dependency statuses. | Final workbook XML/QA and source-fidelity checks | | 01_SOURCE_COVERAGE_AND_RELIABILITY_LEDGER.xlsx | 9D301D0B60AA0A760E21D5B45E90EE4769982649E10190E2B22B07C8CC85CDA4 | C193718EBEDE1866EB2778F68D7F5EA4FAB80A58A49BD94FF3194C80FBC54105 | Yes | Coverage Ledger; Reliability Rules | Targeted audit defect or missing V2 control. | Corrected control/non-evide…

Source lines 38–62; approximately 753 words. Tables/matrices: | Artifact | V1 SHA-256 | V2 SHA-256 | Changed | Exact section/sheet | Old behavior | New behavior / reason | Verification evidence |

Observed verification summary

Decision-tree QA: PASS. - Probability-family QA: PASS. - Workbook structural QA: PASS; 40 pane PASS and 0 pane FAIL. - Requirement-evidence QA: PASS; every PASS row must have a nonempty, machine-resolvable exact locator. - Normalized evidence-reuse review: 194 duplicate groups; 194 independently allowed; 0 unreviewed; 0 substantive mismatches. - Citation/source-fidelity QA: PASS; 167 claims checked.

Source lines 63–71; approximately 51 words.

Remaining dependencies and boundaries

REPORT-DEPENDENT: report pages, exact findings/quotations, transmission timestamp, attachments, redactions, evidence list, and route-changing facts. - UCLA-CONFIRMATION-DEPENDENT: day-zero/day-one convention, completeness/issuance effect, later campus closures, DGE completion trigger, full CDP appearance procedure, and office-specific authority where official text is silent. - COUNSEL-DEPENDENT: waiver/exhaustion/finality, constitutional or mandamus theories, external deadlines/jurisdiction, interim-relief standards, settlement/release terms, and contested remedy authority. - Structured forecast weights remain subjective planning weights; they are not measured base rates. - The root checksum ledger cannot hash itself. It hashes every other ZIP member; the final archive SHA-256 is reported externally in the handoff and package-integrity result.

Source lines 72–79; approximately 99 words.

V1 history retained

V1 did not have persisted freeze panes despite its Artifact 19 certification. V2 does not rewrite that history. The V1 failure remains documented in the V2-0 reproduction table, this ledger, and Artifact 19. V1 files were not overwritten or deleted. > PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION

Source lines 80–84; approximately 56 words.

00_REQUIREMENT_LEDGER_AND_PRIOR_RESPONSE_AUDIT.xlsx

6 sheets; 1,625 aggregate worksheet rows; 0 formulas recorded in the structural inventory.

README

Dimensions: 19 rows × 8 columns; 54 populated cells; 0 formulas; freeze at B6 (x=1, y=5).

• Row 1: A1=V2 Requirement Ledger and Prior-Response Audit
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Direct-evidence ledger. Artifact 19 is generated from the same observed-evidence data; neither artifact is accepted as proof merely because the other points to it.
• Row 5: A5=Control; B5=Observed value
• Row 6: A6=Combined atomic rows; B6=1550
• Row 7: A7=V4 atoms; B7=619
• Row 8: A8=Original-prompt atoms; B8=633
• Closing row 15: A15=COUNSEL-DEPENDENT; B15=1
• Closing row 16: A16=NOT APPLICABLE; B16=48
• Closing row 17: A17=Evidence rule; B17=PASS requires an exact Markdown heading/line, workbook sheet/cell or range, or direct machine-observed file/ZIP result. Filename existence alone is insufficient.

Status Summary

Dimensions: 12 rows × 7 columns; 77 populated cells; 0 formulas; freeze at B6 (x=1, y=5).

• Row 1: A1=Atomic Requirement Status Summary
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Counts derive from the row-level status field. PARTIAL and dependency rows remain visible and prevent an all-PASS conclusion.
• Row 5: A5=Status; B5=Count; C5=Meaning; D5=V4; E5=Original; F5=V2
• Row 6: A6=PASS; B6=1497; C6=Direct evidence satisfies the presently completable requirement.; D6=597; E6=631; F6=269
• Row 7: A7=PARTIAL; B7=0; C7=A presently completable final gate remains open.; D7=0; E7=0; F7=0
• Row 8: A8=FAIL; B8=0; C8=Observed output contradicts or misses the requirement.; D8=0; E8=0; F8=0
• Closing row 8: A8=FAIL; B8=0; C8=Observed output contradicts or misses the requirement.; D8=0; E8=0; F8=0
• Closing row 9: A9=REPORT-DEPENDENT; B9=3; C9=Requires the future report/transmittal fact.; D9=2; E9=1; F9=0
• Closing row 10: A10=UCLA-CONFIRMATION-DEPENDENT; B10=1; C10=Requires UCLA or later controlling official text.; D10=1; E10=0; F10=0

Atomic Requirements

Dimensions: 1554 rows × 15 columns; 23,310 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Atomic Requirement Evidence Ledger
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Every PASS is tied to observed exported-file evidence. Dependency labels are reserved for genuinely unavailable facts or decisions; open repair/QA work remains PARTIAL.
• Row 4: A4=Requirement ID; B4=Controlling instruction; C4=Source location; D4=Faithful requirement text; E4=Requirement-specific acceptance criterion; F4=Exact final artifact
• Row 5: A5=V4-001; B5=00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; C5=work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md:10 — UCLA CRO PRE-REPORT RESPONSE SYSTEM — FINAL PRODUCTION, REPAIR, VALIDATION, AND DEPLOYMENT P…; D5=Status: The actual CRO investigation report and its transmittal email do not exist and will not be available during this run.; E5=V4-001: record the prompt metadata verbatim at work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md:10; no artifact-completion PASS is assigned.; F5=19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md
• Row 6: A6=V4-002; B6=00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; C6=work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md:14 — UCLA CRO PRE-REPORT RESPONSE SYSTEM — FINAL PRODUCTION, REPAIR, VALIDATION, AND DEPLOYMENT P…; D6=Create a genuinely complete, source-grounded, auditable, immediately deployable pre-report response system for Cooper Beaman’s pending UCLA Civil Rights Office investigation under UCLA Procedure 230.2 and the related Division of Graduate Education / Commit…; E6=V4-002: at qa_v2/qa_v2_deployment_completeness.json — primary_file_count, workbook_count, workbook_sheet_count, table_rows_checked, template_counts, playbook_counts, failure_count; qa_v2/citation_sampling.json — metadata.selectedCount, passCount, failCount…; F6=01_SOURCE_COVERAGE_AND_RELIABILITY_LEDGER.xlsx; qa_v2/citation_sampling.json; qa_v2/qa_v2_deployment_completeness.json
• Row 7: A7=V4-003; B7=00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; C7=work/input_package/CRO_CHATGPT_WORK_SOL_ULTRA_STAGE_B_INPUT_PACKAGE_V4_2026-07-22/00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md:16 — UCLA CRO PRE-REPORT RESPONSE SYSTEM — FINAL PRODUCTION, REPAIR, VALIDATION, AND DEPLOYMENT P…; D7=This is a production assignment, not another narrative case summary. The required result is a coordinated set of finished documents, spreadsheets, matrices, playbooks, deadline tools, and ready-to-review draft submissions that can be populated rapidly when…; E7=V4-003: at 02_STAGE_A_INTEGRATION_AND_PROCEDURAL_ARCHITECTURE.md — ## 8. Primary versus sensitivity and internal targets; observed lines 288–292, confirm a populated, operational implementation of “This is a production assignment, not another narrative cas…; F7=02_STAGE_A_INTEGRATION_AND_PROCEDURAL_ARCHITECTURE.md; 03_DEADLINE_CALCULATOR_AND_SEQUENCING_MATRIX.xlsx
• Closing row 1550: A1550=V2-294; B1550=CRO_GPT_WORK_5.6_SOL_ULTRA_V2_REPAIR_CONTINUATION_PROMPT_2026-07-23.md; C1550=work/v2_kit/CRO_GPT_WORK_5.6_SOL_ULTRA_V2_REPAIR_CONTINUATION_PROMPT_2026-07-23.md:471 — UCLA CRO PRE-REPORT RESPONSE SYSTEM — V2 TARGETED REPAIR, INDEPENDENT REVALIDATION, AND FINAL REPACKAGING > Definition of done; D1550=Artifacts 08, 10, and 18 contain the required expansions;; E1550=V2-294: compare the observed text/cell at qa_v2/qa_v2_deployment_completeness.json — baseline_matrix_checks and counts; 18_TWO_PAGE_EXECUTIVE_COMMAND_SHEET.md to “Artifacts 08, 10, and 18 contain the required expansions;”; PASS requires a substantive ma…; F1550=08_EXPECTED_RECORD_OMISSION_CONTRADICTION_MATRIX.xlsx; 10_DGE_CDP_MITIGATION_CROSSWALK.xlsx; 18_TWO_PAGE_EXECUTIVE_COMMAND_SHEET.md; qa_v2/qa_v2_deployment_completeness.json
• Closing row 1551: A1551=V2-295; B1551=CRO_GPT_WORK_5.6_SOL_ULTRA_V2_REPAIR_CONTINUATION_PROMPT_2026-07-23.md; C1551=work/v2_kit/CRO_GPT_WORK_5.6_SOL_ULTRA_V2_REPAIR_CONTINUATION_PROMPT_2026-07-23.md:472 — UCLA CRO PRE-REPORT RESPONSE SYSTEM — V2 TARGETED REPAIR, INDEPENDENT REVALIDATION, AND FINAL REPACKAGING > Definition of done; D1551=the final audit truthfully records any remaining dependency;; E1551=V2-295: compare the observed text/cell at 19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md — Atomic requirement status summary and Dependency register to “the final audit truthfully records any remaining dependency;”; PASS requires a substantive match and no co…; F1551=19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md
• Closing row 1552: A1552=V2-296; B1552=CRO_GPT_WORK_5.6_SOL_ULTRA_V2_REPAIR_CONTINUATION_PROMPT_2026-07-23.md; C1552=work/v2_kit/CRO_GPT_WORK_5.6_SOL_ULTRA_V2_REPAIR_CONTINUATION_PROMPT_2026-07-23.md:473 — UCLA CRO PRE-REPORT RESPONSE SYSTEM — V2 TARGETED REPAIR, INDEPENDENT REVALIDATION, AND FINAL REPACKAGING > Definition of done; D1552=the V2 ZIP is self-verifying;; E1552=V2-296: compare the observed text/cell at qa_v2/qa_v2_package_integrity.json — checks and root_ledger_self_hash_boundary; FINAL_OUTPUT_MANIFEST_V2.csv; FINAL_OUTPUT_SHA256SUMS_V2.txt to “the V2 ZIP is self-verifying;”; PASS requires a substantive match…; F1552=19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md; FINAL_OUTPUT_MANIFEST_V2.csv; FINAL_OUTPUT_SHA256SUMS_V2.txt; qa_v2/qa_v2_package_integrity.json

V2 Defect Disposition

Dimensions: 19 rows × 10 columns; 190 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=V2 Independent-Audit Defect Disposition
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=The independent audit is a defect input, not case evidence. Status reflects observed V2 exports; open final gates remain PARTIAL.
• Row 4: A4=Defect ID; B4=Severity; C4=Artifact / scope; D4=V1 reproduction; E4=Defect; F4=Acceptance test
• Row 5: A5=V2-R001; B5=critical; C5=06_HEARING_VS_COMMENTS_DECISION_SYSTEM.xlsx; D5=Reproduced in Gate V2-0; E5=The first completeness decision branch is reversed.; F5=YES leads to preservation/timestamp/A-B calculation/allegation map; NO leads to defect preservation, cure/clarification, protective dates, extension consideration, and a hard stop on final route scoring.
• Row 6: A6=V2-R002; B6=high; C6=all nine XLSX files; D6=Reproduced in Gate V2-0; E6=No freeze panes exist across the workbook set.; F6=Every scrollable sheet has a structurally verified freeze pane; any N/A is explicitly justified.
• Row 7: A7=V2-R003; B7=high; C7=19_FINAL_REQUIREMENT_COMPLIANCE_AUDIT.md; D7=Reproduced in Gate V2-0; E7=V1 falsely certifies frozen header/control rows.; F7=V2 records V1 failure historically, reports actual V2 pane coordinates, and makes no machine-observable false statement.
• Closing row 15: A15=V2-R011; B15=medium; C15=08_EXPECTED_RECORD_OMISSION_CONTRADICTION_MATRIX.xlsx; D15=Reproduced in Gate V2-0; E15=Matrix functions as a priority inventory rather than an exhaustive operational inventory.; F15=Distinct rows for each scoped action, material outside-scope item, high-value witness/document proposition, DGE integrity item, and Stage A handling rule.
• Closing row 16: A16=V2-R012; B16=medium; C16=18_TWO_PAGE_EXECUTIVE_COMMAND_SHEET.md; D16=Reproduced in Gate V2-0; E16=No explicit ranked top-three planning scenarios.; F16=Add three ranked scenarios with forecast layer, weight/band, and reorder trigger; preserve two-page usability.
• Closing row 17: A17=V2-R013; B17=medium; C17=final package; D17=Reproduced in Gate V2-0; E17=V1 ZIP is not fully self-verifying and input/output manifests are not clearly distinguished.; F17=V2 ZIP includes clearly named input manifest, output manifest, V2 hashes, repair ledger, and independent QA report.

Historical V1 Failures

Dimensions: 9 rows × 8 columns; 72 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Historical V1 Failures Preserved
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=These are historical observations. Later V2 repair does not rewrite V1 as if it passed.
• Row 4: A4=Historical ID; B4=V1 observed failure; C4=Exact V1 locator; D4=Independent evidence; E4=V1 status; F4=Required V2 cure
• Row 5: A5=HIST-V1-001; B5=Reversed first decision-tree branch.; C5=V1 Artifact 06 — Decision Tree first completeness node; D5=repair_logs_v2/V2_BASELINE_DEFECT_REPRODUCTION.md — V2-R001; E5=FAIL; F5=Correct YES/NO branches and hard stop; verify final exported cells.
• Row 6: A6=HIST-V1-002; B6=No persisted freeze panes across any workbook sheet.; C6=qa_v2/v1_workbook_structure.json — 9 workbooks / 34 sheets / 0 panes; D6=Direct worksheet-XML inspection; E6=FAIL; F6=Post-export V2 pane patch plus exact coordinate and structural QA.
• Row 7: A7=HIST-V1-003; B7=Artifact 19 falsely stated frozen control/header rows existed.; C7=V1 Artifact 19 — ## Check F — Spreadsheet quality; D7=Contradicted by qa_v2/v1_workbook_structure.json; E7=FAIL; F7=Record V1 failure and report only observed V2 pane coordinates.
• Closing row 5: A5=HIST-V1-001; B5=Reversed first decision-tree branch.; C5=V1 Artifact 06 — Decision Tree first completeness node; D5=repair_logs_v2/V2_BASELINE_DEFECT_REPRODUCTION.md — V2-R001; E5=FAIL; F5=Correct YES/NO branches and hard stop; verify final exported cells.
• Closing row 6: A6=HIST-V1-002; B6=No persisted freeze panes across any workbook sheet.; C6=qa_v2/v1_workbook_structure.json — 9 workbooks / 34 sheets / 0 panes; D6=Direct worksheet-XML inspection; E6=FAIL; F6=Post-export V2 pane patch plus exact coordinate and structural QA.
• Closing row 7: A7=HIST-V1-003; B7=Artifact 19 falsely stated frozen control/header rows existed.; C7=V1 Artifact 19 — ## Check F — Spreadsheet quality; D7=Contradicted by qa_v2/v1_workbook_structure.json; E7=FAIL; F7=Record V1 failure and report only observed V2 pane coordinates.

Verification Method

Dimensions: 12 rows × 5 columns; 55 populated cells; 0 formulas; freeze at B6 (x=1, y=5).

• Row 1: A1=Verification Method and Noncircularity Controls
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Artifact 00 and Artifact 19 share a data source, but neither is accepted as proof merely because the other cites it.
• Row 5: A5=Control; B5=Method; C5=Input; D5=Output; E5=Acceptance rule
• Row 6: A6=Markdown evidence; B6=Direct line scan; record enclosing heading and exact observed line.; C6=Final exported .md file; D6=Locator + excerpt; E6=PASS requires substantive textual match.
• Row 7: A7=Workbook evidence; B7=oai/artifact-tool reimport; scan exact sheet/cell values and formulas.; C7=Final exported .xlsx file; D7=Sheet/cell locator + value/formula; E7=PASS cannot rest on workbook filename.
• Row 8: A8=Structural counts; B8=Recompute scenario/template/probability/output counts.; C8=Final exported files; D8=Observed count and arithmetic; E8=Observed total must equal acceptance total.
• Closing row 8: A8=Structural counts; B8=Recompute scenario/template/probability/output counts.; C8=Final exported files; D8=Observed count and arithmetic; E8=Observed total must equal acceptance total.
• Closing row 9: A9=Dependency labels; B9=Narrow rules distinguish unavailable facts from unfinished work.; C9=Requirement text + artifact evidence; D9=Dependency or PARTIAL status; E9=Presently completable work may not be hidden as dependency.
• Closing row 10: A10=Artifact 00 self-check; B10=Reimport after export and inspect headers, row count, status values, and ranges.; C10=Final Artifact 00; D10=qa_v2/requirement_audit_validation_v2.json; E10=No missing locator/evidence on PASS rows.

01_SOURCE_COVERAGE_AND_RELIABILITY_LEDGER.xlsx

3 sheets; 71 aggregate worksheet rows; 0 formulas recorded in the structural inventory.

README

Dimensions: 15 rows × 8 columns; 46 populated cells; 0 formulas; freeze at B6 (x=1, y=5).

• Row 1: A1=Source Coverage and Reliability Ledger
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Gate 2 inventory. Full traversal, relevant-passage verification, and page-image verification are distinct statuses.
• Row 5: A5=Control; B5=Value
• Row 6: A6=Package files indexed; B6=39
• Row 7: A7=Case-record files; B7=20
• Row 8: A8=Stage A artifacts; B8=6
• Closing row 11: A11=Full traversal definition; B11=Traversal labels distinguish page/text/sheet traversal from focused proposition verification and do not claim semantic review of every token.
• Closing row 12: A12=Relevant-passage verification; B12=Load-bearing sections checked against page-separated text or rendered page.
• Closing row 13: A13=Page-image verification; B13=Recorded only where a page or worksheet image was actually rendered and visually checked.

Coverage Ledger

Dimensions: 43 rows × 18 columns; 774 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Source Coverage and Reliability Ledger
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Every case file, Stage A artifact, prior-run audit input, and package-control file is represented; filters support tier and review-status audit.
• Row 4: A4=Relative path and filename; B4=SHA-256; C4=File type; D4=Bytes; E4=Date or date range; F4=Source tier
• Row 5: A5=00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md; B5=638EF79F100A30BF559537E8238522FDDE844746B7D313B02776F2C4C560FAE9; C5=.md; D5=32903; E5=2026-07-22; F5=CONTROL / NON-EVIDENCE
• Row 6: A6=00_START_HERE/01_PACKAGE_README.md; B6=96D8DDE8312569DB9F12DD4711934214594A3EACCB3335B0BCD8495533DA2237; C6=.md; D6=2181; E6=See source / metadata; F6=CONTROL / NON-EVIDENCE
• Row 7: A7=00_START_HERE/02_SOURCE_ROLE_MAP.md; B7=7529E4030B87A7E424D67856806B1242262229B10F816610603F8F60587B2AA1; C7=.md; D7=5162; E7=See source / metadata; F7=CONTROL / NON-EVIDENCE
• Closing row 39: A39=03_PRIOR_RUN_AUDIT/05_SUPERSEDED_WORK_MASTER_PROMPT_V3_REFERENCE_ONLY.md; B39=81306CA9DE2EE5C177E024653816880D2CA28A1A9DDA656848282C4558F8E967; C39=.md; D39=15886; E39=See source / metadata; F39=CONTROL / NON-EVIDENCE
• Closing row 40: A40=04_PACKAGE_CONTROL/PACKAGE_MANIFEST.csv; B40=7C067C0668A5D86E6B200DFFCAF641613E036427112188BD2852160170D073BC; C40=.csv; D40=5741; E40=See source / metadata; F40=CONTROL / NON-EVIDENCE
• Closing row 41: A41=04_PACKAGE_CONTROL/PACKAGE_MANIFEST.json; B41=52C83A5F963505A5303C1B46DD2702F49783FD450673613AECBBBD2425964264; C41=.json; D41=9092; E41=See source / metadata; F41=CONTROL / NON-EVIDENCE

Reliability Rules

Dimensions: 13 rows × 4 columns; 52 populated cells; 0 formulas; freeze at A5 (x=0, y=4).

• Row 1: A1=Reliability and Epistemic Rules
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=These rules govern every downstream claim, matrix, forecast, playbook, and template.
• Row 4: A4=Tier / status; B4=Permitted use; C4=Forbidden upgrade; D4=Operational rule
• Row 5: A5=CONTROL / NON-EVIDENCE; B5=Instruction, manifest, checksum, lineage, or audit control; C5=Never case-fact evidence or corroboration; D5=Verify integrity and workflow role only.
• Row 6: A6=Tier 0; B6=Policy identity, exact procedure, official provenance, calculations, source silence; C6=No report-outcome inference; D6=Controls policy/deadline statements.
• Row 7: A7=Tier 1A; B7=Controlling or primary case record; C7=A record of an allegation or party position does not prove it; D7=Use the smallest passage and preserve speaker/author.
• Closing row 9: A9=Tier 2; B9=User-authored synthesis, chronology, or advocacy; C9=Not independent corroboration; D9=Verify load-bearing assertions against Tier 1 where feasible.
• Closing row 10: A10=Tier 3; B10=Prior AI or predictive analysis; C10=Never corroboration or authority; D10=Hypothesis, omission, or salvage use only.
• Closing row 11: A11=Noncitation; B11=Possible report-treatment signal; C11=Not proof of nonconsideration; D11=Use one of the defined treatment statuses.

03_DEADLINE_CALCULATOR_AND_SEQUENCING_MATRIX.xlsx

12 sheets; 1,156 aggregate worksheet rows; 2,150 formulas recorded in the structural inventory.

README

Dimensions: 18 rows × 8 columns; 60 populated cells; 0 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Deadline and Sequencing Table; B1=Deadline and Sequencing Table; C1=Deadline and Sequencing Table; D1=Deadline and Sequencing Table; E1=Deadline and Sequencing Table; F1=Deadline and Sequencing Table
• Row 2: A2=Neutral administrative-policy arithmetic. Reference date: 2026-07-22. Informational only; UCLA confirmation is required for actual use.
• Row 4: A4=Scope; B4=Hypothetical transmissions from 2026-07-22 through 2026-07-31 and an unextended sequence beginning 2026-07-31.
• Row 5: A5=Primary convention; B5=Start date excluded; Saturdays and Sundays excluded; no campus closures were confirmed on the allowed UCLA domains for the relevant period.
• Row 6: A6=Alternative convention; B6=Start date counted when it is a University business day.
• Row 7: A7=Holiday / curtailment sensitivity; B7=A separate scenario treats seven target-period UCLA-observed holidays and three possible late-December curtailment weekdays as non-business days; it also excludes 2027-01-01 if the sequence crosses the year boundary. None was confirmed here as a full-campu…
• Row 8: A8=Method 1; B8=Excel WORKDAY.INTL formulas using the selected exclusion range.
• Closing row 12: A12=Receipt assumption; B12=For the Chancellor period, the hypothetical assumes the Chancellor receives the appeal on the same date it is submitted.
• Closing row 13: A13=Closure warning; B13=Do not treat an observed holiday as a confirmed campus closure without UCLA confirmation.
• Closing row 15: A15=Source rule: “Days mean University business days. It does not include Saturdays, Sundays, or days on which the campus is closed.”

Transmission Matrix

Dimensions: 64 rows × 17 columns; 1,071 populated cells; 240 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Hypothetical Transmission Matrix; B1=Hypothetical Transmission Matrix; C1=Hypothetical Transmission Matrix; D1=Hypothetical Transmission Matrix; E1=Hypothetical Transmission Matrix; F1=Hypothetical Transmission Matrix
• Row 2: A2=One row per transmission date, period, and counting assumption. Method 1 and Method 2 are formula-driven and independently structured.
• Row 4: A4=Calculation ID; B4=Starting event; C4=Transmission date; D4=Period; E4=Days; F4=Counting assumption
• Row 5: A5=TM-001; B5=Hypothetical investigation-report transmission; C5=46225; D5=Hearing-request period; E5=10; F5=A - Starting date excluded
• Row 6: A6=TM-002; B6=Hypothetical investigation-report transmission; C6=46225; D6=Hearing-request period; E6=10; F6=B - Starting date counted if it is a University business day
• Row 7: A7=TM-003; B7=Hypothetical investigation-report transmission; C7=46225; D7=Written-comment period if no hearing; E7=15; F7=A - Starting date excluded
• Row 8: A8=TM-004; B8=Hypothetical investigation-report transmission; C8=46225; D8=Written-comment period if no hearing; E8=15; F8=B - Starting date counted if it is a University business day
• Closing row 60: A60=TM-056; B60=Hypothetical investigation-report transmission; C60=46234; D60=Hearing-request period; E60=10; F60=B - Starting date counted if it is a University business day
• Closing row 61: A61=TM-057; B61=Hypothetical investigation-report transmission; C61=46234; D61=Written-comment period if no hearing; E61=15; F61=A - Starting date excluded
• Closing row 62: A62=TM-058; B62=Hypothetical investigation-report transmission; C62=46234; D62=Written-comment period if no hearing; E62=15; F62=B - Starting date counted if it is a University business day

Excluded Dates

Dimensions: 679 rows × 10 columns; 6,780 populated cells; 0 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Every Excluded Date; B1=Every Excluded Date; C1=Every Excluded Date; D1=Every Excluded Date; E1=Every Excluded Date; F1=Every Excluded Date
• Row 2: A2=One row per excluded starting date, weekend, confirmed closure, or scenario-only holiday / possible curtailment date for every calculation in this workbook.
• Row 4: A4=Calculation ID; B4=Sheet / branch; C4=Anchor date; D4=Event / period; E4=Scenario / assumption; F4=Excluded date
• Row 5: A5=TM-001; B5=Transmission Matrix; C5=46225; D5=Hearing-request period; E5=A - Starting date excluded; F5=46225
• Row 6: A6=TM-001; B6=Transmission Matrix; C6=46225; D6=Hearing-request period; E6=A - Starting date excluded; F6=46228
• Row 7: A7=TM-001; B7=Transmission Matrix; C7=46225; D7=Hearing-request period; E7=A - Starting date excluded; F7=46229
• Row 8: A8=TM-001; B8=Transmission Matrix; C8=46225; D8=Hearing-request period; E8=A - Starting date excluded; F8=46235
• Closing row 675: A675=NH-H-B-20; B675=No-Hearing Branch; C675=46234; D675=Investigation report finalization; E675=H-B - Holiday + possible curtailment sensitivity / start counted if business day; F675=46243
• Closing row 676: A676=NH-H-B-20; B676=No-Hearing Branch; C676=46234; D676=Investigation report finalization; E676=H-B - Holiday + possible curtailment sensitivity / start counted if business day; F676=46249
• Closing row 677: A677=NH-H-B-20; B677=No-Hearing Branch; C677=46234; D677=Investigation report finalization; E677=H-B - Holiday + possible curtailment sensitivity / start counted if business day; F677=46250

Max Sequence

Dimensions: 44 rows × 17 columns; 731 populated cells; 148 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Unextended Hearing-and-Appeal Sequence from 2026-07-31; B1=Unextended Hearing-and-Appeal Sequence from 2026-07-31; C1=Unextended Hearing-and-Appeal Sequence from 2026-07-31; D1=Unextended Hearing-and-Appeal Sequence from 2026-07-31; E1=Unextended Hearing-and-Appeal Sequence from 2026-07-31; F1=Unextended Hearing-and-Appeal Sequence from 2026-07-31
• Row 2: A2=This is the longest sequence obtainable from the stated, unextended periods under the stated assumptions. It is not an absolute maximum because good-cause extensions are permitted without a stated numerical cap.
• Row 4: A4=Scenario; B4=Step; C4=Event; D4=Anchor event; E4=Anchor date; F4=Direction
• Row 5: A5=P-A - Primary / start excluded; B5=1; C5=Investigation report transmitted / issued; D5=Hypothetical input; E5=46234; F5=Forward
• Row 6: A6=P-A - Primary / start excluded; B6=2; C6=Hearing-request period ends; D6=Investigation report transmitted / issued; E6==H5 [cached 46234]; F6=Forward
• Row 7: A7=P-A - Primary / start excluded; B7=3; C7=Hearing completed at the stated 60-Day limit; D7=Investigation report transmitted / issued; E7==H5 [cached 46234]; F7=Forward
• Row 8: A8=P-A - Primary / start excluded; B8=4; C8=Latest date for at least 10 Days’ hearing notice; D8=Hearing completed at the stated 60-Day limit; E8==H7 [cached 46318]; F8=Backward
• Closing row 40: A40=H-B - Holiday + possible curtailment sensitivity / start counted if business day; B40=6; C40=Hearing report forwarded; D40=Hearing completed at the stated 60-Day limit; E40==H37 [cached 46318]; F40=Forward
• Closing row 41: A41=H-B - Holiday + possible curtailment sensitivity / start counted if business day; B41=7; C41=Comments on hearing report due; D41=Hearing report forwarded; E41==H40 [cached 46331]; F41=Forward
• Closing row 42: A42=H-B - Holiday + possible curtailment sensitivity / start counted if business day; B42=8; C42=Vice Chancellor written decision; D42=Hearing report forwarded; E42==H40 [cached 46331]; F42=Forward

No-Hearing Branch

Dimensions: 12 rows × 14 columns; 154 populated cells; 24 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=No-Hearing Branch from 2026-07-31; B1=No-Hearing Branch from 2026-07-31; C1=No-Hearing Branch from 2026-07-31; D1=No-Hearing Branch from 2026-07-31; E1=No-Hearing Branch from 2026-07-31; F1=No-Hearing Branch from 2026-07-31
• Row 2: A2=The 15-Day comment period and 20-Day finalization period are both anchored to investigation-report issuance; they are not added together.
• Row 4: A4=Scenario; B4=Event; C4=Anchor date; D4=Days; E4=First result - Method 1; F4=Independent recomputation - Method 2
• Row 5: A5=P-A - Primary / start excluded; B5=Written comments due if no hearing is requested; C5=46234; D5=15; E5==WORKDAY.INTL(C5,D5,1,’Closure Status’!$A$7:$A$7) [cached 46255]; F5==INDEX(‘Calendar’!$A$5:$A$200,MATCH(INDEX(‘Calendar’!$F$5:$F$200,MATCH(C5,’Calendar’!$A$5:$A$200,0))+D5,’Calendar’!$F$5:$F$200,0)) [cached 46255]
• Row 6: A6=P-A - Primary / start excluded; B6=Investigation report finalization; C6=46234; D6=20; E6==WORKDAY.INTL(C6,D6,1,’Closure Status’!$A$7:$A$7) [cached 46262]; F6==INDEX(‘Calendar’!$A$5:$A$200,MATCH(INDEX(‘Calendar’!$F$5:$F$200,MATCH(C6,’Calendar’!$A$5:$A$200,0))+D6,’Calendar’!$F$5:$F$200,0)) [cached 46262]
• Row 7: A7=P-B - Primary / start counted if business day; B7=Written comments due if no hearing is requested; C7=46234; D7=15; E7==WORKDAY.INTL(C7,D7-IF(AND(WEEKDAY(C7,2)\<=5,COUNTIF(‘Closure Status’!$A$7:$A$7,C7)=0),1,0),1,’Closure Status’!$A$7:$A$7) [cached 46254]; F7==INDEX(‘Calendar’!$A$5:$A$200,MATCH(INDEX(‘Calendar’!$F$5:$F$200,MATCH(C7,’Calendar’!$A$5:$A$200,0))-INDEX(‘Calendar’!$E$5:$E$200,MATCH(C7,’Calendar’!$A$5:$A$200,0))+D7,’Calendar’!$F$5:$F$200,0)) [cached 46254]
• Row 8: A8=P-B - Primary / start counted if business day; B8=Investigation report finalization; C8=46234; D8=20; E8==WORKDAY.INTL(C8,D8-IF(AND(WEEKDAY(C8,2)\<=5,COUNTIF(‘Closure Status’!$A$7:$A$7,C8)=0),1,0),1,’Closure Status’!$A$7:$A$7) [cached 46261]; F8==INDEX(‘Calendar’!$A$5:$A$200,MATCH(INDEX(‘Calendar’!$F$5:$F$200,MATCH(C8,’Calendar’!$A$5:$A$200,0))-INDEX(‘Calendar’!$E$5:$E$200,MATCH(C8,’Calendar’!$A$5:$A$200,0))+D8,’Calendar’!$F$5:$F$200,0)) [cached 46261]
• Closing row 8: A8=P-B - Primary / start counted if business day; B8=Investigation report finalization; C8=46234; D8=20; E8==WORKDAY.INTL(C8,D8-IF(AND(WEEKDAY(C8,2)\<=5,COUNTIF(‘Closure Status’!$A$7:$A$7,C8)=0),1,0),1,’Closure Status’!$A$7:$A$7) [cached 46261]; F8==INDEX(‘Calendar’!$A$5:$A$200,MATCH(INDEX(‘Calendar’!$F$5:$F$200,MATCH(C8,’Calendar’!$A$5:$A$200,0))-INDEX(‘Calendar’!$E$5:$E$200,MATCH(C8,’Calendar’!$A$5:$A$200,0))+D8,’Calendar’!$F$5:$F$200,0)) [cached 46261]
• Closing row 9: A9=H-A - Holiday + possible curtailment sensitivity / start excluded; B9=Written comments due if no hearing is requested; C9=46234; D9=15; E9==WORKDAY.INTL(C9,D9,1,’Closure Status’!$A$10:$A$22) [cached 46255]; F9==INDEX(‘Calendar’!$A$5:$A$200,MATCH(INDEX(‘Calendar’!$I$5:$I$200,MATCH(C9,’Calendar’!$A$5:$A$200,0))+D9,’Calendar’!$I$5:$I$200,0)) [cached 46255]
• Closing row 10: A10=H-A - Holiday + possible curtailment sensitivity / start excluded; B10=Investigation report finalization; C10=46234; D10=20; E10==WORKDAY.INTL(C10,D10,1,’Closure Status’!$A$10:$A$22) [cached 46262]; F10==INDEX(‘Calendar’!$A$5:$A$200,MATCH(INDEX(‘Calendar’!$I$5:$I$200,MATCH(C10,’Calendar’!$A$5:$A$200,0))+D10,’Calendar’!$I$5:$I$200,0)) [cached 46262]

Closure Status

Dimensions: 25 rows × 7 columns; 147 populated cells; 0 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=UCLA Closure and Holiday Status; B1=UCLA Closure and Holiday Status; C1=UCLA Closure and Holiday Status; D1=UCLA Closure and Holiday Status; E1=UCLA Closure and Holiday Status; F1=UCLA Closure and Holiday Status
• Row 2: A2=Only expressly confirmed full-campus closure dates are used in the primary calculations. None were located on the allowed UCLA domains as of 2026-07-22.
• Row 4: A4=Date; B4=Name / status; C4=Classification; D4=Official UCLA source; E4=Express source text / basis; F4=Used in primary calculations?
• Row 7: B7=No expressly designated full-campus closure date located for 2026-07-22 through 2026-12-31; C7=Confirmed campus closure ledger; D7=https://chr.ucla.edu/personnel-and-payroll-transaction/calendars-schedules; E7=The UCLA calendar page says its linked calendar shows UCLA holidays, but the linked file is outside the permitted-domain list; no target-period closure announcement was located.; F7=N/A; G7=Absence of a located announcement is not proof the campus will remain open; confirm with UCLA.
• Row 10: A10=46272; B10=Labor Day; C10=UCLA-observed holiday; not confirmed here as a full-campus closure; D10=https://chr.ucla.edu/policies-and-labor-contracts/procedure-40-2013-holidays; E10=UCLA Procedure 2.210 lists the holiday by name. The displayed date is calendar arithmetic and is not an express UCLA closure designation in the reviewed source.; F10=No - sensitivity scenario only
• Row 11: A11=46337; B11=Veterans Day; C11=UCLA-observed holiday; not confirmed here as a full-campus closure; D11=https://chr.ucla.edu/policies-and-labor-contracts/procedure-40-2013-holidays; E11=UCLA Procedure 2.210 lists the holiday by name. The displayed date is calendar arithmetic and is not an express UCLA closure designation in the reviewed source.; F11=No - sensitivity scenario only
• Row 12: A12=46352; B12=Thanksgiving Day; C12=UCLA-observed holiday; not confirmed here as a full-campus closure; D12=https://chr.ucla.edu/policies-and-labor-contracts/procedure-40-2013-holidays; E12=UCLA Procedure 2.210 lists the holiday by name. The displayed date is calendar arithmetic and is not an express UCLA closure designation in the reviewed source.; F12=No - sensitivity scenario only
• Closing row 18: A18=46384; B18=Possible non-holiday winter-curtailment weekday; C18=Uncertain - possible non-holiday winter-curtailment day; not currently designated as a UCLA closure; D18=https://chr.ucla.edu/news/2025-26-winter-holiday-curtailment; E18=No 2026-27 announcement was located as of 2026-07-22. The source is the prior year’s curtailment notice and is used only to show that non-holiday weekdays may later be designated.; F18=No - sensitivity scenario only
• Closing row 19: A19=46385; B19=Possible non-holiday winter-curtailment weekday; C19=Uncertain - possible non-holiday winter-curtailment day; not currently designated as a UCLA closure; D19=https://chr.ucla.edu/news/2025-26-winter-holiday-curtailment; E19=No 2026-27 announcement was located as of 2026-07-22. The source is the prior year’s curtailment notice and is used only to show that non-holiday weekdays may later be designated.; F19=No - sensitivity scenario only
• Closing row 20: A20=46386; B20=Possible non-holiday winter-curtailment weekday; C20=Uncertain - possible non-holiday winter-curtailment day; not currently designated as a UCLA closure; D20=https://chr.ucla.edu/news/2025-26-winter-holiday-curtailment; E20=No 2026-27 announcement was located as of 2026-07-22. The source is the prior year’s curtailment notice and is used only to show that non-holiday weekdays may later be designated.; F20=No - sensitivity scenario only

Calendar

Dimensions: 200 rows × 9 columns; 1,791 populated cells; 1,568 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Independent Calendar Recomputation; B1=Independent Calendar Recomputation; C1=Independent Calendar Recomputation; D1=Independent Calendar Recomputation; E1=Independent Calendar Recomputation; F1=Independent Calendar Recomputation
• Row 2: A2=Method 2 uses an explicit date-by-date business-day flag and cumulative ordinal. This sheet is intentionally mechanical and auditable.
• Row 4: A4=Date; B4=Weekday; C4=Weekend?; D4=Confirmed closure?; E4=Primary business-day flag; F4=Primary cumulative ordinal
• Row 5: A5=46223; B5==TEXT(A5,”dddd”) [cached Monday]; C5==WEEKDAY(A5,2)>5 [cached 0]; D5==COUNTIF(‘Closure Status’!$A$7:$A$7,A5)>0 [cached 0]; E5==–AND(NOT(C5),NOT(D5)) [cached 1]; F5==E5 [cached 1]
• Row 6: A6=46224; B6==TEXT(A6,”dddd”) [cached Tuesday]; C6==WEEKDAY(A6,2)>5 [cached 0]; D6==COUNTIF(‘Closure Status’!$A$7:$A$7,A6)>0 [cached 0]; E6==–AND(NOT(C6),NOT(D6)) [cached 1]; F6==F5+E6 [cached 2]
• Row 7: A7=46225; B7==TEXT(A7,”dddd”) [cached Wednesday]; C7==WEEKDAY(A7,2)>5 [cached 0]; D7==COUNTIF(‘Closure Status’!$A$7:$A$7,A7)>0 [cached 0]; E7==–AND(NOT(C7),NOT(D7)) [cached 1]; F7==F6+E7 [cached 3]
• Row 8: A8=46226; B8==TEXT(A8,”dddd”) [cached Thursday]; C8==WEEKDAY(A8,2)>5 [cached 0]; D8==COUNTIF(‘Closure Status’!$A$7:$A$7,A8)>0 [cached 0]; E8==–AND(NOT(C8),NOT(D8)) [cached 1]; F8==F7+E8 [cached 4]
• Closing row 196: A196=46414; B196==TEXT(A196,”dddd”) [cached Wednesday]; C196==WEEKDAY(A196,2)>5 [cached 0]; D196==COUNTIF(‘Closure Status’!$A$7:$A$7,A196)>0 [cached 0]; E196==–AND(NOT(C196),NOT(D196)) [cached 1]; F196==F195+E196 [cached 138]
• Closing row 197: A197=46415; B197==TEXT(A197,”dddd”) [cached Thursday]; C197==WEEKDAY(A197,2)>5 [cached 0]; D197==COUNTIF(‘Closure Status’!$A$7:$A$7,A197)>0 [cached 0]; E197==–AND(NOT(C197),NOT(D197)) [cached 1]; F197==F196+E197 [cached 139]
• Closing row 198: A198=46416; B198==TEXT(A198,”dddd”) [cached Friday]; C198==WEEKDAY(A198,2)>5 [cached 0]; D198==COUNTIF(‘Closure Status’!$A$7:$A$7,A198)>0 [cached 0]; E198==–AND(NOT(C198),NOT(D198)) [cached 1]; F198==F197+E198 [cached 140]

Source Rules

Dimensions: 18 rows × 7 columns; 119 populated cells; 0 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Calculation Source Rules; B1=Calculation Source Rules; C1=Calculation Source Rules; D1=Calculation Source Rules; E1=Calculation Source Rules; F1=Calculation Source Rules
• Row 2: A2=Exact or closely bounded source text is paired with the operative anchor. Citations identify the official PDF and printed page.
• Row 4: A4=Rule ID; B4=Event / period; C4=Days; D4=Anchor; E4=Source text; F4=Exact citation
• Row 5: A5=DAYS; B5=Definition of Days; D5=N/A; E5=Days mean University business days. It does not include Saturdays, Sundays, or days on which the campus is closed.; F5=Procedure 230.2, II, printed p. 2; https://www.adminpolicies.ucla.edu/pdf/230-2.pdf; G5=Does not state whether the issuance date is day 0 or day 1.
• Row 6: A6=ISSUANCE; B6=Meaning of issuance; D6=Date of transmission; E6=”Issuance” as used in UCLA Procedure 230.2 and in this guidance means date of transmission.; F6=Attachment B, opening text, p. 1; https://www.adminpolicies.ucla.edu/pdf/230-2-B.pdf; G6=Does not define completeness, time of day, receipt, or start-day inclusion.
• Row 7: A7=HEARING_REQ; B7=Hearing request; C7=10; D7=Investigation report issuance; E7=In the event the Grievant disagrees with the findings in the investigation report, the Grievant may request a formal grievance hearing within ten (10) Days of the issuance of the investigation report.; F7=Procedure 230.2, VI.A.3, printed p. 5; https://www.adminpolicies.ucla.edu/pdf/230-2.pdf
• Row 8: A8=NO_HEARING_COMMENTS; B8=Written comments if no hearing; C8=15; D8=Investigation report issuance; E8=If the Grievant does not request a formal hearing within the time permitted, the Grievant and the Subject of the Grievance have fifteen (15) Days of the issuance of the investigation report, to each submit written comments.; F8=Procedure 230.2, VI.A.4, printed p. 5; https://www.adminpolicies.ucla.edu/pdf/230-2.pdf
• Closing row 14: A14=REPORT_COMMENTS; B14=Comments on hearing report; C14=5; D14=Hearing report issuance; E14=The Grievant and Subject of the Grievance may each submit written comments within five (5) Days of the issuance of the hearing report.; F14=Procedure 230.2, VI.B.10, printed p. 6; https://www.adminpolicies.ucla.edu/pdf/230-2.pdf
• Closing row 15: A15=VC_DECISION; B15=Vice Chancellor decision; C15=15; D15=Hearing report issuance; E15=The Vice Chancellor shall issue a written decision within fifteen (15) Days of the issuance of the hearing report.; F15=Procedure 230.2, VI.B.11, printed pp. 6-7; https://www.adminpolicies.ucla.edu/pdf/230-2.pdf
• Closing row 16: A16=APPEAL; B16=Appeal; C16=5; D16=Vice Chancellor decision issuance; E16=Within five (5) Days following the issuance of the Vice Chancellor’s decision, the Grievant may file a written appeal.; F16=Procedure 230.2, VI.C.1, printed p. 7; https://www.adminpolicies.ucla.edu/pdf/230-2.pdf

LIVE INPUTS

Dimensions: 36 rows × 10 columns; 168 populated cells; 10 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Live Inputs and Exclusion Controls; B1=Live Inputs and Exclusion Controls; C1=Live Inputs and Exclusion Controls; D1=Live Inputs and Exclusion Controls; E1=Live Inputs and Exclusion Controls; F1=Live Inputs and Exclusion Controls
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; B2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; C2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; D2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; E2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; F2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Enter verified facts only. Blank inputs intentionally suppress calculated dates. Primary closures and sensitivity-only dates remain separate.; B3=Enter verified facts only. Blank inputs intentionally suppress calculated dates. Primary closures and sensitivity-only dates remain separate.; C3=Enter verified facts only. Blank inputs intentionally suppress calculated dates. Primary closures and sensitivity-only dates remain separate.; D3=Enter verified facts only. Blank inputs intentionally suppress calculated dates. Primary closures and sensitivity-only dates remain separate.; E3=Enter verified facts only. Blank inputs intentionally suppress calculated dates. Primary closures and sensitivity-only dates remain separate.; F3=Enter verified facts only. Blank inputs intentionally suppress calculated dates. Primary closures and sensitivity-only dates remain separate.
• Row 5: A5=Transmission / case input; B5=Verified value; F5=Downstream verified anchor; G5=Verified value; I5=Operating control; J5=Instruction
• Row 6: A6=Complete report transmission date; F6=Actual / planned hearing date; I6=Earliest plausible date; J6=Use the earlier primary A/B date until UCLA confirms counting.
• Row 7: A7=Native transmittal timestamp; B7=[TRANSMITTAL_TIMESTAMP]; F7=Hearing-report issuance date; I7=Decision target; J7=Three qualifying business days before earliest plausible date.
• Row 8: A8=Printed report date; B8=[REPORT_DATE]; F8=Vice Chancellor decision issuance; I8=Draft target; J8=Two qualifying business days before earliest plausible date.
• Closing row 32: C32==IF(B21=”“,”“,B21); D32=Confirmed-closure mirror 6; feeds sensitivity formulas if entered
• Closing row 33: C33==IF(B22=”“,”“,B22); D33=Confirmed-closure mirror 7; feeds sensitivity formulas if entered
• Closing row 34: C34==IF(B23=”“,”“,B23); D34=Confirmed-closure mirror 8; feeds sensitivity formulas if entered

STRATEGIC DEADLINES

Dimensions: 18 rows × 17 columns; 306 populated cells; 112 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Strategic Deadline and Sequencing Matrix; B1=Strategic Deadline and Sequencing Matrix; C1=Strategic Deadline and Sequencing Matrix; D1=Strategic Deadline and Sequencing Matrix; E1=Strategic Deadline and Sequencing Matrix; F1=Strategic Deadline and Sequencing Matrix
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; B2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; C2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; D2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; E2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; F2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Dates populate only after the corresponding verified anchor is entered. Primary A/B and sensitivity A/B are separate. Internal targets are project-management dates, not UCLA deadlines.; B3=Dates populate only after the corresponding verified anchor is entered. Primary A/B and sensitivity A/B are separate. Internal targets are project-management dates, not UCLA deadlines.; C3=Dates populate only after the corresponding verified anchor is entered. Primary A/B and sensitivity A/B are separate. Internal targets are project-management dates, not UCLA deadlines.; D3=Dates populate only after the corresponding verified anchor is entered. Primary A/B and sensitivity A/B are separate. Internal targets are project-management dates, not UCLA deadlines.; E3=Dates populate only after the corresponding verified anchor is entered. Primary A/B and sensitivity A/B are separate. Internal targets are project-management dates, not UCLA deadlines.; F3=Dates populate only after the corresponding verified anchor is entered. Primary A/B and sensitivity A/B are separate. Internal targets are project-management dates, not UCLA deadlines.
• Row 4: A4=ID; B4=Branch; C4=Event / output; D4=Anchor; E4=Source period; F4=Source rule / citation
• Row 5: A5=DL-01; B5=CRO route; C5=Hearing request; D5=Report issuance; E5=10 Days; F5=Procedure 230.2 §VI.A.3, p. 5
• Row 6: A6=DL-02; B6=No-hearing; C6=Written comments; D6=Report issuance; E6=15 Days; F6=§VI.A.4, p. 5
• Row 7: A7=DL-03; B7=No-hearing; C7=Report finalization; D7=Report issuance; E7=20 Days; F7=§VI.A.5, p. 5
• Closing row 14: A14=DL-10; B14=Appeal; C14=Chancellor appeal; D14=Vice Chancellor decision issuance; E14=5 Days following; F14=§VI.C.1, p. 7
• Closing row 15: A15=DL-11; B15=Appeal; C15=Chancellor decision; D15=Receipt of appeal; E15=10 Days; F15=§VI.C.4, p. 7
• Closing row 16: A16=DL-12; B16=DGE - no mitigation; C16=DGE written denial; D16=DGE receipt of Investigation Materials; E16=30 calendar days; F16=Standards, printed p. 33 (file p. 34)

BRANCH MAP

Dimensions: 14 rows × 8 columns; 112 populated cells; 0 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Procedure 230.2 / DGE / CDP Branch Map; B1=Procedure 230.2 / DGE / CDP Branch Map; C1=Procedure 230.2 / DGE / CDP Branch Map; D1=Procedure 230.2 / DGE / CDP Branch Map; E1=Procedure 230.2 / DGE / CDP Branch Map; F1=Procedure 230.2 / DGE / CDP Branch Map
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; B2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; C2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; D2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; E2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; F2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=This sheet shows sequencing and trigger relationships; it does not resolve source-silent interlocks.; B3=This sheet shows sequencing and trigger relationships; it does not resolve source-silent interlocks.; C3=This sheet shows sequencing and trigger relationships; it does not resolve source-silent interlocks.; D3=This sheet shows sequencing and trigger relationships; it does not resolve source-silent interlocks.; E3=This sheet shows sequencing and trigger relationships; it does not resolve source-silent interlocks.; F3=This sheet shows sequencing and trigger relationships; it does not resolve source-silent interlocks.
• Row 4: A4=Node; B4=Trigger; C4=Immediate action; D4=Next branch; E4=Clock relationship; F4=Source
• Row 5: A5=Receipt; B5=Complete native transmission verified; C5=Hash, index, and enter LIVE INPUTS; D5=Route decision; E5=Issuance \= transmission date; A/B counting retained; F5=Attachment B p. 1
• Row 6: A6=Hearing request; B6=Disagreement plus route-changing need for live record; C6=Submit written deadline-preserving request and representative disclosure; D6=Hearing; E6=10 Days from report issuance; F6=Procedure §VI.A.3
• Row 7: A7=No hearing; B7=No hearing request within permitted time; C7=Submit restrained written comments if useful; D7=No-hearing finalization; E7=15-Day comments and 20-Day finalization run concurrently; F7=§§VI.A.4-.5
• Closing row 10: A10=Appeal; B10=VC decision issued and permissible ground exists; C10=File limited-ground appeal; D10=Chancellor decision; E10=5 Days from issuance; 10 Days from receipt; F10=§VI.C
• Closing row 11: A11=DGE interlock; B11=CRO outcome / Investigation Materials transmitted; C11=Seek continued abeyance and milestone/clock confirmation; D11=DGE mitigation test; E11=Completion milestone and receipt rule are source-silent; F11=Standards p. 33
• Closing row 12: A12=No mitigation; B12=DGE determines materials do not reflect possible substantive mitigating circumstances; C12=Preserve record and review counsel triggers; D12=DGE denial; E12=30 calendar days from DGE receipt; F12=Standards p. 33

QA SAMPLES

Dimensions: 28 rows × 8 columns; 224 populated cells; 48 formulas; freeze at B2 (x=1, y=1).

• Row 1: A1=Independent Deadline QA Samples; B1=Independent Deadline QA Samples; C1=Independent Deadline QA Samples; D1=Independent Deadline QA Samples; E1=Independent Deadline QA Samples; F1=Independent Deadline QA Samples
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; B2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; C2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; D2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; E2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION; F2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Twenty Stage A rows are compared with dates independently recomputed in JavaScript under the same explicit assumptions.; B3=Twenty Stage A rows are compared with dates independently recomputed in JavaScript under the same explicit assumptions.; C3=Twenty Stage A rows are compared with dates independently recomputed in JavaScript under the same explicit assumptions.; D3=Twenty Stage A rows are compared with dates independently recomputed in JavaScript under the same explicit assumptions.; E3=Twenty Stage A rows are compared with dates independently recomputed in JavaScript under the same explicit assumptions.; F3=Twenty Stage A rows are compared with dates independently recomputed in JavaScript under the same explicit assumptions.
• Row 4: A4=Sample ID; B4=Anchor; C4=Period / assumption; D4=Independent expected; E4=Workbook result; F4=PASS / FAIL
• Row 5: A5=QA-01; B5=46225; C5=10 Days / A - start excluded; D5=46239; E5==’Transmission Matrix’!H5 [cached 46239]; F5==IF(D5=E5,”PASS”,”FAIL”) [cached PASS]
• Row 6: A6=QA-02; B6=46225; C6=10 Days / B - start counted; D6=46238; E6==’Transmission Matrix’!H6 [cached 46238]; F6==IF(D6=E6,”PASS”,”FAIL”) [cached PASS]
• Row 7: A7=QA-03; B7=46226; C7=10 Days / A - start excluded; D7=46240; E7==’Transmission Matrix’!H11 [cached 46240]; F7==IF(D7=E7,”PASS”,”FAIL”) [cached PASS]
• Closing row 24: A24=QA-20; B24=46234; C24=Hearing completion / primary A; D24=46318; E24==’Max Sequence’!H7 [cached 46318]; F24==IF(D24=E24,”PASS”,”FAIL”) [cached PASS]
• Closing row 25: A25=QA-21; B25=46234; C25=Hearing completion / holiday sensitivity A; D25=46321; E25==’Max Sequence’!H27 [cached 46321]; F25==IF(D25=E25,”PASS”,”FAIL”) [cached PASS]
• Closing row 26: A26=QA-22; B26=46234; C26=Chancellor decision / holiday-curtailment sensitivity A; D26=46391; E26==’Max Sequence’!H34 [cached 46391]; F26==IF(D26=E26,”PASS”,”FAIL”) [cached PASS]

06_HEARING_VS_COMMENTS_DECISION_SYSTEM.xlsx

6 sheets; 75 aggregate worksheet rows; 27 formulas recorded in the structural inventory.

README

Dimensions: 10 rows × 2 columns; 20 populated cells; 0 formulas; freeze at A5 (x=0, y=4).

• Row 1: A1=Hearing Versus Comments Decision System
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Decision support only, not a legal rule. Enter verified report facts; preserve both deadline assumptions and obtain counsel review for waiver, exhaustion, or finality questions.
• Row 4: A4=Control; B4=Operational rule
• Row 5: A5=Use; B5=Score only after preserving the native transmittal, verifying completeness, and mapping every NOI allegation. If the transmission is incomplete, unreadable, internally inconsistent, or materially redacted, enforce the hard stop unless the earliest plausibl…
• Row 6: A6=Hard triggers; B6=A hard trigger requires immediate focused hearing/counsel analysis; it does not automatically decide the route.
• Row 7: A7=Positive score; B7=Positive values favor considering a hearing; negative values favor presumptive written comments.
• Closing row 6: A6=Hard triggers; B6=A hard trigger requires immediate focused hearing/counsel analysis; it does not automatically decide the route.
• Closing row 7: A7=Positive score; B7=Positive values favor considering a hearing; negative values favor presumptive written comments.
• Closing row 8: A8=Protective target; B8=Complete any chosen submission at least one University business day before the earliest plausible date unless verified facts require otherwise.

Weighted Scorecard

Dimensions: 21 rows × 10 columns; 184 populated cells; 16 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Weighted Hearing / Comments Scorecard
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Enter a verified intensity from 0 to 5 in column F after report receipt. The score is an aid, never a substitute for text, deadlines, or judgment.
• Row 4: A4=ID; B4=Factor; C4=Weight; D4=Directional effect; E4=Allowed input; F4=Verified intensity
• Row 5: A5=F01; B5=Material factual error affecting an allegation result; C5=5; D5=Hearing; E5=[0-5]; F5=0
• Row 6: A6=F02; B6=Outcome turns on disputed credibility; C6=5; D6=Hearing; E6=[0-5]; F6=0
• Row 7: A7=F03; B7=Necessary witness testimony not obtained or materially misstated; C7=5; D7=Hearing; E7=[0-5]; F7=0
• Closing row 16: A16=F12; B16=Delay/resource burden of hearing; C16=-2; D16=Comments; E16=[0-5]; F16=0
• Closing row 17: A17=F13; B17=Report incomplete, inaccessible, or materially redacted; C17=0; D17=HARD STOP / Clarify / Protect; E17=[0-5]; F17=0
• Closing row 18: A18=F14; B18=Waiver, exhaustion, finality, or scope preservation uncertainty; C18=0; D18=Counsel; E18=[0-5]; F18=0

Hard Triggers

Dimensions: 14 rows × 5 columns; 70 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Hard Triggers, Presumptions, and Review Triggers
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Observable triggers only. Each row directs analysis; it does not predetermine an action.
• Row 4: A4=Class; B4=Observable trigger; C4=Presumptive response; D4=Required evidence; E4=Caution
• Row 5: A5=Hard hearing trigger; B5=A scoped allegation is omitted or disposed of without an identifiable analysis and clarification cannot timely cure it.; C5=Immediate hearing and counsel analysis; prepare a minimal protective request if warranted.; D5=NOI-to-report map; clarification result; E5=Noncitation alone is not nonconsideration.
• Row 6: A6=Hard hearing trigger; B6=A material adverse result turns on an express credibility finding that live testimony or cross-examination could concretely test.; C6=Build witness necessity and noncumulative-value proof.; D6=Exact credibility finding; witness confirmation; E6=Do not promise testimony before confirmation.
• Row 7: A7=Hard hearing trigger; B7=The report relies on a material new fact, witness account, or rationale Cooper had no meaningful opportunity to address.; C7=Analyze hearing, correction, and extension routes.; D7=Exact new matter; prior record comparison; E7=Keep legal conclusions counsel-qualified.
• Closing row 10: A10=Presumptive comments; B10=The report contains substantial favorable findings and objections can be stated without reopening credibility.; C10=Preserve favorable findings; contest narrow conclusions.; D10=Exact favorable/adverse extraction; E10=No assumption that findings are immutable.
• Closing row 11: A11=Soft factor; B11=Hearing delay may worsen status, funding, insurance, or placement consequences.; C11=Include in route balancing and interim-relief analysis.; D11=Observable consequence and timing; E11=Resource cost cannot replace merits analysis.
• Closing row 12: A12=Soft factor; B12=DGE can use authenticated report facts even without substantiation.; C12=Prioritize clean crosswalk and prompt rights-preserving notice.; D12=Report facts; DGE standard; E12=Do not assume completion milestone.

Decision Tree

Dimensions: 11 rows × 5 columns; 55 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=One-Page Decision Tree
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=INCOMPLETE-TRANSMISSION HARD STOP: Do not make a final merits-route election from an incomplete, unreadable, internally inconsistent, or materially redacted transmission unless a protective filing is required by the earliest plausible deadline. Preserve al…
• Row 4: A4=Step; B4=Question; C4=YES; D4=NO; E4=Output
• Row 5: A5=1; B5=Is the transmission complete, readable, internally consistent, and accompanied by the stated materials?; C5=Preserve the transmission; capture the native timestamp and metadata; calculate protective dates under both counting assumptions; then proceed to the allegation/evidence map.; D5=Preserve and hash what was received; log the exact defect; request missing materials or clarification using the appropriate template; calculate protective dates without conceding completeness or issuance; consider a good-cause extension; and do not rely on…; E5=Complete-transmission preservation and allegation/evidence map, or incomplete-transmission defect/cure/protective-election record
• Row 6: A6=2; B6=Does a waiver, exhaustion, finality, or scope-preservation question materially affect route choice?; C6=Package focused counsel question before final route choice.; D6=Proceed.; E6=Counsel trigger record
• Row 7: A7=3; B7=Is there a hard hearing trigger supported by exact report text and a primary source?; C7=Build minimal hearing request plus grounds; test whether correction can cure.; D7=Proceed.; E7=Hard-trigger memorandum
• Closing row 7: A7=3; B7=Is there a hard hearing trigger supported by exact report text and a primary source?; C7=Build minimal hearing request plus grounds; test whether correction can cure.; D7=Proceed.; E7=Hard-trigger memorandum
• Closing row 8: A8=4; B8=Would live testimony or cross-examination add specific noncumulative evidence on a material point?; C8=Hearing-leaning; confirm witness and examination objectives.; D8=Comments-leaning.; E8=Witness necessity table
• Closing row 9: A9=5; B9=Are the contested issues primarily documentary or textual?; C9=Use written comments and correction/omission table unless another trigger controls.; D9=Reassess score and counsel flags.; E9=Route comparison

Worked Examples

Dimensions: 7 rows × 7 columns; 49 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Three Fully Worked Hypothetical Examples
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Hypotheticals illustrate use; they are not forecasts or advice.
• Row 4: A4=Example; B4=Verified hypothetical facts; C4=Hard trigger; D4=Score logic; E4=Presumptive route; F4=Route-changing facts
• Row 5: A5=A - Mixed documentary report; B5=Two allegations unsubstantiated; report authenticates M203 timing and Bearden email; no material credibility finding; one policy-element disagreement.; C5=No; D5=Documentary/textual -15; DGE utility -8; no live-evidence value. Illustrative net -23.; E5=Written comments; F5=A newly disclosed material witness account or express credibility rejection could shift to hearing.
• Row 6: A6=B - Adverse credibility report; B6=Report rejects Cooper’s account based on two witnesses; one proffered corroborating witness is absent; adverse result depends on who said what.; C6=Yes; D6=Credibility +25; necessary witness +20; live examination +20; preservation uncertainty triggers counsel.; E6=Hearing analysis; F6=Proof the witness was interviewed and cumulative, or an agreed correction that removes materiality.
• Row 7: A7=C - Incomplete transmission; B7=Email says report and appendices attached; only a redacted report arrives, appendix/evidence list missing, and stated issuance date differs from timestamp.; C7=Completeness trigger before merits score; D7=Do not assign merits weights. Deadline runs shown under A/B without conceding completeness.; E7=No final merits-route election; preserve/hash the receipt, log the defect, request clarification/missing materials, calculate protective A/B dates without concession, and consider extension. Make a protective election only if required by the earliest plaus…; F7=A prompt complete cure plus UCLA confirmation of the operative record/date permits merits scoring; absent cure, only the earliest plausible deadline may require a protective election.
• Closing row 3: A3=Hypotheticals illustrate use; they are not forecasts or advice.
• Closing row 4: A4=Example; B4=Verified hypothetical facts; C4=Hard trigger; D4=Score logic; E4=Presumptive route; F4=Route-changing facts
• Closing row 5: A5=A - Mixed documentary report; B5=Two allegations unsubstantiated; report authenticates M203 timing and Bearden email; no material credibility finding; one policy-element disagreement.; C5=No; D5=Documentary/textual -15; DGE utility -8; no live-evidence value. Illustrative net -23.; E5=Written comments; F5=A newly disclosed material witness account or express credibility rejection could shift to hearing.

Route Assertions

Dimensions: 12 rows × 7 columns; 84 populated cells; 11 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Route Logic Assertions
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Machine-readable V2 assertions compare each required route statement to the final exported source cell. Any FAIL requires repair before use.
• Row 4: A4=Assertion ID; B4=Control; C4=Required exact content; D4=Source cell; E4=Observed exported content; F4=Status
• Row 5: A5=R06-YES; B5=Complete transmission — YES; C5=Preserve the transmission; capture the native timestamp and metadata; calculate protective dates under both counting assumptions; then proceed to the allegation/evidence map.; D5=Decision Tree!C5; E5==’Decision Tree’!C5 [cached Preserve the transmission; capture the native timestamp and metadata; calculate protective dates under both counting assumptions; then proceed to the allegation/evidence map.]; F5==IF(E5=C5,”PASS”,”FAIL”) [cached PASS]
• Row 6: A6=R06-NO; B6=Incomplete transmission — NO; C6=Preserve and hash what was received; log the exact defect; request missing materials or clarification using the appropriate template; calculate protective dates without conceding completeness or issuance; consider a good-cause extension; and do not rely on…; D6=Decision Tree!D5; E6==’Decision Tree’!D5 [cached Preserve and hash what was received; log the exact defect; request missing materials or clarification using the appropriate template; calculate protective dates without conceding completeness or issuance; consider a good-cause e…; F6==IF(E6=C6,”PASS”,”FAIL”) [cached PASS]
• Row 7: A7=R06-HARDSTOP; B7=Incomplete-transmission hard stop; C7=INCOMPLETE-TRANSMISSION HARD STOP: Do not make a final merits-route election from an incomplete, unreadable, internally inconsistent, or materially redacted transmission unless a protective filing is required by the earliest plausible deadline. Preserve al…; D7=Decision Tree!A3; E7==’Decision Tree’!A3 [cached INCOMPLETE-TRANSMISSION HARD STOP: Do not make a final merits-route election from an incomplete, unreadable, internally inconsistent, or materially redacted transmission unless a protective filing is required by the earliest pla…; F7==IF(E7=C7,”PASS”,”FAIL”) [cached PASS]
• Closing row 7: A7=R06-HARDSTOP; B7=Incomplete-transmission hard stop; C7=INCOMPLETE-TRANSMISSION HARD STOP: Do not make a final merits-route election from an incomplete, unreadable, internally inconsistent, or materially redacted transmission unless a protective filing is required by the earliest plausible deadline. Preserve al…; D7=Decision Tree!A3; E7==’Decision Tree’!A3 [cached INCOMPLETE-TRANSMISSION HARD STOP: Do not make a final merits-route election from an incomplete, unreadable, internally inconsistent, or materially redacted transmission unless a protective filing is required by the earliest pla…; F7==IF(E7=C7,”PASS”,”FAIL”) [cached PASS]
• Closing row 8: A8=R06-SCORE; B8=Scorecard completeness stop; C8=Do not make a final merits-route election while the transmission is incomplete, unreadable, internally inconsistent, or materially redacted. Preserve/hash receipt, request cure, calculate protective A/B dates without conceding completeness or issuance, con…; D8=Weighted Scorecard!I17; E8==’Weighted Scorecard’!I17 [cached Do not make a final merits-route election while the transmission is incomplete, unreadable, internally inconsistent, or materially redacted. Preserve/hash receipt, request cure, calculate protective A/B dates without conce…; F8==IF(E8=C8,”PASS”,”FAIL”) [cached PASS]
• Closing row 9: A9=R06-EXAMPLE; B9=Incomplete-transmission worked example; C9=No final merits-route election; preserve/hash the receipt, log the defect, request clarification/missing materials, calculate protective A/B dates without concession, and consider extension. Make a protective election only if required by the earliest plaus…; D9=Worked Examples!E7; E9==’Worked Examples’!E7 [cached No final merits-route election; preserve/hash the receipt, log the defect, request clarification/missing materials, calculate protective A/B dates without concession, and consider extension. Make a protective election only if…; F9==IF(E9=C9,”PASS”,”FAIL”) [cached PASS]

08_EXPECTED_RECORD_OMISSION_CONTRADICTION_MATRIX.xlsx

4 sheets; 116 aggregate worksheet rows; 0 formulas recorded in the structural inventory.

Baseline Matrix

Dimensions: 80 rows × 17 columns; 1,360 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Expected Record, Omission, and Contradiction Matrix — V2 Expanded Baseline
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Expanded operational inventory. On receipt, record the observed treatment status only after full report/evidence-list review. Noncitation is never proof of nonconsideration.
• Row 4: A4=ID; B4=Inventory category; C4=Exact source path; D4=Page / line / section locator; E4=Proposition; F4=Epistemic label
• Row 5: A5=ER-S01; B5=Scoped alleged action; C5=01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf; D5=p. 1, allegation 1; E5=Bisley allegedly failed to accommodate Cooper’s disability when Cooper requested to take the NEURO M203 midterm on a later date.; F5=Complainant account
• Row 6: A6=ER-S02; B6=Scoped alleged action; C6=01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf; D6=p. 1, allegation 2(a); E6=Bearden allegedly discriminated by declining to serve as Cooper’s primary faculty mentor.; F6=Complainant account
• Row 7: A7=ER-S03; B7=Scoped alleged action; C7=01_CASE_RECORD/03_CRO_Notice_of_Investigation_2026-04-08.pdf; D7=pp. 1-2, allegation 2(b)(i); E7=Bearden allegedly harassed Cooper by highlighting unmet expectations and expressing that he lacked the required skills to complete a Ph.D.; F7=Complainant account
• Closing row 76: A76=ER-P13; B76=Stage A handling rule; C76=02_STAGE_A_POLICY_VERIFICATION/PROCEDURAL_TEXT_EXTRACT.md; 02_STAGE_A_POLICY_VERIFICATION/UNRESOLVED_AMBIGUITIES.md; D76=Procedural Text lines 454-488; Unresolved Ambiguities lines 21 and 73-76; E76=The Standards provide a personal appearance before CDP upon written request, but reviewed sources do not supply the detailed appearance procedure or recommendation deadline.; F76=Unknown / source silence
• Closing row 77: A77=ER-P14; B77=Stage A handling rule; C77=02_STAGE_A_POLICY_VERIFICATION/DEADLINE_AND_SEQUENCING_TABLE.xlsx; D77=Source Rules!A4:E15; Transmission Matrix and No-Hearing Branch; E77=Stage A preserves formulas, Assumptions A/B, excluded-date logic, source rules, and primary versus sensitivity calculations.; F77=Source-established procedural fact
• Closing row 78: A78=ER-P15; B78=Stage A handling rule; C78=02_STAGE_A_POLICY_VERIFICATION/CALCULATION_VERIFICATION_LOG.md; D78=lines 74-82 and 177-191; E78=Stage A independently reported 60/60 transmission, 40/40 sequence, and 8/8 no-hearing calculation rows passing, with no formula errors, while retaining specified unresolved uncertainties.; F78=Source-established procedural fact

Status Definitions

Dimensions: 13 rows × 4 columns; 52 populated cells; 0 formulas; freeze at A5 (x=0, y=4).

• Row 1: A1=Treatment-Status Definitions
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Use the narrowest supportable status. Preserve the distinction between report silence, consideration, treatment, scope, submission, and source availability.
• Row 4: A4=Status; B4=Definition; C4=Required proof; D4=Do not infer
• Row 5: A5=Not mentioned; B5=No identifiable reference after a full report search and manual review.; C5=Search terms, pages reviewed, second check.; D5=That CRO did not consider it.
• Row 6: A6=Considered but not cited; B6=The report affirmatively states, or an evidence list shows, consideration without an analysis citation.; C6=Exact methodology/evidence-list text.; D6=Weight, credibility, or acceptance.
• Row 7: A7=Expressly discounted; B7=The report identifies the item and gives a reason for reduced or no weight.; C7=Exact quotation and page.; D7=That the reason is invalid.
• Closing row 9: A9=Cumulative; B9=The report expressly says the item duplicates other evidence.; C9=Exact explanation and the evidence treated as duplicative.; D9=That the underlying evidence is false.
• Closing row 10: A10=Not actually submitted; B10=A native submission/receipt record confirms the item was not delivered.; C10=Native message, portal receipt, or manifest.; D10=This status from an index omission alone.
• Closing row 11: A11=Unavailable underlying exhibit; B11=The fixed package contains only an index, proffer, or description, not the underlying exhibit.; C11=Fixed-package inventory and source search.; D11=That CRO lacked, ignored, or rejected it.

Coverage Summary

Dimensions: 18 rows × 4 columns; 72 populated cells; 0 formulas; freeze at A5 (x=0, y=4).

• Row 1: A1=V2 Expansion Coverage Summary
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Machine-counted inventory coverage. This sheet demonstrates granularity; it does not replace source-fidelity review.
• Row 4: A4=Inventory category; B4=Row count; C4=Structural status; D4=Acceptance evidence
• Row 5: A5=CRO investigation architecture; B5=1; C5=PASS; D5=Every row has an exact path, pinpoint locator, epistemic label, and operational treatment/action fields.
• Row 6: A6=CRO scope/coverage correspondence; B6=1; C6=PASS; D6=Every row has an exact path, pinpoint locator, epistemic label, and operational treatment/action fields.
• Row 7: A7=Critical official correspondence/decision; B7=4; C7=PASS; D7=Every row has an exact path, pinpoint locator, epistemic label, and operational treatment/action fields.
• Closing row 14: A14=Stage A handling rule; B14=15; C14=PASS; D14=Every row has an exact path, pinpoint locator, epistemic label, and operational treatment/action fields.
• Closing row 15: A15=TOTAL DISTINCT INVENTORY ROWS; B15=76; C15=PASS; D15=All IDs unique; all 17 required fields populated.
• Closing row 16: A16=Scoped-action granularity; B16=8; C16=PASS; D16=One row for each of the eight discrete NOI actions.

Blank Omission Log

Dimensions: 5 rows × 10 columns; 50 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Blank Future-Report Omission Log
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Blank operational copy for use only after report receipt. Duplicate the exemplar row for each materially distinct potential omission. Verify complete report review and classify treatment using Status Definitions before asserting an omission; noncitation is…
• Row 4: A4=Tracking ID; B4=Status; C4=Omitted item; D4=Source and date; E4=Proposition; F4=Materiality
• Row 5: A5=OM-[NN]; B5=[TREATMENT_STATUS]; C5=[OMITTED_ITEM]; D5=[SOURCE_AND_DATE]; E5=[PROPOSITION]; F5=[CRITICAL / HIGH / MEDIUM / LOW + WHY]
• Closing row 1: A1=Blank Future-Report Omission Log
• Closing row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Closing row 3: A3=Blank operational copy for use only after report receipt. Duplicate the exemplar row for each materially distinct potential omission. Verify complete report review and classify treatment using Status Definitions before asserting an omission; noncitation is…

10_DGE_CDP_MITIGATION_CROSSWALK.xlsx

3 sheets; 62 aggregate worksheet rows; 0 formulas recorded in the structural inventory.

Baseline Crosswalk

Dimensions: 19 rows × 14 columns; 266 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=DGE / CDP Mitigation Crosswalk — V2 Baseline
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Controlling standard: “substantive mitigating circumstances that could have affected academic performance.” Circumstance, notice, and accommodation/interactive-process issue are separate proof fields.
• Row 4: A4=ID; B4=Source fact / finding; C4=Report page; D4=Disability-related circumstance; E4=University notice; F4=Accommodation or interactive-process issue
• Row 5: A5=DGE-001; B5=NOI confirms formal investigation of disability-discrimination/harassment allegations; C5=[REPORT_PAGE]; D5=Disability-related investigation context; underlying disability facts remain report-dependent.; E5=The NOI supplied formal notice of the scoped allegations; exact actor knowledge and timing beyond the NOI require report verification.; F5=The NOI does not itself establish an accommodation failure or deficient interactive process. Use only a report finding or authenticated request-response history.
• Row 6: A6=DGE-002; B6=M203 later-date request and response; C6=[REPORT_PAGE]; D6=Executive-function, disability, and exam-timing circumstance only as the report authenticates.; E6=The request’s timing and content, Bisley’s receipt, and existing CAE arrangements must be established from the report/primary record.; F6=Determine whether the later-date request engaged an accommodation process, how existing CAE arrangements applied, what response/alternative was provided, and whether the actual barrier was individualized.
• Row 7: A7=DGE-003; B7=Program says CAE arrangements existed; C7=[REPORT_PAGE]; D7=Existing registered-disability and course-accommodation context.; E7=University notice is supported only to the extent the report authenticates the CAE arrangements and recipients.; F7=Distinguish the existence of standard testing accommodations from whether the particular M203, rotation, mentor, or executive-function barrier was identified, discussed, and effectively addressed.
• Closing row 15: A15=DGE-011; B15=Accommodation or interactive-process weakness expressly found by CRO; C15=[REPORT_PAGE]; D15=[EXACT_DISABILITY_RELATED_CIRCUMSTANCE]; E15=[EXACT_UNIVERSITY_NOTICE_FINDING]; F15=[EXACT_ACCOMMODATION_OR_INTERACTIVE_PROCESS_ISSUE]
• Closing row 16: A16=DGE-012; B16=No CRO violation but authenticated disability, notice, timing, or response facts; C16=[REPORT_PAGE]; D16=[AUTHENTICATED_DISABILITY_RELATED_CIRCUMSTANCE]; E16=[AUTHENTICATED_NOTICE]; F16=[AUTHENTICATED_ACCOMMODATION_OR_INTERACTIVE_PROCESS_FACT_OR_SOURCE_SILENCE]
• Closing row 17: A17=DGE-013; B17=Bailey acknowledged simultaneous-service failure; C17=[REPORT_PAGE_OR_NA]; D17=Procedural record-integrity circumstance; not necessarily academic-performance mitigation.; E17=DGE had direct notice of the service defect.; F17=Not an accommodation/interactive-process issue unless a report-specific record links the defect to access or an accommodation request; otherwise mark N/A.

Future Report Copy

Dimensions: 28 rows × 14 columns; 392 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Blank Future-Report Mitigation Crosswalk — V2
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Populate only from the actual report, transmittal, primary record, and clearly labeled accounts. Never duplicate circumstance or notice text into the accommodation/process field.
• Row 4: A4=ID; B4=Source fact / finding; C4=Report page; D4=Disability-related circumstance; E4=University notice; F4=Accommodation or interactive-process issue
• Row 5: A5=FR-001; B5=[SOURCE_FACT_OR_FINDING]; C5=[REPORT_PAGE]; D5=[DISABILITY_RELATED_CIRCUMSTANCE]; E5=[UNIVERSITY_NOTICE]; F5=[ACCOMMODATION_OR_INTERACTIVE_PROCESS_ISSUE_OR_SOURCE_SILENCE]
• Row 6: A6=FR-002; B6=[SOURCE_FACT_OR_FINDING]; C6=[REPORT_PAGE]; D6=[DISABILITY_RELATED_CIRCUMSTANCE]; E6=[UNIVERSITY_NOTICE]; F6=[ACCOMMODATION_OR_INTERACTIVE_PROCESS_ISSUE_OR_SOURCE_SILENCE]
• Row 7: A7=FR-003; B7=[SOURCE_FACT_OR_FINDING]; C7=[REPORT_PAGE]; D7=[DISABILITY_RELATED_CIRCUMSTANCE]; E7=[UNIVERSITY_NOTICE]; F7=[ACCOMMODATION_OR_INTERACTIVE_PROCESS_ISSUE_OR_SOURCE_SILENCE]
• Closing row 24: A24=FR-020; B24=[SOURCE_FACT_OR_FINDING]; C24=[REPORT_PAGE]; D24=[DISABILITY_RELATED_CIRCUMSTANCE]; E24=[UNIVERSITY_NOTICE]; F24=[ACCOMMODATION_OR_INTERACTIVE_PROCESS_ISSUE_OR_SOURCE_SILENCE]
• Closing row 25: A25=FR-021; B25=[SOURCE_FACT_OR_FINDING]; C25=[REPORT_PAGE]; D25=[DISABILITY_RELATED_CIRCUMSTANCE]; E25=[UNIVERSITY_NOTICE]; F25=[ACCOMMODATION_OR_INTERACTIVE_PROCESS_ISSUE_OR_SOURCE_SILENCE]
• Closing row 26: A26=FR-022; B26=[SOURCE_FACT_OR_FINDING]; C26=[REPORT_PAGE]; D26=[DISABILITY_RELATED_CIRCUMSTANCE]; E26=[UNIVERSITY_NOTICE]; F26=[ACCOMMODATION_OR_INTERACTIVE_PROCESS_ISSUE_OR_SOURCE_SILENCE]

Quality Controls

Dimensions: 15 rows × 3 columns; 45 populated cells; 0 formulas; freeze at A5 (x=0, y=4).

• Row 1: A1=Mitigation Crosswalk Quality Controls — V2
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=A row is submission-ready only when every applicable control passes.
• Row 4: A4=Control; B4=PASS criterion; C4=Failure mode prevented
• Row 5: A5=Exact standard; B5=Uses the exact could-have-affected language.; C5=Replacing mitigation with a CRO violation test.
• Row 6: A6=Independent proof fields; B6=Circumstance, University notice, and accommodation/interactive-process issue are each separately populated and are not treated as synonyms.; C6=Inferring a process defect from disability or general notice alone.
• Row 7: A7=Accommodation/process field; B7=Identifies a request, response, provided accommodation, disputed modification, interactive step, N/A, or source silence.; C7=A generic or duplicated field that cannot be audited.
• Closing row 11: A11=Temporal link; B11=Specifies relationship to the academic component.; C11=Chronology without causal relevance.
• Closing row 12: A12=Contrary evidence; B12=States the strongest response fairly.; C12=One-sided advocacy.
• Closing row 13: A13=Possible and substantive; B13=Explains both possibility and materiality.; C13=Conclusory mitigation.

12_BAILEY_PREJUDICE_TABLE.xlsx

2 sheets; 29 aggregate worksheet rows; 0 formulas recorded in the structural inventory.

Prejudice Table

Dimensions: 19 rows × 12 columns; 228 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Bailey Record-Integrity Prejudice Table
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Line/item-specific analysis. The Standards require contemporaneous service, but do not expressly grant unrestricted sur-rebuttal.
• Row 4: A4=ID; B4=Source / line item; C4=Program assertion or material; D4=Previously disclosed?; E4=New ground, explanation, evidence, or characterization; F4=Opportunity lost
• Row 5: A5=B-001; B5=NSIDP response p.5; C5=November 19, 2024 Academic Plan established unsatisfactory progress/requirements; D5=Was the plan and its precise role identified in the original adverse action?; E5=Potentially developed rationale if only generalized grounds were served; F5=Cooper lacked simultaneous response, not necessarily prior access to plan
• Row 6: A6=B-002; B6=NSIDP response p.5; C6=Failure to secure mentor was sufficient and overall degree progress inadequate; D6=Mentor failure appeared in underlying action; overall formulation needs exact comparison; E6=Possible expansion/clarification; F6=No simultaneous copy during Dean review
• Row 7: A7=B-003; B7=NSIDP response p.5; C7=May 30 response added fifth-rotation U and M203 details; D7=Were those bases in the April 28 recommendation/notice?; E7=Potential new reliance or explanatory evidence; F7=No simultaneous response during 15-business-day review
• Closing row 15: A15=B-011; B15=NSIDP response p.8; C15=Program requires three rotations and mentor after three; D15=Was exact rule/citation in original record?; E15=Potential policy/practice assertion; F15=No simultaneous response
• Closing row 16: A16=B-012; B16=NSIDP response p.9; C16=No rotation accommodation request was initiated; D16=Was this absence theory disclosed?; E16=Potential new negative inference; F16=No opportunity to address how notice/request occurred
• Closing row 17: A17=B-013; B17=NSIDP response p.9; C17=Program consulted DGE and CAE and followed accommodations; D17=Were consultation content and records disclosed?; E17=Potential new compliance defense; F17=No opportunity to inspect or answer consultation scope

Deployment

Dimensions: 10 rows × 6 columns; 60 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Bailey Deployment by Scenario and Timing
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Hold the broader memorandum unless an observable trigger makes it material.
• Row 4: A4=Observable event; B4=Use now; C4=Hold; D4=Trigger for broader use; E4=Requested cure; F4=Exact source locator
• Row 5: A5=Before CRO report; B5=Preserve chronology and immutable source copies; C5=Do not send broad Bailey theory; D5=None absent DGE action or report reliance; E5=No external action; F5=Strategic hold rule, not an express UCLA mandate. Observable-record sources: 01_CASE_RECORD/10_DGE_Update_2026-04-24_to_2026-05-04.pdf, PDF file p. 2; 01_CASE_RECORD/11_DGE_Procedural_Appeal_NSIDP_Responses.pdf, PDF file pp. 1, 4–10; service baseline: 01_C…
• Row 6: A6=CRO report omits Bailey issue; B6=No inference of nonconsideration; C6=Bailey package remains DGE-focused; D6=Only if report expressly relies on DGE record integrity; E6=Narrow clarification if material; F6=00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md, §7.9 (distinguish noncitation from nonconsideration); 01_CASE_RECORD/05_UCLA_Procedure_230.2.pdf, §VI.A.2, pp. 4–5 (investigation-report contents). Bailey deployment remains DGE-…
• Row 7: A7=DGE resumes review using NSIDP response/addendum; B7=Send concise preservation paragraph and item table; C7=Constitutional/external theories; D7=DGE indicates reliance without cure; E7=Allow item-specific correction; identify relied-on record; F7=01_CASE_RECORD/06_UCLA_Standards_and_Procedures_for_Graduate_Study.pdf, printed p. 32 / PDF file p. 33, “Student Appeals Process – Procedural Error”; 01_CASE_RECORD/10_DGE_Update_2026-04-24_to_2026-05-04.pdf, PDF file p. 2; 01_CASE_RECORD/11_DGE_Procedural…
• Closing row 6: A6=CRO report omits Bailey issue; B6=No inference of nonconsideration; C6=Bailey package remains DGE-focused; D6=Only if report expressly relies on DGE record integrity; E6=Narrow clarification if material; F6=00_START_HERE/00_FINAL_CHATGPT_WORK_SOL_ULTRA_MASTER_PROMPT_V4_2026-07-22.md, §7.9 (distinguish noncitation from nonconsideration); 01_CASE_RECORD/05_UCLA_Procedure_230.2.pdf, §VI.A.2, pp. 4–5 (investigation-report contents). Bailey deployment remains DGE-…
• Closing row 7: A7=DGE resumes review using NSIDP response/addendum; B7=Send concise preservation paragraph and item table; C7=Constitutional/external theories; D7=DGE indicates reliance without cure; E7=Allow item-specific correction; identify relied-on record; F7=01_CASE_RECORD/06_UCLA_Standards_and_Procedures_for_Graduate_Study.pdf, printed p. 32 / PDF file p. 33, “Student Appeals Process – Procedural Error”; 01_CASE_RECORD/10_DGE_Update_2026-04-24_to_2026-05-04.pdf, PDF file p. 2; 01_CASE_RECORD/11_DGE_Procedural…
• Closing row 8: A8=DGE denies mitigation and relies on contested new assertions; B8=Use full memorandum and prejudice proof; C8=External filing unless counsel advises; D8=Material reliance shown; E8=Reasoned reconsideration on corrected record; F8=01_CASE_RECORD/06_UCLA_Standards_and_Procedures_for_Graduate_Study.pdf, printed p. 33 / PDF file p. 34, “Student Appeals Process – Grounds other than Procedural Error” (Investigation Materials, mitigation determination, and DGE decision); 02_STAGE_A_POLICY…

13_REMEDY_AUTHORITY_MAP.xlsx

2 sheets; 35 aggregate worksheet rows; 0 formulas recorded in the structural inventory.

Remedy Map

Dimensions: 24 rows × 15 columns; 360 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=Remedy-Authority Map
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=A request directed to an office without implementation authority must be labeled as a referral, recommendation, or negotiation request.
• Row 4: A4=Remedy; B4=Office / decision-maker; C4=Authority status / characterization; D4=Procedural vehicle; E4=Factual predicate; F4=Strongest scenario
• Row 5: A5=Accommodated NSIDP reinstatement; B5=Graduate Dean / authorized academic decisionmaker; program implementation; C5=PLAUSIBLE / REFERRAL / UCLA-CONFIRMATION-DEPENDENT — the Graduate Dean has express authority over disqualification, but neither cited source guarantees or specifically enumerates accommodated NSIDP reinstatement.; D5=DGE/CDP recommendation and final decision; negotiated resolution; E5=Report/record shows substantive mitigation and viable academic plan; F5=Favorable or mixed report
• Row 6: A6=Reversal or reconsideration of disqualification; B6=Graduate Dean after DGE/CDP process; C6=EXPRESS DECISION AUTHORITY; REMEDY BREADTH UCLA-CONFIRMATION-DEPENDENT — the Graduate Dean has final authority over disqualification and the appeal disposition, but the cited text does not enumerate every form of reversal.; D6=DGE mitigation review/CDP recommendation; E6=Possible substantive mitigating circumstances and material academic effect; F6=Any report with authenticated mitigation facts
• Row 7: A7=Corrected academic review; B7=DGE / Graduate Dean / program as directed; C7=PLAUSIBLE CURE / UCLA-CONFIRMATION-DEPENDENT; COUNSEL-DEPENDENT if asserted as a legal entitlement — no express unrestricted sur-rebuttal or automatic reconsideration remedy.; D7=Narrow cure request; reconsideration; E7=Material inaccurate/undisclosed relied-on item; F7=Omissive/adverse or Bailey-triggered
• Closing row 20: A20=Training; B20=CRO/department/HR/academic leadership; C20=EXPRESSLY LISTED POSSIBLE PERMANENT OUTCOME/REMEDY; implementation office and content remain UCLA-CONFIRMATION-DEPENDENT.; D20=Recommendation or negotiated resolution; E20=Knowledge/process gap found; F20=Favorable/mixed
• Closing row 21: A21=Record correction; B21=Custodian of academic/administrative record; C21=PLAUSIBLE CORRECTIVE STEP / REFERRAL / UCLA-CONFIRMATION-DEPENDENT — the cited texts do not expressly confer deletion or expungement authority on CRO.; D21=Correction request or remedy decision; E21=Demonstrably inaccurate statement or invalid disposition; F21=Omissive/adverse or Bailey
• Closing row 22: A22=Discipline/referral; B22=Authorized supervisory/disciplinary office; C22=EXPRESS REFERRAL / SEPARATE PROCESS — Vice Chancellor remedial action excludes discipline; the proper administrator and applicable disciplinary process decide.; D22=CRO referral/recommendation; E22=Substantiated conduct meeting referral standard; F22=Broad favorable

Authority Controls

Dimensions: 11 rows × 2 columns; 22 populated cells; 0 formulas; freeze at A5 (x=0, y=4).

• Row 1: A1=Authority and Drafting Controls
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Use before placing any remedy in a submission.
• Row 4: A4=Control; B4=Pass condition
• Row 5: A5=Decisionmaker / exact locator; B5=The exact office and package source locator are identified, or the row is expressly labeled PLAUSIBLE, REFERRAL, or NEGOTIATION with UCLA-CONFIRMATION-DEPENDENT and/or COUNSEL-DEPENDENT status.
• Row 6: A6=Vehicle; B6=The draft states whether it is a recommendation, appeal remedy, interim request, correction, or negotiated proposal.
• Row 7: A7=Predicate; B7=Every remedy is tied to an observable finding or documented consequence.
• Closing row 7: A7=Predicate; B7=Every remedy is tied to an observable finding or documented consequence.
• Closing row 8: A8=CRO boundary; B8=No claim that CRO can implement an academic/degree/funding remedy absent express authority.
• Closing row 9: A9=Academic judgment; B9=Requests for re-evaluation preserve legitimate academic standards.

17_EXTERNAL_REVIEW_AND_COUNSEL_TRIGGER_MATRIX.xlsx

2 sheets; 42 aggregate worksheet rows; 0 formulas recorded in the structural inventory.

Trigger Matrix

Dimensions: 30 rows × 7 columns; 210 populated cells; 0 formulas; freeze at B5 (x=1, y=4).

• Row 1: A1=External Review and Counsel Trigger Matrix
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Every trigger is tied to an observable event. Consultation/preservation is distinct from filing, service, or litigation.
• Row 4: A4=Review type; B4=Observable trigger; C4=Required proof; D4=Authorized next analysis; E4=Timing; F4=Purpose
• Row 5: A5=University administrative counsel; B5=Transmittal creates a concrete waiver, exhaustion, finality, or inconsistent-deadline question; C5=Exact transmittal plus Stage A text; D5=Consultation/preservation; E5=Before earliest internal route target; F5=Route rights may be forfeited
• Row 6: A6=University administrative counsel; B6=Report relies on a material new rationale or unavailable evidence; C6=Report page; prior record comparison; D6=Consultation and correction/hearing preservation; E6=Immediately after verification; F6=Notice/record-integrity issue
• Row 7: A7=University administrative counsel; B7=A scoped allegation lacks a disposition and cure is denied or deadline continues; C7=NOI/report map; cure request/result; D7=Consultation; E7=Before route deadline; F7=Scope/finality risk
• Closing row 26: A26=University administrative counsel; B26=UCLA denies or does not honor a timely Procedure 230.2 hearing request; C26=Native request; timestamps; delivery/receipt proof; A/B deadline calculations; denial or verified nonresponse; D26=Counsel consultation, clarification / reconsideration, and exhaustion-preservation analysis; E26=Immediately after denial or verified failure to act; F26=Preserve the timely election and identify the narrowest internal cure before any external step
• Closing row 27: A27=University administrative counsel; B27=A stated Procedure 230.2 or DGE procedural deadline is not followed and no verified good-cause extension explains the variance; C27=Exact governing rule; A/B calculation; closure record; event timestamps; extension notice or source silence; D27=Counsel consultation, deadline confirmation, prejudice assessment, and rights-preservation analysis; E27=Promptly after the variance is verified; F27=Determine material prejudice, available cure, and whether any protective filing or extension request is needed
• Closing row 28: A28=DGE / disability-rights counsel; B28=DGE takes or schedules irreversible action before UCLA confirms the source-silent CRO completion milestone; C28=DGE notice and effective date; report/hearing/appeal status; exact S\&P language; confirmation requests and responses; D28=Sequencing consultation, record preservation, and tailored interim-relief analysis; E28=Before the action’s effective date; F28=Protect the abeyance question and preserve meaningful CRO/DGE review

Intake Packet

Dimensions: 12 rows × 3 columns; 36 populated cells; 0 formulas; freeze at A5 (x=0, y=4).

• Row 1: A1=Counsel / External-Review Intake Packet
• Row 2: A2=PRE-REPORT STRATEGY WORK PRODUCT — VERIFY AGAINST THE ACTUAL CRO REPORT, TRANSMITTAL, AND CURRENT DEADLINES BEFORE SUBMISSION
• Row 3: A3=Prepare only when a trigger is met; do not transmit without Cooper’s approval.
• Row 4: A4=Item; B4=Required contents; C4=QA
• Row 5: A5=Question memorandum; B5=One page: observable event, exact question, deadline, desired advice; C5=No advocacy adjectives or assumed legal conclusion
• Row 6: A6=Native transmission; B6=Original email/message, headers, attachments, hashes; C6=Immutable and complete
• Row 7: A7=Operative text; B7=Exact policy/procedure pages and Stage A ambiguity; C7=Version/date identified
• Closing row 8: A8=Decision record; B8=Report, NOI, DGE decision, relevant submissions; C8=Indexed and paginated
• Closing row 9: A9=Fact chronology; B9=Only source-cited material events; C9=Accounts and positions labeled
• Closing row 10: A10=Route/deadline sheet; B10=Assumptions A/B, primary/sensitivity, extension status; C10=Second-checker verified

9. Attached Thread-Export and Execution-History Synthesis

The attached exports are not separate substantive authorities. They are execution-history records showing task decomposition, edits, checks, failures, reruns, and finalization. The table below captures every attached export.

9.1 Complete thread-export inventory

9.2 Execution-history interpretation

• The root thread is the authoritative execution chronology: 74,615 lines, 1,268,006 tokens, 738 action records, 38 created-file cards, and 122 edited-file cards.
• Subagents were bounded by specialty: Stage A procedure, case evidence, package requirements, source fidelity, workbook baseline, forecast/audit baseline, source matrices, partial-row triage, normalized-evidence red-team, lexical mismatch triage, evidence sweep, content/process QA, script audit, requirement remapping, heading-only sweep, and reuse-allowlist design.
• The history records genuine iterative correction rather than a single untested generation: citation samples moved through failing states before reaching 167/167; workbook panes were patched and rerun; requirement-evidence mismatches/reuse groups were found and reconciled; packaging was rebuilt and reverified.
• Truncation markers prevent the exports from proving semantic review of every omitted source token, which is why the final source ledger uses precise traversal and focused-verification language rather than categorical “every token” claims.

10. Risk Register, Limitations, and Prioritized Action Plan

10.1 Priority action checklist

• Before report arrival: retain the sealed ZIP and its SHA-256; make a read-only backup; familiarize yourself with Artifacts 05, 18, 03, 06, 08, and 10 in that order.
• At receipt: do not reply first. Preserve, screenshot, export native headers/materials, hash, make immutable and working copies, and record exact time zone/channel.
• Within the first hour: verify completeness/readability/internal consistency; run both deadline assumptions; apply the incomplete-transmission hard stop if needed.
• Within the first day: map all eight scoped actions, favorable/adverse factual findings, omissions, contradictions, witnesses/documents, DGE mitigation, Bailey prejudice, and remedy authority.
• Before route election: populate Artifact 06 and select applicable Artifact 07 modules; use the earliest plausible date; obtain counsel/UCLA confirmation when a trigger applies.
• Before any submission: choose the narrowest Artifact 14 template; replace every placeholder; authenticate every factual assertion; verify recipient/method/deadline; preserve the submitted version and delivery proof.

11. Overall Evaluation

Appendix A — Verified 25-Member Archive Inventory and Checksum Hierarchy

Sealed archive SHA-256: 94B5A900E00667CCA5A38B36B0847FBD11BE839362717FD5243040359244AAEC. The root ledger hashes every member except itself; the archive-level hash seals the root ledger and the complete member set.

Appendix B — Complete Atomic-Requirement Status Index

This appendix includes every one of the 1,550 final atomic rows. It preserves the full faithful requirement text, final status, final artifact, exact evidence locator, and defect/cure note. It is the most granular answer to whether each requested task/subtask was fulfilled.

Atomic requirements 1–100

Atomic requirements 101–200

Atomic requirements 201–300