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.

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.

Burt v. State: A Record-Based Town Hall Brief

Good afternoon. I’m Bradley Burt of Outpost 422.

“Burt v. State” is the working title of this public brief. It is not a court ruling, and this presentation does not ask the public to decide liability. Its purpose is to explain how I am organizing the administrative record, identifying unanswered questions, and preserving the documents connected to my concerns.

I prepared a Notice of Injury and Claim under Wisconsin Statute section 893.82. The notice describes concerns involving the handling of administrative-review requests, submitted evidence, disputed facts, and separate theories raised through the Department of Workforce Development’s Equal Rights Division process.

The notice does not claim that an adverse decision, an investigative error, a denied reassignment request, or a disagreement with an agency automatically proves unlawful conduct, bad faith, damages, or constitutional liability. Those questions depend on the administrative record and, if necessary, later legal review.

Outpost 422 uses a source-controlled method called JEDVIDENCE to keep the record organized. OpenAI may assist me with accessibility, chronology, terminology, research planning, and citation review. But the source remains the authority. AI does not make factual findings, decide credibility, or replace an attorney, agency, or court.

For each item, I ask: What is the source? What is the date? What does the document actually say? And what remains unresolved? This helps separate verified records from my own recollections, disputed statements, missing information, and analysis.

The administrative-law materials also matter here. Agencies can issue rules, make decisions, conduct investigations, and create records—but those different actions have different legal roles. A policy, an investigator’s communication, an administrative decision, and a court judgment should not be treated as the same thing.

My elemental writing framework helps me connect lived experience with documents, chronology, and public context. It is a creative and research method, not a diagnosis of another person and not proof of wrongdoing. The goal is clarity: preserve what happened, identify what the record supports, and acknowledge what the record does not yet establish.

My request is straightforward: preserve the relevant records, review the evidence carefully, correct errors where the record warrants correction, and allow the appropriate administrative and legal processes to do their work.

At Outpost 422, the goal is not to manufacture a conclusion. The goal is to keep the story—and the record—straight. Thank you.

PUBLIC NOTICE | Burt v. State

JEDVIDENCE™ Enters Wisconsin’s Notice-of-Claim Stage

OUTPOST 422® | Journalism eDiscovery™
September 27, 2026

The next stage of Burt v. State: The Wisconsin DVR Documentary is not a declaration of liability.

It is notice.

After months of documenting Wisconsin Equal Rights Division proceedings, administrative appeals, investigative records, public-record responses, and agency correspondence, I am preparing a formal notice under Wis. Stat. § 893.82 concerning documented administrative actions involving the Wisconsin Department of Workforce Development’s Equal Rights Division.

The purpose is straightforward: preserve the record, preserve potential legal rights, and allow the administrative process to continue.

No court has determined that ERD Administrator Colin R. Stroud, Investigator Matthew Meissner, DWD, or another Wisconsin official violated my constitutional or statutory rights.

JEDVIDENCE™ will not manufacture that conclusion.

It will document what happened.

The record begins before the next decision

On June 13, 2026, I submitted a written request to ERD administration seeking administrative review, consideration of investigator reassignment, preservation of records, and a written agency response.

Importantly, the request expressly stated that it was not a personal attack against an investigator. I explained that my concerns involved the handling of evidence and confidence in the investigative process, while reserving available state and federal remedies. Pasted text

That distinction remains important.

Disagreement with an administrative decision does not, by itself, establish misconduct. An investigative mistake does not automatically establish a constitutional violation. And a procedural disagreement does not automatically create civil liability.

The question for JEDVIDENCE is narrower:

What does the documentary record show?

June 17: ERD administration responds

On June 17, ERD Administrator Colin R. Stroud responded directly.

Stroud stated that ERD investigators are neutral factfinders who base their decisions upon information presented by the parties. He further explained that when a complainant objects to the handling or outcome of an investigation, the complainant can appeal to seek redress for errors that may have occurred during the investigative process. He also stated that ERD preserves case records according to the applicable records-retention schedule. Pasted text

That correspondence has become an important documentary marker.

Why?

Because it identifies ERD’s stated corrective mechanism:

If investigative error occurs, appeal provides an avenue for redress.

That proposition can now be tested against what actually happens in the administrative record.

I preserved the specific objection

I subsequently responded that my concern wasn’t simply that an investigator had reached a result I disliked.

I identified concerns involving evidentiary development, record preservation, corroboration, documentary evidence, witness statements, chronology evidence and potentially available objective evidence.

I specifically requested that those matters receive consideration before a final determination was issued. Pasted text

On June 19, Stroud confirmed that the correspondence would be added to the case file. Pasted text

That sequence matters journalistically because it creates a timestamped record before the next administrative outcome exists.

I am not reconstructing an objection after receiving another unfavorable decision.

The objection was documented beforehand.

July 2: ERD defines the administrative boundary

The record developed further on July 2.

Stroud instructed me not to send case material to him for inclusion in individual records. Instead, he directed communications concerning specific cases to the assigned investigator or administrative law judge and stated that, as Division Administrator, he was not directly involved in processing or adjudicating individual cases. Pasted text

That statement is also being preserved exactly for what it says.

JEDVIDENCE will not transform it into something it doesn’t say.

Instead, it establishes another point in the administrative chronology:

Complaint → supervisory notice → agency response → preservation of objection → direction back into the investigative/adjudicative process.

Now the documentary project follows what happens next.

Why I am preparing notice to the Attorney General

Wisconsin law contains a notice procedure for certain civil claims involving state officers, employees or agents.

Wis. Stat. § 893.82 generally requires qualifying claimants to provide a sworn notice describing the circumstances of the injury-causing event within the statutory period.

Preparing that notice does not mean a lawsuit has been filed.

It does not mean liability has been established.

