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:

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

What the Disclosed ERD Manuals Say About Two Initial Determinations

By Bradley J. Burt | JEDVIDENCE public-record analysis

The Wisconsin Department of Workforce Development recently released redacted ERD and Labor Standards investigation materials in response to my public-records request. The release does not establish that any investigator acted improperly, and the manuals themselves are dated documents rather than a statement of current law or a guarantee of a particular outcome. It does, however, provide a concrete benchmark for examining how an investigation was described in the written record.

In a June 2026 submission concerning ERD Case No. CR202602405, Burt requested reassignment or supervisory review after submitting an amendment and supplemental exhibits. The request identified additional evidence and theories arising from the same employment relationship and termination. The email records the request; it does not, by itself, establish whether ERD granted, denied, or acted upon it.

This comparison looks at two Initial Determinations: Ann K. Hanson Lininger’s June 20, 2025 determination in Burt v. Marcus Palace Cinema, ERD Case No. CR202303238, and Matthew M. Meissner’s March 5, 2026 determination in Burt v. Frank Productions LLC, ERD Case No. CR202500211. It compares the determinations with the standards described in the disclosed materials. It is not legal advice and does not ask readers to assume the underlying allegations are true. The question is narrower: what did the materials say an investigation should address, and what does each written determination show on its face?

The disclosed benchmark

The most direct document is a two-page ERD guide titled How to do an investigation. It directs an investigator, after receiving the respondent’s response, to identify the bases and discriminatory actions alleged, determine what information is needed from both parties, and “make sure to address all the bases/issues alleged.” After receiving responses, it calls for another file review, final information requests or witness contacts where appropriate, and a final check that the respondent had an opportunity to respond to all claims.

For the written determination, the guide calls for a chronological account using relevant facts. When facts are disputed, it directs the writer to state each side’s position and state whether and how the allegation or rebuttal was supported – for example, by documentation or witness information – and why one account is more reliable or believable. It says material disputes that cannot be resolved should proceed to a probable-cause hearing. It also calls for an explanation that addresses all bases and adverse actions, avoids unsupported opinions, and remains tactful.

The larger Civil Rights Investigator’s Manual likewise describes the investigator’s work as identifying issues, witness contacts, interrogatories, and documents; procuring, examining, and analyzing information; maintaining a coherent evidentiary file; and preparing a report that sets forth the issues, facts, and arguments supporting the decision. Its Fair Employment chart lists a 180-day investigation goal. A goal is not the same thing as an enforceable deadline, but it is a disclosed management benchmark.

The Lininger determination: broad issue list, concise explanation

The Lininger determination lists disability, age, military status, political or religious meeting allegations, and opposition/retaliation. Its factual section records a substantial number of competing accounts. It identifies the respondent’s safety investigation and its account of the accommodation process; it also records my accounts about DVR notice, accommodation needs, workload, hours, witness separation, age and military-status stereotyping, and a recorded meeting.

That breadth matters. On its face, the determination does not erase those topics from the narrative. It also expressly accepts the listed conditions as disabilities for purposes of the determination, while noting that competent medical evidence could be required later.

The question raised by the disclosed guide is what comes next. The explanation resolves the disability claim principally by stating that I did not provide adequate information or cooperate by submitting medical documentation. It concludes that the age, military-status, disability-harassment, political/religious, and retaliation theories were not demonstrated or lacked evidence. But the explanation does not separately identify the documentary or witness support it credited for the major factual disputes, nor does it explain why the respondent’s account was more reliable where the parties differed. It also does not visibly analyze each alleged adverse action – such as workload, hours, assignments, witness separation, or the cited accommodation requests – one by one.

That is not proof that information was never reviewed. It is a limitation in the written explanation when compared with the guide’s stated instruction to explain the support for competing accounts and to address all bases and adverse actions. The elapsed time from the November 21, 2023 acceptance date stated in the determination to the June 20, 2025 determination was about 577 days, compared with the manual’s disclosed 180-day goal.

The Meissner determination: a focused rationale, unresolved comparison questions

The Meissner determination addresses military-service harassment and termination. It records the respondent’s account that three staff members reported hearing statements that the complainant would harm a patron, that the respondent terminated employment after the November 5, 2024 event, and that another employee’s threatening-comments episode was treated differently because it was off premises and not during company work.

