The Exit - Exhibits

26 Feb, 2026

Supporting exhibits for “The Exit.”

Use the index below to jump to each exhibit section.

Index

• Exhibit A - Kaivac timing / cadence evidence
• Exhibit B - Operations Manager texts (Feb 12, 2026)
• Exhibit C - General Manager email thread (Feb 13–16, 2026)
• Exhibit D - Hostile work environment documentation
• Exhibit E - Resignation email (Feb 16, 2026)
• Exhibit F - HR resignation chain (Feb 10–12, 2026)

Exhibit A

Kaivac Timing Logs & The Three-Schedule Problem

Timing notes and logs showing the real operational cadence and why "constraints can't be excuses" is structurally false under actual labor-process conditions.

Context: This exhibit compares three versions of the night shift schedule at the client's Spokane facility:

• (1) management's original vague text
• (2) the detailed minute-by-minute schedule I created to survive
• (3) the material reality that defeated both.

It demonstrates how management provided insufficient operational guidance, blamed the worker for not meeting schedules the worker had to create, and called material constraints "excuses" while refusing to resource the inputs that would make any schedule achievable.

The Three Schedules

Schedule 1: Management's Original (What They Actually Gave Me)

Source: Text message from Night Area Supervisor, August 14, 2025, 9:25 PM

Verbatim text message:

UTC Night schedule Kaivac 330 - 1200  
340-430 Kaivac men's machine shop south restroom  
440-530 Kaivac men's machine shop north restroom  
Break  
550-600 Vacuum/sweep coustruction trailer  
605-610 Sweep furnace deck control room  
615 - 650 Kaivac womens machine shop south restroom  
Lunch  
730-825 Vacuum admin  
830-900 Clean break rooms (small ther large) (wipe down & sweep)  
905-935 Clean Admin restrooms  
Break  
955-1055 Vacuum production offices  
1100-1125 Restroom restock  
1130-1150 Clean break rooms (wipe down)  

Parsing management's schedule into readable format:

What's missing from management's schedule:

• Clock-in/setup time (3:30-3:40)
• Break #1 duration and timing (mentioned but no start/end)
• Lunch duration and exact timing (mentioned but no start/end)
• Break #2 duration and timing (mentioned but no start/end)
• All transitions between tasks (90+ minutes total)
• What to do during 40-minute gap (6:50-7:30)
• What to do during 20-minute gap (9:35-9:55)
• Closeout procedures (11:50-12:00)
• Concurrent trash/maintenance during Kaivac windows
• Equipment staging requirements
• Any guidance on "float" time or detail work

Total time specified: ~300 minutes of tasks
Total shift time: 510 minutes (8.5 hours)
Unaccounted time: ~210 minutes (3.5 hours)

Management's schedule leaves 41% of shift time unspecified.

Schedule 2: Worker's Survival Adaptation (What I Had to Build)

Source: Self-created schedule to navigate management's gaps (developed August 2025 - February 2026)

Complete minute-by-minute breakdown I created:

TOTAL: 510 minutes (all shift time accounted for)

What I added to management's vague schedule:

• ✅ Specified all break/lunch start/end times
• ✅ Added all transitions (50 minutes total)
• ✅ Labeled "float" windows explicitly (5:15-5:30, 10:00-10:15)
• ✅ Named the 6:50-7:45 gap as "detail rotation / visible fillers" (acknowledging plausibility labor)
• ✅ Added setup time (3:30-3:40)
• ✅ Added closeout time (11:50-12:00)
• ✅ Identified "micro-gaps" (8:50-8:55)
• ✅ Broke supervisor's vague "7:30-8:25 Vacuum admin" into realistic 30-minute window with lunch subtracted
• ✅ Broke supervisor's vague "9:55-10:55 Vacuum production offices" into realistic 25 minutes with break subtracted

This is worker-created operational intelligence filling management's 210-minute gap.

My schedule labeled gaps honestly:

• "Gap window (detail rotation / visible fillers)" - 55 minutes
• "Float" - 30 minutes total
• "Micro-gap" - 5 minutes
• "Transition" - 50 minutes total
• Total acknowledged buffer/gap/filler time: 140 minutes (27% of shift)

I documented what management wouldn't acknowledge: over a quarter of shift time is plausibility labor, not real cleaning demand.

