Update framing: SpeckDL is the narrow waist humans and AI can work in

- Replace 'AI-generated, human-owned' with 'Two-Species Collaboration'
- Add 'Compiles to Wasm' as a distinct philosophy point
- README: new 'Chain of Custody for Intent' section
- Landing: updated hero tagline and philosophy cards
- SpeckDL compiles directly to Wasm through deterministic pipeline

Human intent is encoded in SpeckDL because it is judgeable by a person.
SpeckDL is useful for agentic work because it is easy for AI to write and reason about.

README.md

@@ -4,6 +4,21 @@
 
 Speckl is a multi-agent software development system where the primary artifact is the *specification*, not the code. Every behavior traces back to its source of intent — automatically.
 
+## The Chain of Custody for Intent
+
+Agents generate code. Humans own specifications. The chain of custody for intent stays intact.
+
+That's the old framing. Here's the better one:
+
+**SpeckDL is the narrow waist that both humans and AI can work in.**
+
+- **Human-judgeable** — SpeckDL is declarative enough that a person can inspect a spec and say "yes, this captures my intent." The compiled Wasm is opaque; the spec is not. That's the audit trail. Intent is encoded in the spec *because* it is verifiable by a person.
+- **AI-writable** — SpeckDL's constrained grammar and declarative semantics make it tractable for LLMs to produce and reason about. Agents can draft, iterate, and refactor specs at machine speed — in the same language the human reviews.
+
+The two properties together are symmetric: humans and agents collaborate in the same medium. The human provides direction and judgment. The agent provides speed and iteration. Both operate on the same semantic layer.
+
+SpeckDL compiles directly to **Wasm** through a deterministic pipeline. The compiler isn't just a code generator — it's the enforcement point that guarantees what the human signed off on is what gets executed. If it compiles to valid Wasm, the binary is faithful to the spec by construction.
+
 ## Dark Provenance
 
 Every function, every branch, every side effect in your system is linked to the specification that motivated it. The provenance graph accumulates behind the scenes — invisible until you need it, but always complete. When an auditor asks "why does this code exist?", you don't search Jira. You query the graph.
@@ -25,7 +40,7 @@ speck RetryHandler {
 }
 ```
 
-SpeckDL compiles through a deterministic pipeline:
+SpeckDL compiles through a deterministic pipeline directly to Wasm:
 
 ![SpeckDL compilation pipeline](docs/diagrams/speckdl-pipeline.svg)
 

landing/index.html

@@ -195,7 +195,7 @@
 <header class="hero">
   <div class="hero-content">
     <h1>Speckl</h1>
-    <p class="hero-tagline">Spec-first development with dark provenance.<br>Write what your system should do. Prove it. Ship with full traceability.</p>
+    <p class="hero-tagline">Where humans and AI collaborate in the same language.<br>Spec-first development with dark provenance. Write what your system should do. Prove it. Ship with full traceability.</p>
     <div class="hero-cta">
       <a href="https://codeberg.org/sscoble/speckl" class="btn btn-primary">Source Code</a>
       <a href="https://codeberg.org/sscoble/speckl/src/branch/main/docs/whitepapers/dark-provenance.md" class="btn btn-secondary">Read the Whitepaper</a>
@@ -264,8 +264,12 @@
       <p>If Speck→WASM compilation preserves semantics, human review at the spec boundary satisfies assurance requirements.</p>
     </div>
     <div class="philosophy-item">
-      <h3>AI-Generated, Human-Owned</h3>
-      <p>Agents generate code. Humans own specifications. The chain of custody for intent stays intact.</p>
+      <h3>Two-Species Collaboration</h3>
+      <p>SpeckDL is the narrow waist both species can work in. Human-judgeable and AI-writable. Intent is encoded in the spec because humans can verify it; agents can draft and iterate at machine speed.</p>
+    </div>
+    <div class="philosophy-item">
+      <h3>Compiles to Wasm</h3>
+      <p>SpeckDL compiles directly to Wasm through a deterministic pipeline. The compiler is the enforcement point: if it compiles, the binary is faithful to the spec by construction.</p>
     </div>
   </div>
 </section>