Disabled Veteran’s Corporate-Communication Timeline of Microaggressions and Disclosure Demands by Wisconsin DVR employers and post-secondary education proctoring

When a Workplace “Process” Becomes an Ultimatum: An 18-Record Timeline of Corporate Communication and Microaggressions by DVR Employers

By Bradley J. Burt | ###DVR / JEDVIDENCE™

There is a difference between an employer asking a question and an employer structuring the question so that silence, delay, privacy, or disagreement becomes the penalty. That difference is the center of my current ###DVR chronology.

I use the word ultimatum here in its ordinary, documentary sense: a demand, deadline, compelled disclosure, process condition, or stated consequence. I am not presenting the 18 entries below as legal findings. Some are direct quotations from records; others are my contemporaneous or later accounts that still require comparison against the originating email, policy, witness testimony, and complete administrative record. The point is not to pronounce a verdict. The point is to show a repeatable communication pattern worth examining.

My corporate-communication research began well before the employment disputes now under review. In my 2019 Clarion opinion piece, “Student starts initiative to address microagressions,” I described microaggressions as subtle conduct that can set boundaries and walls—signals that someone is different or unwelcome. In 2023, in “Speak up, speak out on bullying”, I urged documentation, use of available resources, and timely reporting when bias or bullying interferes with a student’s ability to learn and participate.

Those were not predictions of litigation. They were the beginnings of a reporting framework: name the communication, preserve the words, identify the power relationship, and separate what the record proves from what a person reasonably experiences.

The timeline

The first eight entries arise from the 2022 UW–Whitewater record. They include a reported instruction to “take the ‘W’ and deal with it” and drop the matter; a reported condition that future complaints go through one person first; and a reported prohibition on using a lounge “under no condition.” The chronology also records a request for VA records, a refusal to authorize release, and a later written condition that speaking with particular people required signing a release. Other entries describe a same-day response deadline, a statement that an investigation could be stopped only by withdrawing the complaint, and a reported Wednesday 4:30 p.m. reporting deadline that still needs source-date verification.

Each event may have an explanation. A deadline can be administratively necessary. A release may be requested for a specific communication. A complaint process may assign a contact person. But a corporate-communication analysis does not stop at the isolated explanation. It asks what a reasonable recipient is told by the full construction: Who controls access? What must be surrendered to participate? What happens if the deadline cannot be met? Is there a practical alternative?

The Marcus Palace Cinema portion of the chronology contains five entries from 2023–24. My contemporaneous follow-up letter recounts being told to exhaust an open-door process before escalating concerns, not to go above a supervisor, and to keep matters internal. The same record stream describes an HR documentation request after I contacted HR about disability-related work demands. Later correspondence recounts a required interactive-dialogue questionnaire and a meeting demand concerning military service and VA disability without third-party representation. The last two entries must be anchored to original emails or requests before they should be treated as anything beyond my reported account.

That distinction matters. Documentation is not an invitation to overstate. It is a discipline: the letter shows what I said at the time; an original HR email would show what the employer actually required; a decision-maker’s testimony could explain the purpose; and the complete record may support, complicate, or contradict my interpretation.

The final five entries are the most textually specific. On September 19, 2024, Frank Productions HR stated that the Interactive Process Questionnaire had to be completed by a health-care provider and returned by October 3. The notice stated that failure to provide requested information on time may result in rejection of the accommodation request. The questionnaire called for detailed information about impairment, symptoms, treatment, prognosis, functional limitations, and a provider signature. On October 3, HR stated it would proceed temporarily on self-reported information while reserving the ability to request provider information or updates.

Those communications may reflect an employer’s attempt to obtain accommodation documentation. They also present the communication question that the ###DVR project is built to test: when does a process designed to facilitate accommodation become experienced as a condition of dignity, privacy, or continued participation?

Why I call this a microaggression inquiry

Microaggression is not a magic legal label. It is a way of examining small, repeated acts of communication that can carry a larger message about belonging and power. A deadline becomes more than a calendar date when it follows disclosure of a disability. A request for documentation becomes more than a form when it requires broad health information without an understandable boundary. “Keep it internal” becomes more than an instruction when the employee believes it closes off ordinary avenues for reporting concerns.

The operative word is context. The present chronology is not simply a list of things I disliked. It tests a set of variables:

  • Was the communication tied to a protected disclosure, complaint, request for help, or accommodation?
  • Did it impose a deadline, compelled release, gatekeeping condition, or stated consequence?
  • Was the scope tailored to the stated purpose?
  • Was a less intrusive route available and communicated?
  • Did the same person or institution later control investigation, access, evaluation, or discipline?
  • What primary document, witness, policy, or official finding confirms, limits, or contradicts the account?

That is corporate communication research: look beyond polished policy language and examine how the actual message functions for the person who receives it. The question is not whether every document request is improper. It is whether the accumulated form of the requests communicates, “Comply on our terms, disclose what we demand, stay inside the channel we control, or lose access to the process.”

From opinion to JEDVIDENCE™

The ###DVR method is deliberately slower than outrage. It begins with the reporting record, builds a dated chronology, and labels each item by source strength: direct document, contemporaneous report, later account, reported statement, or unverified lead. It then compares competing explanations. An employer’s explanation belongs in the record; so does the employee’s lived experience; so do independent witnesses, policies, case notes, and administrative outcomes.

This is why I distinguish Op-Ed from Exposé. The Op-Ed states my human perspective: I experienced a chain of disclosures, deadlines, forms, and controlled channels as humiliating and coercive. The Exposé identifies the underlying dates, language, sources, omissions, and limits so readers can test that perspective rather than merely adopt it.

The 18-item list supports grounds for inquiry—not a presumption that every institutional actor acted with discriminatory intent. It supports inquiry into whether repeated ultimatum-style communications compounded the burden of reporting, accommodation, and participation for a disabled veteran and DVR client. That is a question of power, accessibility, and institutional design as much as it is a question of any one email.

My research has remained consistent from the Clarion to ###DVR: people should be able to speak up without being made to feel that the price of being heard is surrendering privacy, agency, or credibility. When institutions ask for information, they should explain why, narrow the request, offer a realistic path forward, and avoid turning a support process into a test of compliance.

The next step is verification. I will continue replacing descriptive entries with exact filenames, dates, pages, and audio timestamps; identify gaps instead of filling them with assumption; and preserve contrary evidence alongside supporting evidence. That is how a personal chronology becomes JEDVIDENCE™: not a story that demands belief, but a record that invites examination.

Editorial note: This post reports the author’s perspective and an ongoing documentary chronology. It does not state that any allegation has been proven, and it should not be read as a finding of legal liability. Direct records, policies, witness accounts, and official determinations may corroborate, qualify, or contradict individual entries.

Burt v. State Documentary: Tracking Wisconsin ERD Records, Evidence, and Accountability

Outpost 422 Announces Burt v. State: A JEDVIDENCE Documentary Record Project

A public-interest documentary project examining chronology, evidence preservation, and procedural accountability in Wisconsin civil-rights investigations.