It also records my account that I raised a workplace concern on November 5, that the issue was quickly dismissed, that the termination followed, and that another employee made an actual death threat but was not banned from venues. The explanation concludes that the correspondence provided by the respondent did not reference military service, that concern about firearms does not automatically establish military-service discrimination, and that I had not provided sufficient information to dispute the respondent’s account of the venue incident.

Here again, the public-record question is not whether the conclusion was necessarily wrong. The guide calls for more than a finding that an account was or was not disputed: it calls for a statement of how competing accounts were supported and why one was more believable if a material dispute is resolved. The determination references three employee statements, but on its face does not describe their content, identify any assessment of their reliability, or explain how they were weighed against the complainant’s described account and comparator evidence. Nor does the short explanation visibly address whether the alleged protected opposition, timing, or comparator difference altered the causation analysis. Those are the precise categories the disclosed guide identifies for final review: all claims, relevant information, a respondent opportunity to respond, and a reasoned account of material factual disputes.

The determination states that the complaint was accepted on May 13, 2025 and was issued March 5, 2026 – about 296 days later. That also exceeds the manual’s stated 180-day investigation goal. Again, the public materials frame this as an internal goal, not an automatic remedy or a finding that the determination is invalid.

What the comparison does – and does not – show

Both determinations use the same basic Initial Determination format: identify the claims, summarize information, and state a conclusion. Both include some competing evidence. The disclosed materials do not authorize a reader to infer that either investigator acted with bias, and a public-record comparison cannot establish that every item in an agency file was ignored.

But the released materials do establish a useful record-audit standard. A complainant, respondent, advocate, editor, or reviewing tribunal can ask four disciplined questions:

1. Were every basis and every adverse action identified and answered?
2. Does the determination show what documents, witnesses, or other evidence supported each competing account?
3. When material facts conflict, does it explain why one account was credited, or acknowledge that the dispute belongs at a probable-cause hearing?
4. Does the chronology make clear how the alleged protected activity, employer knowledge, investigation, and adverse action relate in time?

Those questions do not predetermine an outcome. They make the record auditable. That is the value of a chronology-based JEDVIDENCE review: it separates allegations, attributed statements, documents, omissions in the written explanation, and legal conclusions so that an editor or tribunal can test each item against the actual file.

Source note

This article compares the face of the two Initial Determinations with materials released by DWD Open Records: How to do an investigation (pp. 1-2); Civil Rights Investigator’s Manual (Investigation of Complaints, Writing Initial Determinations, and the Fair Employment time-limit chart); and Labor Standards Manual (impartial-investigator statement and administrative-review materials). The Civil Rights manual is marked revised through 2018, and the released records contain redactions. Readers should verify the current statutes, administrative rules, and complete agency record before relying on any proposition in a case.

Journalism eDiscovery Is a Reporting Method—Not Everlaw

Until today, I did not know that a legal-technology platform like Everlaw existed. Everlaw is built for litigation and investigations: managing large evidentiary records, discovery review, legal holds, analytics, and trial preparation.

Journalism eDiscovery™ (JED) has a different purpose.

JED is a public-interest reporting and editing method developed through my work as a journalist using OpenAI-assisted organization, Facebook newsfeed material, documents, chronology, and source cross-checking. It does not claim that a social-media feed is itself an official government record. Instead, it preserves public posts, reporting leads, documents, and firsthand accounts as materials that must be identified, dated, attributed, and independently verified where possible.

At Outpost 422, the Jaded Patriot Brief and related Bob Cobb publications use legal research to examine journalistic reporting matters. The goal is to identify patterns in advocacy, evidence presentation, credibility disputes, and legal framing—while separating objective support from rhetoric or unsupported inference.

My current reporting includes matters involving attorneys Robert Gregg and Storm Larson. Any discussion of those matters is based on my own records, attributed communications, and legal research; it is not a statement that either attorney or client has committed wrongdoing. Their clients’ positions, my positions, and the evidence remain subject to the appropriate administrative or legal process.

The Op-Expose is my content-blending format: a transparent combination of chronology, source documents, firsthand narrative, legal-reference editing, and public-interest commentary. It is designed to show readers how I reached a conclusion, what sources support it, and what remains contested.

