Upstream loss
What continues, what moves, how quickly it recovers and which workload notices.
Verification before publication
Proof has
a method.
Field evidence starts with what the operation needs, what the environment does and what failure looks like. A result becomes a public claim only after its source, scope and wording can survive scrutiny.
The evidence ladder
Four steps from symptom to supported outcome.
Each step answers a different question. Skipping one creates a story that sounds cleaner than the system really is.
- 01
Baseline
Record the operating context, observed symptoms and current dependencies before changing the system.
- 02
Failure paths
Make upstream, power, routing, wireless and workflow dependencies visible enough to test.
- 03
Operational load
Verify under the density, movement, timing and business pressure the site actually creates.
- 04
Outcome
State only what the measurements, period and acceptance conditions directly support.
Useful acceptance tests
Reality is the dashboard.
A green configuration screen is evidence about configuration. The operation still needs tests that exercise the whole path.
Peak conditions
Coverage, capacity and critical workflows under representative concurrency and movement.
Workload isolation
Whether guest, staff, payment, production and surveillance traffic retain the intended separation.
Human recovery
Whether the people responsible can recognise a failure and take the documented next action.
Documentary field notes
The site is part of the system.
Terrain, inherited infrastructure and physical access shape the architecture before a dashboard has anything useful to say. These frames document working conditions in Bohinj; they do not identify a client or claim a measured result.
Documentary archive, 2018–2021 · web derivatives contain no location metadata · original files remain private.
Anonymised Bohinj field case
What the evidence can responsibly say now.
A multi-year project supports an outdoor hospitality operation where guest access and day-to-day systems share a demanding physical environment. The case is public at a qualitative level; the client name, topology and exact operational figures remain private.
An evolving outdoor site
Dated field material records operating context, inherited conditions, groundworks and hands-on installation as the site changed over time.
Complementary access paths
The current system combines terrestrial and Starlink connectivity, reducing dependence on one access technology without turning that intent into a zero-downtime promise.
Separated workloads
Guest, restaurant, staff, surveillance and site-operation traffic are treated as different responsibilities, not one undifferentiated Wi-Fi network.
Demand measured, claims bounded
Recent private snapshots show hundreds of connections and multi-terabyte monthly traffic. Exact figures and raw management views stay outside the public package.
Publication boundary
Real does not automatically mean public.
Client identity, raw topology, exact measurements, security-relevant detail and commercial outcomes remain private until there is a clear right to publish them.
The anonymised qualitative case above uses only the part of the evidence that can carry its own weight. The detailed working case remains outside the deployable package.
- Source and measurement period identified
- Scope and exclusions stated
- Client-safe wording approved
- Security-sensitive detail removed
- No universal claim inferred from one environment
CURRENT STATUSAnonymised qualitative case published.
PRIVATE LAYERIdentity, exact figures and topology held.
NEXT RELEASE GATENamed scope and client-approved metrics.