Link Only Reviewed Public Work
External links are limited to public repositories or active project routes that are still safe to browse.
// Archive
Retired projects and boundary decisions
A public-safe record of work that moved out of the main showcase, was superseded, or is held back for privacy review. Safe public projects still get links; sensitive or private work is summarized without becoming a new index.
6
Decisions Logged
Retired, moved, held, superseded, or archived project decisions.
8
Safe Public Links
Only reviewed public surfaces are linked from this page.
2
Linkless Holds
Sensitive or private contexts stay summarized, not re-listed.
Archive Rules
The archive explains portfolio evolution without reopening private or unsafe surfaces.
Summarize Sensitive Removals
Private, employer-adjacent, regulated-environment, or internal artifacts are described by decision pattern, not indexed by name.
Prefer Maintained Successors
When an older direction has a clearer current replacement, visitors are sent to the maintained public surface.
Decision Log
4 entries include safe public links; 2 entries intentionally do not.
Moved 1 Held 1 Removed 2 Superseded 1 Archived 1
Moved to catalog
Live showcase trim
A small group of older browser demos was removed from the homepage live showcase but kept in the catalog where the work is still safe to browse.
Why
The live grid now prioritizes current screenshots and launch-ready apps; older demos belong in project context instead of competing with active highlights.
Source
Current src/data/projects.ts catalog entries and live-app screenshot policy.
Catalog skipped
Public repos intentionally outside the catalog
Some public repositories are intentionally omitted from the polished portfolio catalog because they are grab bags, placeholders, or lower-signal surfaces.
Why
The portfolio should stay navigable and product-oriented; the archive can name reviewed public exceptions without turning them into headline projects.
Source
src/data/catalog-policy.json intentionallySkippedPublicRepos.
Archived reference
DuplicateFF
DuplicateFF remains visible as a reference architecture rather than a current flagship utility, but it is outside the feed-backed active catalog.
Why
The profile projects feed omits it from the current portfolio set; the archive keeps a direct public GitHub link without generating a project detail page.
Source
SysAdminDoc projects.json feed and current archive policy.
Removed from catalog No public links
Legacy private or archived batch
An older batch of private, archived, or placeholder repositories was removed from the catalog and is not re-listed here by name.
Why
The portfolio should explain the cleanup pattern without turning old private or low-signal repository names into a new public index.
Source
Current archive policy and public/private boundary review.
No public project link is surfaced for this decision.
Held for review No public links
Employer-adjacent boundary hold
Employer-adjacent artifacts that could expose customer or internal context are excluded from visible project surfaces and public screenshots.
Why
Regulated-environment and customer-specific work needs explicit public-safety review before promotion, even when repository metadata is technically public.
Source
src/data/catalog-policy.json privacyReviewRequired and current security-boundary review.
No public project link is surfaced for this decision.
Superseded
Start Menu tooling successor
A legacy Start Menu management direction is represented by the current Start-Menu-Organizer project instead of keeping older names in the portfolio.
Why
The archive should point visitors toward the maintained public surface when an older tool line has a clearer successor.
Source
Current src/data/projects.ts catalog entry for the public successor.