Outpost 422 is developing Burt v. State, a Chat_MP4 documentary project that follows Bradley J. Burt’s effort to organize and preserve the documentary record connected to several Wisconsin Equal Rights Division matters.

The project does not ask viewers to reach a verdict about any person, agency, attorney, or pending case. Its purpose is narrower: to show how source documents, dated communications, investigation procedures, and competing factual accounts can be organized into a traceable chronology.

In September 2026, Burt served a Notice of Injury and Claim under Wis. Stat. § 893.82 concerning his contention that preserved concerns about ERD investigative scope, evidence review, disputed facts, and separately alleged theories were not adequately addressed. The notice expressly does not claim that an adverse determination, investigative error, or disagreement alone proves unlawful conduct, bad faith, constitutional liability, or damages. Those questions remain for the appropriate tribunal and complete record.

The documentary will also examine publicly available ERD investigative guidance. The materials emphasize review of all alleged bases and issues, development of needed information, attention to disputed facts, and chronological writing of determinations. Those standards matter because procedural fairness is not just a legal phrase—it is the difference between a record that can be checked and one that cannot.

JEDVIDENCE is the working method behind the project: journalism, metadata, document authentication, chronology, and AI-assisted organization under human editorial control. The goal is not to use AI as a judge. The goal is to make the evidence traceable before a human decision-maker rules.

As production continues, Outpost 422 will release source-grounded updates, clearly identify allegation versus verified record, and preserve the distinction between advocacy, reporting, and adjudication.

Burt v. State: The DVR Documentary is in development.

JEDVIDENCE: Provenance proves credibility through metadata with OpenAI evidence assembly in documentary form at Outpost 422

SCR 20:1.4 in the Age of Generative AI: A JEDVIDENCE Timestamp

October 5, 2026 | ###JEDVIDENCE | Journalism eDiscovery

Today’s search result on Wisconsin Supreme Court Rule 20:1.4 is a useful timestamp for the JEDVIDENCE project because it identifies the core issue: communication must allow a client to make informed decisions about representation.

The rule concerns the client-lawyer relationship. It is not a free-floating rule that automatically governs an opposing party, an opposing lawyer, a journalist, an AI system, or an administrative agency. That boundary matters. A responsible discussion of generative AI has to begin with what the rule actually addresses, rather than stretching a communication rule into a conclusion it does not make.

The supplied rule text does not mention generative AI. But its communication principles raise a modern question: when technology assists in organizing facts, summarizing records, or drafting language that may affect a client’s matter, what does meaningful human communication look like?

For me, the answer is not “let AI decide.” It is the opposite.

JEDVIDENCE is built as a source-controlled Journalism eDiscovery process: identify the original record, preserve the date and provenance, distinguish a person’s allegation from a document’s contents, identify competing accounts, mark missing evidence, and leave the ultimate conclusion to a human decisionmaker. Artificial intelligence can help locate patterns and formulate questions. It cannot become the witness, the lawyer, the investigator, or the Tribunal.

That distinction became especially important in my October 5 review of the Camp Createability record. The review compared a position statement’s categorical account of notice with a supplied audio recording. The resulting analysis did not declare that anyone committed misconduct. It identified a factual question: whether the recording, if authenticated and accurately transcribed, is consistent with the assertion that Debbie Armstrong had no knowledge of a harassment-related complaint before the June 7, 2025 termination.

That is the JEDVIDENCE function. Not verdict. Not diagnosis. Not character assassination. A record check.

The same discipline applies to the master DVR chronology now being preserved alongside my broader administrative record. The chronology does not manufacture a claim. It organizes DVR-related records, employer communications, administrative actions, competing narratives, and unanswered questions so a reviewer can see what was provided, when it was provided, and what was—or was not—addressed.

I have also given notice to the Wisconsin Attorney General through a Notice of Injury and Claim. That filing is preservation, not proof. It does not establish liability, constitutional wrongdoing, bad faith, or damages. It preserves the record while the relevant administrative matters continue.

The patent-pending JEDVIDENCE concept is likewise not offered as a substitute for evidence. Its value, if it has one, is transparency: a reproducible path from source to chronology, from chronology to question, and from question back to the source.

That is where SCR 20:1.4 belongs in this conversation. Communication is not simply transmitting a conclusion. It is providing enough accurate, understandable information for the human being responsible for the decision to participate meaningfully.

In a generative-AI era, that means showing the work.

JEDVIDENCE rule of the day: Source first. Human review always. Final judgment belongs to the Tribunal.

JEDVIDENCE Meets SCR 20:1.4: Scanning Attorney Work Product, Generative AI and the Documentary Record

OP-EXPOSÉ: The Rule of Communication Meets the Record

A JEDVIDENCE scan asks what an attorney’s work product communicates—and whether the documentary record can test it

By Bradley J. Burt | Outpost 422 / The Jaded Patriot Brief

There is a difference between accusing a lawyer of professional misconduct and examining legal work product through the rules governing the profession.

JEDVIDENCE is interested in the second.

My latest experiment begins with Wisconsin Supreme Court Rule SCR 20:1.4, the communication rule. It requires lawyers to keep their clients reasonably informed, reasonably consult about the means used to accomplish client objectives, respond to reasonable requests for information, and explain matters sufficiently to permit informed client decisions. Wisconsin’s current Rules of Professional Conduct remain contained in SCR Chapter 20. Wisconsin Court System

That does not mean Rule 1.4 gives me, as an opposing party, a communication right against another party’s attorney. It doesn’t. Instead, I am using the Rule as part of an experimental research framework: What happens when we take the communication concepts governing legal representation and use documentary metadata to examine the finished work product?

Exhibit A: The Position Statement

On May 19, 2026, attorney Storm B. Larson of Boardman & Clark submitted an eight-page position statement to Wisconsin’s Equal Rights Division on behalf of Camp Createability, LLC. The document identifies itself expressly as Camp’s response to my discrimination complaint, denies discrimination and retaliation, and asks ERD for a finding of no probable cause. Position Statement of Camp Crea…

That’s our starting point—not my opinion about Larson and not an AI characterization of Larson.

The document itself.

And the document makes propositions capable of being tested.

For example, the position statement says that on June 5, 2025, I mentioned retaliation and harassment to Emily Williams. According to the respondent’s narrative, Williams redirected me to CEO Debbie Armstrong. Position Statement of Camp Crea…

A few paragraphs later comes the proposition at the center of the retaliation defense: Armstrong supposedly had “no idea” I had mentioned retaliation or harassment and terminated me without knowledge of those allegations. Position Statement of Camp Crea…

The legal analysis then makes knowledge decisive. The position statement cites Gunty and Sabol, states that employer knowledge is required, and argues that the retaliation claim fails because Armstrong lacked knowledge of the protected activity when she made the termination decision. Position Statement of Camp Crea…

That is precisely where JEDVIDENCE stops reading like an ordinary reader.

It starts scanning.

Don’t Ask Whether the Lawyer Was Wrong. Ask What the Proposition Requires.