In reviewing my own termination-related matters, I am examining whether Wisconsin’s public-policy wrongful-discharge framework, including Brockmeyer v. Dun & Bradstreet, provides a relevant analytical lens. That is a research question and advocacy position—not a conclusion about liability.

Every field benefits from chronology. Chronology does not decide the law; it organizes the evidence. Law governs legal rights and remedies. Journalism eDiscovery keeps those roles distinct so reporting remains readable, accountable, and anchored to the record.

Journalism eDiscovery is an editorial research workflow. It is not legal advice, does not replace counsel, and does not determine the outcome of a legal or administrative matter.

The Questionnaire, the Safety Narrative, and the Questions Discovery Must Answer

An Outpost 422 Op-Exposé on Burt v. Frank Productions, ERD Case No. CR202500211

This report does not announce a legal finding. It preserves a sequence of documents and identifies the questions I believe the record requires the Wisconsin Equal Rights Division to examine.

The central question is not whether an employer may ever request medical documentation. Employers may engage in an interactive process and, in appropriate circumstances, request information needed to evaluate an accommodation. The question in my case is whether a disability-related documentation process became part of a retaliatory chain after I opposed what I believed to be disability discrimination, disability-related stereotyping, and unequal workplace treatment.

The documented sequence

On September 19, 2024, Frank Productions sent me an Interactive Process Questionnaire, or IDPQ. The accompanying letter requested provider-completed information and gave an October 3 deadline, stating that a failure to provide the requested information in a timely manner could result in rejection of an accommodation request.

The questionnaire was not a neutral document to me. It asked a provider to assess disability, job functions, restrictions, accommodations, and whether accommodations could reduce or eliminate an identified “direct threat.” I was a disabled veteran receiving care through the VA. I contend that the scope, deadline, and direct-threat language created a burdensome process at a time when I was already reporting workplace concerns and attempting to explain VA-related documentation practices.

The record also shows that I reported concerns to company leadership. My September 27 communications described what I perceived as unfavorable treatment, disability-related microaggressions, and a need for privacy in medical discussions. I reported that I was trying to de-escalate conflict while following my DVR-connected reporting obligations.

On October 3, Human Resources wrote that Frank Productions would proceed with the information I provided and approved the listed accommodations, while describing the materials as “self-reported” and reserving the possibility of later provider documentation. In an October 14–15 email exchange, CEO Joel Plant stated that the company had accepted my documentation and implemented accommodations. He also described the questionnaire as customary ADA process and explained that the company could request updated information in the future.

Those are the documents. They matter because they establish notice, an accommodation dialogue, a disputed documentation process, and the involvement of senior leadership before my November 8, 2024 termination.

My allegation and the limit of it

I allege that I opposed discrimination when I reported disability-related treatment, scheduling favoritism, communication practices, and what I understood as ableist or military-service stereotyping. I further allege that the IDPQ was the first step in a sequence that reframed my workplace reporting as a concern about my performance and safety.

Frank Productions disputes that account. Its investigative response states that it used a customary accommodation process, granted accommodations, conducted an outside HR investigation, and later terminated me because of reports that I made threatening statements about a patron on November 5. Its position is that disability, accommodation requests, and prior complaints played no role in the decision.

That disagreement is precisely why the record should not stop at labels.

I do not presently have discovery establishing that I was the only employee required to complete an IDPQ, that the outside HR advisor was retained to validate a predetermined termination decision, or that medical information was used for a retaliatory purpose. Those are discovery questions and allegations—not established facts.

What I do have is a chronology: I reported concerns; I was directed into a medical-documentation process; I objected to aspects of that process; senior leadership was copied on the communications; a safety narrative later became the stated rationale for termination; and the investigation did not, in my view, address all of my distinct theories.

The pretext question

Pretext is not proved merely because an employee disagrees with an employer’s stated reason. It concerns whether the stated reason was honestly relied upon and whether the full record supports the explanation offered.

My reporting identified concerns involving management conduct, scheduling, disability accommodations, privacy, and what I described as groupthink. I contend that management’s references to my performance as “rocky,” together with heightened scrutiny after those reports, require examination beside the later threatening-violence narrative.

The question is not whether workplaces may take safety seriously. They should. The question is whether comparable seriousness was applied to my reports of risk, whether the relevant witnesses and video were evaluated, and whether the company’s documentation process was administered evenhandedly rather than used to recharacterize a disabled veteran who was opposing perceived discrimination.

