Skill
What technical capability is being demonstrated?
Evidence architecture
This route explains how public claims connect to supporting artifacts without turning raw files into the main portfolio experience.
Presentation sequence
Recruiter-facing pages explain relevance before exposing raw artifacts.
What technical capability is being demonstrated?
What administrative or troubleshooting work was performed?
What was directly validated, configured, documented, inconclusive, or not tested?
Which public artifact, manifest, screenshot, export, script output, or report supports the claim?
What environment, access boundary, limitation, and unsupported conclusion must remain visible?
Evidence routes
The architecture foundation adds a stable hub without replacing the established proof, dashboard, library, or case-study routes.
Primary recruiter-facing proof relationships and limitations.
Public artifacts, generated pages, preserved exports, manifests, and supporting records.
Relationships among validated, tested, configured, documented, inconclusive, and not-tested results.
System context, technical work, validation outcomes, and limitations.
Catalog contract
Later evidence phases must use the repository schema and migration contract rather than inventing new field sets.
Source repository, original path, source commit, integrity identifier, and collection context.
Skill, task, result, supported claim, proof route, scope, and limitation.
Public original, sanitized derivative, metadata-only record, or source-reference-only entry.
Scope
Original artifacts remain preserved. Public presentation can use generated pages, summaries, or sanitized derivatives, but the source record and claim boundary must remain traceable.