The proposition can be stripped of rhetoric:

Williams knew → Williams redirected Burt to Armstrong → Armstrong allegedly did not know → Armstrong made termination decision → lack of knowledge defeats claimed causal nexus.

Now we have variables.

When did Williams acquire the information? What exactly was communicated? What did Williams do afterward? With whom did she communicate? What information reached Armstrong? When did it arrive? What documentary artifacts memorialize those communications? Are there emails, texts, notes, phone records, witness accounts or contemporaneous documents? Does later work product describe the event differently?

Those are questions.

They are not findings.

The same technique applies to accommodation. The position statement acknowledges that Armstrong knew I occasionally experienced migraines while simultaneously maintaining that she did not know I possessed a specific disability requiring accommodation. Position Statement of Camp Crea…

Again, JEDVIDENCE doesn’t turn that difference into misconduct.

It turns it into a variable.

What did the employer know? When did it know it? From what source? What did “DVR client” communicate? What disability information was actually disclosed? What accommodation was actually requested? What documentation existed at the time?

Then we find the receipts.

Enter Generative AI

This is where the experiment gets particularly interesting.

Wisconsin legal-ethics guidance isn’t telling lawyers that generative AI itself is unethical. State Bar ethics guidance instead emphasizes that lawyers’ underlying professional responsibilities remain in place when they use AI. Wisconsin commentary has identified competence, confidentiality, supervision, verification, candor, communication and reasonable fees among the existing professional obligations implicated by GenAI. WisBar

And Wisconsin legal-ethics commentary has specifically warned against taking AI-generated legal documents “as-is.” Lawyers remain responsible for oversight and review of the resulting work product. WisBar

That principle works both directions in my experiment.

I don’t get to dump Larson’s position statement into ChatGPT and announce:

“AI says the lawyer violated the ethics rules.”

That would reproduce exactly the methodological problem I’m studying.

Instead:

SOURCE → AI SCAN → VARIABLE → PRIMARY AUTHORITY → DOCUMENTARY COMPARISON → HUMAN VERIFICATION → CORRECTION → CONCLUSION OR UNRESOLVED

If OpenAI misreads the position statement, I correct OpenAI.

If I misremember an event, the contemporaneous record gets to correct me.

If opposing counsel’s proposition survives comparison against the documentary record, it survives.

If the documents contradict my narrative, that contradiction belongs in the dataset too.

And if the evidence cannot answer the question?

UNRESOLVED.

That’s not a weakness. That’s source control.

SCR 20:1.4 Becomes a Microscope, Not a Verdict

The communication rule gives this experiment something more useful than a buzzword.

It gives us variables.

Consultation. Information. Explanation. Status. Decision. Knowledge. Response. Timing. Informed participation.

The State Bar’s AI guidance makes the connection even more interesting. Its 2024 discussion of generative AI explains that lawyers’ existing ethical responsibilities continue when GAI enters the representation, including communication and informed-consent considerations where appropriate. WisBar

So instead of asking whether artificial intelligence should replace a lawyer, JEDVIDENCE asks something much narrower:

Can AI help a human inspect whether legal work product is internally consistent with the documentary information available to test it?

That’s a very different proposition.

AI doesn’t become the witness.

AI doesn’t become the lawyer.

AI doesn’t become the judge.

And AI certainly doesn’t become the source.

It becomes the scanning instrument.

Where Subjective Coding Comes to Die

The Camp Createability position statement contains forceful characterizations. It describes me as responding in a “disrespectfully hostile manner,” says I “stormed” into a room, characterizes me as “visibly agitated and highly emotional,” and reports that others considered my behavior aggressive or frightening. Position Statement of Camp Crea…

Those words matter.

But a JEDVIDENCE scan doesn’t automatically accept them, and it doesn’t automatically reject them.

It asks what each characterization is made of.

Who observed the conduct?

When?

What precisely did the witness see or hear?

Was the characterization contemporaneous or retrospective?

Was there another witness?

Was an account written before or after the employment decision?

Did later versions change?

Does independent documentary evidence corroborate it?

That is what I mean when I say:

Keep the buzzword in the headline. Remove it from the finding.

The Gonzo journalist can describe how the accusation felt.

The researcher must dissect the variable.

The documentary record gets the last word it is capable of giving.

And the tribunal—not ChatGPT and not Bradley Burt—gets the legal decision.

The Experiment

That is the larger point of this project.

Generative AI does not eliminate human responsibility. It makes disciplined human responsibility more important.

Recent Wisconsin State Bar guidance continues to emphasize verification of AI-generated material, including citations. WisBar That is not an argument against the technology. It is an argument for building workflows in which mistakes become visible before they become finished work product.

My experiment therefore isn’t:

Can ChatGPT prove my case?

It is:

Can a human researcher surround generative AI with enough primary material, coursework, legal authority, documentary metadata and competing narratives that both human and machine errors become easier to detect?

That’s JEDVIDENCE.

And SCR 20:1.4 gives us another lens through which to conduct the experiment.

Don’t trust the machine.

Don’t automatically trust the storyteller.

Don’t automatically trust the advocacy document, either.

Scan the communication.

Extract the proposition.

Identify the variable.

Find the source.

Check the timestamp.

Preserve the competing account.

Correct the machine when necessary.

And then—

inspect the receipts.

OP-EXPOSÉ: From Accommodation to “Threat”—Examining Boardman & Clark’s Advocacy Against a Disabled Veteran’s DVR Record

An OpenAI rhetorical analysis of the Gregg and Larson submissions against the documentary record

There is an important document sitting behind this story.

On September 5, 2024, Wisconsin DVR amended Bradley Burt’s Individualized Plan for Employment. The document pictured with this report identifies a long-term goal of becoming a “Project Administrator or Manager or Trainer,” with a target date of December 31, 2026. Its service table traces journalism education, UW-Whitewater degree training, tutoring, job development and graduate-level communication training.

That document does not prove discrimination by anybody.

It does something journalistically different.

It supplies context.

The administrative disputes now surrounding Burt did not arise in a vacuum. They intersected with a years-long vocational-rehabilitation trajectory intended to move him through education and employment toward a defined occupational destination.

And that makes the rhetoric used to describe him worth examining.

Gregg: from complaint to character

Attorney Robert Gregg’s January 30, 2026, response for Frank Productions begins conventionally: the company denies discrimination and retaliation.

Then comes something rhetorically significant.

Gregg writes that Frank Productions had “little or no idea” what Burt was attempting to allege. He subsequently describes Burt’s complaint as a “rambling paragraph of seemingly disjointed elements.” Initial Response w_ attachments… Initial Response w_ attachments…

That may be forceful defense advocacy. It is not itself evidence that the allegations were false.

And that distinction matters.

The complaint described termination for alleged threatening violence and connected that event to earlier complaints to management, disability, a firearms-related journalism reference, and the termination meeting. Gregg’s position was that those allegations failed adequately to connect an adverse action with protected categories. Initial Response w_ attachments…