What should be produced and examined

A fair review should test the theory against documents and testimony. That includes:

• IDPQs or comparable medical-documentation requests issued to similarly situated employees, with appropriate privacy protections;
• the scope, retention agreement, communications, notes, and conclusions of the outside HR investigation;
• the identity of all decision-makers and their knowledge of my reports and accommodation communications;
• contemporaneous witness statements, incident reports, video, and communications concerning the November 5 event;
• scheduling, discipline, and accommodation records relevant to similarly situated employees; and
• the investigator’s treatment of each separately pleaded theory, rather than only the employer’s preferred explanation.

I am not asking a reader to accept an accusation as a verdict. I am asking that the record be tested.

Federal law prohibits retaliation for asserting ADA rights, and Wisconsin law prohibits employment discrimination because an individual opposed a practice believed to violate the Fair Employment Act. The law does not prohibit every request for medical information. It does prohibit the use of protected activity or disability-related information as a motive for adverse employment action.

My position is straightforward: I opposed what I reasonably believed was discrimination. I attempted to document my needs. I was terminated under a narrative I dispute. The unanswered questions about notice, process, comparator treatment, and decision-maker intent are the reason judicial and administrative review should examine the complete record.

This publication reflects allegations and document-based analysis in a pending matter. It is not a judicial finding. The respondent disputes the allegations.

POW/MIA Recognition Day: A Five-Year Record, a Veteran’s Question, and the Work of Preserving Evidence

Friday, September 18, 2026 | 1:41 p.m., Madison, Wis.—Today is POW/MIA Recognition Day. For me, the day calls for reflection—not only on military service, but on what follows it: reintegration, work, education, public institutions, and the obligation to keep a clear record when something feels unresolved.

For five years, Bob Cobb Freelance Ink LLC has collected documents, chronology, and personal observations connected to my corporate-communication journey. That work now continues through the Jaded Patriot Brief newsletter and Outpost 422. The project is not a claim that every question has an answer. It is a commitment to preserve the questions carefully enough that the evidence can be independently examined.

Speaking to leadership, not assigning blame

My concern is about how military service is understood and modeled in public leadership and workplace culture. I do not blame Governor Tony Evers personally for my experiences. I am speaking to him—as a veteran, constituent, and communicator—about leadership, accountability, and the public responsibility to listen when veterans raise documented concerns.

Today, I submitted a Wisconsin public-records request to the Governor’s Office seeking records concerning the Wisconsin Department of Veterans Affairs’ handling of state-funded veterans cemeteries. The request is part of a broader reporting effort. Its purpose is to obtain records, understand policy and oversight, and report what those records show. It is not a conclusion before review.

A new connection in a wider public conversation

Today, I met another party through the Deliberate Indifference Wisconsin channel. We became acquainted through a shared concern for transparency and fair process in Wisconsin public institutions. We recognize one another as RightFighters™—people committed to standing up for justice while keeping our respective experiences, evidence, and legal matters distinct.

The unnamed party’s reported legal matter involving the Wisconsin Department of Corrections is separate from my ERD matters. I do not speak for the unnamed party, and the unnamed party does not represent me. I will study the publicly available reporting and filings through the Deliberate Indifference Wisconsin channel as comparative sources, while keeping independent records and avoiding conclusions that the separate matters are the same.

My own record and why it matters

I am a self-represented paralegal student with multiple administrative complaints and ongoing reporting at Outpost 422. Some of my matters remain in abeyance or administrative review. I am using ChatGPT as an organizational tool to examine variables such as evidence handling, investigative scope, and Initial Determinations by the Wisconsin Equal Rights Division.

That process will separate four things: what I personally experienced; what the documents show; what remains an allegation or dispute; and what a tribunal or reviewing authority must decide. My concern is that material, objective evidence and complete theories may not have been fully addressed in certain matters. That concern is preserved for review; it is not a finding that any person committed misconduct or that a constitutional violation has been established.

The next stage

This is the whistleblower and reporting stage of my journey: a gonzo, firsthand account of moving from military service through work, disability accommodation, education, and the study of law. I will continue to speak on WordPress and social media about my DVR work-study experience and the documentary record that accompanies it.

