Topic 10 · Static project completion + release evidence

Complete, Release, and RecoverTurn one local interaction into a reviewable static release.

A release is not merely a URL. It is a bounded package that opens, behaves as expected, protects public data boundaries, remains usable, and can be restored when a release-only problem appears.

Before class

Bring or recreate the Topic 9 local app and smoke-test handoff, or use the supplied Study Sprint Release Lab. No prior packet, AI account, installed skill, Git history, hosting account, public URL, backend, API key, private data, consent/assent record, or identity evidence is required.

By the end

Four outcomes you can demonstrate.

The focus is judgment students can show, not vocabulary they can merely repeat.

01 · AUDIT

Judge a static project against four release gates using observable evidence.

02 · COMPLETE

Make or justify one bounded completion decision and preserve a last-working checkpoint.

03 · RELEASE

Use an optional public static route or an equal-credit local/course-lab demonstration.

04 · VERIFY

Run the same smoke checks after the route change, diagnose one case, recover, and explain the result.

Class route

Two meetings with separate learning arcs.

Meeting 1 plans 68 taught minutes plus a 12-minute flex and access buffer; Meeting 2 plans 68 plus 12.

MEETING 1

Complete and Package the Local Project

Recover the Topic 9 handoff, define completion, audit four release gates, make one bounded change, save a checkpoint, inspect the package, and run local smoke tests.

80 MIN

00:00–00:12
Recover + define completeOpen an own app or the supplied continuation; separate completion from feature count.
00:12–00:33
Four release gatesAudit purpose, behavior, access, and public safety with visible evidence.
00:33–00:51
Bounded change + checkpointChoose one completion move, test it, and preserve the last-working version.
00:51–01:08
Package + local smoke testMap public files and run exact local checks before any release route.
01:08–01:20
Checkpoint + flex/access bufferRecord evidence; switch to the course lab or projected route when setup blocks work.

Start Meeting 1

MEETING 2

Release, Retest, and Recover

Choose a public or equal-credit local route, inspect the public boundary, retest after the route change, diagnose a controlled release-only failure, recover, and assemble the Topic 11 handoff.

80 MIN

00:00–00:13
Retrieve + release claimReconnect the checkpoint and distinguish a URL from proof of learning.
00:13–00:31
Route + public boundaryChoose public static hosting or an equal-credit local/course-lab demonstration.
00:31–00:51
Post-route smoke + diagnosisRun the same checks, localize one release-only failure, and choose a recovery action.
00:51–01:08
Workflow brief + packetConnect audit, evals, release/recovery, disclosure, limitation, and Topic 11 evidence.
01:08–01:20
Submission + flex/access bufferConfirm accepted routes, cleanup, and LMS-owned deadline details.

Start Meeting 2

Evidence

Release Evidence Packet

Document one bounded completion decision, four release gates, a checkpoint and manifest, before/after route smoke evidence, a release diagnosis or passed edge case, recovery, a short workflow brief, disclosure, limitation, and Topic 11 handoff.

What to submit

Submit one completed packet through the course LMS before Topic 11. Preferred filename: Lastname-Topic10-ReleaseEvidence.pdf; maximum five pages. LMS text, DOCX/export, scanned paper, or an instructor-approved accessible alternative is accepted. The LMS supplies the exact deadline and grading-policy details.
Name the own-app, course-lab, projected/transcript, or approved accessible route; define the release contract and last-working checkpoint; rate all four gates from evidence; record one bounded completion move or justified no-change.
List only authorized public files/data; run the same Open/assets, Normal, Missing/revise, Access, and Public safety checks before and after the release route; record expected and actual results separately.
Diagnose and recover one release-only failure, or analyze a passed release edge case. Include the short audit → eval → release/recover brief, one human-review decision, assistance disclosure, known limitation, and Topic 11 handoff.
A public URL, repository, Git history, hosting account, installed skill, AI tool, code volume, and screenshot are optional and never determine core credit.

Open assignment

Boundary

Use fictional, public, or instructor-approved material. Do not publish or submit secrets, credentials, private prompts, grades, health/identity data, consent/assent records, student names, restricted course files, account/device screens, repository access, private absolute paths, or unnecessary identity evidence. No backend, login, database, model API, analytics, or production-readiness claim is required.

Access: The Study Sprint Release Lab is the account-free course-owned continuation. Public deployment is optional. Reopened local packages, course-lab simulations, projected/transcript runs, paper/LMS text, and approved accessible routes earn equal credit for equivalent evidence. Prior Topic 9 completion, Git, hosting, paid tools, AI access, and a public URL are not gates.

AI disclosure: Name the route, tools or people that materially helped, and what you accepted, changed, rejected, or verified. Do not submit full chats, credentials, or access proof.

References

Core sources and optional extensions.

The class deck contains the required explanation. These links support verification, deeper reading, or alternate access.

Editable Release Evidence PacketPrimary five-page route for audit, smoke, release, recovery, and Topic 11 handoff.Printable Release Evidence Packet PDFPaper/print route. Use HTML, LMS text, DOCX/export, or an approved route for accessible electronic completion.Study Sprint Release LabAccount-free course continuation with local/release smoke and controlled recovery.MDN Learn Web DevelopmentOptional web architecture and development reference.MDN Web Storage APIOptional storage reference; Web Storage is not secure storage.GitHub Pages QuickstartOptional public static route; an account and remote publishing are not required for core credit.Google PAIR GuidebookOptional trust, user control, error, and recovery design reference.AI Workflow Skill MapOptional mapping of planning, handoff, implementation, review, and maintenance practices.

Next week

Topic 11: Research, Sources, and Career Evidence

Carry the project purpose, one supported capability claim, source trail, disclosure, limitation, and career-ready story into the next week—even without a public URL.

Open next week