DETERMINISTIC BY DESIGN

A deterministic verification gate between an AI buying agent and merchant checkout. It parses an AP2 delegation chain, computes the RBI e-mandate envelope as executable predicates, and writes a hash-chained evidence record for every verdict it reaches.

A declared obligation that produced no result becomes INDETERMINATE at construction time and blocks exactly as hard as an outright violation — the difference between "checked and passed" and "never checked" is enforced by the type system, not remembered by convention.

Building PRAMANA against Google's AP2 reference SDK surfaced two defects in its own verification path. Google confirmed the mechanism, classified it as intended behaviour, and invited a public issue — both are now filed upstream as an issue and a pull request.

The finding ships as an executable proof rather than a write-up: `pramana finding` mints two presentations against the installed SDK, runs AP2's own evaluators over each, prints the commit it ran against, and exits non-zero the day the defect stops reproducing.

A fraud-interception system across Android and web. Detection runs in a fixed order — deterministic rules on the device, then retrieval over past cases, and only then a model — so a verdict is explained from evidence rather than invented. Case history is isolated per user with row-level security.

The ordering is the design. Putting the model last means the common cases never reach it, the explanation is always traceable to a rule or a retrieved precedent, and the system degrades to something still useful when the network is gone.

A hybrid rules-plus-ML detection engine over CSV and SFTP ingestion, with DuckDB for in-process analytics and a React dashboard for triage. Backend, frontend, sample data and a Docker Compose stack all live in the repository, with detectors tested in CI.

Every alert carries the rule or feature weight that produced it, and audit reports are generated from the same records the analyst worked from — so what reaches a regulator is not a second, prettier version of events.

A pnpm monorepo: a Fastify 5 modular monolith, a Vite and React 19 client, a shared Zod contracts package and a generated design system. Migrations and seeds are owned by the repository, applied by a one-shot container, and tested against a real Postgres 18 rather than a mock.

Layering is enforced by ESLint rules rather than by convention — the lint step fails if the web app reaches past the contracts package into server internals.

Three layers in one workspace: a FastAPI backend with Celery workers, Next.js reporter and authority portals, and a Hardhat contract project. Reports are classified by an AI pipeline, persisted in Postgres, pinned to IPFS, and mirrored to Sepolia. Deployed, with the container and proxy configuration in the repository.

Jurisdiction scoping is enforced in API logic rather than in the UI — a case is visible only to authorities whose key maps to the same jurisdiction code, so hiding a button is never mistaken for access control.

A Solidity contract set with a React client, Hardhat Ignition deployment modules and a contract test suite. Ballots and tallies settle on-chain, so the result can be independently recomputed rather than taken on trust.

The point of putting an election on-chain is not novelty — it is that verification stops depending on the same party that ran the vote.

A three-tier application — React Native client, Express and SQLite backend, Socket.IO for live sessions — with mood tracking, context retention and a crisis-detection path that routes to professional resources. Backend, frontend, devops and test directories are all present in the repository.

The constraint worth solving was knowing when the model must stop being the interface. Detection triggers a hand-off, not a better reply — the same rule as the fraud work, applied where the stakes are personal rather than financial.

A premium storefront in React 18, TypeScript and Vite. The hero is a scroll-driven 360° sequence, the grid is a bento of material close-ups, and the whole surface runs on spring-based kinetics with a glassmorphic detail modal and a global cart drawer. Deployed and live.

Every other card here argues about correctness. This one is the counterweight: interface craft is its own discipline, and a portfolio that only shows verification logic is hiding half the job.

A Solidity contract on Polygon Amoy storing a certificate id, its hash and its recipient, with a React client where an admin issues through MetaMask and anyone can verify publicly. The smallest project here, and listed as such.

No private key is ever stored or read by the application — every state-changing call is signed in the wallet, which makes the admin panel a convenience rather than a trust boundary.