Portfolio catalog

Selected projects with evidence labels.

The catalog works without JavaScript. Use browser find or the static domain sections below; labels distinguish verified public evidence from design and research.

activeverified-publicDeveloper operationsAutomation and agentsEducation and documentation

CYWF Project Platform

Public project system for organizing repositories, issues, docs, and portfolio evidence.

Problem: A public portfolio needs more than a biography; it needs a project system that shows what exists, what is active, and where evidence lives.

Outcome: A project-centered model that points visitors to repositories, docs, case studies, and safe operational evidence.

Role: Project organization, Repository governance, Public-safe documentation

Tech: TypeScript, GitHub, Markdown

Case study Repository Docs

activeactive-developmentDeveloper operationsEducation and documentation

KP-DEV-HQ Portfolio Platform

Static Astro portfolio and Developer HQ evidence layer for the public CYWF site.

Problem: Previous iterations over-corrected toward telemetry and then toward self-promotional copy, making the site feel less like a project portfolio.

Outcome: A project-first information architecture with curated work up front and Developer HQ evidence available as supporting material.

Role: Portfolio architecture, Astro implementation, Data modeling, Accessibility review

Tech: Astro, TypeScript, Tailwind, GitHub Pages

Case study Repository Docs

activeverified-publicCybersecurityDeveloper operations

FortiPath

Cybersecurity-oriented public project tracked as active work needing hardening.

Problem: Security projects need clear public positioning without leaking implementation details or implying production readiness prematurely.

Outcome: Portfolio entry labels FortiPath as active but still hardening, with deeper claims deferred until public docs mature.

Role: Security framing, Project documentation, Readiness labeling

Tech: TypeScript, GitHub

Case study Repository

activedocumented-designField operations conceptsDeveloper operations

vTOC

Field-team command/coordination concept for Close Protection and Executive Protection contexts.

Problem: Operational tools for field teams need guardrails, approval boundaries, and project-neutral public language before product claims are made.

Outcome: Public entry frames vTOC as an active concept with architecture judgment, not a finished user-facing product.

Role: Concept architecture, Guardrail definition, Project narrative

Tech: TypeScript, Architecture notes

Case study Repository

activeverified-publicData and space systemsDeveloper operations

tle-fetcher

Public satellite-data utility tracked as active work needing hardening.

Problem: Space/data utilities should be easy to evaluate without overstating operational accuracy or live telemetry guarantees.

Outcome: Portfolio entry keeps the project visible as a space-systems/data utility while labeling maturity conservatively.

Role: Data utility framing, Repository evidence mapping

Tech: TypeScript, TLE data

Repository

activedocumented-designField operations conceptsAutomation and agents

AudiFi

Audio intelligence / field-support project tracked as active work needing hardening.

Problem: Audio and field-support concepts require privacy-sensitive framing and clear boundaries around what is prototype versus proven.

Outcome: Public portfolio entry preserves visibility while avoiding unsupported product claims.

Role: Concept framing, Public-safety review

Tech: TypeScript

Repository

prototypeverified-publicDeveloper operations

aliases

Developer workflow helper repository tracked in the public CYWF project set.

Problem: Small workflow tools often disappear from portfolio narratives even though they show how the development environment is maintained.

Outcome: The project catalog includes lightweight utilities alongside larger systems, with maturity labels instead of hype.

Role: Developer tooling, Repository hygiene

Tech: TypeScript

Repository

maintainedverified-publicCybersecurityDeveloper operations

Public Snapshot Pipeline

Committed JSON envelopes for repository, project, discussion, docs, and lab evidence.

Problem: GitHub Pages cannot depend on private runtime tokens or dynamic APIs for core content.

Outcome: Static envelopes keep public evidence routes available while scripts degrade gracefully when optional scopes are missing.

Role: Data contract design, CI scripting, Public-safety review

Tech: JSON, GitHub Actions, TypeScript

Case study Repository Docs

prototypeconcept-researchCybersecurityEducation and documentation

Browser-Local Labs

Progressively enhanced labs for graphs, threat-model thinking, and browser capability checks.

Problem: Interactive demos can overwhelm performance and blur illustrative data with authoritative evidence.

Outcome: Labs metadata labels purpose, privacy, limitations, and hydration policy.

Role: UX framing, Hydration policy, Accessibility alternatives

Tech: React islands, Astro, Canvas/SVG

Docs