WRWEB ENGINEERING
REFORGING07 · 1/7
ALL LESSONS→WEEK 07→MONDAY

UNDERSTAND · HTTP + HYPERMEDIA

Links as affordances

Hypermedia controls state30–60 MINUTESCORE + PRACTICAL
01

GROUND

Problem

What becomes confusing, fragile, or impossible without understanding links as affordances? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

HTTP and hypertext scale by exchanging representations through standardized methods, status codes, headers, links, and forms.
02

LEARN

Concept explanation

Links as affordances belongs to “Hypermedia controls state”. Hypermedia representations advertise valid next actions through links and forms.

For links as affordances, trace concrete input, state transition, output, and failure through a request/response contract whose method, status, headers, representation, and next actions are observable.

A client sends a request; a server returns a representation plus metadata. Hypermedia controls advertise valid next actions. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Observable

Evidence produced by the links as affordances experiment: output, state, trace, bytes, timing, or diagnostics.

Invariant

Condition that must remain true while inputs or implementation of links as affordances change.

Boundary

Point where links as affordances crosses ownership, representation, time, process, network, or trust.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Baseline · one variable

SETUPBuild three server-rendered states connected only by links and POST forms.

OBSERVEEvery state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.

WHY IT MATTERSThis isolates the normal contract of links as affordances; preserve its raw evidence as the control for every later comparison.

Boundary · same contract, harder input

SETUPDisable JavaScript and complete full workflow.

OBSERVERecord what remains invariant and the first representation, owner, size, or timing value that changes in curl · Chromium Network · server logs.

WHY IT MATTERSA boundary example is useful only when one named dimension changes and everything else stays comparable.

Failure · evidence before repair

SETUPSubmit invalid transition and return useful 4xx representation with recovery link.

OBSERVECapture the first divergence from the baseline, including exact input, diagnostic, state, and recovery result. Expected recovery: Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.

WHY IT MATTERSThe diagnostic is part of the interface. Repair the proven cause, not the most visible symptom.

Cross-layer · follow ownership

SETUPTrace links as affordances one layer below its usual abstraction through a request/response contract whose method, status, headers, representation, and next actions are observable.

OBSERVECompare curl -v output, request method, status, cache metadata, redirects, and representation bytes.

WHY IT MATTERSThe lower layer is earned when it explains evidence the current layer cannot. Otherwise keep links as affordances at the simpler boundary.

03

SEE

Worked example

Start from supplied lab.sh. Focus: Build three server-rendered states connected only by links and POST forms.

  1. Run: chmod +x lab.sh && ./lab.sh
  2. Save baseline evidence. Compare curl -v output, request method, status, cache metadata, redirects, and representation bytes.
  3. Boundary case: Disable JavaScript and complete full workflow.
  4. Failure case: Submit invalid transition and return useful 4xx representation with recovery link.
RESULT
Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable. Starter-level baseline: headers.txt begins with an HTTP status line; body.txt contains the representation; byte count is greater than zero.
04

START HERE

Starter material

PREREQUISITEScurl plus a POSIX shell. Baseline uses public example.com and needs no account or API key.

ONE-TIME SETUPmkdir reforging-http && cd reforging-http

Create lab.sh, paste this exact content, then run the command below.

#!/usr/bin/env sh
set -eu
url="${1:-https://example.com/}"
printf '%s\n' '# links as affordances'
curl -sS -D headers.txt -o body.txt "$url"
sed -n '1,12p' headers.txt
printf 'body bytes: ' && wc -c < body.txt
RUNchmod +x lab.sh && ./lab.sh

STOP / CLEANUPNo background process. Remove headers.txt and body.txt only after saving evidence.

05

DO WITH GUIDANCE

Guided exercise

Observe one rule: links as affordances

  1. Normal case: Build three server-rendered states connected only by links and POST forms.
  2. Write predicted evidence from this named case before running starter.
  3. Change one input while holding environment constant.
  4. Run exact normal case. Save commands, inputs, outputs, and diagnostics in notebook.
  5. Explain changed evidence using lesson mental model in no more than five sentences.
Concrete guided solution
  1. Copy the supplied lab.sh unchanged and run: chmod +x lab.sh && ./lab.sh
  2. Write this prediction before inspecting output: Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.
  3. Perform only the named normal case: Build three server-rendered states connected only by links and POST forms.
  4. Save the raw output, then annotate input → transition → evidence. Use curl · Chromium Network · server logs to confirm the transition rather than inferring it.
  5. Compare prediction with evidence; if they differ, keep both and write the rule that explains the difference. Reference baseline: headers.txt begins with an HTTP status line; body.txt contains the representation; byte count is greater than zero.
06

DO ALONE

Independent exercise

Find the boundary: links as affordances

  1. Create second case from blank file: Disable JavaScript and complete full workflow.
  2. Then create controlled failure: Submit invalid transition and return useful 4xx representation with recovery link.
  3. Use curl · Chromium Network · server logs to prove behavior, then repair controlled failure.
  4. Compare result against supplied acceptance checks and reference approach before marking complete.
Concrete independent solution
  1. Duplicate the starter into a clean comparison case; change only this boundary: Disable JavaScript and complete full workflow.
  2. Save its evidence beside the baseline and identify the first changed value. Compare curl -v output, request method, status, cache metadata, redirects, and representation bytes.
  3. Create the exact controlled failure: Submit invalid transition and return useful 4xx representation with recovery link.
  4. Reproduce baseline exactly: Build three server-rendered states connected only by links and POST forms.
  5. Write observation table with columns input, state transition, output, and failure for links as affordances.
  6. Run boundary case unchanged: Disable JavaScript and complete full workflow.
  7. Trigger controlled failure: Submit invalid transition and return useful 4xx representation with recovery link.
  8. Compare evidence with reference outcome: Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.
  9. Rerun baseline, boundary, and repaired failure together. Accept only if all reproduce: Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.
