Skip to content

PUBLIC_RELEASE_AUDIT.md

Latest commit

 

History

History
75 lines (46 loc) · 2.67 KB

PUBLIC_RELEASE_AUDIT.md

File metadata and controls

75 lines (46 loc) · 2.67 KB
Raw

Public Release Audit

Scope

This audit covers:

  • the current tracked working tree
  • ignored local artifacts visible on disk
  • the git history reachable from main

Current Tracked Tree

Safe

  • No current tracked files reference a prior hiring process or named external organization.
  • No named organizations or people were found in the current tracked tree.
  • No private email addresses were found in current tracked file contents.
  • The current tracked screenshots are product screenshots only.
  • The bundled SQLite database is small (484K) and appears intentional as part of the reproducible local-demo story.

Fixed During This Pass

  • Replaced the portfolio README with a public-facing case-study README.
  • Removed handoff-oriented filenames from the current tree and replaced them with neutral public names.
  • Renamed the generated artifact surface to dataset_snapshot.
  • Removed the old absolute local path leak from the generated snapshot output by storing repository-relative paths.
  • Replaced the remaining evaluation-style API/UI phrasing with product-oriented copy.

Current Ignored Local Artifacts

These files exist locally but are ignored and are not part of the public repo:

  • .npm-cache/
  • backend/.venv/
  • backend/data/raw/
  • artifacts/transcripts/
  • scripts/__pycache__/ and other cache directories

The artifacts/transcripts/ directory is especially important: it contains local working-session transcripts and should remain ignored or be deleted locally before any broader machine/image sharing.

Git History Findings

Sensitive History

Commit a956d7c still contains deleted private prep materials and earlier handoff-oriented files.

The deleted files are no longer in the current tree, but they remain recoverable from history.

Commit Metadata

Both commits in the repository currently use the author email:

  • Gabriel Ramirez <gabriel.ramirezdev@gmail.com>

This is not present in file contents, but it is embedded in commit metadata and will be public on GitHub.

Recommendation

Current Tree

The current tracked tree is in good shape for a public portfolio release.

History Rewrite

If you want a strict public-safety standard, a history rewrite is recommended before promoting the repo broadly because:

  1. deleted private prep materials are still present in commit history
  2. commit metadata exposes a personal email address

Because the repo currently has only two commits, the cleanest options are:

  1. create a fresh public repo from the current sanitized tree
  2. or rewrite history with git filter-repo and force-push

If you keep the current history, the repo is still usable as a portfolio project, but it is not fully sanitized.