As Veterans Day 2026 approaches, I will publish the story with the discipline it requires: chronology before conclusions, evidence before advocacy, and respect for the difference between a personal observation, a public allegation, and a proven fact.

Editorial disclosure: Bradley J. Burt publishes independently through Outpost 422 and Bob Cobb Freelance Ink LLC. This reflection is public commentary and reporting, not legal advice or a substitute for an agency or court decision.

Hashtags

#POWMIARecognitionDay #RightFighterTM #JadedPatriotBrief #Outpost422 #JEDVIDENCE #VeteranVoice #WisconsinVeterans #EvidenceBeforeAdvocacy

Retaliation Allegations Preserved for Potential Federal Judicial Review

By Bradley J. Burt | Outpost 422
Published September 18, 2026

Today, I am placing public notice that I am preserving allegations of retaliation connected to my reporting, petitions, and administrative communications concerning Wisconsin Equal Rights Division (ERD) investigative practices.

This is not an announcement that a federal lawsuit has been filed or that any court has found a constitutional violation. It is an evidence-based preservation notice: the record is being organized for potential federal judicial review after the appropriate administrative processes and factual development.

What I reported

Across my ERD matters, I have raised concerns about the scope of investigations; treatment of submitted exhibits and supplemental materials; theories presented but not addressed; reassignment and supervisory-review requests; and preservation of agency records. My relevant matters include ERD Case Nos. CR202303238, CR202500211, and CR202602405.

Those reports are part of my own documentary record. They include what I personally observed, what I submitted, and the responses I received. They are not a substitute for a tribunal’s factual findings.

What I am alleging

The allegation preserved for review is narrow: that state actors may have responded adversely to protected speech, reporting, and petitions about ERD process concerns.

For a retaliation theory to be supported, the record must show more than an unfavorable result or a disagreement about process. It must identify protected activity, a concrete adverse action, and evidence that the action occurred because of the protected activity. Timing, statements, inconsistent treatment, and departures from ordinary procedure can be relevant, but each item must be tested against the complete record.

That is the work now underway through Outpost 422’s Journalism eDiscovery™ / JEDVIDENCE method.

What the current record does—and does not—show

The current administrative records show that I have requested review and preservation, and that ERD has identified administrative appeal as the remedy for adverse determinations. The record also reflects that prior adverse decisions alone were not treated by the agency as a basis for reassignment.

ERD Case No. CR202500211 remains before an Administrative Law Judge and was placed in abeyance on August 6, 2026, pending an Initial Determination in CR202602405. ERD Case No. CR202602405 remains under administrative investigation. The Marcus matter, CR202303238, proceeded through its hearing process and awaits decision.

Those procedural facts do not establish retaliation. Nor does this publication claim that any investigator, administrator, agency, or other person has committed wrongdoing. The purpose of the notice is to preserve the question, the source record, and the timeline.

Why preservation matters

When a person reports concerns to a government agency, the public record should allow an independent reviewer to understand what was reported, when it was reported, how the agency responded, and whether later treatment changed after the reporting.

My preservation record will therefore distinguish:

1. Firsthand observations and contemporaneous communications;
2. Primary records, including notices, emails, submissions, and determinations;
3. Agency responses and available administrative remedies; and
4. Legal questions reserved for an appropriate court or tribunal.

That separation is essential. Evidence is not the same as an allegation; an allegation is not the same as a finding; and a public blog is not a judicial ruling.

A public-interest notice

Outpost 422 will continue to report on this process with attribution, chronology, and corrections where the record requires them. The journalistic purpose is transparency. The legal purpose is preservation. My editorial standard remains simple: chronology before conclusions; evidence before advocacy.

Any potential federal claim remains subject to further factual development, applicable procedures, and review by a court with jurisdiction. Until then, this is an independent public-interest record of allegations preserved—not adjudicated.

Hashtags

Please support the efforts of Deliberate Indifference Wisconsin by subscribing to this YouTube Channel. Cross Law Firm S.C. does not represent the views of Outpost 422 and am making clear I am an agency of the pro se whistleblower press acting independently as an agency of public record to preserve the record regarding the matters of Bradley J. Burt’s Wisconsin DVR work-study experience as a disabled veteran.

