# Technical Archaeology > **Evolutionary Nexus:** [[articles/The Evolutionary Roots of Silicon Valley|The Evolutionary Roots of Silicon Valley]] places this method within the Bay Area lineage joining natural history, evolutionary mechanism, computation, and post-biological continuity. **Domain:** Systems history / technology studies / infrastructure studies **Doc Type:** Developed Concept Node **Maturity:** Developed ## Definition **Technical archaeology** reconstructs how present systems inherit material components, architectures, operational practices, and stated objectives from earlier technical regimes. It asks four different questions: what function persisted, what institution or personnel transmitted it, what objective builders explicitly inherited, and how much coordination the surviving record supports. The method therefore joins artifacts to documents. Functional resemblance can establish a lineage of problems or mechanisms; [[wiki/Transmitted Objective|Transmitted Objective]] requires a documented act of inheritance; [[wiki/Coordination Ladder|Coordination Ladder]] measures the degree of organization visible among the actors. ## Method 1. Date the artifact, capability, or operational system. 2. Identify its material and organizational predecessor. 3. Locate citations, personnel transfers, procurement records, budgets, design reports, or institutional mandates that transmit a purpose. 4. Separate invention, restricted deployment, public release, and cultural recognition through [[wiki/Permission Lag|Permission Lag]]. 5. Record conclusions in an evidence ledger whose tiers can change when new evidence appears. [[articles/A History of Machine Intelligence|A History of Machine Intelligence]] applies the method across ancient mechanisms, formal logic, electronic substrate, cybernetics, neural learning, state programs, and contemporary AI infrastructure. [[articles/Oh Sure, It’s All Brand New!|Oh Sure, It’s All Brand New!]] supplies the access-history method, while [[articles/The Evolutionary Roots of Silicon Valley|The Evolutionary Roots of Silicon Valley]] demonstrates regional reconstruction from geology, institutions, personnel, and industrial descent. ## Evidence Ledger ### Established - Present systems contain dated components, standards, and architectures inherited from earlier systems. - Invention, operational deployment, public release, and cultural recognition frequently occur on different dates. - The Project X article records multiple explicit acts of intellectual and institutional inheritance. ### Strongly indicated - Combining artifact history with transmitted objectives explains the machine-intelligence lineage more completely than product-launch chronology alone. ### Plausible - Some programs described publicly as new may extend restricted or institutionally bounded predecessors whose records remain incomplete. ### Unresolved - The degree of coordination among apparently convergent lineages. This rises with common directives, budgets, command structures, and acknowledged inheritance; it falls when complete records show independent development toward similar functions. ## Sources / Provenance - [[articles/A History of Machine Intelligence|A History of Machine Intelligence]]. - [[articles/Oh Sure, It’s All Brand New!|Oh Sure, It’s All Brand New!]]. - [[articles/The Evolutionary Roots of Silicon Valley|The Evolutionary Roots of Silicon Valley]]. - [Michael S. Mahoney, “The Histories of Computing(s)” (2005)](https://doi.org/10.1179/030801805X25927). ## Relationships - **Method controls:** [[wiki/Transmitted Objective|Transmitted Objective]], [[wiki/Coordination Ladder|Coordination Ladder]], and [[wiki/Anti-Teleology Norm|Anti-Teleology Norm]]. - **Access-history control:** [[wiki/Permission Lag|Permission Lag]]. - **Machine-history application:** [[wiki/Machine Intelligence Continuum|Machine Intelligence Continuum]] and [[wiki/Project X - Machine Intelligence History|Project X - Machine Intelligence History]]. - **Regional application:** [[wiki/Silicon Valley|Silicon Valley]].