Skip to content

thedman/govagentic-demo

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Govagentic Demo

Public portfolio demonstration of AI governance concepts applied to third-party risk assessment.

Repository Identity

Quick Reference

  • Repository: govagentic-demo
  • Type: public portfolio demo
  • Runtime: static frontend with synthetic vendor/control/audit data
  • Data posture: synthetic demonstration data only
  • Primary audience: portfolio reviewers, AI governance stakeholders, and third-party risk practitioners

What this repository IS

This repository is a public demonstration of AI governance and third-party risk assessment concepts. It is designed to show interaction patterns, reasoning quality, and demo architecture without exposing real client data or a full proprietary methodology.

What this repository is NOT

  • Not the production Govagentic application or website.
  • Not connected to real vendors, clients, controls, audits, or employer environments.
  • Not a source of truth for production hosting, customer data, or operational workflows.
  • Not a safe place to store API keys or runtime credentials.

Common Context Switch Mistakes

  • Do not confuse this repository with govagentic, which is the production-facing repo.
  • Do not replace synthetic data with real vendor, client, audit, or assessment data.
  • Do not assume public demo behavior reflects production architecture or deployment.
  • Do not commit secrets; live credentials belong only in the hosting provider's secret manager.

AI Agent Guidance

Keep the demo concise, public-safe, and synthetic. Preserve the boundary between portfolio demonstration and production Govagentic work.

Portfolio Demo Notice

This repository uses synthetic vendor, control, assessment, and audit data. It is not connected to production systems or real client environments.

No secrets or credentials are intended to be stored in this repository. Any live API credentials used by the demonstration must be stored server-side in the hosting platform's secret manager and rotated outside the public codebase.

The demo preserves enough detail to show architecture and reasoning quality while avoiding publication of a complete proprietary governance methodology.

About

No description, website, or topics provided.

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors