<?xml version="1.0" encoding="UTF-8"?>
<spec xmlns="https://vibevm.org/spec/1">
  <title id="root">go-ai-native-mcp — README</title>
  <status stage="doc" state="work" audience="user,dev"/>
  <p p="1">The README of `org.vibevm.ai-native/go-ai-native-mcp@1.0.0`, as the package ships it.</p>
  <section id="go-ai-native-mcp-mcp-org-vibevm-ai-native-go-ai-native-mcp-root" title="go-ai-native-mcp (mcp:org.vibevm.ai-native/go-ai-native-mcp) {#root}">
    <p p="2">&lt;status stage="doc" state="done" audience="user"/&gt;</p>
    <p p="3">@fact:SERVED-OVER-MCP-AS-ONE-STDIO-BINARY The AI-Native Go discipline served over MCP: one stdio binary, the discipline command surface plus the tcg type oracle, launched by an agent host straight from this package's slot. @status:impl/done</p>
    <p p="4">@fact:SERVING-NEEDS-NO-VIBE-ON-THE-MACHINE Serving needs no vibe anywhere on the machine (PROP-027 §2.6). @status:impl/done</p>
    <p p="5">&gt; @fact:campaign-in-flight-note Campaign in flight: built end-to-end per &gt; GO-AI-NATIVE-PLAN v0.1, the campaign plan, which is authored outside &gt; this package; the server brief is `spec/tools/discipline-mcp-go.xml`. &gt; This README is finalized at campaign close. @status:spec/done</p>
  </section>
</spec>