And it does not mean the administrative proceedings have ended.

The notice is being prepared to preserve potential rights while the underlying administrative record continues to develop.

For purposes of protecting against a potential deadline dispute, I am presently treating June 17, 2026 as the conservative working date for the Stroud-related notice analysis.

The notice will identify documented events and preserve potential claims without representing unresolved allegations as established facts.

March 5 remains evidence—not a manufactured new deadline

There is another important distinction.

The March 5, 2026 Initial Determination involving Investigator Matthew Meissner remains part of the documentary history.

My pending JEDVIDENCE submission alleges that the determination did not separately adjudicate every theory I contend was properly presented. The filing asks ERD for corrective proceedings, including complete investigation or, alternatively, a de novo probable-cause hearing. RE_JEDVIDENCE_Motion_Brief_and_… RE_JEDVIDENCE_Motion_Brief_and_…

But Journalism eDiscovery will not artificially move the March 5 date forward.

Instead:

March 5 becomes supporting evidence.

Any subsequent Initial Determination or ALJ decision will be examined as its own event.

That distinction is essential to credible evidence reporting.

The STEMoir now has a control variable

ERD’s own investigative instructions provide an unusually useful benchmark.

They tell investigators to identify the bases and discriminatory actions alleged, determine what additional information is necessary and make sure to address all alleged bases and issues. How to do investigation (1)

Those instructions also direct investigators preparing determinations to address the bases and adverse actions and explain material factual disputes and their evidentiary support. The instructions state that unresolved material factual disputes need to proceed to a probable-cause hearing. How to do investigation (1)

That gives the STEMoir a measurable structure:

Written ERD standard → evidence submitted → administrative action → determination → appeal → corrective opportunity → resulting record.

The agency’s written standard becomes the control.

The actual administrative record becomes the observed variable.

JEDVIDENCE performs the comparison.

The adjudicator decides what that comparison legally means.

What happens next

The next steps will be documented rather than predicted.

I will complete the Wisconsin notice-of-claim process concerning the presently identified Stroud events while continuing to participate in the existing ERD proceedings.

I will preserve the certified filing record.

I will continue pursuing the pending administrative remedies.

When another Initial Determination is issued, JEDVIDENCE will compare that determination against the allegations actually presented, the evidence actually submitted, ERD’s documented investigative procedures and the objections already preserved in the record.

When an Administrative Law Judge rules, that decision will be added to the chronology too.

The result may support my allegations.

It may contradict them.

It may resolve some questions while creating others.

That uncertainty isn’t a weakness in Journalism eDiscovery™.

It is the reason for doing it.

Burt v. State will not begin with the conclusion and work backward toward supporting evidence.

It will move forward through the record.

Notice → preservation → investigation → determination → appeal → adjudication → review.

And wherever that record ultimately leads, the same rule applies:

THE RECORD DOES NOT NEED A SIDE. IT NEEDS TO BE READ.

Outpost 422® | Journalism eDiscovery™ | JEDVIDENCE™
Primary sources. Human submission. AI-assisted evidence framing. Transparent chronology. Human adjudication.

Outpost 422® | JEDVIDENCE™

Burt v. State: Before the Courthouse Comes the Record

MADISON, Wis. — Sept. 27, 2026 — Burt v. State: The Wisconsin DVR Documentary is moving into its next reporting phase. But the next chapter is not a lawsuit.

It is procedure.

On September 11, I sent Wisconsin Attorney General Josh Kaul a Notice of Potential Federal Constitutional Claim, Request for Administrative Review, and Preservation of Records concerning three of my Wisconsin Equal Rights Division matters.

The notice identified proceedings involving three separately assigned ERD investigators and raised a narrow question that Journalism eDiscovery™ will continue examining: when a complainant presents multiple claims, evidence, and disputed facts, does the administrative record demonstrate that each theory was identified, associated with the relevant evidence, evaluated, and ultimately explained?

I did not ask the Attorney General to assume that an investigator engaged in misconduct simply because I disagreed with an administrative determination.

That distinction matters.

My September 11 notice expressly recognized that an erroneous decision, an incomplete investigation, or disagreement over evidence does not automatically amount to a constitutional violation. Instead, I preserved potential questions involving the Fourteenth Amendment and 42 U.S.C. § 1983 while asking that the underlying government record be preserved.

Now another procedural question has emerged:

What must happen under Wisconsin law before certain claims against state officers, employees, or agents can ever reach a courtroom?

The September 11 notice is part of the record—not the end of the analysis

Journalism eDiscovery™, or JEDVIDENCE™, requires me to resist a tempting shortcut: calling one document something that the document itself does not establish.

My September 11 correspondence documents notice of a potential federal constitutional theory, a request for administrative review, and a preservation request. I will preserve it exactly that way.

I am not presently representing that the email independently satisfied every requirement of Wisconsin’s statutory notice-of-claim procedure.

That question requires separate legal research.

This is precisely what JEDVIDENCE is supposed to do. Human beings supply the source material. AI assists in organizing the chronology, testing assertions against documents, identifying possible causal relationships and contradictions, and flagging unanswered questions. AI-generated observations are not transformed into evidence merely because a computer produced them.

That same limitation appears in my current Frank Productions ERD submission. My filing defines JEDVIDENCE as a transparent organizational method that separates identified source materials from allegations, advocacy, administrative findings, recollection, and AI-assisted analysis. RE_JEDVIDENCE_Motion_Brief_and_…

The human submits. The AI frames and tests. The record supplies the evidence. The adjudicator decides.

JEDVIDENCE enters the Wisconsin notice-of-claim phase

One statute now requiring careful examination is Wis. Stat. § 893.82, governing certain claims against Wisconsin state officers, employees, and agents.

This creates an important documentary distinction.

