Jason V. Holmes
Back to projects

Workflow architecture / volunteer operations

Volunteer Treasury Workflows

Turn a reimbursement into a traceable sequence of evidence, review and human approval.

Architecture case study · Successor implementation and acceptance pending

Historical treasury dashboard illustration labeled demo tenant and sample data
Historical web-platform concept. Fictional names, balances and organizational examples. This illustration predates the Google Workspace successor and is not a production screenshot or deployment proof. Open full illustration ↗

01 / the operational problem

Keep the receipt, decision and payment connected.

Volunteer reimbursements combine small records with consequential decisions: what was purchased, which fund covers it, how currency was converted and who approved payment. The design aims to make that chain understandable on a phone and reviewable during handover.

I developed treasury-specific requirements and architecture around approval controls, evidence retention and reproducible outputs. Operational workbook history informed the requirements; it is not acceptance evidence for an application.

Current evidence boundary

  • Earlier web-platform repository retired on 1 November 2026
  • Current direction: Google Workspace
  • Implementation and verification work remain open in the reviewed record
  • No completed end-to-end reimbursement or deployment acceptance verified

02 / proposed workflow

Every handoff needs evidence.

  1. RequestReceipt + line items
  2. ConvertRate rule + provenance
  3. ReviewFund and evidence checks
  4. ApproveAuthorized human decision
  5. RecordCheck entry + signed output

Intended workflow, not an executable demo. A diagram or screenshot does not establish that these controls have been implemented or passed acceptance.

03 / control requirements

Design the controls before claiming the outcome.

01

Approval before payment

The architecture requires approval before check entry and treats exceptions and corrections as auditable records.

02

Explain the conversion

The proposed currency rule retains the transaction date, rate evidence and fallback basis. Deterministic logic must be verified separately.

03

Reproduce the output

Voucher, reconciliation and reporting designs need defined inputs, retained evidence and acceptance checks.

04 / architecture transition

A new stack needs its own proof.

The earlier design used Next.js, Supabase and Vercel. The November successor direction uses Google Workspace for the request workflow and records. Database-trigger and row-level-security claims from the former architecture do not transfer to the successor.

The next evidence is a verified implementation baseline, controlled workflow and access checks, reproducible output, and operational acceptance. A completed full-year platform pilot has not been verified.

What is available here

Requirements, architecture, traceability approach and historical fictional-data illustrations. No live application, private financial records, receipt photos, credentials or youth records are embedded or linked.

05 / provenance

Preserve the foundation and its contributors.

Foundation patterns derive from SpendWise, the UMGC CMSC 495 capstone by Leighton Tidwell, Jason Holmes and Eric Hill. Treasury-specific design and code work is distinct from that shared baseline. The public case study records consent for reuse and requires preserving applicable attribution and rights.

This is independent work and does not imply organizational endorsement. The public case-study text and images reserve reproduction rights; code snippets are MIT-licensed unless noted. This page references an existing public illustration and grants no reuse rights.

Discuss a workflow or evidence review.

I connect operational needs to requirements, interfaces, controls and verification under human approval gates.

Start a conversation

Evidence reviewed 17 November 2026. No product deployment or transaction performed during this portfolio review.