All projects

Web · Procurement controls

Procura

A procurement workspace with owned drafts, manager decisions, stale-edit protection and transactionally recorded request history.

Explore the application
Procura approved test request with line items, manager approval and persisted status history.
View full capture

Procura opening application capture

Persisted browser-test workflow · Synthetic records

Development work

My work connects the React request interface to Express policies, validated inputs, PostgreSQL transactions and authorization/concurrency tests.

Developed with AI coding assistance.

Current evidence

Authorization, race & rollback test records

Local development report · 17 November 2026 · Uncommitted snapshot

Scope & limitations
Request & approval sliceSource repository is privateSee application

Problem & approach

Employees need to submit purchasing needs, managers need to decide them, and reviewers need an attributed history. Administrative access should not automatically mean approval authority.

I implemented the request-to-decision slice: multi-line drafts, submission, manager approval or rejection, scoped search and persisted history. The wider procurement workspace is a roadmap, not a completed receiving or inventory system.

  1. 01

    Draft

    The owner creates and edits request lines.

  2. 02

    Submit

    Validation and a version check protect the transition.

  3. 03

    Review

    A manager decides; the decision and event commit together.

Inside the application

  • PrepareCreate and edit owned drafts with validated line items.
  • DecideManagers review submitted requests; self-approval and non-manager decisions are rejected.
  • InspectSearch authorized records and inspect attributed status and approval history.

System architecture

01 / Browser

React + Vite

Draft forms, review queue, server search and request history.

02 / Server authority

Express + Zod

Cookie sessions, object policies, validated commands and versions.

03 / Persistence

Prisma → PostgreSQL

Business write and audit event share one transaction.

Implemented single-organization modular monolith. Development-only fictional roles cannot authenticate API calls. Receiving and inventory are outside this persisted path.
  • TypeScript
  • React
  • Express
  • Prisma
  • PostgreSQL
  • Zod

Engineering decisions

Separate administration from approval

I keep approval as an explicit manager policy, with a self-approval check. An administrator can maintain an owned request without gaining decision authority.

Reviewed: Request policy and decision service

Reject stale decisions

Updates match the expected version and eligible state before changing anything. A stale edit or simultaneous decision returns a conflict instead of replacing newer work.

Reviewed: Version-aware request transactions

Verification & status

Authorization, race & rollback test records

Local development report · 17 November 2026 · Uncommitted snapshot

The local report records 26 tests: 17 real PostgreSQL lifecycle tests and 9 unit/HTTP checks. Coverage includes simultaneous decisions, stale edits, self-approval denial and forced audit-failure rollback.

Reviewed 17 November results, not rerun here. This implementation is in an uncommitted local working tree ahead of the private GitHub baseline; no release or published-commit verification is claimed.

Request & approval slice

The request-to-approval workflow is persisted and connected to the interface. Captures show isolated database-backed browser tests.

Suppliers, orders, receiving, the inventory ledger and full reporting need persisted implementation. Dependency advisories and deployment/identity operations remain open.

Lessons & next steps

A workflow is only as trustworthy as its denied actions and failed writes. I treat conflict handling and audit rollback as product behavior, not just database details.

Review dependency advisories and stabilize the local milestone, then implement suppliers/orders before transaction-safe receiving.

Source & evidence access

The repository remains private. This case study shares reviewed implementation summaries and safe application captures, not source code or operational records.

Private local working tree based on cf40460, inspected 18 November 2026. Source remains private and unchanged by the portfolio work.

Another project

FreshKeep

Android · Household inventory