My September 11 submission can be preserved as the federal constitutional/preservation notice in the chronology.

The next phase is determining separately whether § 893.82 applies to any contemplated Wisconsin claim, which events could trigger its requirements, which state actors would fall within it, what deadlines apply, and what constitutes proper statutory notice and service.

The documentary will not assume those answers.

It will document them.

That means identifying the alleged event first, then the potential defendant, the potential cause of action, the requested remedy, the applicable notice requirement, the administrative-review pathway, and ultimately the proper court—if litigation ever becomes appropriate.

Meanwhile, the ERD process continues

There is another reason not to confuse these different procedural tracks: my administrative proceedings have not simply disappeared because constitutional questions have been preserved.

In Burt v. Frank Productions LLC, ERD Case No. CR202500211, my current JEDVIDENCE motion asks that the existing abeyance be modified or lifted sufficiently to permit corrective proceedings. I request either a complete investigation by a different investigator or, alternatively, a de novo probable-cause hearing where disputed evidence can be developed on a formal record. RE_JEDVIDENCE_Motion_Brief_and_…

The filing also asks ERD to identify clearly which claims and theories are actually within the case so that the administrative record will be unambiguous if later judicial review becomes necessary. RE_JEDVIDENCE_Motion_Brief_and_…

That is significant to the documentary because JEDVIDENCE isn’t supposed to replace administrative adjudication.

It is supposed to make the chronology readable.

The DVR record is another missing piece

On September 26, I also requested my complete Wisconsin Division of Vocational Rehabilitation consumer record.

That request seeks the available chronology of my DVR participation—including case documentation, employment-related records, communications, accommodation materials, assessments, referrals, service records, and associated correspondence. RE_JEDVIDENCE_Motion_Brief_and_…

I do not yet know what the complete DVR production will establish.

Neither does AI.

That is exactly why obtaining the records comes before drawing conclusions from them.

A September 23 DWD response transmitted through Representative Andrew Hysell’s office stated that ERD investigators consider information provided by the parties. My JEDVIDENCE filing therefore asks for an opportunity to supplement the administrative record with relevant DVR material after it is produced. RE_JEDVIDENCE_Motion_Brief_and_…

That sequence matters:

Request → production → authentication → comparison → analysis → submission → adjudication.

Not:

Suspicion → conclusion.

Journalism eDiscovery is becoming the documentary

This is where Burt v. State and JEDVIDENCE converge.

The documentary will follow documents through the institutions that create, receive, preserve, investigate, challenge, and adjudicate them.

Some records may support my allegations.

Some may support an opposing account.

Some may expose gaps.

Some may resolve questions that presently appear significant.

And some may produce entirely new questions.

That uncertainty isn’t a weakness in Journalism eDiscovery. It is a requirement of the method.

My September 25 transparency notice already states that the methodology distinguishes source documents from allegations, opposing accounts, administrative findings, legal arguments, recollections, and AI-assisted analysis. It also says publication decisions remain separate from evidentiary submissions. RE_JEDVIDENCE_Motion_Brief_and_…

That separation will remain central to Outpost 422 reporting.

What happens next

The immediate JEDVIDENCE assignment is therefore not “sue Wisconsin.”

It is to build the procedural map before deciding whether there is eventually a road to court at all.

I will preserve the September 11 Attorney General correspondence as its own historical artifact. I will examine Wisconsin’s notice-of-claim requirements separately. I will continue developing the ERD administrative records. I will obtain and examine my DVR consumer record. And where evidence conflicts, JEDVIDENCE will identify the conflict rather than decide which version wins.

Any eventual judge or administrative decision-maker gets that job.

That is also why the central line of Burt v. State: The Wisconsin DVR Documentary remains simple:

THE RECORD DOES NOT NEED A SIDE.
IT NEEDS TO BE READ.

Outpost 422® | Journalism eDiscovery™ | JEDVIDENCE™
Primary sources. Human submission. AI-assisted evidence framing. Transparent chronology. Human adjudication.

Outpost 422 | Journalism eDiscovery™

When the CEO Has a Law Degree: JEDVIDENCE Examines the Corporate Decision-Making Record

MADISON, Wis. — Journalism eDiscovery™ is opening a new examination into an important distinction in employment reporting: what happens when a corporate employment decision involves executives with legal education, outside counsel, human resources personnel, and an internal investigative process?

The question is not whether having a law degree makes a corporate decision right or wrong. It does not. Nor does legal education establish that an executive was acting as an attorney when making a business decision.

The Journalism eDiscovery approach asks a narrower question:

What does the contemporaneous record show about who knew what, who advised whom, what evidence was considered, and how the ultimate employment decision was reached?

The Frank Productions dataset

In my pending employment-discrimination reporting involving Frank Productions, CEO Joel Plant occupies an unusual position in the documentary chronology: he was a corporate decision-maker, but he also has a legal-education background associated with the University of Wisconsin Law School.

That fact matters as context, not as proof of wrongdoing.

Wisconsin’s diploma privilege provides a pathway through which eligible UW Law School and Marquette University Law School graduates can satisfy Wisconsin’s legal-competence requirement for admission without taking the bar examination, provided the other requirements for admission are satisfied. A law degree alone therefore should not be confused with proof that a particular person obtained admission through diploma privilege—or that the person was acting as legal counsel during a particular corporate event. Wisconsin Court System

That distinction is precisely the kind of distinction JEDVIDENCE is designed to preserve.

The next source: corporate ethics

My next research dataset will examine a corporate in-house counsel ethics manual.

Rather than beginning with the conclusion that somebody acted improperly, Journalism eDiscovery will extract the manual’s standards first. Those standards can then become variables for examining the documentary record.

The questions include whether the materials address investigative scope, evidence preservation, conflicting accounts, witness interviews, conflicts of interest, confidentiality, retaliation safeguards, documentation, corporate decision-making and the respective roles of executives and attorneys.

