Applied AI projects
The cases cover contract intake, contract review, interview scoring, policy review, API packaging, and agent/browser controls. Interactive cases use fictional or synthetic data. Cases that cannot be released safely stay static.
Internal-pilot origins · Clean-room public treatment · No private repositories, production data, or adoption claims
Project library
The format follows what can be shown safely: an interactive demo, guided replay, technical case, static case, or architecture note. These are supporting cases, not six additional flagship products.
Interactive Demo · 01
Product contributor & Co-DeveloperAn interactive reconstruction of contract preapproval: parse a fictional intake, show where each field came from, run fixed risk rules, and record a human decision.
Field set, risk states, human decision, synthetic workbook, and action timeline
Guided Demo · 02
Product contributor & Co-DeveloperA fictional contract review that keeps rule matches, prepared AI suggestions, and the reviewer's accept, modify, or reject decision separate in the audit trail.
Finding trail, prepared suggestion, human decision, and printable HTML redline
Product Replay · 03
Product contributor & Co-DeveloperA fictional interview replay with six prepared scores. The reviewer can change each score, write feedback, and save an audit record; the test record never enters ranking.
Six-dimension scorecard, human adjustments, feedback, and audit record
Static Case · 04
Product contributor & Co-DeveloperA static walkthrough of fictional policy clauses, the issue found in each one, the cached support, a prepared recommendation, and the reviewer's final decision.
Issue, evidence, recommendation, and human-decision trail
Technical Case · 05
Product contributor in a multi-contributor projectA technical case that maps one fictional Spring Boot controller into four prepared outputs: OpenAPI, CLI help, an Agent Skill, and a validation manifest.
Prepared OpenAPI, CLI help, Skill example, and validation-manifest downloads
Architecture Note · 06
Enterprise-adaptation contributorA static architecture note showing how agent, browser, relay, and server layers are separated, where human confirmation is required, and why no executable demo is public.
Static architecture and non-release rationale