There is therefore a legitimate legal dispute buried underneath the rhetoric:

Was Burt merely assembling unrelated events, or was he attempting—imperfectly—to describe a causal sequence that investigators were obligated to examine?

That question cannot be answered by calling the narrative rambling.

It requires investigation.

Burt’s September 17, 2024, contemporaneous letter to his DVR director is particularly important here. Almost two months before his termination, he complained about management, confidentiality, scheduling and what he perceived as disability-related workplace problems. He asked DVR for a confidential progression process and said he wanted to resolve the grievance before resorting to the employer’s whistleblower mechanism. Letter to DVR Director

That document doesn’t establish retaliation.

But it makes the earlier workplace dispute contemporaneous rather than retrospective.

Larson: from conduct to characterization

Storm Larson’s May 19, 2026, Camp Createability position statement employs a comparable defense structure in a different employment dispute.

Camp denies discrimination and retaliation and asks ERD for no probable cause. Position Statement of Camp Crea…

The factual narrative then uses highly descriptive language: Burt allegedly responded in a “disrespectfully hostile manner,” “stormed” into a room, was “visibly agitated and highly emotional,” raised his voice and frightened a child. Camp further reported that another employee said she was afraid to return to work. Position Statement of Camp Crea…

Those are consequential allegations.

But rhetorically, notice what happens.

The reader encounters characterization before adjudication.

Burt’s account looks substantially different. His Statement of Facts describes inadequate onboarding, disagreements over documentation practices, workplace communications he perceived as indirect targeting, reports to his DVR counselor, and an accommodation dispute concerning additional time to answer a telephone. CAMP CREATEABILITY STATEMENT OF…

Again, neither narrative becomes true merely because an advocate wrote it.

That is precisely where an investigator enters the story.

Wisconsin’s manual changes the lens

The ERD materials supplied for this project provide perhaps the most useful editorial rule of all.

The Division’s investigation checklist tells investigators, after receiving the employer’s response, to identify the discrimination bases and actions alleged, determine what additional information is required from both parties, address all bases and issues, and seek comparative information where appropriate. How to do investigation (2)

Its final-review checklist then asks three separate questions: Has the complainant supplied the basic elements? Has the respondent supplied a legitimate nondiscriminatory explanation? And has the complainant supplied evidence suggesting either discrimination or that the employer’s stated explanation may be pretextual? How to do investigation (2)

Then comes the line that, from my perspective, belongs at the center of this Op-Exposé:

“Disputes of material fact that cannot be resolved need to proceed to a merits hearing (probable cause).” How to do investigation (2)

That does not mean every factual disagreement establishes probable cause. Wisconsin’s LIRC describes probable cause as more than suspicion or a prima facie showing but less than the ultimate merits determination. Labor & Industry Review Commission ERD itself currently explains that probable cause isn’t a finding of liability; it means enough believable information exists to send the matter to a merits hearing. Wisconsin Workforce Development

That distinction is critical.

The rhetorical collision

My comparison therefore doesn’t produce the headline “Boardman Clark lied.”

The documents reviewed do not justify that conclusion.

They produce a considerably more interesting journalism question:

When employer advocacy transforms disputed conduct into a character narrative, did the neutral investigator independently test the underlying events—or simply choose between competing stories?

Gregg presents an allegedly confusing complainant whose allegations lack sufficient legal connection.

Larson presents an employee allegedly beset by performance and behavioral problems.

Burt presents himself differently: a DVR participant documenting workplace concerns, requesting accommodations or assistance, reporting perceived discrimination and attempting to connect later adverse actions to those events.

Each side has a narrative.

Probable cause is supposed to require something other than narrative preference.

The missing middle is where JEDVIDENCE lives

This is where my analysis would concentrate—not on adjectives, but on records.

Who knew about disability and when? What accommodations were actually requested? What did DVR communicate to the employers? What complaints preceded termination? Who received them? What contemporaneous witness statements exist? What do scheduling records show? What documentation existed before termination rather than afterward? Were materially conflicting accounts investigated through witnesses or additional document requests?

Those questions matter particularly because Larson’s submission expressly disputes whether Camp knew about specific disabilities and whether the telephone request was an accommodation. It also argues that the decisionmaker lacked knowledge of Burt’s retaliation complaints. Those are factual propositions susceptible to documentary and witness testing, not merely rhetorical resolution.

The Frank Productions record presents its own version of the same problem. Burt’s contemporaneous DVR letter establishes that workplace concerns existed before his November termination. Letter to DVR Director Gregg’s submission establishes that the employer vigorously disputed the legal connection between those concerns and the termination. Initial Response w_ attachments…

The question for a fact-finder isn’t which paragraph sounds better.

It is what the evidence does with the disagreement.

The veteran in the paperwork

And here the September 2024 IPE becomes more than a background exhibit.

That doesn’t immunize Burt from workplace discipline. Veteran status doesn’t make his recollections automatically correct. DVR participation doesn’t transform an ordinary workplace dispute into discrimination.

But neither should later allegations erase the documented journey that preceded them.

That’s where I find the rhetorical danger in these records.

A human being can disappear underneath litigation adjectives.

“Hostile.”

“Agitated.”

“Rambling.”

“Aggressive.”

“Threatening.”

Some may ultimately prove accurate descriptions of particular conduct. Some may prove incomplete. Some may represent witness perception. Others may turn out to be advocacy.

An investigation exists to determine which is which.

That is why Wisconsin’s own manual instructs investigators to state each side’s version, identify its documentary or testimonial support, resolve material disputes where possible, and send unresolved material factual disputes forward when the probable-cause standard is satisfied. How to do investigation (2)

And that is my OpenAI PONG after reading these materials:

Gregg and Larson were advocates. Their submissions should be read as advocacy. Burt is the complainant. His submissions should be read as allegations and evidence offered in support of them. None should substitute for the investigator’s independent examination of the underlying record.

Wisconsin’s current public explanation says essentially the same thing from another direction: the Equal Rights Officer acts independently and represents neither party. Wisconsin Workforce Development

That—not whether I like one lawyer’s rhetoric—is the Op-Exposé worth pursuing.

Because the most consequential question isn’t whether an employer’s attorney can construct a powerful narrative.

Of course an advocate can.

The question is what happens when that narrative reaches the desk of the person whose job is to investigate it.

OpenAI/JEDVIDENCE™ disclosure: This article is an AI-assisted rhetorical and documentary analysis requested by Bradley J. Burt. It distinguishes employer allegations, Burt’s allegations, documentary facts, and my analytical observations. It does not accuse Robert Gregg, Storm Larson, Boardman Clark LLP, Frank Productions LLC, Camp Createability LLC, DVR, or any individual of criminal, unethical, discriminatory, or otherwise unlawful conduct. Those questions belong to the appropriate fact-finders.

