Skip to content
PR

Selected work

Four systems, one open-source project, and the decisions behind them.

Each entry states the real problem, one engineering decision, and the proof that the behaviour is what the design claims. Scope notes say what is deliberately not claimed.

Featured work

Flagship systems

Ordered LYTA, PARTHA, KALYX, ReturnProof. Roughly one screen of detail each.

01Live

LYTA

An edge-native workspace with persistent files, cited retrieval, and resilient streaming.

What it solves
Keeps a reusable document library across conversations, so users do not upload files and rebuild their context from zero each time.
Engineering decision
The SSE response is opened before the model runs, so an upstream failure becomes a controlled in-stream error instead of a platform crash page mid-answer.
Proof
Manual end-to-end verification of upload, retrieval, citation and streaming failure paths. Controlled error responses exercised by forcing upstream failures.

TypeScript · Cloudflare Workers · Durable Objects · Workers AI · SSE · PDF.js · Mammoth

Scope note: LYTA does not use a dedicated external vector database.

LiveRepository
CITED STREAM
Diagram: documents orbit a persistent workspace core; retrieved fragments illuminate and form a cited response trail.

Documents orbit a persistent workspace core; relevant fragments illuminate and form a cited response trail.

02Pre-alpha prototype

PARTHA

Repository intelligence that turns fragmented codebase knowledge into structured evidence.

What it solves
Gives engineers and AI tools one reusable source of truth for a codebase, so architecture, dependencies and technical context do not have to be re-derived for every task.
Engineering decision
Builds React, TypeScript, FastAPI and PostgreSQL services around one shared repository intelligence model.
Proof
Each supported fact keeps its repository revision, file path and line source, so reports and AI features can be checked against the code that produced it.

React · TypeScript · FastAPI · Python · PostgreSQL · Redis · Docker

Scope note: PARTHA is an active pre-alpha prototype, not a hosted production service. Claims about encryption, token rotation, egress controls, contributor counts or production usage are deliberately not made here.

Repository
PARTHA logo

The PARTHA project mark.

03Academic dissertation

KALYX

Tamper-evident execution history with deterministic trust verification.

What it solves
Lets investigators verify whether execution logs were altered, deleted or reordered after a system compromise.
Engineering decision
Once the trust boundary is broken, the ledger refuses further appends. A broken chain is never quietly extended into a plausible-looking history.
Proof
pytest over ledger construction, replay, and break detection paths.

Python · FastAPI · Angular · Raspberry Pi · eBPF · pytest

Scope note: KALYX verifies the integrity of accepted evidence. It does not prove the original source was truthful, and it does not prevent attacks.

RepositoryLearning site
#1#2#3#4#5TRUST BREAKANCHORED CHECKPOINT → INDEPENDENT SERVICE
Diagram: a chain of hash-linked blocks, with a visible fracture at the point where verification detects tampering.

A sequence of linked blocks travels across the viewport; altering one block creates a visible fracture through the remaining chain.

04Active project

ReturnProof

Deterministic evidence reconciliation for conflicting returns data.

What it solves
Decides which of two disagreeing sources to trust for a returned shipment, field by field, so stock and supplier-credit decisions are defensible.
Engineering decision
Evidence is resolved per claim field, never per source, and every decision keeps the ID of the rule that produced it, so a wrong outcome can be traced back to a rule rather than argued about.
Proof
pytest across the reconciliation engine and the Django API. Vitest for frontend units. Playwright for the end-to-end claim workflow.

Python · Pydantic · Typer · Django · Django Ninja · React · TypeScript · TanStack Query · pytest · Vitest · Playwright

Scope note: Not deployed in a regulated production environment.

Repository
WAREHOUSESUPPLIERCONDITIONBATCHEXPIRYQUANTITYCREDIT
Diagram: two conflicting evidence streams enter a resolver, split into per-field ribbons, and are written into an append-only ledger with rule IDs.

Two contradictory streams collide and are separated into field-level evidence ribbons before joining an auditable ledger.

Open source

OpenShield

Open-source Azure Cloud Security Posture Management

OpenShield is officially migrating into OWASP. Parth is a current OpenShield project maintainer with write and merge access, and will become a maintainer under the OWASP umbrella once the migration completes.

Commercial cloud-security posture tools can be unaffordable for startups, SMEs, universities, and student teams, leaving them with limited visibility into Azure misconfiguration.

  • Tests and documentation CODEOWNER
  • Built the OpenShield Learn contributor portal
  • Azure detection rules, compliance mappings, and CLI remediation guidance
  • Alembic migrations and clean-PostgreSQL CI validation
  • OpenSSF Best Practices passing badge

Scope note: Maintainer role is on the OpenShield project itself. OpenShield is progressing through OWASP governance; that process is not complete.

RepositoryLearnDashboard

  1. L1

    Azure topology scan

    Subscription resources are enumerated and inspected.

  2. L2

    Detection rules

    Azure misconfiguration rules produce findings.

  3. L3

    Compliance mapping

    Findings map to compliance controls.

  4. L4

    CLI remediation

    Each mapping carries matching remediation guidance.

  5. L5

    Tests, docs, migrations

    Alembic migrations and clean-PostgreSQL CI keep the database reliable.

Python · Azure SDK · Flask · PostgreSQL · Alembic · React · GitHub Actions · CodeQL

Coursework

University coursework projects

Academic work, kept deliberately lighter than the flagship systems. Expand any entry for detail.

C1Payment Routing SystemExpand

Payment operations need visibility into provider attempts, latency, status, and who is authorised to act on a payment.

  • Angular full-stack operations workspace
  • Flask API and MongoDB
  • JWT authentication
  • Merchant, finance, and admin roles
  • Server-side merchant data scoping
  • Provider-attempt history
  • Search, filtering, sorting, pagination, dashboards, and analytics
  • Automated frontend and backend tests

Angular · TypeScript · Flask · MongoDB · JWT · Chart.js · Vitest

Scope note: It records and exposes routing attempts. It is not an automated payment-provider selection engine.

Repository ↗
C2FieldSightExpand

Field researchers need to submit structured environmental observations with photo evidence into a searchable cloud system.

  • Express API deployed on Azure App Service
  • Cosmos DB for metadata
  • Blob Storage for images
  • API-key protected routes
  • Timing-safe API-key comparison
  • Application Insights telemetry
  • GitHub Actions deployment
  • Deliberate cost and scaling trade-offs

Node.js · Express · Azure App Service · Cosmos DB · Blob Storage · Application Insights · GitHub Actions

Scope note: Azure AD, Managed Identity, autoscaling and rate limiting are not implemented.

Repository ↗
C3SecureSenseExpand

Tamper detection often sends raw sensor data to a remote server, increasing latency and privacy exposure. SecureSense performs inference on-device.

  • Arduino Nano 33 BLE Sense
  • Motion, light, and proximity data
  • Deterministic feature extraction
  • Random-forest classifier
  • Independent session split to reduce leakage
  • Held-out Session 3 result: 83.33% accuracy and 0.8324 macro-F1
  • Five-window live voting result: 86.67%

Arduino Nano 33 BLE Sense · Embedded C++ · Python · Random forest

Scope note: Academic/embedded coursework, not a commercial security product.

Want the compressed version? Email me or read the résumé.