diff --git a/README.md b/README.md
index f46bbd7..22d433c 100644
--- a/README.md
+++ b/README.md
@@ -67,6 +67,89 @@ signed = sign_record(record, key=signing_key)
 
 Targeting the [Agentic AI Foundation (AAIF)](https://agenticai.foundation) at the Linux Foundation. Active standardization track in [CoSAI WS4](https://github.com/oasis-open-projects/coalition-for-secure-ai). Builds on [RFC 9711 (EAT)](https://www.rfc-editor.org/rfc/rfc9711), [RFC 9334 (RATS)](https://www.rfc-editor.org/rfc/rfc9334), and SCITT draft-22.
 
+## Frequently asked questions
+
+### What is TRACE?
+
+TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools.
+
+### What does a TRACE Trust Record prove?
+
+A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger.
+
+### What standards is TRACE built on?
+
+TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability.
+
+### How do I create and verify a Trust Record?
+
+Install the Python library with `pip install agentrust-trace`, sign a record with `TrustRecord.sign(claims, signing_key)`, anchor it to a SCITT ledger with `record.anchor()`, and check it with `record.verify(verifying_key)`.
+
+### How does TRACE relate to AGT and cMCP?
+
+TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details.
+
+### What is the current status of TRACE?
+
+The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production.
+
+<script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [
+    {
+      "@type": "Question",
+      "name": "What is TRACE?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What does a TRACE Trust Record prove?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What standards is TRACE built on?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "How do I create and verify a Trust Record?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "Install the Python library with pip install agentrust-trace, sign a record with TrustRecord.sign(claims, signing_key), anchor it to a SCITT ledger with record.anchor(), and check it with record.verify(verifying_key)."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "How does TRACE relate to AGT and cMCP?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What is the current status of TRACE?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production."
+      }
+    }
+  ]
+}
+</script>
+
 ## Contributing
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) and [GOVERNANCE.md](GOVERNANCE.md). All contributors must agree to the [ANTITRUST.md](ANTITRUST.md) policy.
diff --git a/docs/index.md b/docs/index.md
index 4d4a1bc..93fd7c6 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -78,86 +78,3 @@ record.verify(verifying_key)         # raises on invalid
 ```
 
 [Full API reference →](schema.md) · [Changelog →](../CHANGELOG.md) · [GitHub →](https://github.com/agentrust-io/trace-spec){ target=_blank }
-
-## Frequently asked questions
-
-### What is TRACE?
-
-TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools.
-
-### What does a TRACE Trust Record prove?
-
-A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger.
-
-### What standards is TRACE built on?
-
-TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability.
-
-### How do I create and verify a Trust Record?
-
-Install the Python library with `pip install agentrust-trace`, sign a record with `TrustRecord.sign(claims, signing_key)`, anchor it to a SCITT ledger with `record.anchor()`, and check it with `record.verify(verifying_key)`.
-
-### How does TRACE relate to AGT and cMCP?
-
-TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details.
-
-### What is the current status of TRACE?
-
-The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production.
-
-<script type="application/ld+json">
-{
-  "@context": "https://schema.org",
-  "@type": "FAQPage",
-  "mainEntity": [
-    {
-      "@type": "Question",
-      "name": "What is TRACE?",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools."
-      }
-    },
-    {
-      "@type": "Question",
-      "name": "What does a TRACE Trust Record prove?",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger."
-      }
-    },
-    {
-      "@type": "Question",
-      "name": "What standards is TRACE built on?",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability."
-      }
-    },
-    {
-      "@type": "Question",
-      "name": "How do I create and verify a Trust Record?",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "Install the Python library with pip install agentrust-trace, sign a record with TrustRecord.sign(claims, signing_key), anchor it to a SCITT ledger with record.anchor(), and check it with record.verify(verifying_key)."
-      }
-    },
-    {
-      "@type": "Question",
-      "name": "How does TRACE relate to AGT and cMCP?",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details."
-      }
-    },
-    {
-      "@type": "Question",
-      "name": "What is the current status of TRACE?",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production."
-      }
-    }
-  ]
-}
-</script>