EDITOR’S NOTE: This analysis represents OpenAI’s analytical perspective on documents supplied for review. It is not a judicial finding, an ERD determination, a finding of attorney misconduct, or a conclusion that discrimination occurred. Robert E. Gregg and Storm B. Larson represented their respective clients and were entitled to dispute Bradley Burt’s allegations. The purpose of this JEDVIDENCE™ exercise is narrower: compare the rhetoric of those advocacy documents with the evidentiary questions Wisconsin’s own investigative materials tell a neutral investigator to ask.

It shows a vocational destination extending through December 2026. Journalism training, university education, tutoring, job development and additional communication education appear as pieces of an organized rehabilitation plan.

Quadratic Logic™: How Outpost 422 Is Building a Human-AI Scribe to Find 18 Recurring Patterns in the Documentary Record

Quadratic Logic: Building the Human-AI Scribe From the Documentary Record

OUTPOST 422 | JEDVIDENCE™ | JED422-RESEARCHER

After years of collecting emails, administrative filings, employment records, agency determinations, correspondence, timelines, screenshots and firsthand notes, I discovered something important: the story isn’t contained in any single document.

It exists in the relationships between them.

That observation became the foundation of Quadratic Logic, the analytical framework behind my developing JEDVIDENCE™ methodology and the Jaded Patriot Brief.

The experiment asks a deceptively simple question:

What happens when a human journalist and an AI scribe repeatedly examine the same documentary record from four different directions?

The four corners are:

Lived Experience + Documentary Evidence + External Corroboration + AI-Assisted Variable Analysis.

None of those corners is permitted to become the truth by itself.

My memory isn’t the record. An employer’s position statement isn’t the record. An investigator’s determination isn’t necessarily the entire record. And ChatGPT certainly isn’t the record.

The documents remain the sources.

The Human-AI partnership instead operates as a scribe—organizing, comparing, indexing and repeatedly testing those sources while the human remains responsible for interpretation, verification and publication.

That distinction is fundamental.

Accuracy Through Convergence

The goal isn’t to create an artificial intelligence that tells readers what happened.

It is to develop a workflow capable of showing readers why a particular proposition can—or cannot—be supported by the available record.

A source enters the system as a PING.

The Human-AI workflow examines dates, speakers, claims, documents, contradictions and corroborating material. JED422-RESEARCHER can then compare those findings against statutes, administrative rules, judicial decisions and other authoritative materials.

The resulting organized evidentiary product becomes the PONG:

JEDVIDENCE™.

Accuracy therefore isn’t based upon trusting AI.

It comes from making the AI show its work against human-controlled source material.

The 18 Recurring Variables

Scanning my employment and administrative matters as a combined dataset has exposed recurring questions. They are not findings that every employer, attorney or government official committed wrongdoing. They are research variables—patterns sufficiently recurrent to justify systematic examination.

The eighteen themes currently emerging from the dataset are:

1. Accommodation communication.
Who knew about a disability-related limitation, when did they know it, and what happened afterward?

2. DVR involvement.
When vocational-rehabilitation professionals were involved, what communications existed between DVR, employers and the worker?

3. Notice gaps.
Were people or organizations who appeared important earlier in the chronology included when later decisions were made?

4. Documentation versus recollection.
Do contemporaneous emails, messages and records support later descriptions of events?

5. Timeline compression.
Do later narratives combine separate events in ways that change their apparent meaning?

6. Retaliation chronology.
What protected or complaint-related activity preceded an adverse action, and what intervening events occurred?

7. Escalating rhetoric.
Did terminology describing an employee become more severe over time, and what evidence accompanied that change?

8. “Threat” characterization.
When conduct or speech was described as threatening, what precisely was said or done, who witnessed it, and what contemporaneous evidence exists?

9. Witness foundation.
Was a factual proposition based upon firsthand observation, hearsay, inference or later reconstruction?

10. Missing witnesses.
Were potentially corroborating or contradicting witnesses interviewed, identified or otherwise represented in the record?

11. Missing physical or digital evidence.
Did potentially relevant video, email, scheduling, personnel or other electronic evidence exist, and was it examined?

12. Progressive discipline.
What coaching, warnings, improvement plans or disciplinary steps existed before termination—and what did the employer’s own policies contemplate?

13. Decision-maker separation.
Who supplied information, who characterized it, and who actually made the employment decision?

14. Military-service language.
When military background entered workplace discussions, exactly what was said, by whom, and in what context?

15. Administrative narrative versus source record.
Does an investigative determination accurately reflect the material evidence submitted to the agency?

16. Unresolved documentary conflicts.
When two records materially disagree, does the administrative analysis acknowledge and resolve the conflict?

17. Procedural completeness.
Were the theories actually raised by the complainant investigated and addressed under the governing procedural framework?

18. Record provenance.
Can every important proposition ultimately be traced backward to its original source?

These variables don’t determine the answer.

They determine where we look.

That’s Where Quadratic Logic Changes Journalism

Traditional narrative journalism often moves forward:

Event → Interview → Story.

JEDVIDENCE can move forward, backward and sideways.

A termination letter can be compared against an earlier email. That email can be compared against DVR documentation. The resulting discrepancy can be checked against another witness’s account. The chronology can then be tested against Wisconsin employment law and administrative procedure.

Quadratic Logic keeps asking four questions:

What did I experience?

What does the documentary evidence establish?

What can an independent source corroborate?

What patterns emerge when AI examines the variables across the complete dataset?

Agreement among those corners increases confidence.

Disagreement is equally valuable.

A disagreement tells the researcher where another investigation is required.

The Human Remains in Command

This may be the most important lesson from the experiment.

AI should not become the witness.

It shouldn’t become the judge.

It shouldn’t quietly transform an allegation into a fact because the allegation appeared repeatedly in the dataset.

That is why Outpost 422 increasingly labels information according to epistemic status: documented fact, allegation, perception, inference, disputed proposition, legal argument or independently verified finding.

The Human-AI scribe becomes useful precisely because it can preserve those distinctions.

And when it gets something wrong, the human corrects it and sends the corrected proposition back through the analytical loop.

That makes JEDVIDENCE less like asking a chatbot a question and more like maintaining a continuously tested research notebook.

From Four Employment Cases to a Research Laboratory

My individual matters provided the source material, but the experiment has become larger than any single dispute.

Marcus Palace Cinema, Frank Productions, Camp Createability and Madison College contain different parties, different circumstances and different procedural histories.

They should not be collapsed into one allegation.

Quadratic Logic instead asks whether recurring structural questions can be examined consistently across independent matters.

Who knew what?

When?

What document proves it?

Who witnessed it?

What changed?

What evidence contradicts it?

Was the contradiction addressed?

What rule governed the decision?

And can another researcher reproduce the analysis?

Those questions are becoming the grammar of the Human-AI scribe.

Journalism From the Trenches of Metadata

That is what we’re building at Outpost 422.

Not an AI oracle.

Not a machine that declares winners and losers.

Not software that turns suspicion into fact.

We’re developing a Human-AI evidentiary scribe designed to preserve chronology, provenance, contradiction and uncertainty while helping a human researcher navigate documentary volumes that would otherwise be extraordinarily difficult to compare manually.