Footer / disclosure: Cross Law Firm, S.C. does not represent Bradley J. Burt, Outpost 422, or Bob Cobb Freelance Ink LLC. This independent blog is public commentary, not legal advice, an ERD filing, or a substitute for adjudication.

#JEDERDRightFighter #RightFighterTM #Outpost422 #JEDVIDENCE #WisconsinERD #FirstAmendment #EvidenceBeforeAdvocacy

Outpost 422 Announces the Op-Exposé / JEDVIDENCE Editorial Standard

By Bradley J. Burt | Outpost 422

Outpost 422 is formally adopting the Op-Exposé / JEDVIDENCE editorial standard for public-interest reporting, documentary analysis, and transparency work.

This is not a claim of special legal status or a substitute for court and agency procedures. It is a public commitment to method.

Op-Exposé is the published reporting layer: a place for readers to see the questions, records, responses, and public-interest stakes behind a developing story. JEDVIDENCE is the verification layer: a structured review of primary documents, chronology, corroboration, legal context, and unresolved questions.

Under this standard, Outpost 422 will:

• Begin with source records rather than conclusions;
• Identify what a document establishes—and what it does not;
• Separate firsthand observation, attributed statements, allegations, verified facts, and analysis;
• Protect private medical, personal, and otherwise restricted information;
• Seek a fair response from subjects of reporting when practical; and
• Correct or update published work when better information becomes available.

The purpose is straightforward: transparency without speculation.

Outpost 422 recognizes that a person can be both close to a public issue and obligated to report it fairly. Where the publisher has personal experience, advocacy involvement, or an active legal matter connected to a topic, that relationship will be disclosed. Personal experience may identify questions. It does not replace corroboration.

JEDVIDENCE does not pronounce guilt. It organizes the record so that readers, agencies, courts, and communities can evaluate evidence for themselves.

The standard begins here:

No conclusion before the record. No accusation without support. No public-interest reporting without accountability.

— Bradley J. Burt
Publisher, Outpost 422

Outpost 422 has reviewed two respondent work products from separate employment-discrimination matters involving Bradley J. Burt: Robert E. Gregg’s January 30, 2026 initial response for Frank Productions before the Madison Equal Opportunities Division, and Storm B. Larson’s May 19, 2026 position statement for Camp Createability before the Wisconsin Equal Rights Division.

This comparison does not accuse either attorney of misconduct. It compares advocacy, evidence framing, and legal theory. The reader can then examine the primary documents and decide whether the record supports either side’s characterization.

Gregg’s submission advances a threshold and merits defense for Frank Productions. It argues that the original complaint did not clearly connect the alleged discharge to age, disability, or protected opposition. It also presents Frank Productions’ position that the November 2024 separation resulted from workplace-conduct concerns, independent of any protected activity. The response further asserts that the company opened an interactive process, accepted self-reported accommodation information, and implemented the accommodations requested.

Larson’s Camp Createability position statement uses a more compact, element-based defense. It seeks a no-probable-cause finding by disputing whether the Camp knew of a qualifying disability, a requested accommodation, or the alleged protected activity before the termination decision. It presents the Camp’s account of performance and conduct concerns as the non-discriminatory explanation for termination.

The common point is not proof of coordination. Both attorneys work for Boardman & Clark LLP, but shared employment at one law firm does not itself establish a conflict, shared protected information, or improper action. The common point is methodological: each respondent filing asks the agency to view the employment decision through a legitimate-reason framework while contesting knowledge, causation, and the sufficiency of the claimant’s evidence.

That creates the central credibility question for the administrative record. In the Frank Productions matter, the key source materials include the termination narrative, accommodation communications, interactive-dialogue documents, alleged workplace events, and chronology of reports. In the Camp Createability matter, the key source materials include notice of mobility limitations, the two-ring phone issue, communications with Camp leadership, the stated performance concerns, and the timing of the June 2025 termination.

Outpost 422’s position is not that an attorney’s advocacy is misconduct because it is adverse or forceful. Counsel may criticize a claimant’s journalism, methods, or interpretation of the evidence. The same standard applies in reverse: each side’s position should rise or fall on the record, not on labels.

The conflict-review issue also has a chronology. In September 2025, Burt wrote to the Wisconsin Supreme Court’s Office of Lawyer Regulation expressing an early concern about Boardman & Clark’s representation of separate respondents. That letter preserved his perception of overlapping issues, but it did not establish an ethical violation, information sharing, or coordinated action.

