Skip to content
← Free FDE training guides

Free learning / Start guide

Your first client-delivery portfolio

Choose a starting route, prepare your workspace and plan six working sessions.

No account needed. Use your own copy for writing and keep the original as a reference.

LockedIn Labs · LockedIn FDE Training · Learner start guide · Edition 1

This guide turns the six-lesson client-delivery course into a sequence of working sessions. Your project is a fictional administrative intake assistant. The goal is to leave with work you can explain to a receiving engineer and an operator: a useful problem, a bounded implementation, evidence and a handoff.

Choose your starting route

Your starting pointBegin hereBring to the first review
New to software deliveryRead the workbook's engagement and source packet; draw the request journey on paper. Pair with someone who can explain a small JavaScript function.A workflow sketch and three questions you cannot yet answer
Software engineer new to AI deliveryRun the offline starter, inspect its authorization and source-selection steps, then read the discovery lesson.One actual trace and one assumption the trace cannot prove
Experienced with AI prototypesAttempt the field-change drill before reading its worked interpretation; then review the gaps in your packet.Your first decision, evidence and one revised assumption

These are self-selected learning routes, not placement decisions. The full course uses existing Academy access. The free files below work without an account or an API key. If you cannot run Node.js yet, follow the workbook as a tabletop exercise and label outputs “expected, not executed.” Do not invent a successful run.

Choose a short practice for your current gap

In the free practice library, choose a topic rather than attempting every exercise before your first portfolio. The time labels describe the exercises; setup, discussion and revision can add time.

What you need nextTopic to chooseFirst useful task
Decide what the client should automateDiscoveryCompare lookup, drafting, workflow and agent choices against the supplied brief
Move from running code to explaining a diffImplementationMake the first bounded code change, then investigate the output contract
Understand what happens between agent stepsAgent engineeringTrace proposed tools or loop limits; use source lifecycle when procedures change
Decide what the evidence supportsEvaluationChallenge the effort claim or review the delivery packet
Let another person continue the workHandoffRepair an operator state and observe the receiving task

Keep the first attempt and one revision in the relevant portfolio section. A topic selection changes only what you see; it does not enroll you or record completion. Use the six-session sequence below when you are ready to connect the artifacts.

For a self-contained interactive session, open the AI route-selection lab. Make a first prediction, inspect a paired request and keep your original reasoning when a changed deadline alters the comparison. You can download a local record without Academy access.

Continue through the free guides

Each online guide ends with three concrete artifacts to keep and a suggested next free session. Start with the workbook, practice discovery, investigate source and draft quality, then work through recovery, review capacity, a changed brief, receiving review and the enterprise rehearsal. Use the “Keep your work & continue” link in the section navigation to find that handoff. This is an optional study sequence, not an enrollment or completion record; keep your writing in your own working copy. Academy instruction remains available through the separate related-lesson link.

Start with an editable portfolio

Download the six-session portfolio template and open it in a text or Markdown editor. It gives you a compact place for the discovery brief, implementation record, service boundaries, evaluation, handoff and individual defense. Keep one document or split its numbered sections into the six files below.

Start with the discovery section and retain your first attempt. Add evidence IDs as you work, preserve unrun cases and record why feedback changed your decision. The final receiving-team checklist helps you prepare a packet another person can inspect. This is your local working copy; downloading it does not save work to Academy or record completion.

Prepare one small workspace

  1. Download the workbook and starter from the course page.
  2. Keep the starter unchanged as your reference and edit a separate copy.
  3. Use Node.js 24 for the optional code exercise. Ask your usual support contact for help installing tools through an approved source if necessary.
  4. Run node fde-client-delivery-starter.mjs supported from the download folder. The result should identify a scripted draft using ADMIN-FORM-04, version 3.
  5. Create a local portfolio folder with the six artifact names below. Use only invented records. Record the file revision, command and output when you run code.

A syntax error is a debugging task, not a reason to erase the attempt. Check the filename, the Node version and the first reported error. Retain the original starter so you can compare the smallest changed section. Never paste credentials or real customer information into a help request.

From a successful run to your first edit

If the starter runs but the next code change feels unclear, follow the workbook's twenty-minute first-change exercise. You will change one request category, introduce conflicting current sources, apply a supplied procedure-owner decision and confirm that unauthorized access still stops. Keep the original file and your predictions beside the actual runs. No package, model account or API key is needed. This optional extension adds time beyond the core lesson estimate.

Six working sessions

The suggested core lesson time is about eleven hours. Building, revision, optional labs and receiving-team practice take additional time. Spread the sessions across as many days as you need; this is a planning guide, not a promise of job readiness.

