WORK / CASE FILES · 2026
DOC DY-WORK / 12 CASE FILESSystems shaped by security thinking, operational clarity, and practical delivery — each one presented as a case file that can be inspected.
00 / FIELDWORK PROTOCOL
Every case file separates what exists, what it demonstrates, and what still needs hardening. The goal is a portfolio that can be inspected rather than a gallery of unsupported claims.
Project statements are connected to source records, schemas, tests, captures, or reports. Constraints remain visible so a prototype is never presented as a production deployment.
Prototype marks an interaction or architecture under validation. Research System marks an investigative workflow. In Development marks active construction without a finished-production claim.
Work begins with the user, assets, and trust boundaries; moves through the smallest testable architecture; and ends with evidence, operating signals, and a clear next-hardening list.
Security is treated as a delivery constraint from the first model—not a final checklist.
01 / CASE FILES
Security, automation, AI, and product engineering case studies — open any file for the system question, architecture, risk register, and verified outcomes.
A prototype messaging backend that normalizes channel operations behind adapters and moves message work through Redis-backed queues.
A research system connecting price ingestion, technical indicators, news sentiment, ensemble prediction, backtesting, an API, and a dashboard.
A Flask portfolio and content-management application with database fallbacks, contact protections, response headers, and public-page contract tests.
Prototype RunPod workflow for provisioning GPU compute, transferring prompts, running media jobs, retrieving outputs, and tearing down resources.
A prototype workflow concept for organizing inbox triage, message templates, and operator-approved follow-up actions.
A prototype enterprise resource planning concept connecting inventory, purchasing, sales, and operational reporting.
A prototype school operations concept for student records, classes, attendance, communication, and progress views.
A prototype restaurant operations concept connecting menus, tables, orders, kitchen flow, stock, and daily reporting.
A prototype attendance concept for check-in records, approvals, schedule context, and role-aware reporting.
A prototype accounting product concept for chart of accounts, journal entries, reconciliation, and review states.
A prototype billing concept for customer accounts, invoices, line items, payment status, and operator review.
A prototype staff operations concept for profiles, roles, leave, attendance context, and manager workflows.
The most useful first message names the operating problem, the people affected, the known constraints, and the outcome you need. Everything else can be figured out together.