Then comes the See-Saw.

Manual says → Record shows.

Where the two converge, JEDVIDENCE records convergence. Where they differ, it records the difference. Where the available evidence cannot answer the question, the result is unresolved.

Diploma privilege is not the story

This examination should not become an argument about Wisconsin’s diploma privilege.

Wisconsin continues to recognize diploma privilege for eligible graduates of UW and Marquette law schools. Wisconsin Court System The Wisconsin court system also maintains attorney-admission information by type of admission, distinguishing diploma privilege, examination and proof-of-practice admissions. Wisconsin Court System

The relevant reporting question is therefore not:

“Did legal education authorize the corporate action?”

It is:

“What role, if any, did legal training, legal counsel and corporate investigative practices actually play in the documented decision?”

Those are very different propositions.

Three datasets, one experiment

September 25, 2026, now marks a methodological checkpoint for Outpost 422.

I have requested my complete Wisconsin DVR consumer record, rather than selecting only records concerning employers or disputes. I am separately examining how ERD investigators manage claims. The corporate-ethics material provides a third perspective.

Together, those sources create the next Journalism eDiscovery triangulation:

RECORD → REGULATOR → CORPORATION

The employment cases will eventually be examined against all three.

No conclusion gets written in advance.

No allegation becomes a fact because it appears in a brief.

No corporate explanation becomes a fact merely because management wrote it.

And no AI observation becomes evidence simply because a machine identified a pattern.

The source remains the evidence. JEDVIDENCE examines the source. The human verifies the result.

That is the experiment now underway at Outpost 422®.

#JournalismeDiscovery #JEDVIDENCE #Outpost422 #CorporateEthics #LegalResearch #ConvergentMedia #HumanAI #DocumentaryJournalism #EmploymentReporting

OpenAI Timestamp Scan: From Outpost 422 to the 2027 BOB COBB Evidence-Preparation App

September 25, 2026 — Outpost 422

There are moments in a long-running journalism project when the archive stops looking like a collection of old stories and begins looking like a blueprint.

This is one of them.

An OpenAI-assisted review of the Outpost 422 timeline—from the original Convergent Media Hypothesis Method®, through the BOB COBB identity, Oracle-based information collection, Blogcasting, academic research, and today’s Journalism eDiscovery™/JEDVIDENCE™ workflow—reveals a consistent idea: collect the record first, organize it, compare competing accounts, and then tell the story.

In 2027, Bob Cobb Freelance Ink LLC intends to begin translating that educational journalism experiment into the Outpost 422 app, an evidence-preparation environment for subscribers.

What BOB COBB is—and what it is not

The proposed application is an educational, journalism and document-organization product. Its purpose is to help users learn how to organize workplace and administrative records, construct chronologies, identify potentially significant inconsistencies, separate evidence from characterization, prepare questions for further investigation, and turn complicated documentary records into understandable convergent-media narratives.

It is not a law firm, attorney, government investigative agency, court, or adjudicator. Its output will not determine that discrimination, retaliation, fraud, misconduct, illegality, or any other violation occurred. AI-generated flags are research leads requiring human verification—not findings of liability.

Likewise, use of a trademark or registered trademark designation identifies branding; it does not itself transform a publication into legal advice, establish a privilege, or determine the legal status of the underlying material.

That boundary is fundamental to JEDVIDENCE:

DOCUMENT → SOURCE → TIMELINE → AI FLAG → CORROBORATION → HUMAN REVIEW → PUBLICATION

The artificial intelligence assists with the middle of that chain. Humans remain responsible for the beginning and the end.

Three case studies will help build the laboratory

The initial educational development will draw heavily from records surrounding my disputes involving Marcus Theatres, Camp Createability, and Frank Productions.

These organizations will not be labeled guilty by an algorithm. They instead provide unusually extensive real-world documentary records from which the methodology can demonstrate how a subscriber might examine questions such as:

• What did each party say, and when?
• Does a later explanation match the contemporaneous record?
• Which propositions are documented facts, disputed allegations, attributed statements, or AI-generated inferences?
• Are documents missing from an otherwise continuous chronology?
• Did policies and recorded actions correspond?
• Which facts require independent corroboration?
• What evidence supports—and what evidence cuts against—the reporter’s working hypothesis?

That last question is especially important. A credible evidence scanner must be capable of identifying evidence unfavorable to the person submitting the documents. BOB COBB cannot be a machine for confirming what its user already believes.

The resulting publications will therefore describe these disputes as case studies and identify disputed propositions as disputed.

Why employment-law publishing provides an interesting model

There is an established tradition of lawyers and employment-law organizations teaching through real cases.

Wisconsin employment attorney Robert E. Gregg and the Boardman Clark Labor & Employment Law Group provide a useful example of the publishing format, not an endorsement of Outpost 422 or its conclusions. Boardman Clark publishes a recurring Employment Law Update discussing developments and decided cases for an employment-law audience. Its September 2026 archive, for example, contains discussions involving administrative discrimination proceedings, retaliation, accommodations and other workplace-law developments. Boardman Clark

Boardman Clark Employment Law Update

Gregg has also used individual cases to illustrate broader workplace lessons. A 2018 article, for example, assembled cases involving workplace comments and explained what employers could learn from them. Significantly, Boardman Clark expressly labels that material general information rather than individualized legal advice. Boardman Clark

That educational distinction is one Outpost 422 can adopt while maintaining a fundamentally different journalistic perspective.

Boardman Clark describes its employment practice as representing and advising employers in areas including discrimination, accommodations, investigations, audits, discipline, termination and employment litigation. Boardman Clark Outpost 422’s proposed project comes from the documentary-journalism side: What can the underlying record teach a reader about evidence preparation and source verification?

