When: Campus and Main Street expose the same vocabulary, authority, navigation, or relationship fracture.
Then: Repair and retest the shared content before advancing W/ Faculty or W/ Builders.
W/ LEARNING PATHWAYS · WACK-LEARNING-PILOT-0001
TWO ROOMS.
ONE GATE.
Two rooms. One shared observation grammar. No program advances on enthusiasm alone.
Run one disciplined cold read in W/ Campus and one in W/ Main Street, capture the first point where the material needs oral rescue, and use the paired observations to decide what deserves the next bounded pilot.
ROOM 01W/ CAMPUSFirst failed instruction
ROOM 02W/ MAIN STREETFirst failed reconstruction
PAIRED OBSERVATION
REPAIR COREFACULTY?BUILDERS?HOLD
NO OBSERVATION → NO EXPANSION
Safety and authority boundary
This is a privacy-preserving practitioner pilot method. It is not user research consent, student assessment, member profiling, a PCI DSS assessment, a compliance result, or a substitute for the participant's own authority. Use anonymous participant labels and fictional or sanitized material only. Do not enter names, email addresses, cardholder data, credentials, client evidence, restricted architecture, grades, employment data, or assessment findings. The public tool keeps working text on the device and transmits nothing.
Shared protocol
Remove the author. Watch the material work.
A cold read is useful only when the facilitator resists becoming the missing interface.
- 01
Freeze the tested version
Record the exact public URL and visible release label before the session. Do not change the material during the cold read.
- 02
State the safe boundary
Explain that the exercise uses fictional or sanitized material, records no identity, and evaluates the material rather than the participant.
- 03
Let the reader work
Read the task exactly as written. Do not translate vocabulary, point to the answer, or supply a missing relationship.
- 04
Capture the first fracture
Record the first hesitation, incorrect inference, missing link, or request for explanation—not every stylistic preference.
- 05
Name the oral rescue
If intervention becomes necessary, record the exact explanation, example, or navigation cue the facilitator supplied.
- 06
Ask before teaching
Ask what the reader expected, what they thought the instruction meant, and what evidence would have made the next move obvious.
- 07
Propose the smallest repair
Prefer one changed sentence, relationship, example, label, or sequence over a new content franchise.
- 08
Define proof of improvement
State what a second cold reader must be able to do without oral rescue before the repair is accepted.
DEVICE-LOCAL PILOT WORKBENCH
Capture the first fracture.
Evaluate the material—not the reader. Working text stays in this browser until you download it. Nothing is submitted or stored by the site.
PARTICIPANT
One student or early-career reader who has not been coached on the W/ Campus material.
OBJECTIVE
Find the first place where the reader cannot reconstruct the payment story, authority boundary, or lab instruction without oral explanation.
SUCCESS CONDITION
A cold reader can complete the five tasks and explain where their conclusion stops without the facilitator supplying missing vocabulary or relationships.
SILENT TASK RUN
Let the reader work.
Check a task after the reader attempts it. Completion does not mean success; the observation record preserves what happened.
Record the material failure.
Decision gate
A fracture can earn a repair. A pattern can earn a pilot.
One completed anonymous Campus observation and one completed anonymous Main Street observation against recorded public versions. A single anecdote may trigger a repair; it does not automatically commission a new program.
When: The Campus reader can do the technical work, but the facilitator needs a clearer sequence, rubric, answer boundary, or authority prompt.
Then: Commission the smallest three-session Faculty pack needed to test that teaching problem.
When: A cold reader can follow the base payment story but cannot reconstruct the architecture, webhook, identity, deployment, provider, or test relationships of a fictional build.
Then: Commission one bounded hosted-payment capstone and test the account-data and security-influence paths together.
When: The evidence is only preference, the facilitator coached before the fracture, the tested versions differ materially, or either open program still needs a base repair.
Then: Record the limitation, repair the pilot, and run another cold read.
Portable field kit