RTT Mastery Scenario Gauntlet — Instructor Version

archive_org module — instructor_materials/scenario_gauntlet_instructor.md#

Purpose of This Instructor Guide#

This guide provides:

• correct answers for all five scenarios
• structural reasoning aligned with RTT/1
• common student misconceptions
• grading notes for each task
• operator‑chain alignment

All reasoning is structural, not content‑based.

Scenario 1 — Government Records Portal#

Snapshots: 2012, 2013, 2016, 2019, 2023
Structural Changes:

• 2012→2013: none
• 2013→2016: template update
• 2016→2019: navigation restructure
• 2019→2023: minor CSS shift
  Substrate: HTML
  Collection: govdocs

Instructor Key#

1. Drift Levels

• 2012→2013: none
• 2013→2016: minor
• 2016→2019: moderate
• 2019→2023: minor

2. Continuity Kernel

• header
• footer
• records index

3. Continuity Breaks

• none

4. Substrate Stability

• HTML → medium stability

5. Most Reliable Snapshot

• 2023
  Reasoning: low drift, strong continuity, stable substrate, no breaks.

Scenario 2 — Vintage Software Index#

Snapshots: 2011, 2014, 2018, 2022
Structural Changes:

• 2011→2014: none
• 2014→2018: minor layout update
• 2018→2022: none
  Substrate: HTML
  Collection: vintagesoftware

Instructor Key#

1. Drift Levels

• none
• minor
• none

2. Continuity Kernel

• header
• footer
• version listing

3. Stability & Drift Risk

• very high stability
• technical collections tend to be versioned and stable

4. Why Stable?

• versioned systems rarely change structure
• minimal redesign pressure

5. Most Reliable Snapshot

• 2022

Scenario 3 — Academic Journal Archive#

Snapshots: 2012, 2015, 2018, 2021, 2024
Structural Changes:

• 2012→2015: template refresh
• 2015→2018: navigation restructure
• 2018→2021: CMS migration
• 2021→2024: minor CSS update
  Substrate: Mixed (HTML + PDF)
  Collection: journals

Instructor Key#

1. Drift Levels

• minor
• moderate
• high (CMS migration)
• minor

2. Regime Shift

• 2018: static → CMS

3. Continuity Kernel

• header
• footer
• journal index
• issue listing

4. Mixed Substrate Notes

• PDF layer increases stability
• HTML layer drift must be considered

5. Most Reliable Snapshot

• 2024
  Reasoning: post‑migration stabilization + strong continuity + mixed stability.

Scenario 4 — Local News Archive#

Snapshots: 2010, 2011, 2013, 2016, 2017, 2020, 2024
Structural Changes:

• 2010→2011: minor CSS
• 2011→2013: moderate layout
• 2013→2016: high (redesign)
• 2016→2017: none
• 2017→2020: high (CMS migration)
• 2020→2024: minor CSS
  Substrate: HTML
  Collection: news

Instructor Key#

1. Drift Levels

• minor
• moderate
• high
• none
• high
• minor

2. Continuity Breaks

• none in timeline
• structural breaks due to redesign + CMS migration

3. Continuity Kernel

• weak or minimal
  (news sites often lack stable structure)

4. Why High Drift?

• frequent redesigns
• business‑driven layout changes
• CMS migrations common

5. Most Reliable Snapshot

• 2024
  Reasoning: post‑migration stabilization; earlier snapshots unstable.

Scenario 5 — Museum Exhibit Archive#

Snapshots: 2013, 2014, 2016, 2019, 2023
Structural Changes:

• 2013→2014: none
• 2014→2016: minor layout update
• 2016→2019: mixed substrate introduced
• 2019→2023: navigation restructure
  Substrate: Mixed
  Collection: cultural

Instructor Key#

1. Drift Levels

• none
• minor
• moderate (substrate change)
• moderate

2. Continuity Kernel

• header
• footer
• exhibit index

3. Mixed Substrate Notes

• HTML + image → medium stability
• image layer increases stability
• HTML layer drift must be considered

4. Regime Shifts

• 2016: HTML → mixed substrate

5. Most Reliable Snapshot

• 2023
  Reasoning: stable mixed substrate + strong continuity + post‑shift stabilization.

Grading Guidance#

Mastery: 45–50
Proficiency: 38–44
Developing: 30–37
Needs Support: ≤29

Common Student Misconceptions#

• Confusing content changes with structural drift
• Treating visual differences as drift
• Misidentifying substrate stability
• Assuming newest snapshot is always best
• Listing content blocks as continuity kernel elements

Instructor Tips#

• Emphasize structure over content
• Encourage sketching snapshot layouts
• Reinforce drift as structural, not semantic
• Use continuity kernel as anchor for reasoning