The subscriber does not purchase a verdict

This may become the most important rule governing the 2027 application.

A subscriber should never be able to purchase a predetermined conclusion.

Uploading 200 pages and asking BOB COBB to “prove retaliation” should not produce 200 pages supporting retaliation. The scanner should instead identify what supports that hypothesis, what contradicts it, what remains unknown, what requires another source, and what cannot responsibly be concluded from the supplied material.

That is the difference between advocacy automation and evidence preparation.

BOB COBB is being designed for the latter.

Subscribers could ultimately use structured workspaces for chronology construction, source inventories, exhibit preparation, contradiction flags, quotation verification, claim/evidence matrices, provenance tracking, correction logs and publication preparation.

The application should repeatedly remind users that those products are research and educational work product—not judicial findings or substitutes for professional legal advice.

From “black hat” to a testable flag

Outpost 422 has historically used the language of “black hat” business practices. JEDVIDENCE gives us a better way to operationalize that concept.

Rather than instructing artificial intelligence to decide that an organization is unethical, the application can flag observable documentary conditions: changing explanations, contradictory dates, policy/document conflicts, unexplained evidentiary gaps, inconsistent descriptions of the same event, unsupported factual assertions, or differences between contemporaneous and later accounts.

Those observations can be tested.

Motive generally cannot be read from a document merely because two documents conflict.

That distinction protects both the subject of the reporting and the integrity of the reporter.

The sheepdog gets a database

BOB COBB began as a journalism identity.

Then it became an archive.

Then came cloud collection, Blogcasting, convergent-media experimentation, academic research, data-trail analysis and eventually Journalism eDiscovery.

The 2027 application is the next proposed iteration: the sheepdog gets a structured evidence environment.

Its job will not be to bark “guilty.”

Its job will be to point toward the part of the record that deserves another look.

And every time artificial intelligence gets something wrong, the correction belongs in the methodological history too. The AI error, source verification, human correction and reason for that correction become part of the provenance trail.

That is how an experimental journalism application earns credibility.

The 2027 promise

Outpost 422 will continue doing what its archive shows it has been attempting for years: connecting journalism, education, documentary evidence and convergent media.

Only now we have considerably better tools.

Archive the source.
Scan the record.
Flag the contradiction.
Test the hypothesis.
Show the contrary evidence.
Verify with a human.
Correct the machine.
Publish what the evidence can actually support.

That is the proposed Outpost 422 / BOB COBB subscriber model for 2027.

And the principle underneath it remains remarkably simple:

We flag the question. The evidence answers it.

Publisher’s note: References to pending or disputed employment matters describe allegations, documentary questions and educational case studies unless an identified tribunal or authoritative source has established the proposition stated. BOB COBB/JEDVIDENCE materials are for journalism, research and educational evidence preparation and are not legal advice.

Op-Exposé | The TDIU Paradox

A Disabled Veteran Tried to Work. Then VA Asked Whether Working Proved He Could Work.

By Bradley J. Burt | Outpost 422 | JEDVIDENCE

There is a paradox buried inside the employment record of a disabled veteran trying to remain in the workforce. Work too little, and an employer may question availability.

Work enough, and the Department of Veterans Affairs may question unemployability.

Between those two poles sits my experience with Wisconsin’s Division of Vocational Rehabilitation, Marcus Theatres, Frank Productions LLC, and, today, an employer with whom I have developed a substantially different working relationship.

This Op-Exposé examines that journey through Journalism eDiscovery—JEDVIDENCE—not to declare the outcome of pending administrative disputes, but to preserve and compare their documentary records.

The central question is deceptively simple:

What does successful employment look like for a disabled veteran who can work, but cannot necessarily work under the same conditions, duration or availability expected of every other worker?

I. THE ORDINARY WORLD — A Veteran Trying to Work

My story did not begin with litigation. The story about what it’s like and where I am now began with Wisconsin DVR and an attempt to return successfully to employment.

That distinction matters.

The documentary record predating my present disputes contains repeated references to limitations on how long and under what conditions I could work. Those limitations existed before the later ERD theories, before the Frank Productions termination, and before VA questioned my continued eligibility for Total Disability based on Individual Unemployability.

My employment experiment therefore wasn’t simply about finding a paycheck. It was about determining whether employment and disability could coexist.

And not every employer has produced the same result.

My current employer knows about my limitations. From my perspective, we have established a mutually beneficial, good-faith relationship without recreating the medical-questionnaire conflicts at the center of my earlier disputes. Management has even sought my perspective when considering disabled-veteran employment.

That experience provides an important control variable for this investigation. The question isn’t whether employers and disabled veterans can work together.

I know from personal experience that they can. The question is why my experiences with Marcus Theatres and Frank Productions developed so differently.

II. THE CALL TO ADVENTURE — “FIVE-HOUR SHIFTS ARE MY LIMIT”

The documentary trail begins before Frank Productions.

During my employment with Marcus Palace Cinema, I documented that disability affected my availability and the length of shifts I could sustain.

That eventually became part of an accommodation dispute involving medical verification and what information an employer could request.

I subsequently brought an Equal Rights Division complaint. Marcus disputes my allegations. That procedural posture matters: an administrative complaint is not an adjudicated finding of discrimination.

But the Marcus record became significant for another reason. It created a contemporaneous benchmark. Long before VA questioned whether my earnings demonstrated employability, I was documenting the opposite problem:

I wanted to work, but I was telling employers that there were limits to how I could work.

That distinction would become enormously important later.

III. CROSSING THE THRESHOLD — FRANK PRODUCTIONS

Then came Frank Productions.

I entered the live-events workplace through a DVR-supported employment journey and encountered another version of the same underlying variable:

availability.