The ambition is substantial:

PING → Quadratic Logic → JED422-RESEARCHER → Human Verification → PONG → JEDVIDENCE™.

Every iteration adds another opportunity to test the methodology.

Every discrepancy becomes another variable.

Every correction strengthens the provenance trail.

And every source remains available for the most important question investigative journalism can ask:

Show me the record.

Outpost 422 — Stoic Journalism From the Trenches of Metadata™

When Safety Language Becomes the Whole Story: Corporate Communication, Consequences, and the Record in Burt v. Frank Productions

When Safety Language Becomes the Whole Story

Corporate Communication, Consequences, and the Record in Burt v. Frank Productions

Corporate communication is not merely tone. It is the system by which an employer decides what an event means, who gets believed, and what consequence follows. In an employment dispute, that system can be necessary: an employer must respond to safety reports, investigate workplace conflict, and protect patrons and employees. But the same system deserves scrutiny when its language converts a disputed workplace exchange into a permanent professional and public-safety identity.

That is the communication question raised in Burt v. Frank Productions. Frank Productions maintains that it terminated Bradley Burt after receiving reports that he made repeated, on-duty statements about harming a patron and sent angry messages to a shift lead containing an image that the recipient interpreted as intimidating. The company’s January 2026 response describes these allegations as a valid, nondiscriminatory safety basis for termination and an indefinite venue ban. Burt disputes the characterization, denies threatening violence, and contends that the complete message sequence, video context, witness foundation, and security evidence must be reviewed before the narrative is accepted as fact.

The ban letter itself is consequential. It did not only end employment. It barred Burt from FPC and FPC Live venues in multiple states “until further notice.” That decision may be warranted if the underlying safety allegations are established and consistently handled under company policy. Yet the seriousness of the consequence makes the process especially important. A broad ban based on a belief that communications could jeopardize safety is not proof that the communications were a threat, that every relevant fact was reviewed, or that comparable cases received the same response.

This is where the corporate-communication study becomes relevant. “Machiavellianism” is used here as an analytical term, not a diagnosis or accusation about any individual: the risk that institutional messaging begins with a desired outcome and then selects language that makes the outcome appear inevitable. In a workplace setting, that can occur when an employee’s complaints are reduced to “disorganized,” “irrational,” or “without merit” before the underlying evidence is fully tested. Those descriptions may be advocacy or management opinion; they are not independent proof of intent, credibility, or danger.

The consequentialism variable asks a narrower question: what did each communication cause, or foreseeably contribute to, in the decision chain? Burt’s account identifies disability-related complaints, accommodation and privacy communications, reports of perceived unequal treatment, and workplace concerns before the November 5, 2024 event. FPC identifies its own accommodation process, prior outside-HR review, and an asserted safety incident as the decision context. The legal issue is not resolved by choosing one storyline at the outset. It is whether protected opposition or protected-status context was known to decision-makers and played a role in how the later event was interpreted, investigated, and punished.

The potential causal connection is therefore not simply that Burt complained and was later terminated. Timing alone is not enough. The record must show, if it exists, that decision-makers knew of protected activity; that the adverse action followed; and that the stated safety reason was inconsistent, selectively enforced, weakly investigated, or influenced by someone with a prohibited motive. The corresponding defense is equally concrete: that FPC independently and honestly concluded, from reliable evidence, that the alleged conduct justified termination and a ban regardless of any complaint or protected status.

That is why the complete record matters. The relevant materials include the unedited message thread with timestamps and links, the original video or image context, every November 5–8 incident report, witness accounts identifying firsthand knowledge, any security footage and retention records, decision-maker communications, and comparator evidence concerning other bans for alleged threats or aggressive conduct. A policy citation is not a substitute for the facts to which the policy was applied. Nor is a personal diary, social-media post, or litigation brief a substitute for corroboration.

The source-controlled approach does not claim that FPC, its managers, or its counsel acted unlawfully. It does not claim that a safety concern was invented. It does not ask the public to pronounce a verdict. It asks a disciplined question: did the process preserve the distinction between an employee’s contested words, another person’s interpretation of those words, an employer’s policy judgment, and the extraordinary consequence that followed?

That distinction is the heart of JEDVIDENCE. It keeps the story testable:

Source → Date → Claim → Competing Account → Corroboration → Missing Evidence → Bounded Conclusion.

Burt’s position is that his workplace advocacy and disability-related reporting were part of the context management knew before his termination and ban. Frank Productions’ position is that the safety allegations independently justified both decisions. The record presently establishes that these are competing accounts. The Tribunal—not corporate rhetoric, social-media commentary, an attorney’s filing, or an AI scan—must decide what evidence is credible and whether any protected characteristic or protected opposition was a factor in the outcome.

Editorial transparency: This article is AI-assisted, source-controlled reporting based on records selected by Bradley J. Burt. It distinguishes the company’s stated position, Burt’s disputed account, and unresolved evidentiary questions. It is not legal advice, a finding of misconduct, or a tribunal decision.

Burt v. State: Audio and Records Examine DVR Workplace Retaliation Claims

FOR IMMEDIATE RELEASE

Outpost 422 Announces Burt v. State Documentary and Op-Exposé Investigation

Source-controlled reporting examines DVR-connected employment, disability accommodation, workplace safety, and administrative process.

MADISON, Wis. — Outpost 422 today announced Burt v. State: The Wisconsin DVR Documentary, an independent public-interest reporting project produced through its Op-Exposé® and JEDVIDENCE™ methodology.

The documentary examines Bradley J. Burt’s experiences as a disabled veteran and Wisconsin Division of Vocational Rehabilitation client across employment, education, and administrative proceedings. It will organize recordings, contemporaneous communications, accommodation materials, public records, agency correspondence, and related filings into a documented chronology.

The project does not treat allegations as findings. Instead, it distinguishes source material, recorded statements, agency records, witness information, disputed assertions, and unresolved questions. Its reporting focus includes how disability-related documentation, workplace-safety concerns, character narratives, and pro se participation are handled when they intersect with DVR-connected opportunities.

“Op-Exposé is the reporting layer,” Burt said. “The work is to preserve the record, test competing narratives against the documents and audio, and make the unanswered questions understandable to the public.”

Outpost 422 emphasizes that the documentary is not a single lawsuit and does not allege that separate employers, attorneys, or agencies acted in concert. Individual legal and administrative matters remain separate and are addressed through their respective procedures. The project’s purpose is public documentation, source verification, and informed accountability reporting.

The first release will introduce the master chronology and the evidence-preservation framework behind Burt v. State. Additional reporting will be published through Outpost 422 as records are reviewed and verified.

Media and source inquiries: Outpost 422
Website: outpost422.com
Project: Burt v. State: The Wisconsin DVR Documentary

When Employment Defense Turns Personal: JEDVIDENCE Tests Boardman & Clark Attorneys’ Advocacy Against Wisconsin SCR Rules and the Timestamped Record

When Advocacy Becomes Characterization: Why I Asked Wisconsin’s Attorney General to Look at the Record

