Project index / 05 cases

Five cases.
Every decision visible.

Two independently owned software projects and three fictional design exercises. Open a case to see the problem, my contribution, a working example or design, and the limits of its evidence.

Professional experience is in my résumé
Source lineage / real local artifact
SourceFictional Markdown
TransformPassthrough backend
ManifestSHA-256 retained
11 chunksSource + section + page
chunk / 0009Evidence rulespage:2
Reviewed CLI output11 chunks
Sourcefictional-expense-review-standard.mdSHA-256 22611878d966…
Generated chunk / 0009Evidence rulesFictional Expense Review Standard / Evidence rules

Source identity and section path stay attached to the converted text.

Real CLI output; invented source; static browser replay.

01 / Document AIIndependent software

Document Context

Prepare documents without losing their source.

Local conversion produces structured Markdown and source-linked chunks for downstream AI workflows.

Evidence: Real CLI artifact from a fictional standard

Design decisionKeep source identity and section context attached to each chunk.
Proposed operating model
One request.
Connected decisions.
  1. 01Request
  2. 02Decompose
  3. 03Specialist challenges
  4. 04Human review
  5. 05Future state
  6. 06Change loop
Fictional design recordReview / 03
Use caseStaff knowledge assistant
Open decisionWhich local policy and approval path apply in a real organization?

Specialists receive questions; a model does not issue an approval.

Concept diagram; simulated prewritten responses; no running agents.

02 / AI operating modelFictional design concept

AI Use Case Studio

Make an AI use case reviewable before build.

A proposed workspace connects intake, dependencies, specialist questions, and future-state design.

Evidence: Fictional concept walkthrough

Design decisionKeep agent proposals separate from human approval.
Fictional working example
Evidence is a check.Approval is a decision.
Human disposition + written reason
Fictional review recordEX-1042
P-01Receipt recorded.Present
P-02Manager approval missing.Gap
P-03Business purpose recorded.Present

The reviewer records the disposition and reason.

Invented records; inspectable rules; human decisions.

03 / Risk operationsFictional design exercise

Evidence Review

Show missing evidence before a reviewer decides.

Deterministic checks expose the reason for each gap while leaving the decision with a person.

Evidence: Three fictional review records

Design decisionRequire a reasoned human disposition even when checks pass.
Fictional working example
LedgerReference + cents
=
Operations feedUnique counterpart

Ambiguous reference? Keep the exception open.

Fictional rule outputException day
TXN-205amount varianceOpen
TXN-206ambiguous referenceOpen
TXN-207missing feedOpen

Duplicate and mismatched records are not forced into a pair.

Invented records; inspectable rules; human decisions.

04 / ReconciliationFictional design exercise

Ledger Match

Keep ambiguous ledger matches open for review.

Exact reference-and-cent pairing separates clear matches from four types of exception.

Evidence: Two invented batches with rule tests

Design decisionNever force a match when source records are ambiguous.
Fictional working example
01 / SignalPossible duplicate
02 / Supporting recordCompare the entries
03 / Human ownerDecide the next check

Advisory queue · no automatic posting

Fictional journal reviewMay 2026
J-401Account 6150 / EAST$4,200
J-402Account 6150 / EAST$4,200

A possible duplicate needs evidence. No posting changes automatically.

Invented records; inspectable rules; human decisions.

05 / Financial closeIndependent prototype

Close Workbench

Bring close exceptions into one reviewer queue.

Journal and invoice signals appear with supporting records and the next human check.

Evidence: Working static prototype with fictional data

Design decisionTreat every flag as advisory, not an accounting conclusion.
About these cases

Document Context and Close Workbench are independently owned; their browser examples are fictional or fixed as labeled. Cleared résumé outcomes do not authorize publication of employer or client code, screenshots, data, or detailed project case studies; those remain under separate review.