My December 17, 2023 DVR-related report documented my concern about an availability-driven scheduling system and my difficulty competing within it as a disabled veteran.

That record matters because of when it was created. It wasn’t written after my termination. It wasn’t drafted for an ERD hearing. It wasn’t written after VA questioned my TDIU. It documented the employment problem while I was still attempting to make the job work.

That is one of the foundational principles of JEDVIDENCE:

Chronology tests narrative.

IV. TESTS, ALLIES AND ADVERSARIES — THE IDPQ

By September 2024, the employment relationship entered another phase. Frank Productions sent me an Interactive Process Questionnaire as part of its accommodation process.

The document sought medical information concerning impairment, symptoms, treatment, prognosis, activities affected by the condition, limitations and accommodation. It also contained something particularly significant to my subsequent reporting.

The questionnaire asked the health-care provider whether there was a “significant risk of substantial harm” if I performed my position and, if so, whether accommodation could reduce or eliminate that risk.

My dispute concerns how that process was handled and how much medical information was necessary—not the general proposition that employers may engage in an interactive accommodation process.

Frank Productions subsequently maintained that it accepted the documentation supplied and implemented my requested accommodations.

That position belongs in this story.

So does mine.

Posture check: the existence of an IDPQ doesn’t establish discrimination. My contention is that the scope, administration and subsequent treatment of disability information must be examined within the complete chronology.

V. APPROACH TO THE INMOST CAVE — FROM ACCOMMODATION TO “THREAT”

That chronology eventually reaches November 2024.

Frank Productions terminated my employment on November 8 following a disputed series of workplace events and communications.

The company attributed threatening conduct to me. I deny threatening violence. I confided in a shift lead as instructed when a patron entered the venue who threatened to kill me in 2021.

That factual conflict cannot responsibly be solved by simply repeating either side louder.

My current ERD submissions instead ask a series of evidentiary questions.

What did the witnesses actually hear? Who was present? What security training had employees received? What did surveillance show?

What radio traffic existed? What evidence did the decisionmakers examine? What did the relevant decisionmakers already know about my disabilities and accommodation communications?

And what happened to potentially contrary evidence?

That is DemonSpeak in its simplest form:

Claim → counterclaim → contemporaneous document → missing evidence → corroboration → factfinder.

HR is the demon from which the management speaks through and HR speaks DemonSpeak through reports, emails, statements presented after the fact like presented by Attorney Robert Gregg’s Initial Response w/attachments on behalf of FPC.

The purpose isn’t to have AI declare which witness is telling the truth. It is to identify what evidence could answer the question.

VI. THE ORDEAL — TERMINATION

The November 8 termination changed the trajectory of the story. Frank Productions’ characterization became part of my subsequent administrative record.

I challenged it through Wisconsin’s employment-discrimination process and incorporated my DVR history, accommodation communications and employment chronology into my filings.

My position is that the accommodation and disability chronology provides necessary context for evaluating the termination. Frank Productions disputes that interpretation.

The litigation posture therefore remains important:

allegation is not finding; chronology is not causation; temporal proximity is not automatically retaliation.

But chronology tells us what to investigate next.

And another institution eventually asked a very different question about the same period of employment.

VII. THE ABYSS — OCTOBER 31, 2025

On October 31, 2025, the Department of Veterans Affairs issued the document that changes the scale of this story.

VA had received information from the Social Security Administration indicating that my wages during calendar year 2024 exceeded the applicable poverty threshold.

VA therefore opened a review of my continued eligibility for Individual Unemployability. The proposal was consequential.

VA proposed discontinuing IU and reducing my compensation to my underlying 90-percent schedular evaluation.

But the same document contains an important qualification.

VA explained that earnings did not automatically exclude me from IU and that it would review the facts and circumstances before making its decision.

That is the heart of the paradox.

I had spent years trying to demonstrate to employers that I could work within limitations.

Now I had to explain to VA why having worked didn’t necessarily establish that I possessed the ability to maintain substantially gainful employment.

My subsequent VA submission expressly incorporated my employment experiences into that explanation. I identified the November 8, 2024 FPC termination as the date from which I contended that my ability to obtain gainful employment had fundamentally deteriorated.

The employment litigation had crossed into the veterans-benefits record.

VIII. THE REVELATION — THE FIVE GENERALS OF HELL

JEDVIDENCE now permits the chronology to be reduced to five variables.

General One: Capacity.
What work could I actually sustain?

General Two: Accommodation.
What did employers know about those limitations, and what accommodations or documentation did they request?

General Three: Interpretation.
How did disability-related, security-related and workplace communications acquire their eventual meanings?

General Four: Adverse Action.
What evidence actually supported the employment decisions that followed?

General Five: Aftermath.
What happened when those employment records encountered ERD, DVR and ultimately VA’s TDIU system?

None individually proves discrimination.

Together they create an evidence landscape.

And that landscape produces what I call Quadratic Logic:

Disability limitation + employment effort + accommodation/documentation conflict + adverse employment action = an administrative record whose meaning changes depending upon which institution is examining it.

An employer may ask whether the employee can perform the job.

ERD may ask whether disability played an unlawful role in an employment action.

DVR evaluates employment and rehabilitation.

VA asks whether service-connected disability permits substantially gainful employment.

Those questions overlap.

They are not identical.

IX. THE ROAD BACK — THE ERD RECORD

The next phase became preservation.

I objected to assigning overlapping Frank Productions matters to the same ERD investigator who had already reached conclusions in a related matter.

Importantly, my written reassignment request expressly stated that I was not accusing the investigator of misconduct, bad faith or personal animus.

I raised an appearance-of-impartiality concern and requested a fresh review.

ERD administration disagreed.

Deputy Administrator Matthew White subsequently explained the Division’s procedural position: ERD does not conduct an administrative review of a no-probable-cause determination in the manner I requested. The prescribed challenge is the appeal process.

