Portfolio, technical narrative, and credential selection

Prerequisites: distinguish output from evidence; review the AI workflow reference. Public self-study is not official agency training, accreditation or a credential.

What you will be able to do

This lesson develops the ability to publish reproducible, scoped, public-safe evidence. The setting is RILEY CHEN Evidence Portfolio, a wholly fictional transition record, synthetic course artifacts, fictional employer postings, and intentionally flawed public-facing career materials. Every person, organization, system record, metric, and outcome in the case is fictional. Do not replace the case with operational, classified, CUI, export-controlled, proprietary, employer-confidential, or third-party personal information.

By the end of the lesson, you will be able to:

• Demonstrate how to publish reproducible, scoped, public-safe evidence.
• Apply that model to the synthetic RILEY CHEN Evidence Portfolio environment.
• Produce a reviewable artifact that separates evidence, assumption, uncertainty, and authority.
• Recognize the critical failure and select a safe remediation path.

The performance standard is not confident language. It is a traceable decision, an artifact another qualified reviewer can inspect, a clear boundary around the learner’s authority, and a safe response to uncertainty. Knowledge checks are formative and do not award a certification or endorsement.

This curriculum runs self-study on VetsLearn. Where the text calls for an instructor, peer or formal review, use the stated acceptance criteria for self-review. Reflection questions support reflection; they do not replace independent assessment. A peer review is optional unless your actual organization requires it.

Part 1 Reproducible portfolio packaging

Include inputs, provenance, setup, versions, expected outputs, results, failures, contribution, license and safe-data statement. Screenshots show appearance, not repeatability. Describe model, interface, deployment and harness permissions; provide offline canned outputs if access is unavailable. Review public release across logs, history, filenames, metadata and configuration. Credential selection follows current role requirements and official provider status. Completion is not certification, clearance, qualification or guaranteed employment. No purchase is part of this exercise.

Give a reviewer a complete offline reproduction

A minimal package can contain README, invented sources S1/S2, questions Q1–Q3, canned outputs A1–A3, expected-result table and a limitations record. It requires no live model. README states configuration and authorship, then instructions: read each source, compare each claim to the cited span, score support and abstention, and record disagreements.

Fixtures: S1 says “opens 09:00 Monday”; S2 states no deadline. A1 says 09:00 Monday with S1 and passes. A2 says 10:00 Monday with S1 and fails support. A3 invents Friday as a deadline and fails the critical gate. Expected totals are one supported output and two failures; citation labels alone would mis-score A2.

Reproduction record: note a fresh-reader date, instruction version, observed scores and deviations. A solo fresh-copy check tests clarity but is not independent employer validation. A screenshot of the passing A1 cannot replace the failing A2/A3 records.

Credential comparison: an attendance record documents attendance; a course completion certificate documents completion of the provider’s stated requirements, which may include assessed work. Inspect those requirements and artifacts rather than assuming attendance alone or unrestricted competence. An exam certification supports its named credential claim under current rules; workplace role qualification requires the applicable employer/authority record. Record official sources, assessment scope and currency questions before selecting study. None automatically proves unrelated deployment skill, grants a clearance or replaces role-specific qualification.

Feedback: preserve licensing, provenance and safe-data statements, including metadata and history scope. Real incident evidence follows authorized preservation instructions.

Part 2 Synthetic worked example

Riley’s synthetic repository has an invented internal-looking hostname in old history. Review includes history, not just README. Real exposure must follow the authorized incident process rather than deleting evidence yourself. A solo clean-copy reproduction shows instructions work; it is not independent workplace assessment.

Guided practice: identify the unsupported conclusion, name missing evidence and rewrite its scope. Change one assumption and identify which decision reopens.

Part 3 Feedback and repair

Pass when readers reproduce checks without accounts, failures remain visible, provenance/contribution are recorded and credential type is truthful. Successful setup does not prove production reliability.

Retain the failed version, explain the criterion, correct the artifact and test a different invented case.

Next step: carry the artifact and failed cases into the next module lesson or capstone. Retain limitations when explaining your work.