Explore the portfolio

Open to AI/ML and software engineering internships.

Back to portfolio

ForgeGuard Contain

Turns a supplier notice into record-backed exposure, a revision-bound human decision, and durable inventory or task actions in a sandbox.

Locally verified prototype
ForgeGuard Contain workspace showing supplier-notice exposure and review state
Current containment workspace using synthetic records. The authored example path is labelled no model run.Open full capture

Solo project; AI-assisted development.

Authored fault scenarios

40 / 40

Stored local synthetic-fixture checks: stale approval, duplicate intent, fencing, lost acknowledgement, and recovery. Live model qualification remains open.

Validation notes

The idea

The problem

Supplier notices need traceable affected lots and approvals that remain valid only for the reviewed record revision.

The implementation

What I built

Connected lot tracing, revision-bound approval, durable sandbox receipts, and explicit pending inference states.

  • React
  • FastAPI
  • PostgreSQL
  • Python
  • SQLite

Features

  • Trace notices to affected demonstration lots
  • Approve the exact reviewed revision
  • Recover sandbox actions through durable receipts

Architecture

  • React case register and review interface.
  • FastAPI with SQLite development storage and a PostgreSQL deployment adapter.
  • Bounded inference worker and sandbox inventory/task actions.

Engineering decisions

  • Invalidate stale approvals when the reviewed record changes.
  • Keep authored examples visibly separate from live model requests.
  • Show unavailable inference as pending instead of manufacturing a result.

Validation and measured results

  • Stored local evidence records 40/40 authored fault scenarios covering stale approval, duplicate intent, fencing, lost acknowledgement, and recovery.
  • Real HTTP and PostgreSQL adapter checks exercise authority, revision, persistence, and receipts.

Limits and unfinished work

  • Demonstration notices, records, and policies are authored synthetic fixtures.
  • Live model quality, AMD workload, and public deployment are not qualified.
  • A sandbox hold is a software state change. No factory savings or physical containment result is claimed.

Evidence and sources

  • Local verification notes

    Stored authored synthetic fault scenarios and local adapter checks. No public source or downloadable receipt is attached.

Explore the project archive

Find your way

12 results found.

Use Tab or arrow keys to explore. Enter opens a result. Escape closes search.

Portfolio assistant

Answers from published portfolio records.

A closer look

Find the work behind the skills.

Ask about engineering decisions, validation, experience, or project limitations. Each answer links back to its sources.

AI can make mistakes. Check the linked records. Your question is sent to Google Gemini.