SessionWork to completeEvidence to keepReady to continue when
1. DiscoverInterview the fictional sponsor, operator and technical owner using the workbook. Separate supplied facts from assumptions.01-discovery.md: problem, baseline, smallest useful slice and decision rolesA partner can explain which operator task improves and what remains unknown
2. BuildRead the starter, run a permitted scenario and make one bounded change in a copy. Use the implementation lesson to prepare and review AI assistance if available.02-implementation.md: intent, changed lines, observed output and unresolved limitationYou can explain the changed behavior without relying on an AI-generated summary
3. Design boundariesTrace identity, location, procedure and output. Draw both supported and manual paths.03-service-boundary.md: input/result contract, data journey and exception rowsThe receiver can point to the enforcing control and useful next action for each exception
4. EvaluateUse the workbook's cases to compare expected and actual results. Keep failed and unexecuted rows.04-evaluation.md: candidate/fixture versions, case evidence and scoped decisionEvery claimed result has evidence, and a boundary failure cannot disappear into an average
5. Transfer operationWrite the runbook, then let another person drive source inspection and manual recovery.05-handoff.md: receiving actions, gaps, revision and recovery rolesThe receiver can continue the synthetic task without you taking over
6. DefendAssemble the packet and run the ten-minute demonstration. Answer one changed-brief challenge.06-decision.md: recommended next scope, evidence, uncertainty and individual revisionYour recommendation follows the evidence, including reasons to withhold expansion

Lesson entry points (Academy access required):

Find a teaching section quickly

In a lesson's Learn stage, expand Jump to a section and choose the topic you need. The heading receives keyboard focus and moves into view, so you can resume from the relevant explanation without scanning the entire lesson. Choose Learn again to return to the reading guide. This navigation does not clear your practice writing or count a section as completed.

Work with a delivery partner

Rotate builder and receiver roles after each session. The builder explains one claim and the evidence behind it. The receiver asks one question, attempts one relevant action, and records where the explanation or handoff breaks down. Each person retains their own reasoning and revision even when the implementation is shared. Review the work against the lesson's published criteria; do not compare learners by how confidently they present.

Use a five-minute closing conversation:

  • What did we actually observe, and what did we only expect?
  • Which assumption could change the next decision?
  • What is the smallest useful action before our next session?

If working alone, narrate the receiver's actions and label the result a self-review. That is useful practice; it does not establish independent acceptance.

When you get stuck

Bring a small, answerable question to the lesson mentor, facilitator or peer. The mentor is a learning aid; a response does not authorize a production change or award a credential. Use this brief with synthetic details only:

Text example
Lesson and artifact:
What I intended to happen:
Exact step or command I tried:
Observed result or first error:
Relevant small excerpt (no secrets or customer data):
My current explanation:
The specific decision I need help with:

Do not replace a difficult case with a happy-path screenshot. For a conceptual gap, revisit the section named in knowledge-check feedback. For a code gap, compare the changed lines against the reference. For a receiving gap, repair the handoff and repeat the one action that was unclear.

Pack the work for review

In Academy, use the existing practice and evidence workflow available to your account. If you do not have that access, keep the portfolio locally and arrange a facilitated review through your existing program contact. Do not send private materials to an invented submission address.

Use the receiving-review sheet for a 25-minute peer or self-review. Agree a question, trace the six artifacts, let a receiver attempt one task and retain one actionable repair with its next evidence.

Before presenting, make sure the six files use the same scope, candidate and source versions. Open with the operator task; show a supported result and a useful failure path; let the receiver act; close with the next decision. Identify scripted behavior clearly. Keep course completion, any provider-issued credential, independent qualification and an employer's staffing decision distinct.

Free resources:

Choose an additional practice lab

The free practice library collects the discovery interview, executable output-contract and tool-dispatch investigations, draft-review calibration, incident trace and enterprise rehearsal. Choose the exercise that addresses your current gap; completing every optional lab is not a prerequisite for starting the core course. Keep its artifact with the corresponding session. Worked instruction and review guidance remain in your existing Academy course.

Before you move on

Keep the evidence of your work.

  • A starting route and a realistic first session.
  • A local place to keep your six portfolio artifacts.
  • One question to bring to a facilitator or delivery partner.

Keep these in your own working copy. Reading this page does not save work or record completion.

Suggested next free session

Client delivery workbook

Set up the shared case before your first interview. This is a suggested sequence; choose the practice that addresses your current gap.

Open the next free guide
Have Academy access?

Continue with worked explanations, practice and review in the related lesson.

Open the related Academy lesson →
Back to top ↑