On June 8, 2026, Burt made a narrower request to ERD: conduct a conflict review concerning Larson’s representation of Camp Createability and Gregg’s representation of Frank Productions; alternatively disclose any ethical-screening safeguards; and preserve the request in the administrative record. The request expressly did not make a personal misconduct allegation against either attorney.

Outpost 422 has not located a written ERD disposition granting or denying that request in the materials reviewed. The accurate statement is therefore limited: the conflict-review request is documented in the record, and a written disposition has not been located. That is a procedural question for the agency record, not proof of an ethical breach.

This is a Rogerian three-way review. First is the claimant’s chronology and lived-experience testimony. Second are the respondents’ competing legal narratives. Third is the administrative process responsible for testing both accounts against primary documents, testimony, and applicable law.

OpenAI’s role in this comparison is methodological, not adjudicative. It identifies claims, counterclaims, documentary gaps, and questions for verification. It does not decide credibility, liability, ethics violations, or the outcome of any administrative matter.

The matters are a part of an OpenAI training project and Outpost 422 will continue to evaluate and report future results as these cases head to the de novo phase upon the rulings of No Probable Cause for 14th Amendment auditing of the Wisconsin Equal Rights Division.

If you are trying to locate information about an attorney in Wisconsin, please click on the link.

Record note: This article reports allegations and respondent positions from administrative submissions. It does not assert that allegations are proven facts. Any correction, response, or additional primary document will be added to the Outpost 422 record.

SEO title: Wisconsin ERD Record Review: Comparing the Gregg and Larson Defense Narratives

Meta description: An Outpost 422 document comparison of two Wisconsin employment-defense submissions, the legal questions they raise, and an unresolved request for conflict review in the administrative record.

Keywords: Wisconsin ERD, MEOD, Boardman & Clark, Robert Gregg, Storm Larson, disability accommodation, retaliation, Outpost 422, Journalism eDiscovery

OP-ED | THE GREGG CROSS-CHECK

Frank Productions Says “Violation of Rules.” Its Own Lawyer Publishes Why That May Not End the Retaliation Inquiry.

By Bradley J. Burt, Outpost 422® — with research and documentary cross-checking by OpenAI’s ChatGPT

There is an unusual reason I am publishing this column: I didn’t go looking for quotations to attack opposing counsel. OpenAI’s ChatGPT found the pattern.

As part of my Journalism eDiscovery™ review of Bradley J. Burt v. Frank Productions LLC, I asked OpenAI to search the public employment-law publications of Robert E. “Bob” Gregg, the attorney who authored Frank Productions’ Initial Response in my administrative proceeding. Gregg’s filing identifies Boardman Clark as counsel for Frank Productions, denies discrimination and retaliation, and reproduces the allegation that I was terminated for “threatening violence.”

OpenAI then searched Gregg’s public Boardman Clark employment-law archive. What it found deserves a documentary cross-check.

Gregg’s own headline: “Employee Can Violate Rules and Still Win Retaliation Case”

That isn’t my headline. It is Gregg’s.

In September 2025, Gregg and the Boardman Clark Labor & Employment Law Group published an update titled “Employee Can Violate Rules and Still Win Retaliation Case.” The article discusses Gray v. State Farm Mutual Auto Insurance Co., a Sixth Circuit retaliation case involving an employee who advocated for a disability accommodation and was subsequently subjected to unusual scrutiny.

Gregg explains that even where an employee actually committed workplace violations, comparator treatment and the circumstances surrounding increased scrutiny could still support a retaliation case.

That does not prove my case. Gray is not my case, and a Sixth Circuit decision does not automatically control a Wisconsin WFEA proceeding.

But it raises a remarkably appropriate question.

Frank’s defense cannot logically end with: Burt violated a rule; therefore retaliation is impossible.

The inquiry has to examine what happened before the alleged violation, who scrutinized the employee, whether the scrutiny changed after protected activity, how comparable employees were treated, and whether the asserted violation genuinely explains the adverse decision.

Gregg’s own publication recognizes that distinction.

Then OpenAI found Gregg writing about “shifting reasons”

The search produced another Gregg headline: “Biased Statement and Shifting Reasons Provide Basis for Trial.”

