CodeZEWM_EXCMON

TitleForensic systems investigation · record REC-041

DisciplineSystems investigation · evidence & information design · spatial reconstruction

DatePackage files 11–12 Jun 2026 · Project year TBC

StatusDesigned · investigation package

[ LAB · AS DESIGNED ][ INVESTIGATION · AS EVIDENCED ] [+]

The failure was not a missed alert.

It was an inherited governance condition. A forensic systems investigation into how a reefer temperature exception, REC-041, lost its owner across fragmented institutional layers — told in six A4 evidence frames.

REC-041 concept render: a dark evidence chamber seen from the front left. A blue-grey monitor wall holds a pale violet-framed plaque with six lines of evidence text, a red rail runs above it, and a steel table with dark evidence placards sits in the lower right. — Specimen 05 · REC-041 chamber · schematic from generator constants — not a render · 30° isometric Specimen 05 · REC-041 v02 · concept render — Blender Cycles, 3840 × 2160, cropped 3:2 · a static visualisation, not a measured scene

[ On this sheet ]
02Question1 min
03Mechanism3 min
04Inside2 min
05Pigment & material2 min
06Decisions1 min
07Claim ledger2 min
08Provenance1 min
09Next specimen1 min

Code: ZEWM_EXCMON · REC-041
Discipline: Forensic systems investigation
Date: Files 11–12 Jun 2026 · year TBC
Status: Designed · investigation package
Physical evidence: None — a digital investigation package
Image: Schematic from generator constantsConcept render · Blender Cycles
Sheet: 07 / 11

02 · Question

Seven exceptions. Nobody owned them.

Why did a reefer temperature excursion keep recurring — seven incidents in 48 hours — without anyone owning it? The investigation argues the cause was not a missed alert or a software bug. Corrective action CAPA-2241 had been open for 11 days. The owner field was unassigned. A monitoring dependency, REEFER-MON-VQ1, was dead; sync age was unknown; escalation was blocked; Shift B-2 ran an undocumented workaround. The method has four steps — incident reconstruction, evidence clustering into a six-category taxonomy, a recurrence map and a failure-chain map — held together by one semantic colour code, so each colour carries one meaning.

03 · Mechanism

Eight nodes, five layers, no stable owner.

Rebuilt live from the frames' own colour tokens. Every figure in this section: investigation narrative; data provenance not stated.

System-chain map · exception ownership pathSignal origin → institutional recurrence

01Monitor signalRepeated temp excursion detectedSystem
02Sync uncertaintyData freshness could not be verifiedSystem
03CAPA staleCorrective action remained openProcess
04Owner unassignedAuthority field unresolvedAuthority
05Escalation blockedException path failed before responseProcess
06Shift B-2 workaroundUnofficial human adaptation recordedHuman
07Root unverifiedInstitutional cause remained unconfirmedGovernance
08Governance recurrenceFailure pattern repeated across ownership gapsGovernance

Rebuilt from Frame 04 · node labels, layer tags and split colours as printed · investigation narrative; data provenance not stated

[ Trace the chain ]

Node 08 / 08 · Governance recurrence · governance layer — failure pattern repeated across ownership gaps

The trace follows the order printed on Frame 04. It is a narrative chain, not a timed or measured sequence. The dashed return arc to node 01 is this sheet's reading of “recurrence”; Frame 04 does not draw it. Investigation narrative; data provenance not stated.

It failed because responsibility moved faster than documentation.
Frame 04 · thesis line · designed copy

[ Isolate one meaning ]

All six meanings shown · 8 chain nodes · 7 wall rows · 6 artifacts

Recurrence wall · temp excursion × 7 / 48 h

RPN 312 → 334

Risk increasing after detection · two printed values, nothing in between

INC-01 / Temp excursion / Ack delayedState breach detected, delayed acknowledgementBreach
INC-02 / Temp excursion / Owner pendingState ownership field unresolvedGovernance
INC-03 / Temp excursion / Escalation misroutedState exception path failedFailure
INC-04 / Temp excursion / CAPA linkedState corrective action attached but unresolvedWarning
INC-05 / Temp excursion / Sync age unknownState data freshness could not be verifiedSystems
INC-06 / Temp excursion / Shift B-2 workaroundState unofficial human adaptation recordedHuman adaptation
INC-07 / Temp excursion / Root unverifiedState institutional cause remained unconfirmedRecurrence

Rebuilt from Frame 03 · rows in printed order; the package gives no incident times, so rows are spaced evenly, not timed · investigation narrative; data provenance not stated

Evidence table · recovered artifacts