07

COMPARE

Expected result

  • Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.
  • headers.txt begins with an HTTP status line; body.txt contains the representation; byte count is greater than zero.
  • Controlled links as affordances failure produces captured evidence; repair restores stated invariant without hiding error.
08

PROVE

Acceptance checks

Lesson is complete only when every check is true. Each check is stored locally and travels with your JSON backup.

0/5 complete · saved on this device

09

UNSTICK

Hints

Reveal hints
  1. Start with supplied normal case exactly as written: Build three server-rendered states connected only by links and POST forms.
  2. For boundary case, change only named dimension: Disable JavaScript and complete full workflow.
  3. If result is confusing, diff raw inputs and evidence before editing implementation.
  4. If tool shows nothing useful, move observation one boundary lower: representation, runtime, OS, or network.
10

VERIFY

Solution

Attempt both exercises before opening reference approach.

Reveal reference solution
  1. Run unmodified starter and preserve baseline evidence: headers.txt begins with an HTTP status line; body.txt contains the representation; byte count is greater than zero.
  2. Reproduce baseline exactly: Build three server-rendered states connected only by links and POST forms.
  3. Write observation table with columns input, state transition, output, and failure for links as affordances.
  4. Run boundary case unchanged: Disable JavaScript and complete full workflow.
  5. Trigger controlled failure: Submit invalid transition and return useful 4xx representation with recovery link.
  6. Compare evidence with reference outcome: Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.
11

PREDICT · INSPECT · BREAK · DEBUG · MEASURE

Interrogate reality

Prediction: write expected output, state transition, ordering, and failure evidence before running either exercise.

Inspection: Use curl verbose mode and Chromium Network to trace methods, redirects, caching, cookies, payloads, initiators, and timing.

Measurement: Count requests, bytes, round trips, cache hits, server time, and client synchronization code.

INSPECT

Capture raw evidence before explaining.

BREAK

Change one assumption and force controlled failure.

DEBUG

Find cause with curl · Chromium Network · server logs before editing fix.

TOOL DRILL · keyboard only · record one retrievable command or shortcut
12

MASTERY + FRONTIER + BOUNDARY

Own the knowledge

TEACH

Explain links as affordances at beginner, intermediate, and senior depth.

REBUILD

Recreate smallest useful example from blank file without notes or AI.

RETRIEVE

Schedule recall for day 1, 7, 30, and 90.

Creative frontier lab

Try first without opening the solutions. The constraints invite invention; the reference gives one concrete direction, never the only valid answer.

Constraint inversion

Re-solve links as affordances by removing the most convenient abstraction. complete the workflow using links, forms, redirects, and status codes with JavaScript disabled.

CONSTRAINTKeep the same inputs, observable result, and failure evidence; change the means, not the contract.

ORIGINAL IDEATurn subtraction into a design tool: the missing abstraction should reveal which responsibility it used to hide.

Reveal frontier solution
  1. Freeze the contract as three fixtures: Build three server-rendered states connected only by links and POST forms. / Disable JavaScript and complete full workflow. / Submit invalid transition and return useful 4xx representation with recovery link.
  2. List every convenience used by the starter; remove the highest-level one while preserving chmod +x lab.sh && ./lab.sh.
  3. Implement the smallest replacement using complete the workflow using links, forms, redirects, and status codes with JavaScript disabled.
  4. Run all fixtures and compare raw evidence. Keep the simpler version unless the removed abstraction has a demonstrated benefit.
Representation x-ray

Build an explanation artifact for links as affordances: save a complete request/response transcript that another person can replay.

CONSTRAINTA peer must be able to locate the first divergence without reading implementation code.

ORIGINAL IDEATreat the explanation itself as a product: make invisible transitions visible, replayable, and diffable.

Reveal frontier solution
  1. Create one row or timestamped event for each transition in: Build three server-rendered states connected only by links and POST forms.
  2. For every row record input, representation, owner, operation, output, and tool evidence from curl · Chromium Network · server logs.
  3. Replay Disable JavaScript and complete full workflow.; highlight only changed rows.
  4. Replay Submit invalid transition and return useful 4xx representation with recovery link.; stop at the first divergent row and attach its recovery action.
Adversarial remix

Combine the boundary and failure into a new user-visible scenario for links as affordances. make every failure response advertise a valid recovery action.

CONSTRAINTDo not merely add more input. Invent a recovery interaction, alternate representation, or self-checking behavior.

ORIGINAL IDEAMake the system teach its own limits: the artifact should expose the invariant and offer a safe next action when it breaks.

Reveal frontier solution
  1. Combine these two pressures without changing them: Disable JavaScript and complete full workflow. AND Submit invalid transition and return useful 4xx representation with recovery link.
  2. Name the invariant that must survive and the user-visible evidence when it cannot: Every state exposes next valid actions; refresh after POST does not duplicate mutation; failure remains navigable.
  3. Implement this original direction: make every failure response advertise a valid recovery action.
  4. Demonstrate baseline, combined failure, recovery, then baseline again; save the sequence as a regression fixture.

Capability frontier

Push links as affordances until another layer becomes justified. Record one robust technique, one contextual trade-off, and one labeled hack or historical curiosity.

CORE · PRACTICAL · CONTEXTUAL · HACK · FRAGILE · HISTORICAL · GOLF

Boundary

Hypermedia becomes strained when interactions require high-frequency local manipulation or long-lived peer state.

If this vanished tomorrow…

Use URLs, links, forms, server-rendered documents, status codes, and explicit refresh.

Why next layer is earned

HTML is earned when the representation must become a navigable, semantic document.