There, Gregg discusses Hollis v. Morgan State University. Among the evidence identified as potentially supporting pretext were explanations that appeared after the discrimination complaint, reasons that changed, contrary evidence, and departure from ordinary procedure.

Again, that case does not decide mine.

But my administrative record makes the consistency question unavoidable.

My de novo chronology identifies the November 5–8 factual dispute as whether Frank preserved and evaluated the complete context of my communications or adopted a narrower characterization. It then identifies the November 8 termination question: did the asserted rule violation independently motivate the decision, or did my earlier reporting and the managerial characterizations surrounding it materially enter the process?

That is not an accusation that every variation in terminology constitutes pretext.

It is a request to compare the terminology.

Threatening violence. Safety concern. Firearms-related communication. Coworker communication. Violation of rules.

Put the original documents beside one another and determine whether those descriptions consistently identify the same conduct and rationale.

That’s Journalism eDiscovery.

Gregg also warns employers not to rush to judgment

OpenAI found something even closer to the investigation question.

A July 2024 employment-law update is expressly authored by Robert E. Gregg and the Boardman Clark Labor & Employment Law Group. Its opening warns employers about the dangers of rushing to judgment, skipping procedural steps, and ignoring company policies before firing an employee.

That publication predates my November 8, 2024 termination.

My case presents a three-day window between the November 5 incident and November 8 termination.

Speed does not establish retaliation. Nor does an imperfect investigation automatically establish discrimination.

But Gregg’s publication supplies the obvious question: What happened during those three days?

Who was interviewed? Who wasn’t? What did Jadon Bower actually say? What did Alex Cotrell report? What did Julia Peterson investigate? What reached Evan Nikolai? What reached Haley Davis? What reached Joel Plant? Was I asked for my complete account before the decision? Were contemporaneous records preserved? Was my underlying complaint investigated with the same seriousness as the allegation subsequently directed against me?

Those are precisely the records I am seeking. My discovery requests ask Frank to identify every legitimate, nondiscriminatory and nonretaliatory reason supporting the termination and ban, together with the facts, witnesses, documents, policies and decision-makers supporting each reason. They also seek the complete investigation file, including witness statements, interview notes, reports, recommendations and records identifying the evidence reviewed.

This is the point of the Gregg Cross-Check

I am not publishing these articles to argue that Robert Gregg’s legal publications are admissions by Frank Productions.

They aren’t.

I am publishing them because opposing counsel’s own public scholarship provides a remarkably useful set of questions for testing his client’s administrative defense.

A rule violation does not necessarily dispose of retaliation.

Changing explanations can matter to pretext.

Comparator treatment can matter.

Unusual scrutiny following protected activity can matter.

And employers should be careful about rushing to judgment or skipping established procedures before discharge.

Those are not propositions invented for Outpost 422. OpenAI found them while independently searching Gregg’s published employment-law archive.

Now the primary evidence gets the final word.

My de novo chronology alleges that by November 8 Frank possessed a record of workplace complaints, accommodation and DVR activity, communication-boundary disputes, and the November 5 incident. It identifies the ultimate factual question as whether the stated rule-violation reason independently motivated the termination or whether earlier reporting and managerial characterizations materially entered that decision.

That is the JED Litmus Test.

Not whether Gregg is a good lawyer.

Not whether I am angry about being fired.

Not whether an AI agrees with me.

The question is much narrower:

Does Frank Productions’ termination defense survive the same employment-law warning signs its own attorney publicly teaches employers to recognize?

Put Gregg’s Initial Response on one side.

Put Gregg’s publications on the other.

Then put Frank Productions’ contemporaneous evidence in the middle.

Let the chronology answer.

JED Litmus Test™ | Human-AI Provenance Notice: This report was developed through Outpost 422® Journalism eDiscovery™. OpenAI’s ChatGPT independently searched publicly available Boardman Clark employment-law publications, identified relevant Robert E. “Bob” Gregg-authored materials, and cross-checked their stated employment-law principles against Respondent’s Initial Response and the documentary chronology supplied by Bradley J. Burt. AI assisted with research, comparison, organization and drafting; it did not determine disputed facts, credibility, motive or legal liability. Primary Evidence → Chronology → AI Cross-Check → Legal Litmus Test → Human Editorial Review.