01 / 06WarningCAPA-2241 stale 11DCorrective action opened, not closed.
02 / 06GovernanceOwner: unassignedAuthority migrated without documented handoff.
03 / 06ArchiveREEFER-MON-VQ1 deadMonitoring dependency inactive at time of recurrence.
04 / 06FailureEscalation blockedException path failed before institutional response.
05 / 06SystemsSync age: unknownData freshness could not be verified.
06 / 06Human adaptationAudit gap / Shift B-2Human workaround layer not captured in official trace.

Rebuilt from Frame 02 · the same six labels are modelled as steel plates in the REC-041 scene · investigation narrative; data provenance not stated

04 · Inside

Six A4 frames, shown whole.

SystemsFailureWarningGovernanceHuman adaptationArchive

Frame 01, REC-041 spatial reconstruction: the hero render in the centre of a bone A4 plate, a spatial legend on the left (violet panel, red SLA rail, evidence table, dark room), evidence signals on the right and the thesis line below. — Frame 01 / 06 · Spatial reconstructionREC-041 evidence chamber — where the failure lived · A4 landscape plate, 3508 × 2480 · shown whole, uncropped · opens the full PNG

Frame 02, evidence table: six artifact cards in a two-by-three grid, each with a coloured left bar and a category tag, beside a governance-pattern column. — Frame 02 / 06 · Governance artifactsPhysicalized CAPA / ownership — what the failure left behind · A4 landscape plate, 3508 × 2480 · shown whole, uncropped · opens the full PNG

Frame 03, recurrence panel: seven incident rows INC-01 to INC-07 with coloured bars and category tags, beside a recurrence interpretation column. — Frame 03 / 06 · Recurrence panel7 incidents / 48h — how the failure repeated · A4 landscape plate, 3508 × 2480 · shown whole, uncropped · opens the full PNG

Frame 04, system map: eight square nodes on a hairline from signal origin to institutional recurrence, a five-layer legend and a chain interpretation column. — Frame 04 / 06 · System mapException ownership path — why ownership collapsed · A4 landscape plate, 3508 × 2480 · shown whole, uncropped · opens the full PNG

Frame 05, case study summary: three text columns covering project type, role and methods, and why it matters, with four frame links along the bottom. — Frame 05 / 06 · Case study summaryRecruiter-facing synthesis — why the investigation matters · A4 landscape plate, 3508 × 2480 · shown whole, uncropped · opens the full PNG

Frame 06, website landing blueprint: a sticky left thesis column with the scroll order and three buttons, beside five frame thumbnails on a vertical timeline. — Frame 06 / 06 · Website landing blueprintPortfolio landing-section composition · A4 landscape plate, 3508 × 2480 · shown whole, uncropped · opens the full PNG

Portfolio package · PDF

ZEWM_EXCMON · portfolio package

Frames 01–06 in order, copied losslessly from the six locked frame PDFs — no re-encode, no resize, no added pages.

Pages: 6 · A4 landscape · 842 × 595 pt
Source: 300 DPI plates
Size: ≈ 3.57 MB

Open the PDF

05 · Pigment & material

Each colour carries one meaning.

[ Semantic key · frame CSS, exact ]

Systems

#3E78B8

Authored · frame CSS · monitor signal, sync state

Failure / breach

#C0413F

Authored · frame CSS · escalation, breach

Warning / CAPA

#C98A28

Authored · frame CSS · also the thesis rule

Governance

#6E54C8

Authored · frame CSS · authority, recurrence

Human adaptation

#1E9C9C

Authored · frame CSS · workaround, shift

Lower the emission. Keep the red.

REC-041 v01 render: the same chamber, dimmer, with a salmon-pink rail and no placards on the table.

A · v01 · preserved original hero

Exposure 0.60 · light ×1.00 · plaque 3.0 · inset 0.50 · rail strength 3.0, which Filmic washed to salmon. Kept as the preserved original.

Designed · render parameter

Selected

REC-041 v02 render: brighter chamber, red rail, a dark reveal plate behind the plaque and placards on the table.

B · v02 · portfolio pass

Same camera and composition. Exposure 0.85 · light ×1.22 · plaque 3.7 · inset 0.95 · rail 0.70 · adds a 2.86 × 1.42 m reveal plate and five placards.

Designed · render parameter

REC-041 v01 render. — Concept render — Blender Cycles · v01 and v02 from one generator, same 33 mm camera, same 3:2 crop · left of the line v01, right v02

REC-041 v02 render, same camera. — Concept render — Blender Cycles · v01 and v02 from one generator, same 33 mm camera, same 3:2 crop · left of the line v01, right v02

