This ledger separates inspectable artifacts from business context and external authority. A live URL proves deployment, not adoption. A repository proves inspectability, not impact. Every material claim states its boundary.
Verified
A public artifact or automated catalog directly supports the claim.
Demonstrated
A runnable implementation supports the capability, with explicit environment limits.
Contextual
A real career or business result is described, but primary records are confidential or external.
Spine API health
Server-side probes of VAP, AegisAI, and Enterprise RAG /health. Warm budget: 3s. Render Free interim: first hit after idle often takes 15–40s (spin-down). Starter upgrade lands later for always-on panels — see cloud free-tier split for AWS/GCP infra proof meanwhile.
Probing spine APIs…
Dedicated page: /spine-health
The public Substack RSS feed and local catalog show a sustained series from April 2026 through the current control-plane thesis.
Boundary: Publishing cadence demonstrates sustained authorship, not independent readership, citation, or adoption.
Home, hire, work panel, and /technical-review lead with AegisAI → VAP → Enterprise RAG → Content Factory → ADR hub.
Boundary: Spine is the recommended review path; catalog demos remain available under Full portfolio.
12 platform URLs and 5 teaching pattern viewers are catalogued and checked by portfolio CI.
Boundary: Several free-tier APIs can cold-start; catalog live does not imply customer production traffic.
Every counted repository has an explicit catalog entry and review link.
Boundary: Repository count measures inspectability, not adoption or engineering impact.
The architecture portfolio exposes numbered ADRs and the local validator checks the count when the sibling repository is present.
Boundary: ADRs document decisions; reviewers should still inspect implementation and tests.
The golden-eval registry defines six suite kinds and selected consumers use suites as CI gates (adversarial suite enterprise_rag_adversarial_v1).
Boundary: Not every suite currently gates every platform; coverage is stated per repository.
Public script + JSON artifact: health → VAP/ERAG (auth-gated honestly) → AegisAI approval_required → FinOps meter. See GOLDEN_PATH.md and docs/artifacts/golden-path/latest.json.
Boundary: Full ask→answer needs VAP_API_KEY/RAG_API_KEY; ACF live publish still requires Clerk.
Enterprise case study describes the workflow, architecture responsibility, governance boundary, and reported operational result.
Boundary: Employer-confidential result; underlying operational records are not public.
Career history is cross-checkable through the public LinkedIn profile and the portfolio career timeline.
Boundary: LinkedIn is the credential source; the portfolio does not independently certify employment.
External authority gates
These are intentionally not presented as completed. They are the remaining evidence needed for a defensible top-1% authority claim.