Lab 30: Link Integrity Scanner

time to tie your shoes

Lab 30: Link Integrity Scanner

Automated internal link analysis and digital system self-awareness

The Experiment

What happens when a digital system examines its own connectivity? This tool scans internal links for health, missing targets, and circular references โ€” but more than utility, it’s an exploration of self-awareness in networked content.



Live Results

Health Overview

Total Links: โ€”
Valid Links: โ€”
Broken Links: โ€”
Health Score: โ€”

Detailed Analysis

Broken Links
No analysis performed yet
Circular References
No analysis performed yet
Orphaned Pages
No analysis performed yet

Connection Mapping



Technical Notes

This scanner operates entirely in the browser, analyzing the current page’s link structure. In a production environment, this could be expanded to:

  • Server-side analysis: Complete site crawling
  • Database integration: Historical link health tracking
  • Automated monitoring: Regular integrity checks
  • Repair suggestions: Automated fix recommendations

Philosophical Implications

What does it mean for a system to examine itself? This tool represents a form of digital introspection โ€” the archive becoming aware of its own connectivity, its own coherence.

The circular references we detect aren’t bugs but features: every self-referential link is a moment where the system acknowledges its own existence. The health score becomes a measure not just of technical integrity but of narrative coherence.

In the end, broken links are like gaps in memory โ€” places where the intended connection failed. But unlike human memory, we can measure these gaps precisely, map them, even repair them.

The question remains: does fixing every broken link make the system more coherent, or does it eliminate the productive spaces where new connections might emerge?


Lab Results

Methodology: Client-side JavaScript analysis with real-time reporting
Coverage: Single-page analysis (current page links)
Accuracy: High for anchor links, limited for cross-page validation
Performance: Non-blocking, progressive analysis

This experiment explores the boundary between utility and self-reflection โ€” a tool that serves the site while questioning the nature of digital connection itself.


Lab 30 complete โ€ข Next: Archive optimization strategies

*Last touched: April 5, 2026*