Outpost 422 | Jaded Patriot Brief | JEDVIDENCE™

I am not asking the public to decide whether two Wisconsin lawyers violated professional-conduct rules.

I am asking something more basic.

Read what was written about me. Then read what the contemporaneous records say.

That distinction is at the center of my Journalism eDiscovery—or JEDVIDENCE™—review of employment-discrimination matters involving Frank Productions LLC and Camp Createability LLC. Both employers have been represented in administrative proceedings by attorneys from Boardman & Clark LLP.

My concern is not that lawyers defended their clients vigorously. That is their job.

My concern is what happens when an employment-discrimination case shifts away from dates, documents, accommodation communications and workplace events and toward increasingly negative characterizations of the employee reporting discrimination.

I have now brought my broader concerns to the attention of the Wisconsin Attorney General. What follows is not a finding of attorney misconduct, nor do I claim the Attorney General has adopted my allegations. It is my documented argument for why the underlying chronology deserves scrutiny.

Start With the Words

In Frank Productions’ January 30, 2026 response, attorney Robert Gregg didn’t merely argue that my allegations failed legally.

The memorandum characterized my complaint as a “rambling paragraph of seemingly disjointed elements.” Initial Response w_ attachments…

Later, the rhetoric escalated. The filing says I “blew the issue out of all proportion” and describes my complaint as an “extreme and irrational overreaction.” Initial Response w_ attachments…

Still later, my description of one workplace occurrence is called “a misrepresentation, a fabrication.” The memorandum then attributes to me a broader “tendency to overreact, distort small or routine matters, and greatly magnify them into major crises.” Initial Response w_ attachments…

That is more than a denial.

It constructs a theory about the reliability of the person making the discrimination complaint.

Gregg’s filing goes further still, telling the investigator that my account demonstrates a supposed tendency to “dwell on perceived wrongdoings,” recharacterize events, invent details and “demonize” others. Initial Response w_ attachments…

Frank Productions is entitled to dispute my allegations. Its witnesses are entitled to dispute my recollection. Its attorneys are entitled to advocate forcefully.

But those characterizations can also be tested.

Then Camp Createability

A separate Boardman & Clark attorney, Storm Larson, submitted Camp Createability’s position statement on May 19, 2026.

Again, the employer denies discrimination and retaliation. That denial itself is unremarkable. Camp is entitled to defend itself.

What interests me is the construction of the factual narrative.

Camp’s submission says that “from almost the start” of my employment, I exhibited performance problems. It describes a later interaction as “disrespectfully hostile,” says I “lambast[ed]” a coworker, “stormed into” another employee’s room, became “visibly agitated and highly emotional,” and frightened a child. Position Statement of Camp Crea…

The narrative then expands into fear and safety. According to Camp’s position statement, an employee was afraid to return to work, a parent reported that a staff member felt unsafe around me, and another parent reportedly would not send a child back while I remained employed. Position Statement of Camp Crea…

Those are serious allegations.

They are also testable factual propositions.

And that is where chronology matters.

The Record Before the Litigation Narrative

My JEDVIDENCE method does not begin by declaring either attorney dishonest.

It asks when each proposition entered the record.

That matters enormously in the Camp case because the contemporaneous DVR chronology provides an independent checkpoint before the termination dispute developed.

The question becomes remarkably simple:

If performance problems existed “from almost the start,” what did the contemporaneous employment record look like while those problems supposedly were occurring?

Where are the contemporaneous warnings?

Where are the disciplinary meetings?

When was the website-video problem first documented as a performance deficiency?

Who knew about it?

What was communicated to me?

What was communicated to DVR?

And what changed between successful employment and termination?

Those questions do not require anyone to accept my interpretation.

They require documents.

The 48-Hour Window

Camp’s filing admits that I was terminated on June 7, 2025. It disputes my contention that the termination followed protected activity because Armstrong allegedly did not know about my allegations when she made the decision. Position Statement of Camp Crea…

That gives investigators an unusually concrete proposition to examine.

Camp says Armstrong lacked knowledge.

I contend information had been reported.

JEDVIDENCE does not settle that dispute by adjective.

It asks whether a documented transmission path existed before the termination decision.

Who spoke with whom? When? What did Williams know? What did Coughlin know? What did Armstrong receive? When was the termination decision actually made?

Those answers should determine how much weight either narrative receives.

The Wisconsin Professional Boundary

This is also why I believe Wisconsin’s Rules of Professional Conduct provide an appropriate public-interest framework for examining advocacy.

SCR 20:3.1 says that a Wisconsin lawyer may not knowingly advance a factual position unless there is a non-frivolous basis for doing so. Wisconsin expressly applies a subjective standard to an ethical violation under this rule. The commentary simultaneously recognizes an advocate’s obligation to use legal procedure for the client’s benefit and the obligation not to abuse that procedure. Wisconsin Court System

That distinction prevents me from jumping from “I found a contradiction” to “the lawyer committed misconduct.”

Those are not equivalent propositions.

A lawyer may rely upon a client’s account. Witnesses may disagree. Memories may conflict. Evidence can emerge later. An attorney can advance an argument that ultimately loses without violating an ethical rule.

But chronology still matters.

If a material factual assertion conflicts with contemporaneous evidence, the next question is what factual basis supported the assertion when counsel made it.

If subsequent evidence undermines that assertion, the next question becomes what counsel knew and when.

Those are legitimate questions. They are not findings of misconduct.

Other professional rules provide additional boundaries. SCR 20:3.4 addresses such matters as obstructing access to evidence, falsifying evidence and certain improper trial assertions. Nothing in the two position statements I reviewed, standing alone, proves conduct of that kind. Wisconsin Court System

Wisconsin maintains a formal lawyer-regulation system precisely because determining whether conduct crosses a professional boundary requires more than a disappointed opposing party’s accusation. The Wisconsin Supreme Court’s Office of Lawyer Regulation screens and investigates grievances within its jurisdiction. Wisconsin Court System

My Argument: Stop Profiling the Reporter and Examine the Record

This is where I believe the public-interest issue emerges.

In one employment dispute, I am described as irrational, prone to distortion and fabrication, and someone who magnifies ordinary events.

In another, I am portrayed through a vocabulary of hostility, agitation, fear and danger.

I dispute those characterizations.

But my answer is not to substitute equally inflammatory descriptions of the lawyers.

My answer is discovery.

Take every material adjective out of these submissions.

Replace it with a date.

Replace “irrational” with the underlying communication.

Replace “hostile” with the actual message.

Replace “unsafe” with the original complaint.

Replace “performance problems from almost the start” with the contemporaneous performance record.

Replace “no knowledge” with the communication chain.

Then compare all of it with records created before anyone knew litigation would require a narrative.

That is Journalism eDiscovery.

The Silent Argument

I contend that the cumulative effect of these narratives resembles a smear campaign because the focus repeatedly shifts toward portraying the reporting employee as irrational, hostile, dangerous or unreliable.

But that is my characterization of the pattern—not an adjudicated fact.

