# Version-Control Standard

This portfolio is kept as a reviewable public repository. The goal is to make the work easy to inspect while keeping private source code and credentials out of scope.

## Commit Hygiene

- Use short, descriptive commit messages.
- Group related changes together.
- Keep generated output, caches, dependency directories, and local environment files out of commits.
- Prefer case-study summaries over large raw archives.

## Public Portfolio Boundary

- Public repositories can be linked directly.
- Private repositories should be summarized with scope, responsibilities, decisions, and outcomes.
- Do not publish private source code, credentials, tokens, local `.env` files, unpublished datasets, or organization-specific implementation details.

## Review Checklist

Before publishing, check:

- `git status --short` shows only intentional files.
- A repository search for credential, placeholder, and unfinished-work terms returns no public-facing leaks.
- Private repositories are represented as case studies, not copied source.
- README links work from GitHub.
- The GitHub Pages site loads `index.html`, `styles.css`, and `script.js`.