[ v01 ← compare → v02 ]

Parameter	v01	v02
Exposure	0.60	0.85
Light multiplier	1.00	1.22
Plaque emission	3.0	3.7
Inset emission	0.50	0.95
Rail emission	3.0	0.70
Reveal plate	—	2.86 × 1.42 m
Evidence placards	—	5

Rail colour in both · #D94B4B · authored · unchanged — only the emission strength moved, so the semantic red never shifts

Designed · render parameters read from the generator

07 · Claim ledger

What is claimed, at what level.

Claim	Value	Level	Qualifier
Incident record	REC-041 · reefer temp excursion	Designed	Investigation narrative; data provenance not stated
Recurrence	7 incidents / 48 h · INC-01 → INC-07	Designed	Narrative; no incident times are given
Risk priority number	RPN 312 → 334	Designed	Narrative figure; no FMEA worksheet found
Corrective action	CAPA-2241 · stale 11 days	Designed	Narrative · “opened, not closed”
Root cause	Unverified	Designed	Narrative · no confirmed institutional cause
Failure chain	8 nodes · 5 layers	Designed	As printed on Frame 04
Evidence taxonomy	6 artifacts · 6 semantic colours	Designed	As printed on Frame 02
Package	6 pages · A4 landscape 842 × 595 pt · ≈ 3.57 MB	Designed	As listed in the package README · file 3,752,001 bytes
Evidence chamber	14.0 × 11.0 × 3.2 m	Specified intent	Generator constants; see the open item on as-rendered scale
Camera	33 mm at (−2.6, −3.0, 1.70) m · aimed at (0, 5.17, 1.80)	Specified intent	Read from code
Render	3840 × 2160 · Cycles 256 samples · OpenImageDenoise · Filmic · 16-bit · Metal GPU · motion blur off	Designed · render parameter	Settings read from code; output size checked
v01 → v02	Exposure 0.60 → 0.85 · light ×1.22 · plaque 3.0 → 3.7 · inset 0.50 → 0.95 · rail 3.0 → 0.70	Designed · render parameter	Both renders exist; deltas read from the generator's parameter set
Physical evidence	None	Not claimed	A digital investigation package

Not claimed

Measured incident data
A real employer incident
An FMEA worksheet behind RPN 312 → 334
A measured or validated room — the chamber is a static visualisation
Animation or a walkthrough — still images only

Open items

TBC Project year: 2026 on the live site; a September 2026 redesign draft says 2024–2025. Owner to confirm.
TBC Data provenance: no document says whether REC-041 is a real incident or a constructed scenario.
TBC As-rendered scale: the generator builds every box from a 1 m cube scaled by half of each listed dimension, so the walls, floor, table, rails and plates come out at half their listed sizes (their positions are unchanged); the screen, plaque and reveal planes are full size. Read from code, not measured in the render. The schematic on this sheet draws the listed constants. Owner to confirm the intent.
TBC Legends disagree: the code names amber the breach line, Frame 01 calls red the breach pressure and amber the evidence table; Frame 04 codes the governance layer red while its governance nodes are violet.
TBC Render typeface: the generator's docstring says IBM Plex Mono; its font search lists Courier New first, so the in-render text is Courier New. The A4 plates use IBM Plex Mono.

08 · Provenance, credits, revisions

Where every image comes from.

§01 Lab · isometric evidence chamberSchematic from generator constants — not a render
§01 Investigation · REC-041 v02 heroConcept render — Blender Cycles, cropped 3:2
§03 · chain, recurrence wall, evidence tableRebuilt in HTML from the frames' CSS tokens
§04 · frames 01–06A4 plates, HTML exported to PNG and PDF · shown whole
§06 · v01 and v02 heroesConcept render — Blender Cycles, same camera and crop
ToolsBlender Cycles driven by a Python scene generator · HTML/CSS plates · IBM Plex Mono
CollaboratorsNone credited in the package
Public filePortfolio package PDF · 6 pages

Rev	Date	Change
01	11 Jun 2026	REC-041 v01 hero rendered — kept as the preserved original
02	11 Jun 2026	v02 portfolio pass rendered; Frame 01 built around it
03	12 Jun 2026	Frames 02–06 locked; six frames bound into the package PDF
04	2 Oct 2026	Sheet 07: isometric schematic, live chain / wall / table, frames as AVIF; live PNG and PDF links kept

Dates 01–03 are file dates; the project year is still to be confirmed.

09 · Next specimen

Not a camera backpack.

CLX-CT-01 · creator-tech carry system · designed, CAD blockout · evidence 40% verified

Open sheet 08