The evidence must decide whether my characterization survives scrutiny just as surely as the employers’ characterizations must.

That is why Outpost 422 will not declare that Gregg, Larson, Boardman & Clark, Armstrong or either employer violated Wisconsin’s professional-conduct rules merely because their accounts conflict with mine.

Instead, I am publishing the test:

SOURCE → DATE → SPEAKER → FIRSTHAND OR HEARSAY → CONTEMPORANEOUS RECORD → LATER CHARACTERIZATION → CORROBORATION → CONTRADICTION → UNRESOLVED FACT

Wisconsin’s professional rules establish boundaries.

The administrative record supplies evidence.

The Attorney General and other appropriate authorities determine what falls within their respective jurisdictions.

And ultimately, the documents should speak louder than any lawyer—including the arguments I make for myself.

That is the point of JEDVIDENCE:

Chronology before characterization.
Contemporaneous evidence before advocacy.
Provenance before inference.

And when someone calls the reporter irrational, hostile or dangerous?

Show me the timestamp.

‘Blind Reliance’ or Verified AI? What JEDVIDENCE and Mata v. Avianca Reveal About Wisconsin ERD

When Opposing Counsel Called It “Blind Reliance”: What the JEDVIDENCE Record Actually Shows

By Bradley J. Burt | The Jaded Patriot Brief / Outpost 422
JEDVIDENCE analysis assisted by OpenAI

Attorney Joshua Welsh gave this documentary project a useful challenge.

In his response opposing my Motion to Compel in my Wisconsin Equal Rights Division matter involving Marcus Palace Cinema, Welsh characterized my work as relying heavily on artificial intelligence and argued that “blind reliance” on AI had taken the case off course.

That is advocacy by opposing counsel—not an adjudicated finding about my research methodology. But rather than dismissing the criticism, I decided to test it.

That is what JEDVIDENCE is supposed to do.

Put the criticism into the machine

The question I gave OpenAI was not: “Prove Welsh wrong.”

The better question was: What does the documentary record allow us to say about how AI has actually been used?

That distinction matters because my evolving State v. Burt DVR documentary timeline contains years of emails, administrative filings, employer responses, exhibits, public records, legal authorities and my own contemporaneous accounts. OpenAI has helped me sort chronology, identify competing propositions, locate contradictions and convert a sprawling documentary landscape into questions that a human researcher can investigate.

That does not make OpenAI a witness.

It does not make an AI response evidence.

And it certainly does not make an AI-generated legal citation an authority simply because the machine produced it.

The documents remain the documents.

Then came Mata v. Avianca

For a control, we examined the federal sanctions decision in Mata v. Avianca, Inc.

That case provides an unusually useful warning about AI-assisted legal work. The federal court did not declare AI inherently improper. Instead, the court focused on the human gatekeeping obligation and sanctioned conduct involving nonexistent judicial decisions and false quotations and citations that had not been properly authenticated.

That is almost a blueprint for what JEDVIDENCE must never become.

Read the Mata v. Avianca sanctions opinion on Justia

The lesson isn’t “trust AI.”

It isn’t “never use AI.”

It is much less glamorous:

Verify the source.

Welsh’s criticism becomes a testable variable

Once that principle is applied to my own work, “blind reliance” stops being a rhetorical contest and becomes an empirical question.

Can I produce the underlying document?

Can another person locate the passage?

Can I distinguish what the employer said from what I said?

Can I identify what an investigator or ALJ actually decided?

Can I show when OpenAI supplied analysis rather than evidence?

Can I correct the machine when it gets something wrong?

Those are much better questions than whether someone generally “trusts AI.”

My own Marcus submission illustrates why this matters. I made numerous allegations and arguments about disability accommodation, management conduct and retaliation. Those remain my assertions unless independently supported or adjudicated. I also expressly criticized opposing counsel under Wisconsin’s professional-conduct framework. 5_22_2025_RESPONSE TO INVESTIGA… JEDVIDENCE should not silently convert any of that advocacy into established fact simply because I wrote it.

The same rule applies to opposing counsel.

The documentary gets another test

The Frank Productions record provides an especially useful example.

In October 2024, CEO Joel Plant wrote that Frank Productions had accepted the documentation I provided and implemented requested accommodations. Joel Plant Email Chain 09_19_20… Plant separately explained the company’s understanding of its ADA process, acknowledged that my VA provider had not completed the company’s form, and nevertheless stated that FPC had implemented the accommodations. Joel Plant Email Chain 09_19_20…

Those emails do not prove my discrimination or retaliation theories.

But they are fixed documentary points.

Later, attorney Robert Gregg’s January 2026 response presented Frank Productions’ litigation position, denying discrimination and retaliation. Initial Response w_ attachments… His submission separately described the company’s account of the November 5 incident and asserted that protected status and protected activities played no role in the termination decision. Initial Response w_ attachments…

Now we have something an AI can legitimately help examine:

Contemporaneous record versus subsequent litigation narrative.

Not who is evil.

Not who is lying.

Not who wins.

Just: What does each source say, when was it created, and where do the propositions converge or diverge?

Wisconsin’s public-hearing architecture matters too

This work also concerns a governmental administrative process, not merely private workplace storytelling.

Wisconsin DWD says that when an ERD matter proceeds to hearing, the hearing is generally open to the public and news media. Wisconsin Workforce Development ERD’s online-hearing page specifically provides a contact route for media access. Wisconsin Workforce Development Parties also exchange proposed hearing exhibits and file them with the Division under ERD’s hearing procedures. Wisconsin Workforce Development

Wisconsin Supreme Court Rule Chapter 61 separately governs electronic-media and photography coverage of judicial proceedings. It is not the rule governing ERD proceedings, but it forms part of the broader Wisconsin public-proceeding/media landscape informing this journalism experiment. Wisconsin Courts

None of that means every document in an employment dispute is automatically publishable. Medical records, protected information, mediation communications, personal identifiers and material subject to specific restrictions require separate screening.

That’s another job for the firewall.

Down Range Denouement

After scanning Welsh’s criticism, Mata, the administrative record and the methodology I have been developing with OpenAI, I don’t think the useful question is whether AI deserves to be trusted.

Machines don’t get that privilege.

Neither does my memory.

Neither does an attorney’s argument.

Each proposition gets tested against its source.

If Welsh says my work demonstrates blind reliance on artificial intelligence, that criticism belongs in the documentary because it challenges the integrity of the experiment.

Then the experiment gets to answer—not with another accusation, but with receipts.

Source. Date. Author. Proposition. Corroboration. Contradiction. Correction. Human review.

That is the emerging rule of the State v. Burt documentary:

Don’t ask the audience to trust the machine. Give them enough provenance to check its work.

Editor’s note: This article reports and analyzes disputed administrative proceedings. References to arguments by attorneys, employers, complainants and other participants identify their respective positions and should not be understood as independent findings of misconduct or liability. JEDVIDENCE and BOB COBB are reporting/analytical methodologies, not adjudicative authorities.