Factory, facilities, and sustainability evidence atlas Map route state, utilities, abatement, and resource accounting before any factory decision.
Move across cluster-tool routing, facility and abatement, and equipment-sustainability evidence using one bounded review surface. Each family preserves its own controls, normalized proxies, exact ledgers, source spine, role gates, traceability boundary, accounting boundary, and accountable replacement-evidence questions.
Use this page when the simulation is the primary artifact. The linked lesson explains the concept; the linked lab keeps the visual replay surface available.
Select one of three evidence families before loading row data; the first view exposes only bounded metadata, row counts, source posture, rights boundary, and export contracts.
Hold the family-specific categorical controls fixed, then compare eight ordered evidence states without treating the state index as time, event order, queue duration, equipment history, meter sequence, or control progression.
Switch among each packet's actual equipment, automation, scheduling, facilities, EHS, integration, emissions, utilities, and assurance views to expose which observations, measurements, genealogy, accounting boundaries, uncertainty records, and approvals remain accountable.
Compare six selected normalized teaching proxies and three exact integer ledgers inside each family while keeping route state, facility and exhaust context, resource metering, operating-state attribution, emissions, and allocation boundaries separate.
Use the source spines and replacement slots to plan owned route records, equipment identity, facility measurements, utility meters, abatement evidence, operating-state events, allocation rules, inventories, uncertainty, validation, and human review before any factory or sustainability decision.
Choose the evidence family before loading the validated rows.
Compact metadata is present at first paint. The browser fetches one validated gzip CSV transport only after this explicit selection, verifies the restored canonical bytes, and discards them when the family changes.
selected packet
Cluster-tool routing and operating-state evidence
Which routing topology, chamber matching, queue-time, residency, carryover, substrate tracking, and factory-handoff evidence still blocks a defensible cluster-tool review?
Review the selected packet and accounting boundary, then load exactly one validated family gzip CSV. The browser verifies the restored canonical bytes; changing families discards the loaded rows, and raw CSV plus row-bearing JSON remain outside the website.
The browser filters one validated canonical CSV selected by the user after decompressing and verifying it. It does not solve factory, facility, abatement, resource, emissions, or accounting physics; transfer source numbers; import measurements; infer compliance; recommend settings; operate equipment; certify an inventory; accept material; or make a disposition or release decision.
Methods are written for citation discipline: the extraction rule matters as much as the plotted value.
method
Cluster-tool routing and facility/abatement each enumerate 6,912 rows over 3,456 physical configurations; equipment sustainability enumerates 5,760 rows over 2,880 physical configurations, for 19,584 deterministic rows and 9,792 evidence pairs.
Keep this method attached when reusing the figure or metric.
method
Each family keeps its own routing, facility, operating-state, metering, emissions, allocation, and evidence controls; normalized equations; eight-state regime map; actual role gates; replacement-evidence bridge; and three exact integer teaching ledgers.
Keep this method attached when reusing the figure or metric.
method
Independent no-import verifiers passed 16/16 for every family, source-scope locks passed 37/37 for every family, and deterministic replay parity was exact for all twelve regenerated packet artifacts.
Keep this method attached when reusing the figure or metric.
method
Sixty link-only official or primary-source metadata anchors and forty-eight bounded claim nodes define terminology, rights, evidence ownership, accounting boundaries, and replacement questions without supplying generated numbers.
Keep this method attached when reusing the figure or metric.
method
The transport contract publishes three deterministic gzip CSV transports plus twelve compact-manifest, metric-contract, model-card, and source-spine artifacts while retaining raw canonical CSV and three row-bearing JSON artifacts with canonical evidence only.
Keep this method attached when reusing the figure or metric.
LIMITS
What this page does not claim.
The MVP is useful because the limits are visible. These statements prevent a teaching simulation from being cited as silicon evidence.
non-claim
All states, regimes, proxies, gates, and priority cues are original categorical or dimensionless teaching constructs, not factory schedules, utility values, facility capacities, abatement performance, emissions inventories, equipment utilization records, compliance findings, or production predictions.
Carry this boundary into any derivative note, paper draft, or slide.
non-claim
The nine exact integer ledgers establish deterministic bookkeeping consistency only. They do not establish causality, calibration, allocation validity, mass or energy balance completeness, traceability, uncertainty, qualification, safety, compliance, or production fitness.
Carry this boundary into any derivative note, paper draft, or slide.
non-claim
No source body, source number, equation, coefficient, material property, process condition, equipment setting, meter reading, emission factor, inventory row, model parameter, result, specification, threshold, control limit, or named-tool output enters the generated data.
Carry this boundary into any derivative note, paper draft, or slide.
non-claim
The browser loads one selected-family deterministic gzip CSV only after explicit user action and verifies the restored canonical bytes. It cannot dispatch work, command or operate equipment, size facilities, set abatement, certify an inventory, claim compliance, accept material, dispose a wafer, or publish automatically.
Carry this boundary into any derivative note, paper draft, or slide.
EVIDENCE
Trace the claim back to artifacts.
The evidence route remains the catalog-level browser; this page is the simulation-level reading card.
evidence note
Input audit passed 53/53 across three packet-complete families, 19,584 rows, 9,792 physical configurations, 60 sources, 48 claim nodes, and fifteen bounded candidate public assets.
SA-INT-FACTORY-FACILITIES-047
evidence note
All three independent packet verifiers passed 16/16 and all three source-scope locks passed 37/37; the preintegration verifier passed thirteen hashes and seven semantic gates.
SA-INT-FACTORY-FACILITIES-047
evidence note
Source reachability closed at 44 reachable and 16 access-gated records, with zero recorded hard or network failures in the packet audits.
SA-INT-FACTORY-FACILITIES-047
evidence note
The browser excludes 180,771,310 bytes of row-bearing JSON and 39,333,178 raw CSV bytes, then fetches one selected-family gzip transport only after explicit action; no all-family CSV preload is permitted.
SA-INT-FACTORY-FACILITIES-047
evidence note
Every family public manifest is compact and row-free, every gzip transport restores to the exact canonical byte count and SHA-256, every other copied public artifact matches its canonical SHA-256, and all raw CSV and private row JSON names remain absent from public data.
SA-INT-FACTORY-FACILITIES-047
Source spine
These links anchor the public teaching model. They do not convert the replay into a qualified process recipe or signoff result.