“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.
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.
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_…
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.
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®.
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
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.
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?
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 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:
A first-person December 17, 2023 DVR onboarding memo.
Frank Productions’ September 19, 2024 Interactive Dialogue Questionnaire letter.
Frank Productions HR Manager Haley Davis’s October 3, 2024 accommodation email.
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.
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?
Lived account What did a person personally see, hear, report, or experience?
Documentary record What do the emails, texts, video, policy documents, metadata, witness statements, and timelines actually show?
Governing rule What workplace policy, administrative procedure, or legal standard applies?
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.
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:
Were every basis and every adverse action identified and answered?
Does the determination show what documents, witnesses, or other evidence supported each competing account?
When material facts conflict, does it explain why one account was credited, or acknowledge that the dispute belongs at a probable-cause hearing?
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 Everlawexisted. 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.
