Update readme

Author: mheadd

README.md

@@ -227,7 +227,15 @@ SpecOps was developed to address the unique challenges of government legacy syst
 
 The methodology combines proven practices from incremental modernization (Strangler Fig pattern), infrastructure as code (GitOps), and specification-driven development, adapted for the era of AI-assisted software development.
 
-The goal: Make legacy modernization more effective, sustainable, and knowledge-preserving for everyone.
+### Built on Specification-Driven Development
+
+SpecOps builds on the foundation of [specification-driven development](https://github.com/github/spec-kit), an approach where specifications are created before implementation and serve as the authoritative source of truth. As GitHub's [spec-kit](https://github.com/github/spec-kit) describes it:
+
+> "Specification-driven development is a software development approach where you write a detailed specification of your software's behavior before writing any implementation code. The specification serves as both documentation and a contract that your implementation must fulfill."
+
+GitHub's spec-kit provides essential tooling for this approach, including specification templates, validation tools, and integration with AI coding agents. SpecOps extends these principles specifically for legacy system modernization, adding workflows for extracting specifications from existing systems, domain expert verification processes, and patterns for incremental replacement.
+
+**The goal**: Make legacy modernization more effective, sustainable, and knowledge-preserving for everyone.
 
 ---
 

docs/index.html

@@ -437,7 +437,7 @@ <h4>The SpecOps Solution</h4>
                         <h4>Specification-Driven Development</h4>
                         <p>
                             The specification precedes and governs all implementation. Once the legacy system's behavior is 
-                            captured in a verified specification, AI coding agents use that specification to generate modern 
+                            captured in a verified specification, <a href="https://github.com/github/spec-kit">AI coding agents</a> use that specification to generate modern 
                             implementations—transforming documented knowledge into working code.
                         </p>
                     </div>
@@ -614,18 +614,6 @@ <h3>Instruction Sets</h3>
                         <span class="arrow">→</span>
                     </p>
                 </a>
-
-                <a href="https://github.com/mheadd/spec-ops/blob/main/public/REFERENCE-IMPLEMENTATION.md" class="doc-card">
-                    <div class="doc-card-header">
-                        <span class="doc-icon">🚧</span>
-                        <h3>Reference Implementation</h3>
-                    </div>
-                    <p>
-                        <em>(In Development)</em> A complete, working example of SpecOps applied to a real legacy system. 
-                        Will provide reusable artifacts, templates, and lessons learned.
-                        <span class="arrow">→</span>
-                    </p>
-                </a>
             </div>
         </div>
     </section>
@@ -637,7 +625,10 @@ <h2 class="section-title">Get Started</h2>
                 Join the community building a better approach to legacy modernization
             </p>
             <div class="cta-buttons">
-                <a href="https://github.com/mheadd/spec-ops" class="btn btn-primary">
+                <a href="mailto:hello@adhoc.team" class="btn btn-primary">
+                    Contact Us
+                </a>
+                <a href="https://github.com/mheadd/spec-ops" class="btn btn-secondary">
                     View on GitHub
                 </a>
                 <a href="https://github.com/mheadd/spec-ops/discussions" class="btn btn-secondary">