Projects using Playwright in GatineauProjects using Playwright in Gatineau
Projects
People
Cover image for DAY 16: CONDITION TRACE 30 Days
DAY 16: CONDITION TRACE 30 Days of Real Business Problems Phase II I stopped at Day 15. Not because I ran out of problems. The format was becoming predictable. So I changed the rules. Phase II starts with a problem from museum conservation. Condition reports can document what was visible at different moments — but they cannot always prove when a physical change actually occurred. So instead of asking: “Where did the damage happen?” I reframed the problem: Trace when the feature first appears in the documentation. That became CONDITION TRACE. The prototype follows a fictional museum-loan case involving the same vessel across four signed condition records. Earlier examinations were completed under diffuse light. During the return-arrival inspection, the conservator introduces raking light. As the grazing angle changes, a hairline crack on the vessel’s upper-right shoulder becomes legible. That observation is preserved as OBS-04 and carried through a traceable evidence chain: SRC-03 → OBS-04 → CMP-01 → LIM-01 → FND-01 But the system deliberately refuses to overstate what the evidence proves. The earlier examinations were not performed under equivalent lighting conditions. So the conclusion remains narrow: FIRST DOCUMENTED APPEARANCE AUGUST 3, 2026 Not: “The damage happened on August 3.” Not cause. Not responsibility. Not liability. The interface follows the same principle. Light becomes an examination instrument. The observation persists through comparison. The evidence lineage remains visible. And the final finding must be deliberately sealed. The goal wasn’t to make an interface that looks forensic. It was to make the boundary of the evidence visible and traceable. TRACE THE RECORD. NOT THE BLAME. Live prototype: https://day16-condition-trace.vercel.app Day 16 / 30 Phase II begins.
1
46
Cover image for Day 9/30: VOLLENT A critical operational
Day 9/30: VOLLENT A critical operational change should not become executable just because every message was delivered. VOLLENT is an operational acknowledgment interlock that keeps execution physically open until every required recipient acknowledges the exact active version. In this scenario, a venue load-in changes from 2:00 PM to 3:00 PM. Three recipients have acknowledged it. Andre’s message was delivered but not acknowledged. So, the circuit stays open. Once Andre confirms the exact change: Delivery → acknowledgment → circuit closure → authorization → evidence receipt The signature interaction turns a missing acknowledgment into a physical gap. When the final recipient responds, the rails close, authorization becomes available and a version-bound receipt records the full sequence. SENT IS NOT SAFE. Delivery proves transmission. Acknowledgment releases execution. Built with React, Playwright, Remotion and FFmpeg. Communication channels are simulated in this working prototype, and the receipt tokens are deterministic demonstration artifacts rather than cryptographic proof. Live prototype: https://faadil1.github.io/vollent/ Full case study: https://contra.com/p/oc2QerNL-vollent-operational-acknowledgment-interlock?r=faadil_boussari #ProductDesign #InteractionDesign #UXDesign #Prototyping #FrontendDevelopment #MotionDesign Full case study: available on my Contra profile.
6
160