Schedule 3: Reality (Why Even Worker-Created Detail Can't Compensate for Under-Resourced Inputs)

From my field manual distributed to coworkers on my final day:

"In reality, the labor demand comes in blocks, not a steady stream. Once the anchors are completed (Kaivacs + required passes + closeout), the building usually does not generate honest work at the same pace as the paper schedule."

Even my detailed self-created schedule assumed perfect conditions:

3:30-3:40 PM - Setup (I scheduled 10 minutes)

• Assumes: Kaivac tank filled, parts functional, machine accessible
• Reality: Often not ready - setup extends into first Kaivac window OR worker absorbs variance by rushing later
• No buffer in either management's schedule or my adaptation

3:40-4:30 PM - First Kaivac (supervisor said 50 min, I kept it)

• Assumes: Equipment ready, restroom accessible, no day shift interference
• Reality: 4:00-4:15 PM is day shift break wave - restroom traffic peaks
• Actual completion: 4:20-4:50 depending on conditions
• Neither schedule accounts for day shift break wave interference

4:40-5:15 PM - Second Kaivac (supervisor said 4:40-5:30, I adjusted to 35 min)

• I noticed the supervisor's 50-minute window was too long, adjusted to 35 minutes
• But 4:40-5:15 PM is PEAK day shift break wave
• Even my optimized timing can't compensate for scheduled work during maximum restroom traffic

6:50-7:45 PM - Gap Window (supervisor didn't mention, I labeled explicitly)

• Supervisor's schedule just... skipped this time (6:50 jump to 7:30 "Lunch")
• I labeled it honestly: "gap window (detail rotation / visible fillers)"
• Reality: By 6:50 PM, all Kaivacs done, day shift exited, building clean, no real demand
• I documented the dead zone management wouldn't acknowledge

10:35-11:00 PM - Production Offices (supervisor said 9:55-10:55, I adjusted to 25 min)

• Supervisor allocated 60 minutes
• I recognized this was excessive, adjusted to 25 minutes realistic time
• Reality: Often conditional - if floors clean, this task takes 10-15 minutes or unnecessary entirely
• Even my realistic timing assumes task is always needed

11:50-12:00 PM - Closeout (supervisor didn't mention, I scheduled 10 min)

• Supervisor's schedule ends at 11:50 with "clean break rooms" - no closeout specified
• I added 10 minutes for: trash carts, equipment rinse/plug-in, prep for tomorrow
• Reality from field manual: Closeout requires cart reset, closet prep, equipment staging, trash consolidation
• 10 minutes insufficient for multi-step process

What This Three-Layer Analysis Proves

1. Management provided insufficient operational guidance

• Night Area Supervisor's text schedule leaves 210 minutes (41% of shift) unaccounted
• No break/lunch timing specified
• No transitions specified
• No guidance on gaps
• No setup or closeout procedures

2. Worker had to build detailed operational intelligence themselves

• I created minute-by-minute breakdown management wouldn't provide
• I labeled gaps honestly ("gap window," "float," "micro-gap")
• I specified all break/lunch windows management left vague
• I added setup and closeout management ignored
• My self-created schedule was MORE detailed and accurate than management's

3. Management then blamed worker for not meeting schedule that WORKER had to create

• General Manager's February 15 email: "constraints can't be used as an excuse for subpar performance"
• He was demanding I meet a schedule that:
  • Night Area Supervisor provided in vague, incomplete form
  • I had to detail and operationalize
  • Still couldn't account for under-resourced inputs (equipment failures, access delays, day shift interference)

4. Even perfect worker-created schedule can't compensate for material conditions

• My detailed adaptation assumed equipment ready (often wasn't)
• My detailed adaptation assumed restroom access available (often blocked)
• My detailed adaptation couldn't prevent Kaivac windows overlapping day shift break waves (supervisor's schedule caused this)
• My detailed adaptation couldn't eliminate dead zones (acknowledged them honestly instead)

The fundamental problem:

• Management gave vague, incomplete schedule
• Worker built detailed operational map to survive
• Management refused to resource inputs that would make schedule achievable
• Management blamed worker when material reality didn't match worker's self-created schedule
• Management called material constraints "excuses" when worker was the ONLY one who documented reality accurately

Dead Zones Documented

Context: The dead zones weren't my fault for bad scheduling - they're structural to episodic cleaning demand. But management's response was the problem:

Management's vague schedule (Schedule 1) just ignored them - left 210 minutes unaccounted
My detailed adaptation (Schedule 2) labeled them honestly - "gap window," "float," "micro-gaps"
Management's response blamed me for "subpar performance" when material reality didn't match schedules

From my field manual - how to navigate the dead zones I honestly named:

Dead Zone #1: 6:50 - 7:45 PM (55 minutes labeled, ~85 minutes actual)

What supervisor's schedule (Schedule 1) showed: Nothing - just jumped from 6:50 PM last Kaivac to "Lunch" then "7:30 Vacuum admin" (6:50-7:30 gap completely ignored)

What my adaptation (Schedule 2) showed: 6:50-7:45 labeled as "Gap window (detail rotation / visible fillers)" - honest acknowledgment this is plausibility labor, not real cleaning

What actually exists:

• Day shift has exited (6:00-7:00 PM)
• All three Kaivac restrooms completed
• Trash surge from day shift exit already handled
• Building floors clean, restrooms serviced, no production mess

What worker must do (from my field manual):

"Treat ~6:50–8:15 as a dead-zone risk window: stay task-legible or low-visibility."

• Perform detail work (baseboards, high dusting, spot cleaning)
• Rotation tasks (closet org, supply audits, equipment maintenance)
• Stay visible with tools in hand if crossing admin areas
• Route downtime to low-visibility zones (closets, back corridors)
• Avoid admin/break/conference zones without defensible task

Enforcement risk:

"Sitting/idle posture in admin offices, break rooms, main walkways, conference rooms → 'visibility incident' → report/email → paperwork/disciplines."

High-risk zones during dead zones include admin offices, break rooms, main walkways. Presence without tools/task = "legible idleness" = reportable.

Dead Zone #2: 9:35 PM - 11:30 PM (~115 minutes when accounting for conditional tasks)

What supervisor's schedule (Schedule 1) showed:

• 9:35 PM admin clean ends
• "Break" (no timing)
• 9:55-10:55 PM Vacuum production offices (60 min)
• 11:00-11:25 PM Restroom restock (25 min)
• 11:30-11:50 PM Clean break rooms (20 min)
• Shows tasks but leaves 20-minute gap (9:35-9:55) unspecified

What my adaptation (Schedule 2) showed:

• 10:00-10:15 PM Float (restock cart, check Kaivac)
• 10:15-10:30 PM Break #2
• 10:35-11:00 PM Production offices (reduced to 25 min from supervisor's 60)
• Shows all time accounted but acknowledges most post-9:30 work is conditional

What actually exists:

• All restrooms serviced (Kaivac earlier + admin clean just completed)
• Trash collected during day shift exit
• Floors clean, no production mess (day shift gone)
• Building is already clean by 10:30 PM

What worker must do:

• Detail work, preventive tasks, equipment staging
• Stay visible if late admin staff present
• Protect closeout prep time (need full 30 min before midnight for cart/closet/trash/equipment reset)

Enforcement risk:

"Sloppy closeout (carts out, closets messy, trash not staged, Kaivac not rinsed/plugged) → morning read-out complaints → deferred visibility discipline."

Closeout quality judged next morning. If carts messy, closets disorganized, Kaivac not reset = complaint to supervisor = "didn't do job properly" narrative.

Total Dead Zone Time Across Shift: ~3 hours 20 minutes minimum

6:50-8:15 PM: 85 minutes
9:35-11:30 PM: 115 minutes
Plus scattered gaps: Equipment staging (10 min), transitions, forced visibility management

This is structural, not individual failure. Management's schedule shows 2:45 of specific cleaning windows. Shift is 8:30. Management claims "multiple vacuum/clean blocks, two break-room passes, admin restrooms, production offices, plus float/transition time" to account for the gap, but provides no specific timing or task definition for most of these. In practice: Remaining ~5:45 must be filled with equipment staging, quick passes (construction trailer, furnace deck), break-room maintenance, detail work, closeout prep, and "staying visible"-most of which has no posted time windows and becomes plausibility labor to fill dead zones.

From field manual:

"Anchors are real; everything after anchors is conditional; the rest is plausibility labor to keep downtime non-legible."

What It Shows

1. Worker built operational intelligence management should have provided

Management gave vague, incomplete schedule (41% unaccounted). I created minute-by-minute breakdown to survive. Management then blamed me for not meeting schedule I had to create.

2. "Constraints can't be excuses" is base/superstructure inversion

General Manager's February 15 email acknowledged inputs insufficient (equipment readiness, access limits, realistic timing) but demanded outputs anyway (meet schedule exactly). Called variance absorption "subpar performance" rather than acknowledging schedule assumes perfect conditions management won't resource.

3. Dead zones are structural, not worker-created

3+ hours per shift exist where management's schedule shows no tasks but shift hasn't ended. This isn't laziness - it's gap between blocky demand (restrooms need servicing at specific times) and continuous coverage (8.5 hour shift). Management's schedule ignores this. My schedule labeled it honestly. Management blamed me for the gap.

4. Three-schedule framework shows management incompetence → worker compensation → management blame

1. Management failed to provide adequate guidance (Schedule 1: vague, 41% gaps)
2. Worker compensated by building detailed operational map (Schedule 2: worker-created intelligence)
3. Management blamed worker for not meeting schedule worker had to create when material reality (Schedule 3) defeated both

What General Manager Got Wrong

General Manager's February 15 email:

"While I recognize site constraints are real, they can't be used as an excuse for subpar performance."

But here's what makes this particularly absurd:

The schedule he was defending didn't even exist in usable form until I created it:

1. Night Area Supervisor's original schedule (August 14, 2025) left 210 minutes (41% of shift) unaccounted - no break timing, no transitions, no gap guidance, no closeout procedures

2. I built detailed minute-by-minute breakdown to survive - specified all breaks, added transitions, labeled gaps honestly, added setup/closeout

3. My worker-created schedule was MORE detailed than management's - I documented reality management refused to acknowledge

4. General Manager blamed me for not meeting the schedule I had to create because management wouldn't provide adequate operational guidance

The three-schedule analysis proves:

• Management's schedule (Schedule 1) was insufficient - Night Area Supervisor's text left massive gaps, no timing for breaks/lunch, no procedure guidance
• My adaptation (Schedule 2) filled management's gaps - I created the operational intelligence they should have provided
• Even my detailed schedule couldn't compensate for material reality (Schedule 3) - equipment failures, access delays, day shift interference that no schedule can fix

When General Manager said "constraints can't be excuses":

• He was demanding I meet a schedule that didn't exist in actionable form until I created it
• He was blaming me for gaps in operational guidance that MANAGEMENT failed to provide
• He was treating my honest labeling of dead zones ("gap window," "float") as worker failure rather than acknowledging structural reality
• He was refusing to resource the inputs (equipment readiness, realistic timing, access coordination) that would make ANY schedule achievable

This is base/superstructure inversion at its clearest: Management blames worker for "subpar performance" when the actual problem is management providing vague guidance and refusing to resource inputs.

Evidence Note

This exhibit draws from:

• Original text message from Night Area Supervisor (August 14, 2025, 9:25 PM)
• My self-created detailed schedule (developed August 2025 - February 2026)
• Posted facility document "SPK Site Layout w/ Restroom Cleaning Schedule" (Client's facility map showing only Kaivac windows)
• Field manual "Night Shift - How It Actually Runs (v2)" distributed to coworkers February 16, 2026
• General Manager's email February 15, 2026 ("constraints can't be excuses")

All schedules and quotes reproduced verbatim with minimal editing for clarity. Three-schedule framework demonstrates management incompetence → worker compensation → management blame pattern.

Exhibit B

Operations Manager Text Exchange (February 12, 2026)

The February 12 exit-call push and the refusal-to-phone boundary. Format control versus documentation threshold.

Context: On February 12, 2026, the Operations Manager for OneNorth Integrated Facility Solutions attempted to conduct an "exit interview" via phone call. I held a written-only boundary across five escalation attempts spanning approximately one hour. When forced to ask specific questions in writing, he never followed up. This exchange demonstrates how phone calls function as format control to keep conversations below documentation thresholds.

The Exchange

February 12, 2026 · 3:47 PM

Operations Manager:

I just got your resignation notice today. We're sorry to lose you, but understand. I have a couple questions. If you could give me a call when you're free, I'd appreciate it.

My response:

Thanks. Please email me the questions/topics ([email address]) or text me here and I'll reply in writing today. If you still need a call after that, send a few times that work for you and I'll pick one. I'm still planning to work my scheduled shifts through Feb 21 as per my resignation.

Operations Manager:

A phone call would be much easier. I am available right now if you are. I am available from 8am-5pm tomorrow. If I have done something and you are not comfortable talking with me, my boss would be more than happy to take your call. He is available all day tomorrow also. Here is his contact info [General Manager's name and phone number]

My response:

Understood, nothing's wrong and you haven't done anything to make me uncomfortable. I prefer to answer in writing because I've documented the night-shift labor process in detail (workflows, constraints, handoffs), so if you send your questions in writing I can reference specifics and give you the most accurate, actionable answers. Send your questions by text/email and I'll reply today. If anything still needs a call after that, I can schedule one for tomorrow.

Operations Manager:

This is not about what you do or how you do it. But our conversation may bring up questions that I would be happy to submit to you in writing. This is more about company experience work environment, employee relations, supervisor issues.

My response:

Those topics are also detailed in my notes, and I can provide the feedback you need in writing. I'm going to decline discussing it by phone.

Operations Manager:

Will you send me your notes? Or only answer the specific questions I ask?

My response:

I won't be able to send raw notes, but I can answer specific questions.

Time: 4:55 PM

No further contact. The Operations Manager never sent written questions.

What This Shows

The five-attempt sequence followed a predictable escalation: direct request, personalization ("if I've done something to offend you"), escalation lever (offering the General Manager as alternative), scope expansion ("work environment, employee relations, supervisor issues"), raw data extraction ("would you be willing to send me your notes"). Each attempt tried a different angle to get past the written-only boundary. When all five failed, the conversation ended entirely.

The smoking gun is the silence after. If the Operations Manager genuinely wanted exit feedback, written questions would have served that purpose. He never sent them. Format mattered more than content, which means unrecorded extraction was the goal, not information. The final request for raw notes makes this explicit: worker notes are personal documentation, analysis, and organizing infrastructure created on worker's own time. Handing them over gives management unfiltered access to observations about other workers and the ability to reframe worker analysis in management's narrative, without offering anything in return. It came last because it's the biggest ask, positioned after four smaller requests to build compliance momentum.

By holding the written-only boundary, I prevented unrecorded extraction, created evidence of the extraction attempt, and forced everything into a format management could be held accountable for. The General Manager's subsequent email proved the attempts were coordinated: when phone format failed, retention theater via email was the next move.

Format control is narrative control. Phone calls suppress artifacts. Written communication creates them.

Exhibit C

General Manager Email Thread (February 13–16, 2026)

The complete retention theater cycle: solicitation → structural critique → material refusal → immediate resignation → blank response.

Context: Email exchange between myself and the General Manager of OneNorth Integrated Facility Solutions from February 13-16, 2026. This five-email sequence documents the complete retention theater cycle: solicitation for feedback → structural critique with material retention conditions → categorical refusal of pay with expanded documentation requests → immediate resignation → blank response. It shows that retention conversations without decision power are intelligence extraction operations.

The Exchange

EMAIL 1 - General Manager Solicits Feedback (February 13, 3:32 PM)

From: General Manager, OneNorth
To: Stephen Hibpshman
Subject: Follow Up/Feedback Regarding Your Notice
Date: Thursday, February 13, 2026, 3:32 PM

Good Afternoon Stephen,

I understand that you've given your notice, and I'm sorry to see you leaving OneNorth. [The Operations Manager] mentioned that you'd prefer to communicate electronically; while I always value a live conversation, I'm happy to respect your preference and reach out this way instead.

First, I want to thank you for your time with us. You've been a great teammate and a reliable worker at Collins. When we first spoke last summer, you mentioned a potential move around early 2026. I wanted to see if your departure aligns with that original timeline, or if there are specific issues at the jobsite that influenced your decision to leave sooner.

If there are things we can improve on-site or changes that need to be made, I'd truly value your honest feedback. My goal is to make sure we're supporting the team properly.

I'm still open to a quick call if you change your mind, but please feel free to reply here with any thoughts you're comfortable sharing.

Best regards,

[General Manager signature]

EMAIL 2 - My Structural Critique with Retention Conditions (February 13, 3:54 PM)

From: Stephen Hibpshman
To: General Manager, OneNorth
Date: Thursday, February 13, 2026, 3:54 PM

Good Afternoon,

Thanks for reaching out. I appreciate you coordinating with me over email so I can communicate with accuracy and clarity.

My departure does not align with what we discussed last summer. At the time, I expected to return to school around early 2026. I decided not to do that, and my intent was to stay with OneNorth. The fact that I'm resigning anyway is a sign that conditions at the Collins site outweighed the reasons to stay.

On retention, pay matters, but it has to match the reality of the assignment. At Collins, the job has become high-pressure in a way that doesn't show up in the job description. A lot of performance is judged by paperwork and "proof" (logs, notes, timestamps, who saw what) rather than just the actual condition of the work and trust in employees (especially the site supervisor) to meet the standard. When supplies run low, access is limited, or restroom closure windows are tight, the schedule and expectations don't adjust-workers absorb it, and it can later be treated as a performance issue. That mix wears people down.

Separately, there has been an ongoing employee-relations issue on day shift (M.). I'm not going to reduce my resignation to a single person, but his pattern of passive-aggressive notes and antagonistic behavior around shared processes has made cross-shift coordination harder. If you need corroboration, I can provide a few specific examples.

If you want actionable changes that would improve retention at Collins:

1. Make expectations match the real work. Set clear, realistic standards based on actual task times, access limits, supply availability, and the way shifts hand off to each other.
2. Reduce vague or last-minute directives and avoid judging people after the fact without context. If something is required, make it specific: what, where, by when, and why.
3. Fix recurring choke points: supply availability/access, equipment availability, and realistic restroom closure windows that align with the site conditions. There has been an issue with coordination between the client and operations level management, sometimes taking weeks to receive word on changes and pertinent information regarding site conditions. This has led to us interfacing directly with the client more often than not rather than escalating up the chain of command. These are predictable reasons tasks slip and then become "issues."
4. Support clean cross-shift handoffs instead of relying on paperwork as the main control tool. The site runs better when shifts share accurate information, not when the log becomes a way to assign blame.

If OneNorth wants to discuss retention of myself directly: over the last couple months I've had to train several new employees and standardize routines myself just to keep the site stable across handoffs. If you want me to stay, it would require a materially different Collins setup (less "gotcha" compliance pressure, more realistic workflow/time windows, and stable cross-shift cooperation) and a pay rate that reflects both the conditions of the assignment and the extra training/standardization load I've been carrying. Otherwise, resignation remains my plan.

I'm happy to answer specific follow-up questions.

Regards,
Stephen Hibpshman

EMAIL 3 - General Manager's Extraction Request + Material Refusal (February 15, 9:25 AM)

From: General Manager, OneNorth
To: Stephen Hibpshman
Date: Saturday, February 15, 2026, 9:25 AM

Hi Stephen,

I appreciate you laying this out with such clarity. It's helpful to see the gap between the "official" job and the daily reality you're experiencing.

I want to be transparent: as a commercial contractor, we have a firm obligation to meet the customer's scope of work. Collins pays for a specific result, and we have to deliver that to keep the contract. While I recognize site constraints are real, they can't be used as an excuse for subpar performance; however, I don't want our internal environment making your job harder than it needs to be.

To help me address this, I'd like more detail on a few specific areas:

1. Documentation & M.
You mentioned that the communication log is being used by M. to assign blame.

• Request: Could you provide a few specific examples or photos of these notes? If the log is being used as a weapon rather than a tool, I need to see it so I can address the behavior immediately. We want a culture of respect, and I won't tolerate behavior that negatively impacts the team.

2. Supply & Equipment Choke Points
To ensure the site stays stable, I need to know which specific supplies or equipment are consistently missing and whether they are OneNorth or client-provided. This helps me determine if I need to escalate this to the client or fix our internal ordering.

3. Training and Standardization
You mentioned you've been training new employees and standardizing routines. While I value that you've stepped up to keep the site stable, this concerns me because we have supervisors and protocols in place for onboarding.

• Request: Which specific employees did you train, and what routines did you standardize? Have you shared these insights or the issues with the training process with [Site Supervisor]/[Night Supervisor]/[Operations Manager]? I need to understand why this didn't go through the proper supervisory channels and instead was performed by you.

Moving Forward
Stephen, you've proven yourself to be a reliable teammate over the last six months. I'd hate to lose someone with your eye for detail and your willingness to lead. While I can't offer a pay adjustment at this time-as those are earned through tenure and consistent production over time-I can commit to fixing the culture and the "choke points" you've identified.

If we can resolve the issues with M. and streamline the supply and training process, I'd love to keep you on the team. I believe you have the potential to grow with OneNorth as we continue to improve the Collins site.

While I'm happy to keep this in email, I would still welcome a 15-minute meeting. A quick conversation is often the best way to ensure your feedback leads to the changes you want to see.

Please send over those examples regarding M. and the training when you can.

Best regards,

[General Manager signature]

EMAIL 4 - My Immediate Resignation (February 16, 3:30 PM)

From: Stephen Hibpshman
To: General Manager, OneNorth
Date: Sunday, February 16, 2026, 3:30 PM

[General Manager],

I'm resigning effective immediately. I will arrive on schedule to drop off any company property in my possession.

Your last email made it clear that OneNorth is not interested in addressing the structural conditions I raised. You asked for detailed documentation and operational breakdowns, but you also stated that pay adjustments are categorically unavailable and framed my feedback as a compliance problem rather than a site management problem. You are trying to extract data from me instead of having a concrete retention conversation.

I'm not interested in providing free consulting to fix problems you've already decided not to resource properly. I'm also not available for a call, meeting, or further written requests for "examples" and "specifics" unless you're prepared to make material changes to the job itself.

Why I'm Leaving

You wrote: "While I recognize site constraints are real, they can't be used as an excuse for subpar performance."

That sentence is the problem. The "constraints" I described aren't excuses-they're the material conditions of the work. When the Kaivac isn't reliably usable, when supplies aren't staged properly, when restroom closure windows don't align with the actual time required to complete the scope, and when new hires are onboarded during production because there's no dedicated training coverage, the worker absorbs the gap. You can call that "subpar performance" if you want, but it's a predictable outcome of under-resourced site management.

You also asked me to document M.'s behavior, supply choke points, and the training I performed, but you didn't commit to fixing any of it. You committed to "addressing the culture" and "streamlining the process," which are non-answers. If you were serious about retention, you would have said: "We'll establish a formal night lead role with adjusted pay, we'll add dedicated onboarding coverage, and we'll define a Kaivac readiness protocol with clear ownership." You didn't. You asked for more data and offered nothing.

That tells me everything I need to know.

On M.

Attached are the photos I documented (drawings + comms/log examples). This includes material left on shared surfaces and examples of the comms log being used in a passive-aggressive/blame-assigning way rather than a neutral coordination tool.

Note: Some of the drawings contain imagery that reads as antisemitic stereotypes. Regardless of intent, placing that content on shared work surfaces affects the work environment and cross-shift relations.

[Attachments: 20251228_143059.jpg, 20251115_170859.jpg, image.png, image.png]

I'm providing this documentation, but I want to be clear: if you're approaching this as "find the bad employee," you'll use whatever I send to isolate M. and declare the issue resolved. That doesn't fix the underlying coordination failures, the passive-aggressive blame culture, or the structural handoff problems between shifts.

The real issue is this: the communication log and documentation requirements are being used as post-hoc performance management tools instead of live coordination tools. Workers are judged after the fact based on whether they "proved" they did the work, not on whether the work was actually done to standard. That creates an incentive to cover your ass in writing rather than collaborate across shifts. M. is operating inside that system. Removing him won't fix it.

On Training and Standardization

You wrote: "I need to understand why this didn't go through the proper supervisory channels and instead was performed by you."

It went through the Site Supervisor. I coordinated with him continuously. The problem is that the Site Supervisor is scheduled as production labor with his own cleaning route. He can't pause production to onboard new hires without falling behind on the same scope you're holding him to. So in practice, new hires get trained by whoever is physically present during production. That was me for the night shift.

If you think that's a problem, the fix is to add dedicated onboarding coverage or reduce the Site Supervisor's production load during turnover periods. Asking me to explain why I "took it upon myself" to train people misses the point: I didn't take it upon myself. The site required it, and no one else was available to do it without cannibalizing their own scope.

On Supply and Equipment

You asked for specifics on which supplies are missing and whether they're OneNorth or client-provided. I already told you: the issue is equipment readiness, not missing soap. The Kaivac and its parts/condition are the primary choke point. The fix is to treat Kaivac readiness as a required input with clear ownership, a defined restock/replacement cadence, and an unambiguous escalation path.

I built cart/closet stocking checklists and a readiness protocol for my own night routes because this layer wasn't stable or standardized. If you want to replicate that across shifts, go ahead. But don't ask me to do the work of designing it for you when you've already said you're not willing to pay for it.

Final Word

I gave you a clear, actionable list of changes that would improve retention at Collins. You responded by asking for more documentation, deflecting responsibility onto "proper supervisory channels," and offering no material changes to the job. That's you performing management theater.

I'm out.

Stephen Hibpshman

EMAIL 5 - General Manager's Blank Response (February 16, 3:36 PM)

From: General Manager, OneNorth
To: Stephen Hibpshman
Date: Sunday, February 16, 2026, 3:36 PM

[No content-signature block only]

What This Exchange Shows

1. The Complete Retention Theater Cycle

Step 1: Solicitation (February 13, 3:32 PM)
General Manager requests "honest feedback" with collaborative language: "sorry to see you leaving," "great teammate," "I'd truly value your honest feedback." Creates appearance of partnership and genuine concern.

Step 2: Structural Critique with Material Conditions (February 13, 3:54 PM)
I provide detailed analysis of site problems with four actionable fixes. I state material retention conditions explicitly: "materially different Collins setup... and a pay rate that reflects both the conditions of the assignment and the extra training/standardization load."

Step 3: Material Refusal + Extraction Request (February 15, 9:25 AM)
General Manager categorically refuses pay ("I can't offer a pay adjustment at this time-as those are earned through tenure"), offers vague symbolic concessions ("fixing the culture"), and requests detailed documentation (photos, examples, names of employees trained, supply lists, OneNorth vs. client designation).

Step 4: Immediate Resignation (February 16, 3:30 PM)
I recognize extraction pattern, resign immediately, provide bounded documentation with anti-scapegoat framing embedded, refuse further consulting.

Step 5: Blank Response (February 16, 3:36 PM)
General Manager sends email with signature only, no content. No acknowledgment, no response, nothing.

The cycle proves: Retention conversations are only real if material terms are negotiable. Otherwise, it's intelligence-gathering dressed as feedback.

2. "Constraints Can't Be Excuses" - Base/Superstructure Inversion in One Sentence

The General Manager wrote:

"While I recognize site constraints are real, they can't be used as an excuse for subpar performance."

This sentence reveals the fundamental contradiction:

What it acknowledges: Material conditions exist (equipment readiness, supply availability, realistic time windows, staffing for training)

What it demands: Worker meet performance standards anyway

What it moralizes: Variance absorption (the gap between insufficient inputs and demanded outputs) as worker failure

This is base/superstructure inversion: Management admits the foundation (base) is insufficient, but demands the structure (performance standards, compliance) stand anyway, then blames the worker when it doesn't.

My response:

"The 'constraints' I described aren't excuses-they're the material conditions of the work. When the Kaivac isn't reliably usable, when supplies aren't staged properly, when restroom closure windows don't align with the actual time required to complete the scope, and when new hires are onboarded during production because there's no dedicated training coverage, the worker absorbs the gap. You can call that 'subpar performance' if you want, but it's a predictable outcome of under-resourced site management."

3. Extraction Pattern - Scope Expansion After Each Response

Initial request: "Honest feedback," "any thoughts you're comfortable sharing"

After detailed critique, becomes:

• Specific examples of M.'s behavior (photos requested)
• Supply lists with OneNorth vs. client designation
• Names of employees I trained
• Documentation of routines I standardized
• Explanation of why I "took it upon myself" to train
• Commitment to "share insights" through "proper supervisory channels"

Each response triggered larger extraction request. Scope expanded from "thoughts" to granular operational intelligence-all while material changes remained categorically unavailable.

4. Deflection to Process - Converting Structural Problems into Worker Failures

I documented: Site Supervisor is scheduled as production labor, can't onboard new hires without falling behind on his own scope, so training falls to whoever's present during production.

General Manager reframed: "I need to understand why this didn't go through the proper supervisory channels and instead was performed by you."

This converts:

• Structural problem (supervisor can't train without cannibalizing production) into
• Worker process failure (you didn't follow channels)

My response:

"It went through the Site Supervisor. I coordinated with him continuously. The problem is that the Site Supervisor is scheduled as production labor with his own cleaning route. He can't pause production to onboard new hires without falling behind on the same scope you're holding him to."

This protected the Site Supervisor explicitly while forcing the structural problem back into view.

5. Material Refusal as Deal-Breaker

General Manager: "I can't offer a pay adjustment at this time-as those are earned through tenure and consistent production over time."

Pay categorically off the table while requesting free operational consulting (photos, breakdowns, training documentation, supply analysis). This proves retention was never the goal-the conversation was extraction from the start.

I resigned the next day.

Evidence Note

This email exchange occurred February 13-16, 2026 via company email between myself and the General Manager of OneNorth Integrated Facility Solutions. All five emails reproduced verbatim with minimal redactions for publication (names changed to titles/initials, personal identifying details removed).

Attachments referenced in Email 4 (M. documentation) are documented separately in Exhibit D.

This exchange demonstrates the complete retention theater cycle: solicitation → material refusal → extraction → exit. The pattern is replicable across low-wage jobs where management wants intelligence without offering resources.

Exhibit D

Hostile Work Environment Documentation

Communication log weaponization and shared workspace drawings documented as operational exposure and constructive knowledge.

Context: Selected documentation of a day shift worker's use of shared coordination tools (communication log, workspace drawings) as passive-aggressive control mechanisms. Submitted to management February 16, 2026 in my resignation email with explicit anti-scapegoat framing: "M. is operating inside that system. Removing him won't fix it."

Purpose: Tactical solidarity - removing obstacle to crew function while preventing management from using "bad egg" narrative to avoid addressing systemic issues.

Editorial Decision: Describe, Don't Reproduce

This exhibit DESCRIBES photo evidence but does not reproduce antisemitic imagery.

Why:

1. Reproducing harm vs. documenting pattern: Antisemitic imagery causes harm when reproduced. Description serves the tactical purpose (showing the pattern exists) without amplifying harm.
2. Prevents "racist janitor" framing: Publishing images risks exhibit becoming "look at the bad guy" story instead of system analysis. Description keeps focus on structural mechanism.
3. Evidence exists in official record: Photos were submitted to the General Manager February 16, 2026. Management has constructive knowledge. I don't need to re-publish to show documentation occurred.
4. Organizing principle: Show the pattern, name the mechanism, prevent scapegoating. Don't make the exhibit about individual pathology.

Communication Log Entries (Pattern Evidence)

Context: The communication log was worker-initiated infrastructure, not management-provided. The Night Area Supervisor had given us official log sheets weeks earlier. I found them, formalized the log by hanging it in the supply cage, and coordinated with the Site Supervisor to make it actually useful for cross-shift handoffs-solving real operational coordination problems between day and night shifts. Within approximately two weeks of implementation (early-to-mid February 2026), M. (day shift) began using it for passive-aggressive commentary targeting night shift operational decisions.

Selection criteria: Entries showing pattern of:

• Aggressive formatting and tone
• Sarcastic "advice" framing routine work as worker failure
• Accusations without evidence or verification

Example 1: Trash Accusation (February 7, 2026)

M.'s log entry (verbatim from photo):

"Don't leave trash in anything!!!!!"

What this shows:

• Multiple exclamation points (five) = aggressive tone
• "Don't leave trash in anything" - command, not coordination request
• No specifics: What trash? Where? Was this actually found or preemptive complaint?
• "anything" is maximally vague - can mean trash cans, supply areas, equipment, anywhere
• Can't verify or dispute because no evidence provided

What this does:

• Creates paper trail implying night shift leaves workspace dirty
• Unfalsifiable (so vague it can't be disproven)
• Aggressive tone in shared tool
• Forces defensive response or silence (both bad options)

Example 2: Work Ethic Accusation (February 8, 2026)

M.'s log entry (verbatim from photo):

"Pro tip: standing in the cage for hours on end is not working."

What this shows:

• "Pro tip" is sarcastic framing - condescending tone
• Direct accusation: night shift "standing in the cage for hours on end"
• Implies worker is shirking ("not working")
• No evidence: How does M. know night shift stood in cage? Was he there?
• Accusation is impossible - night shift works 3:30 PM-12:00 AM, M. works day shift (not present to observe)

What this does:

• Accuses night shift of time theft with zero evidence
• Sarcastic "pro tip" format mocks while accusing
• Creates narrative: night shift hides in supply cage instead of working
• M. can't have observed this (different shifts) - pure fabrication
• Weaponizes shared log to create "lazy night shift" story for management

Pattern Analysis

What these entries reveal:

NOT coordination:

• No specific information (where was trash? what task wasn't done?)
• No verifiable claims (M. can't observe night shift - works different hours)
• No actionable requests (what does M. want night shift to do differently?)

IS documentation theater:

• Creates paper trail of "night shift problems"
• Aggressive/sarcastic tone establishes hostility
• Unfalsifiable accusations (too vague or unverifiable to dispute)
• Builds narrative for management review

Key tell - the cage accusation: M. works day shift. Night shift works 3:30 PM-12:00 AM. M. cannot observe night shift "standing in the cage for hours on end" because he's not present during those hours. This isn't mistaken observation - it's fabricated accusation weaponizing coordination infrastructure I'd formalized only weeks earlier to solve actual handoff problems.

Timeline context: The formalized log had been operational for approximately two weeks when these entries appeared. Worker-initiated coordination tool became weaponized within weeks of implementation when management oversight remained absent.

What coordination entries should look like:

• Specific information: "Restroom 3 out of paper towels"
• Verifiable: Can check if true
• Actionable: Clear what's needed
• Neutral tone: "FYI" not "Pro tip"
• During own shift: Report what you observe during your hours

M.'s entries fail all criteria.

Drawing Evidence (4chan-Style Antisemitic Imagery)

Photos submitted to General Manager February 16, 2026:

Location: Cardboard left in supply cage (shared workspace) where night shift accesses supplies, stages equipment, and performs routine work.

Primary Evidence: Cardboard with Multiple Offensive Caricatures (4chan Aesthetic)

Description (not reproduced):

This cardboard surface contains multiple crude drawings in what I identified as "4chan style" antisemitic imagery - characterized by deliberately crude aesthetic, mixing multiple offensive stereotypes, and "ironic" hate framing that creates plausible deniability.

Visual elements present:

• Multiple human figures drawn in intentionally crude style
• Text reading "U CAN'T CROSS EVERYTHING OUT" (central, prominent)
• Figure with text on clothing referencing antisemitic "goy" slur
• Center: Figure in wheelchair (disability mockery)
• Multiple figures with exaggerated facial features consistent with racist/antisemitic caricature traditions
• Scattered additional markings and crude drawings
• Overall composition: approximately 8-10 separate drawn elements across cardboard surface

4chan aesthetic markers:

• Deliberately crude drawing style (amateur, "just doodling" appearance)
• Multiple offensive stereotypes mixed together (antisemitism + disability mockery + others)
• "Ironic" framing via crude style (creates plausible deniability - "just cartoons")
• Insider signaling (recognizable to those familiar with chan-board hate culture)
• Text element "U CAN'T CROSS EVERYTHING OUT" suggests previous removal attempts and defiance

Context:

• Supply cage is shared workspace - both shifts must access this area
• Cardboard used as drawing surface, left prominently displayed
• Night shift worker encounters this during:
  • Supply retrieval (multiple times per shift)
  • Equipment staging (Kaivac prep, cart loading)
  • Closeout procedures (inventory checks, restocking)
• No operational purpose - purely expressive/decorative content
• Size and placement ensure visibility during routine work

What "4chan style" signifies:

This aesthetic is not random doodling. It's a specific internet hate culture style characterized by:

• Plausible deniability: Crude style allows "just joking" defense
• Insider recognition: Those familiar with chan boards recognize the signaling
• Multiple targets: Mixing offensive stereotypes (antisemitism, disability mockery, etc.) in single image
• Defiant persistence: "U CAN'T CROSS EVERYTHING OUT" text suggests this is response to previous removal attempts
• Ironic detachment: Crude style creates distance ("not serious" defense) while delivering serious harm

Impact on workplace:

• Creates hostile environment in space worker must use to perform job
• Can't avoid encountering (supply cage essential to shift operations)
• Reporting risks "can't take a joke" dismissal (plausible deniability built into aesthetic)
• Associates routine work tasks (getting supplies) with harassment exposure
• "U CAN'T CROSS EVERYTHING OUT" implies this is intentional, repeated behavior resistant to intervention

Additional Evidence: "Billions Thrown Away" Image

Description (not reproduced):

• Separate cardboard piece with figure and speech bubble
• Text: "billions thrown away"
• Visual style and phrasing consistent with antisemitic financial control conspiracy theories
• Same crude aesthetic as primary image

Context:

• Also found in supply cage/shared workspace area
• "Billions" language evokes antisemitic tropes about Jewish financial manipulation/waste
• Reinforces pattern: this isn't isolated incident but sustained hostile environment

Pattern Across Evidence

Communication log + drawings = coordinated hostile environment:

Log entries (Feb 7-8):

• Aggressive accusations ("Don't leave trash in anything!!!!!")
• Fabricated work ethic attack ("standing in the cage for hours on end is not working")
• Sarcastic, mocking tone ("Pro tip:")

Drawings (multiple over time):

• 4chan-style antisemitic imagery
• Disability mockery
• Financial conspiracy theory language
• "U CAN'T CROSS EVERYTHING OUT" defiance

Combined effect:

• Shared coordination tools weaponized (log entries)
• Shared workspace made hostile (drawings)
• Worker must engage with both to perform job
• Plausible deniability built in ("just log entries," "just doodles")
• Pattern shows intentionality, not random conflict

What This Shows

1. Worker-Initiated Tools Need Oversight Too

I formalized the communication log to solve real coordination problems-found the official log sheets the Night Area Supervisor had provided weeks earlier, hung them in the supply cage, worked with the Site Supervisor to make them useful for actual shift handoffs. Within two weeks, M. was weaponizing it. Entries weren't verified before traveling up chain as "night shift problems." No management review meant unilateral narrative control. Drawings in the same shared workspace created hostile environment without consequence.

The lesson isn't that workers shouldn't create coordination infrastructure. The lesson is that even well-intentioned worker-initiated tools become control mechanisms when oversight is absent. System enabled this behavior through supervision gaps, not through the tool's existence. Individual removal won't fix oversight gap that allows any coordination tool-management-created or worker-created-to be weaponized.

2. Hostile Environment ≠ Just "Interpersonal Conflict"

Management frames workplace conflicts as personality clashes requiring mediation. But antisemitic imagery isn't interpersonal - it's harassment. Passive-aggressive log entries aren't communication issues - they're weaponized documentation creating liability. Framing as "M. vs. Night Shift" individualizes systemic failure to supervise shared tools.

3. Documentation with Structural Framing Prevents Scapegoating

When worker submits evidence of M.'s behavior, management's easy response: "We'll deal with M." (fire him, transfer him, "talk to him"). Problem appears solved. But:

• Communication log still exists as unilateral control surface
• No defined standards for equipment staging or supply documentation
• No oversight of what gets written in log
• No review of workspace for hostile content

I fused evidence to structural analysis: "M. is operating inside that system. Removing him won't fix it." Makes it impossible to extract evidence (photos, log entries) without importing critique (oversight gaps, tool weaponization, hostile environment enablement).

4. Removing Obstacle ≠ Moral Performance

This isn't about M. being "bad person" and me being "good person calling out racism." It's cold tactical calculation:

Problem: M.'s behavior was obstacle to crew function

• Log entries created defensive labor (night shift had to respond or look incompetent)
• Drawings created hostile environment (night shift encountered harassment during routine work)
• Coordination tools became individual accountability traps (shared log = unilateral narrative weapon)

Solution: Document pattern + embed structural mechanism + submit on exit

• Pattern proves this isn't one-off incident (multiple log entries, multiple drawings over months)
• Structural framing prevents "bad egg" collapse (removing M. doesn't fix oversight)
• Exit timing maximizes impact (can't be retaliated against, management must respond in official record)

Outcome: Removes obstacle while protecting remaining workers from "M. was the whole problem" narrative

Tactical Solidarity Framework

Why this matters for other workers:

Most workplace harassment documentation follows this pattern:

1. Worker experiences problem (hostile behavior, weaponized tools)
2. Worker reports to management
3. Management "deals with" individual (firing, discipline, transfer)
4. Problem appears solved
5. System that enabled behavior remains unchanged
6. Next person fills same role, behavior repeats

Anti-scapegoat organizing prevents this cycle:

Step 1: Document the Pattern (Not Just Incidents)

Bad: "M. drew an antisemitic image on Dec 28"
Good: "Multiple antisemitic drawings over 2+ months in shared workspaces" + photos timestamped

Why: Single incident = individual "bad day." Pattern = enabled behavior.

Step 2: Name the Mechanism (Not Just the Person)

Bad: "M. is hostile and needs to be removed"
Good: "Communication log operates as unilateral control mechanism when entries aren't verified. Workspace supervision absent allows hostile content to persist."

Why: Naming mechanism makes removal insufficient response. Management must address system.

Step 3: Fuse Evidence to Analysis (Make Them Inseparable)

Bad: Submit photos, let management interpret
Good: Submit photos + structural framing in same document ("M. is operating inside that system. Removing him won't fix it.")

Why: Management can't extract facts without importing your critique. Evidence travels with analysis.

Step 4: Protect Remaining Workers (Prevent "Problem Solved" Narrative)

Bad: Hope management fixes system after removing individual
Good: Explicitly document what system changes are required (log entry review, workspace supervision, defined standards)

Why: Creates accountability for actual fixes, not just individual removal.

Step 5: Time Submission Strategically (Maximize Impact, Minimize Retaliation)

Bad: Report during employment, hope for best
Good: Document during employment, submit on exit in official channel (resignation email)

Why: Can't be retaliated against after exit. Management has constructive knowledge in official record. Creates discoverable liability.

What General Manager Received (February 16, 2026)

Email attachment description (from my resignation email):

"I'm also attaching documentation of M.'s passive-aggressive communication log entries and drawings left in shared workspace areas. Some of this content includes antisemitic imagery and stereotypes. I want to be clear: M. is operating inside that system. Removing him won't fix it. The communication log operates as a unilateral control mechanism when entries aren't verified against actual conditions. The workspace lacks supervision, allowing hostile content to persist for months. These aren't interpersonal conflicts - they're system failures that create liability."

Attachments:

• 20251228_143059.jpg (antisemitic caricature in supply cage)
• 20251115_170859.jpg (antisemitic symbolism in handoff area)
• image.png (×2 - additional examples)

What this achieves:

1. Constructive knowledge: General Manager now has official notice of antisemitic harassment in workplace
2. Liability documented: If OneNorth doesn't investigate/address, they have constructive knowledge of hostile environment
3. Anti-scapegoat embedded: "Removing him won't fix it" prevents "we fired M." from being sufficient response
4. System failures named: Log verification, workspace supervision explicitly identified as gaps
5. Protects remaining workers: Site Supervisor and other day shift workers protected from "you should have reported this" blame (night shift worker reported on exit)

For Other Workers: When and How to Use This Approach

When to Use This Approach:

✅ DO use when:

• Behavior creates obstacle to crew function (not just "annoying")
• Pattern is documented (multiple incidents over time)
• System enablement is clear (oversight gaps, weaponized tools)
• You're exiting anyway (removes retaliation risk)
• Evidence serves tactical purpose (protects remaining workers, prevents scapegoating)

❌ DON'T use when:

• Single incident (not pattern)
• Interpersonal conflict (can be resolved through communication)
• You need to maintain working relationship (still employed)
• Evidence is weak or ambiguous
• Would expose other workers to retaliation

How to Execute:

1. Document pattern during employment - Timestamp each incident, screenshot/photo evidence, note location/context
2. Identify system enablement - What oversight failed? What tools were weaponized? What standards are absent?
3. Draft structural framing - "X is operating inside Y system. Removing X won't fix Y."
4. Fuse evidence to analysis - Submit together in same document, make them inseparable
5. Submit on exit in official channel - Resignation email, exit interview response, official company email
6. Name required system changes - Explicitly state what fixes are needed (not just individual removal)
7. Protect remaining workers - Document how system failures affected crew, prevent blame-shifting

Goal: Remove obstacle + prevent scapegoat narrative + protect remaining workers + create management liability for systemic failures.

This is tactical solidarity in practice.

Evidence Note

This exhibit draws from:

• Communication log entries (February 7-8, 2026) photographed and preserved. Log was worker-initiated coordination infrastructure, I formalized it using official log sheets the Night Area Supervisor had provided weeks earlier, hanging them in supply cage and coordinating with Site Supervisor to make them useful for shift handoffs. Weaponized within approximately two weeks of implementation.
• Photographs of drawings in shared workspace (supply cage at the client facility)
• My resignation email to General Manager (February 16, 2026) containing M. documentation with anti-scapegoat framing
• Field observations of hostile work environment created by weaponized coordination tools

All log entries reproduced verbatim. Drawing descriptions based on actual photographs submitted to management but not reproduced here to avoid amplifying harm. Structural framing preserved as submitted in official company email.

This documentation demonstrates how coordination infrastructure (even worker-initiated tools designed to solve real operational problems) can be weaponized when oversight is absent, and how anti-scapegoat framing in official submissions prevents management from treating systemic problems as individual pathology.

Exhibit E

Resignation Email (February 16, 2026)

Immediate resignation sent via company email as tactical record move: discoverability, constructive knowledge creation, and refusal of unpaid intelligence.

Context: Immediate resignation email sent to the General Manager of OneNorth Integrated Facility Solutions on February 16, 2026 at 3:30 PM, terminating employment effective same day. This email refuses further intelligence extraction, provides documentation with anti-scapegoat framing embedded, protects the Site Supervisor explicitly, and names management behavior as "theater." Sent via official company email system, creating timestamped, discoverable record.

Purpose: This exhibit demonstrates how to weaponize official compliance systems-using the same channels management designed for control to create management liability and preserve worker analysis in institutional record.

The Email

From: Stephen Hibpshman
To: General Manager, OneNorth
Date: Sunday, February 16, 2026, 3:30 PM

[General Manager],

I'm resigning effective immediately. I will arrive on schedule to drop off any company property in my possession.

Your last email made it clear that OneNorth is not interested in addressing the structural conditions I raised. You asked for detailed documentation and operational breakdowns, but you also stated that pay adjustments are categorically unavailable and framed my feedback as a compliance problem rather than a site management problem. You are trying to extract data from me instead of having a concrete retention conversation.

I'm not interested in providing free consulting to fix problems you've already decided not to resource properly. I'm also not available for a call, meeting, or further written requests for "examples" and "specifics" unless you're prepared to make material changes to the job itself.

Why I'm Leaving

You wrote: "While I recognize site constraints are real, they can't be used as an excuse for subpar performance."

That sentence is the problem. The "constraints" I described aren't excuses-they're the material conditions of the work. When the Kaivac isn't reliably usable, when supplies aren't staged properly, when restroom closure windows don't align with the actual time required to complete the scope, and when new hires are onboarded during production because there's no dedicated training coverage, the worker absorbs the gap. You can call that "subpar performance" if you want, but it's a predictable outcome of under-resourced site management.

You also asked me to document M.'s behavior, supply choke points, and the training I performed, but you didn't commit to fixing any of it. You committed to "addressing the culture" and "streamlining the process," which are non-answers. If you were serious about retention, you would have said: "We'll establish a formal night lead role with adjusted pay, we'll add dedicated onboarding coverage, and we'll define a Kaivac readiness protocol with clear ownership." You didn't. You asked for more data and offered nothing.

That tells me everything I need to know.

On M.

Attached are the photos I documented (drawings + comms/log examples). This includes material left on shared surfaces and examples of the comms log being used in a passive-aggressive/blame-assigning way rather than a neutral coordination tool.

Note: Some of the drawings contain imagery that reads as antisemitic stereotypes. Regardless of intent, placing that content on shared work surfaces affects the work environment and cross-shift relations.

[Attachments: 20251228_143059.jpg, 20251115_170859.jpg, image.png, image.png]

I'm providing this documentation, but I want to be clear: if you're approaching this as "find the bad employee," you'll use whatever I send to isolate M. and declare the issue resolved. That doesn't fix the underlying coordination failures, the passive-aggressive blame culture, or the structural handoff problems between shifts.

The real issue is this: the communication log and documentation requirements are being used as post-hoc performance management tools instead of live coordination tools. Workers are judged after the fact based on whether they "proved" they did the work, not on whether the work was actually done to standard. That creates an incentive to cover your ass in writing rather than collaborate across shifts. M. is operating inside that system. Removing him won't fix it.

On Training and Standardization

You wrote: "I need to understand why this didn't go through the proper supervisory channels and instead was performed by you."

It went through the Site Supervisor. I coordinated with him continuously. The problem is that the Site Supervisor is scheduled as production labor with his own cleaning route. He can't pause production to onboard new hires without falling behind on the same scope you're holding him to. So in practice, new hires get trained by whoever is physically present during production. That was me for the night shift.

If you think that's a problem, the fix is to add dedicated onboarding coverage or reduce the Site Supervisor's production load during turnover periods. Asking me to explain why I "took it upon myself" to train people misses the point: I didn't take it upon myself. The site required it, and no one else was available to do it without cannibalizing their own scope.

On Supply and Equipment

You asked for specifics on which supplies are missing and whether they're OneNorth or client-provided. I already told you: the issue is equipment readiness, not missing soap. The Kaivac and its parts/condition are the primary choke point. The fix is to treat Kaivac readiness as a required input with clear ownership, a defined restock/replacement cadence, and an unambiguous escalation path.

I built cart/closet stocking checklists and a readiness protocol for my own night routes because this layer wasn't stable or standardized. If you want to replicate that across shifts, go ahead. But don't ask me to do the work of designing it for you when you've already said you're not willing to pay for it.

Final Word

I gave you a clear, actionable list of changes that would improve retention at Collins. You responded by asking for more documentation, deflecting responsibility onto "proper supervisory channels," and offering no material changes to the job. That's you performing management theater.

I'm out.

Stephen Hibpshman

What This Email Shows

1. Weaponizing the Official System

Sent via company email, creating timestamped, attributable, discoverable record in OneNorth's institutional system. Management cannot delete or "misremember" this. If lawsuit, investigation, or audit occurs, this email is part of official record.

Why this matters: Official channels are designed for management control-email retention for liability management, documentation for discipline. But those same channels preserve worker-authored analysis in forms management can't erase.

2. Facts Fused to Structural Framing

I provided exactly what management requested (M. documentation, training details, equipment specifics) but embedded my analysis in same document. Impossible to extract evidence without importing structural critique. Every factual claim travels with mechanism explanation.

Examples:

• M.'s drawings documented + "M. is operating inside that system. Removing him won't fix it."
• Training burden documented + Site Supervisor's constraint named + structural fix specified
• Equipment issues documented + ownership gap identified + responsibility deflection called out

3. Liability Creation Through Documentation

Antisemitic imagery documented in official company email = constructive knowledge. Management now has legal obligation to investigate or document why they chose not to. Creates institutional record of hostile work environment that survives beyond my individual departure.

4. Anti-Scapegoat Framing Prevents Narrative Collapse

"If you're approaching this as 'find the bad employee,' you'll use whatever I send to isolate M. and declare the issue resolved."

Explicitly blocks management from converting M.'s removal into declaration of victory. Forces acknowledgment that individual removal doesn't fix systemic coordination failures.

This prevents:

• "Bad egg" narrative (individual pathology explains systemic problem)
• Premature problem closure (management declares issue solved via removal)
• Harm to remaining workers (next person faces same system)

5. Protecting Site Supervisor Through Documentation

Site Supervisor explicitly named as coordinating continuously, with his constraints documented (scheduled as production labor, can't onboard without scope loss). Blocks management from scapegoating supervisor for worker-provided training.

This protects:

• Horizontal solidarity (doesn't blame Site Supervisor)
• Structural analysis (names actual cause: understaffing)
• Remaining workers (prevents "you should have escalated" narrative)

Nine Tactical Deployment Moves

These are offensive uses of official systems-not defensive compliance.

Move 1: Immediate Resignation as Rupture

"Effective immediately" terminates extraction window before management can expand requests further. No notice period, no gradual transition, no additional "feedback" sessions.

Function: Prevents management from using remaining work period to extract more intelligence or pressure toward phone call. Exit happens on my timeline, not theirs.

Move 2: Name Extraction Explicitly

"You are trying to extract data from me instead of having a concrete retention conversation."

Function: Forces management behavior into the open. They can't later claim this was good-faith negotiation. Email explicitly identifies it as intelligence-gathering operation.

Move 3: Deconstruct Their Framing

"The 'constraints' I described aren't excuses-they're the material conditions of the work."

Function: Reverses base/superstructure inversion. What management calls "excuses" are documented as structural inputs management refuses to resource. Forces the contradiction into official record.

Move 4: Identify Non-Answers as Non-Answers

"You committed to 'addressing the culture' and 'streamlining the process,' which are non-answers."

Function: Distinguishes material changes (pay, staffing, equipment) from symbolic concessions ("culture fixes"). Shows what actual retention would require. Creates standard for evaluating management's future claims.

Move 5: Provide Evidence with Anti-Scapegoat Embedded

M.'s photos provided with explicit warning: "If you're approaching this as 'find the bad employee,' you'll use whatever I send to isolate M. and declare the issue resolved."

Function:

• Creates management liability (antisemitic imagery documented = must investigate)
• Blocks "bad egg" narrative (structural mechanism named in same document)
• Protects remaining workers (prevents management from declaring problem solved via removal)

Move 6: Protect Site Supervisor Explicitly

"It went through the Site Supervisor. I coordinated with him continuously."

Function:

• Documents supervisor involvement (not worker "taking it upon himself")
• Names Site Supervisor's constraint (scheduled as production labor)
• Blocks scapegoating (site required training, no alternative available)
• Preserves horizontal solidarity (doesn't blame Site Supervisor for structural problem)

Move 7: Refuse Free Consulting

"I'm not interested in providing free consulting to fix problems you've already decided not to resource properly."

Function: Terminates unpaid diagnostic labor. Once material changes refused, I stop providing operational intelligence. No more photos, no more supply lists, no more training documentation-unless they pay for it.

Move 8: Force Into Official System

Sent to company email (not personal account), with company subject line thread.

Function:

• Creates discoverable record (email retention policies, legal discovery)
• Timestamped and attributable (can't be "misremembered")
• Constrains later narrative (management can't claim ignorance of issues)
• Institutional record survives individual actors (if General Manager leaves, email remains)

Move 9: Name the Theater

"That's you performing management theater."

Function: Final framing. Not angry denunciation-cold analytical assessment. Names the game, refuses to play, exits cleanly. Forces management to either refute the characterization or accept it into institutional record.

What Management Wanted vs. What They Got

Management wanted:

• Raw intelligence on M. (photos without structural framing)
• Training details (names, specifics without Site Supervisor protection)
• Supply lists (operational data without ownership gap analysis)
• Continued extraction (meetings, calls, "feedback sessions")
• Clean scapegoat (M. as individual problem, removal as solution)

Management got:

• All of the above, but fused to worker analysis they can't separate
• Immediate resignation with no further engagement available
• Structural mechanism documented alongside individual evidence
• Constructive knowledge of hostile environment in official record
• "Management theater" characterization in institutional email

The gap between what they wanted and what they got is the tactical value of this approach.

Evidence Note

This email was sent via OneNorth company email system February 16, 2026 at 3:30 PM. Text reproduced verbatim with minimal redactions for publication (names changed to titles/initials, email addresses removed).

Attachments referenced (M. documentation) are detailed separately in Exhibit D.

This resignation demonstrates how workers can weaponize official compliance systems-using the same channels management designed for control to create management liability and preserve worker analysis in institutional record that survives individual departure.

Exhibit F

HR Resignation Chain (February 10–12, 2026)

HR confirmation of last day, final paycheck timing, and benefits end date. HR states they will notify the Operations Manager on February 12, anchoring the February 12 call-push as post-notice extraction, not routine offboarding.

Context: Email chain between myself and Northwest Center HR from February 10–12, 2026. This exchange documents:
(1) My formal resignation notice delivered in writing,
(2) HR's confirmation of last day in system,
(3) HR stating they will notify Operations Manager, that day, and
(4) written confirmation of final paycheck timing and benefits end-date.
This establishes that the Operations Manager’s February 12 “exit interview” phone-call push occurred after resignation was already an administrative fact and after HR stated they would notify him.

Purpose: Provide a clean, timestamped administrative record to anchor the exit timeline and distinguish routine offboarding logistics from discretionary intelligence extraction attempts.

The Exchange

EMAIL 1 - My Resignation Notice to HR (February 10, 2026 · 4:38 PM)

From: Stephen Hibpshman
To: Northwest Center HR (HR inbox)
Subject: Notice of Resignation (Last Day: February 21, 2026)
Date: Tuesday, February 10, 2026 · 4:38 PM

Hello Northwest Center HR,

This email serves as formal notice of my resignation from my position at Northwest Center. My last day of work will be Saturday, February 21, 2026.

Please notify any relevant managers/supervisors (Ops, shift leads, HR/payroll) as needed for coverage and offboarding.

I intend to work my scheduled shifts through February 21. Please confirm receipt of this notice, my separation date in your system, and any offboarding steps required (return of uniforms/equipment, where/when to return them).

Please also confirm in writing the timing of my final paycheck and any payout treatment of accrued vacation/PTO per company policy, and the end date of any benefits coverage.

Thank you,
Stephen Hibpshman

EMAIL 2 - Forwarded Copy (February 11, 2026 · 5:28 PM)

From: Stephen Hibpshman
To: Human Resources Business Partner/Recruiter, Northwest Center
Date: Wednesday, February 11, 2026 · 5:28 PM

(Forwarded copy of Email 1 for continuity.)

EMAIL 3 - HR Confirms Dates + Notifies Ops Manager (February 12, 2026 · 9:52 AM)

From: Human Resources Business Partner/Recruiter, Northwest Center
To: Stephen Hibpshman
Date: Thursday, February 12, 2026 · 9:52 AM

Hello Stephen,

Thank you for reaching out to me and letting me know of your resignation.

I have your last day of employment with us as Saturday, February 21st, 2026, at Collin’s Aerospace. I will inform the Operations Manager of your resignation today. I ask that you please reach out them and coordinate when to return uniform, keys, etc.

With your last working day being 2/21/2026, your final paycheck will be on Friday, February 27th, 2026. This will include the pay period of 2/8-2/21. Unfortunately, due to you not being with the company for at least 1 year, there will not be any PTO payout.

I do see that you are receiving $50 for the student loan contribution. You are receiving that on your paycheck for tomorrow (2/13) so February will be the last month you will receive this and effective 3/1/2026 you will no longer receive anymore benefits from NWC.

Please let me know if you have any further questions before your departure.

[Signature block / contact details omitted for publication.]

What This Exchange Shows

1. Administrative timeline anchor. Resignation notice is sent February 10; HR confirms last-day and final paycheck timing February 12.
2. Trigger chain: HR → Ops. HR explicitly states they will inform Operations Manager on February 12.
3. Format difference matters. HR logistics occur cleanly in writing; the later “exit interview” pressure is discretionary and format-controlled.

Evidence Note

Text reproduced from the email thread with minimal edits for readability and redactions of contact details and non-essential boilerplate. Dates/times preserved as shown in the message headers.

#accountability #documentation