White emphasized something enormously important for my evidence project:

“Because the appeal hearing is de novo, it does not proceed on the administrative record.”

He further explained that I would bear the burden of presenting the evidence necessary to demonstrate probable cause.

I acknowledged that position while preserving my disagreement over reassignment.

That exchange helps explain why preservation has become central to JEDVIDENCE.

If the hearing begins anew, the complainant needs the evidence.

X. THE RESURRECTION — A DIFFERENT EMPLOYMENT EXPERIMENT

And that brings the story to 2026.

Something unexpected happened.

I went back to work.

My current employment relationship has not reproduced the same accommodation conflict.

I have communicated my limitations.

The employer has worked with me.

From my perspective, neither side is pretending that disability doesn’t exist. We instead discuss what I can reasonably contribute.

Management has even sought my perspective concerning disabled-veteran employment.

That doesn’t prove Marcus or Frank Productions discriminated against me.

But journalistically, it provides something extremely valuable:

a comparison.

Same veteran.

Same underlying service-connected disability landscape.

Different employer.

Different interaction.

Different outcome.

That is precisely the kind of variable JEDVIDENCE is designed to examine.

XI. RETURN WITH THE ELIXIR — THE PRECEDENT I AM PURSUING

My objective is larger than winning an argument on WordPress.

I want the administrative record preserved.

I want the documentary evidence tested.

I want the appropriate factfinder—not social media, not an employer, not me, and not an AI model—to determine the disputed legal and factual questions.

And I want the resulting record to help answer a problem that extends beyond my individual cases:

How should employers engage disabled veterans who want to work, possess valuable skills, but need employment structured around genuine service-connected limitations?

The answer cannot simply be:

Don’t work.

Nor should it be:

Work exactly like everyone else or leave.

My present employment experience suggests there is considerable territory between those extremes.

That territory is where good-faith communication lives.

The JEDVIDENCE Posture Check

This investigation distinguishes between documents, firsthand observations, attributed statements, allegations, competing explanations and adjudicated findings.

Marcus Theatres and Frank Productions dispute material aspects of my allegations. My ERD complaints and filings do not themselves establish discrimination, retaliation, pretext or unlawful medical inquiry. Those questions remain for the appropriate administrative and judicial processes.

Likewise, the October 31, 2025 VA letter does not establish that either employer caused VA’s proposed action.

What it establishes is narrower—and significant.

VA received wage information concerning 2024, questioned whether those earnings demonstrated sustained gainful employment, proposed discontinuing IU, and invited evidence explaining the circumstances surrounding those wages.

My employment history became part of that answer.

That is why preserving the record matters.

The Monomyth Comes Full Circle

I began this journey trying to work.

After Marcus, Frank Productions, DVR, ERD and a proposed VA TDIU reduction, I am still trying to work.

But now there is another data point.

An employer and disabled veteran can communicate about limitations without automatically turning that conversation into an adversarial medical-documentation battle.

My present employment experience doesn’t decide my previous cases.

It gives us something perhaps more valuable for investigative journalism:

a control.

And that returns this story to where it started.

A disabled veteran wants to work.

The question isn’t whether he should be allowed to try.

The question for the evidence is what happened when he did.

OUTPOST 422 | JEDVIDENCE
Primary documents. Chronology. Competing accounts. Posture checks. Let the record speak before drawing the conclusion.

Suggested SEO headline:
The TDIU Paradox: How My DVR Employment Journey From Marcus Theatres and Frank Productions Reached a VA Unemployability Review

Suggested social headline:
I Tried to Work With TDIU. Then VA Asked Whether Working Proved I Could Work.

For the accompanying thumbnail, the strongest pairing remains “FPC → TDIU AT RISK? | THE DOCUMENT TRAIL.” The question mark is important: it communicates the investigation without announcing a causal conclusion the record has not yet established.

DemonSpeak DVR Scan: When the Accommodation Record Starts Talking Back

Outpost 422 | Journalism eDiscovery™ | First-person reporting, document comparison, and bounded inference

DemonSpeak is not a verdict. It is the examination flag: the moment a workplace narrative becomes loud enough that the underlying record must be made to speak for itself.

This DVR data scan compares four record layers in Burt v. Frank Productions LLC, MEOD Case No. 2025-00002:

1. A first-person December 17, 2023 DVR onboarding memo.
2. Frank Productions’ September 19, 2024 Interactive Dialogue Questionnaire letter.
3. Frank Productions HR Manager Haley Davis’s October 3, 2024 accommodation email.
4. Attorney Robert Gregg’s January 30, 2026 initial response for Frank Productions.

The method is simple: chronology before conclusions; evidence before advocacy.

The record begins before the termination

My December 17, 2023 DVR onboarding memo was addressed to CEO Joel Plant, Senior Market Director Lauren Toler, and DVR representative Brock Hansen. In it, I reported that I was a disabled veteran with availability limits, that scheduling practices were affecting me, and that I was bringing concerns forward.

That memo is evidence of what I wrote and the notice I attempted to provide. Standing alone, it does not prove each recipient opened or received it. The delivery record—email headers, sent messages, replies, or testimony—remains the necessary corroboration.

That distinction matters.

The employer’s own accommodation record

On September 19, 2024, Frank Productions sent an Interactive Process Questionnaire letter. The letter states that prior health-condition discussions had occurred in October 2023 and that more recent communications were being treated as a request for reasonable accommodation. It requested provider information and stated that failure to provide it by October 3 could result in rejection of the request.

Then, on October 3, HR responded in writing. Haley Davis acknowledged that the medical material was incomplete and “self-reported,” but said the company would proceed with it for the time being. The email listed accommodations for headaches, position changes for knee pain, lifting assistance above 20 pounds, and warm clothing or reassignment for cold exposure.

