About the site
A place to read The Interdependent Way, examine its claims, and follow the work that grows around it.
How to read this site
Begin with The Way. Open a title to read its text. Article Labs offer interpretation, applications, and research where available; exact source remains accessible in its own disclosure. The directory leads to the technical textbook, narratives, projects, and other work.
- Canon and textbook
- Source-owned writing, with its identity and origin available for inspection. Publication here leaves authorship, license, and claim status with the source.
- Interpretation and narrative
- Companion explanations, applications, and stories. A useful reading remains distinguishable from the material it interprets.
- Research and non-study context
- The research section separates studies and systematic evidence syntheses from legislation, standards, guidelines, and doctrine. See the review method.
- Implementation and frontier
- Built work and unresolved claims have different standing. A functioning demonstration establishes only what was actually tested.
- hmmm
- An unresolved constraint, preserved with enough context for someone to continue honestly.
About me contains Erin’s personal narrative. By the builder contains dated, attributed observations from the AI builder; those entries express the builder’s judgment.
Practices behind the pages
Make the structure readable
Use descriptive headings, semantic page regions, ordinary links, and a skip link. Keep repeated navigation in a predictable order, and give each destination a clear purpose. These choices follow W3C’s page-structure guidance and consistent-navigation guidance.
Let the content arrive first
The reading pages are generated as HTML. JavaScript adds conveniences such as copying, search, and map interaction. Essential reading and links remain available without it. This follows GOV.UK’s progressive-enhancement guidance. Static reading still requires the page to have loaded; this is not an installed offline application.
Respect small screens and different ways of using a page
Allow text to reflow, keep keyboard focus visible, honor reduced-motion preferences, and provide room around controls. The relevant W3C guidance covers reflow, visible focus, and target size and spacing. Maps and tables may need their own scrolling area.
Make every extra element earn its place
Navigation helps people move; a reading guide explains the choices. Neither needs to repeat the other in every section. Export controls belong to reusable text. Map and status scripts load on the pages that use them. Source copies and recovery editions remain because they support verification and resilience.
Measure the claim being made
Release checks cover content contracts, internal links, browser behavior, automated accessibility findings, and static file-size budgets. Delivery speed and responsiveness need separate measurements: Core Web Vitals track loading, interaction, and visual stability. Small files alone do not establish a good real-user experience.
Keep evidence attached to its owner
skill-lib guides audit and repair. METAPAT’s domain restraint keeps structural comparison from becoming borrowed authority. Website behavior is evaluated through web standards and observed use; presentation does not validate the theories presented.
Checks, corrections, and limits
The published build record identifies the site revision and source snapshots. Corrections to source writing belong in its source repository; corrections to navigation, rendering, or these pages belong in the website issue tracker. Include the page URL, what happened, and what you expected.
hmmm: automated checks cover a bounded set of failures. Manual assistive-technology testing, user research, and real-user performance remain separate work. See Accessibility for the current scope and the dated site audit for evidence.