Specify an enforceable download gate

Objectives

Halcyon Clinics needs a machine-readable plan for its document download change. The delivery lead proposes a dependency-only scan and treats an unavailable scanner as a clean result. Neither decision demonstrates that a patient cannot read someone else's document.

Complete the fields from the release contract below. Keep the field structure; use testing-category acronyms and a boolean where requested. This plan records the requirement, verification scope and release decision behavior, not a claim that checks have already run.

Requirement R-17: enforce per-document authorization on the server.
Acceptance test: a different patient requesting a document must be denied.
Design: model browser-to-API trust boundary before implementation.
Code gate: static analysis of application source, independent of execution.
Component gate: inventory third-party versions and known vulnerabilities.
Runtime gate: external requests against a running service, no internal probes.
Required test unavailable or failed: block release.
Maximum unresolved critical findings without an exception: 0.
Evidence must bind both commit identifier and artifact digest.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

1. Step 1

   Trace the denied path

   Copy the requirement reference from the contract, then describe who is denied and why. Check that your sentence distinguishes another person's access from a permitted download.

   Requirement and denied cross-patient test are explicit

2. Step 2

   Locate changed assumptions

   Describe the two endpoints whose trust differs. Do not substitute transport encryption for a statement about which components are trusted.

   Design identifies the client-to-service boundary

3. Step 3

   Match observation points

   For each category field, ask whether its input is application code, borrowed components, or responses from an executing service. Use the corresponding category abbreviation taught in the room.

   Three testing methods match their observation points

4. Step 4

   Represent uncertainty honestly

   Choose the boolean that prevents an absent result from satisfying a required test. Avoid a quoted sentence in a boolean field.

   Missing required results cannot pass the gate

5. Step 5

   Set the allowed finding count

   Translate the contract's limit into a numeric value. This count is about findings without an applicable exception, not all historical findings.

   Unexcepted critical findings respect the release limit

6. Step 6

   Bind both identities

   List the two identities named in the contract. One identifies reviewed source; the other identifies the exact built output considered for deployment.

   Evidence identifies both source and built artifact

Rules summary

• XP on pass

  40 bonus XP the first time every check goes green.

• Paid hints

  2 available. Each costs 25% of the lab XP (about 10 XP).

• Reveal solution

  Scores 0 XP and unlocks only after 3 check runs.

• Attempt cap

  60 check runs per learner. The runner warns you in the last 10.

• Drafts

  Your editor content is saved in this browser, so a reload will not lose work.

• Walkthrough

  Always free and never penalised: use it before spending a hint.