# Chapter 14 - Beyond Coding (The Architecture in Other Domains) | Loop Engineering

[← All chapters](/ch/)

# Chapter 14 - Beyond Coding: The Architecture in Other Knowledge Domains

                Last updated 2026-07-13. This page hosts the cross-domain extension material for Chapter 14 and links into the [domain-specific materiality patterns](/materiality/) that ground the per-field calibration.

### Companion activity

Pick one non-coding domain in the [materiality patterns](/materiality/), then list the evidence standard, oversight requirement, and non-negotiable control for that domain.

### What this chapter argues

                The examples in Parts I and II are often coding-flavored because software work makes loops, tools, tests, and state unusually visible. Chapter 14 treats transfer beyond software as a set of thought experiments and candidate adaptations: a clinician, legal team, policy analyst, and educator each need different evidence, oversight, privacy, and accountability practices. The five-region map can help structure those conversations, but the examples demonstrate possible application, not proof of universal fit. Domain professionals and governing rules remain authoritative.

### Key sources

Chapter 14 cites in the print book: D22. Entries below are the sources this page draws on; some are related literature cited elsewhere in the book rather than in this chapter.

This chapter draws on cross-domain author sketches and the broader trust-calibration literature already cited in Chapter 13. The materiality dial in this chapter sits on the same Lee & See (2004) foundation.

- D20 - Lee, J. D., and See, K. A. (2004). Trust in automation: Designing for appropriate reliance . [doi.org/10.1518/hfes.46.1.50_30392](https://api.crossref.org/works/10.1518/hfes.46.1.50_30392)

### Primary-source links

- [Correa, "Meet Alex: The AI Dog Trainer Who Actually Gets Your Dog" (August 2025)](/examples/) - non-coding domain proof-of-concept relevant to the cross-domain argument.

### Chapter contents

- Four short cross-domain walks (healthcare, legal, policy, education).

- The per-domain region mapping: same regions, different content.

- The materiality posture each domain demands (forward reference to the patterns catalog).

- The pattern that holds across domains: the discipline is at the handoffs, not within the layers.

### Related resources

                The [materiality patterns by domain](/materiality/) page extends each cross-domain walk with the full calibration table for that field - including the compensating controls that domain-specific stakes demand. The [worked examples section](/examples/) hosts longer cross-domain traces.