Those are not my interpretations. They are FPC’s written records.

The documents establish that, by October 3, FPC had recognized specified restrictions and approved specific accommodations. They do not, by themselves, establish whether every supervisor received the information, whether the accommodations were consistently implemented, or whether additional requests were properly evaluated.

Gregg’s response: the respondent’s theory

In the January 30, 2026 initial response, attorney Robert Gregg denied discrimination and retaliation. He argued that FPC lacked knowledge of my health conditions until the September 2024 interactive process, apart from a May 2024 elevator-light issue. He further argued that FPC accommodated the restrictions despite incomplete provider verification.

Gregg also presented FPC’s termination theory: that my employment ended on November 8, 2024 because of alleged on-duty statements on November 5 about harming a patron, not because of disability, protected activity, or retaliation.

That is a party’s litigation position. It is not an adjudicated finding.

The DVR quadratic

The comparator has four corners:

Record layer	What it can establish	What remains open
First-person/DVR notice	What I reported, when I reported it, and the recipients I identified	Actual receipt and decision-maker knowledge
Employer accommodation documents	That FPC opened an interactive process and approved listed restrictions	Consistent implementation and scope
Respondent legal response	FPC’s stated non-discriminatory explanation and litigation framing	Credibility, completeness, and motive
Independent proof	What a neutral decision-maker may ultimately find	Requires testimony, underlying messages, logs, video, and agency record

The core question is not whether one document “wins.” The question is whether the chronology holds.

FPC’s own papers acknowledge an accommodation process, a health-information request, and written approval of specified restrictions. My earlier memo reflects a reported DVR-linked concern before that formal process. Gregg’s response draws a line between generalized awareness and actionable knowledge of particular restrictions. That line is now an evidence question, not a slogan.

What the record still needs

A complete comparison requires the underlying materials, not merely the parties’ summaries:

• Sent-message and receipt records for the December 2023 memo.
• DVR communications and any employment-plan documents relevant to notice.
• HR and management emails from September through November 2024.
• The November 5 incident reports, witness statements, security logs, video, and message history.
• The drafting history and approval trail for the termination and venue-ban decision.
• Testimony from the decision-makers and witnesses with firsthand knowledge.

No conclusion before the record.

DemonSpeak, in this method, is the disciplined refusal to let an institution’s final-sounding language become the final word. The first-person account is preserved. The employer’s records are preserved. The lawyer’s response is preserved. The missing evidence is named.

Human observation starts the story. Documents test it. Chronology exposes contradictions. The record—not the rhetoric—determines what can be responsibly published or proved.

Editorial note: This is an AI-assisted, human-directed document comparison for reporting and record organization. It distinguishes firsthand account, party position, documentary record, and unresolved questions. It is not a judicial finding or legal advice.

What Is a DemonSpeak Scan?

Outpost 422’s JEDVIDENCE definition

At Outpost 422, a DemonSpeak scan is a metaphorical, evidence-first editorial method for examining charged workplace and legal language.

It is not a diagnosis. It is not a spiritual verdict. It is not an AI finding that any person acted unlawfully, deceptively, or with bad intent.

It is a pause button.

When a message, filing, text thread, or workplace narrative uses language that turns a disputed event into a sweeping conclusion, the scan asks: What does the record actually establish—and what still needs proof?

The four-part test

Outpost 422 uses a simple quadratic framework:

Q\text{Claim} = \text{lived account} + \text{documentary record} + \text{governing rule} + \text{bounded inference}

1. Lived account
   What did a person personally see, hear, report, or experience?
2. Documentary record
   What do the emails, texts, video, policy documents, metadata, witness statements, and timelines actually show?
3. Governing rule
   What workplace policy, administrative procedure, or legal standard applies?
4. Bounded inference
   What conclusion is reasonable to explore—but must remain identified as an inference rather than a proven fact?

How the scan works

A DemonSpeak scan converts emotionally loaded language into an accountable evidentiary question.

• “They lied” becomes: “I dispute this statement and request the original record, author, date, and corroboration.”
• “This was retaliation” becomes: “I reported a concern on this date; an adverse action followed; the record should be reviewed for knowledge, timing, and stated reasons.”
• “This proves bad faith” becomes: “This record raises a question about whether the stated policy was applied consistently.”
• “Management targeted me” becomes: “I contend the sequence and treatment were disparate; the relevant communications and comparator records should be reviewed.”

That is not softness. It is precision.

What JEDVIDENCE does—and does not do

Journalism eDiscovery™ organizes a record through chronology, primary documents, firsthand reporting, and AI-assisted editing. It helps identify contradictions, missing records, unsupported wording, and questions for neutral review.

It does not decide a pending case. It does not determine credibility. It does not label people. It does not replace an investigator, judge, attorney, journalist, or factfinder.

AI can help locate patterns and sharpen questions. Human beings must verify sources, assess context, and make decisions.

Why this matters

Workplace conflicts are often preserved through fragments: a phone screenshot, a scheduling app, an email chain, a policy excerpt, a video clip, or a statement written after the fact. Each fragment may matter. None should be overstated.

The purpose of a DemonSpeak scan is to protect the record from both distortion and emotional overreach. It asks the writer to separate:

• what is known;
• what is reported;
• what is disputed;
• what is missing; and
• what a fair reader could reasonably infer.

That is the Outpost 422 standard: speak plainly, preserve the source, mark the limits, and let the evidence carry the weight.

Publication note: This article describes an editorial and evidence-organization method. It does not make findings about any person or pending matter. Readers should review original records and seek appropriate professional guidance for legal, medical, employment, or safety concerns.

#Outpost422 #JEDVIDENCE #JournalismEDiscovery #EvidenceFirst #MediaLiteracy