Evidence architecture

The skill comes first. The artifact verifies it.

This route explains how public claims connect to supporting artifacts without turning raw files into the main portfolio experience.

Presentation sequence

Five questions guide every proof relationship.

Recruiter-facing pages explain relevance before exposing raw artifacts.

04

Proof

Which public artifact, manifest, screenshot, export, script output, or report supports the claim?

Evidence routes

Existing proof surfaces remain available.

The architecture foundation adds a stable hub without replacing the established proof, dashboard, library, or case-study routes.

MAP

Claim-to-artifact proof

Primary recruiter-facing proof relationships and limitations.

LIB

Evidence library

Public artifacts, generated pages, preserved exports, manifests, and supporting records.

STA

Evidence status

Relationships among validated, tested, configured, documented, inconclusive, and not-tested results.

LAB

Home Lab case study

System context, technical work, validation outcomes, and limitations.

Catalog contract

Every migrated record will carry provenance and boundaries.

Later evidence phases must use the repository schema and migration contract rather than inventing new field sets.

PUB

Publication classification

Public original, sanitized derivative, metadata-only record, or source-reference-only entry.

Scope

Preservation without overstatement.

Original artifacts remain preserved. Public presentation can use generated pages, summaries, or sanitized derivatives, but the source record and claim boundary must remain traceable.