Publish AGT response documentation

Author: dbhurley

docs/.vitepress/config.mts

@@ -79,6 +79,7 @@ export default defineConfig({
 
     nav: [
       { text: 'Guide', link: '/guide/getting-started' },
+      { text: 'AGT', link: '/integrations/agt' },
       { text: 'Integrations', link: '/integrations/overview' },
       { text: 'API', link: '/api/overview' },
       { text: 'Issues', link: 'https://github.com/meshguard/issues' },
@@ -101,6 +102,7 @@ export default defineConfig({
           items: [
             { text: 'Agent Identity', link: '/guide/identity' },
             { text: 'Policies', link: '/guide/policies' },
+            { text: 'Migrating from AGT Local', link: '/guide/migrating-from-agt-local' },
             { text: 'Trust Scoring & Delegation', link: '/guide/trust-scoring' },
             { text: 'Anomaly Detection', link: '/guide/anomaly-detection' },
             { text: 'Role-Based Access Control', link: '/guide/rbac' },
@@ -110,6 +112,7 @@ export default defineConfig({
             { text: 'Compliance Reports', link: '/guide/compliance-reports' },
             { text: 'Analytics Dashboard', link: '/guide/analytics' },
             { text: 'Alerting', link: '/guide/alerting' },
+            { text: 'SIEM Egress', link: '/guide/siem-egress' },
             { text: 'Agent Discovery', link: '/guide/agent-discovery' },
             { text: 'OpenTelemetry Integration', link: '/guide/otel' },
             { text: 'CLI Reference', link: '/guide/cli' },
@@ -119,6 +122,7 @@ export default defineConfig({
           text: 'Deployment',
           items: [
             { text: 'Self-Hosted', link: '/guide/self-hosted' },
+            { text: 'Multi-Cloud & Air-Gapped', link: '/guide/deployment/multi-cloud-sovereign-airgap' },
             { text: 'Guardian Sidecar', link: '/guide/guardian-sidecar' },
             { text: 'Enterprise', link: '/guide/enterprise' },
           ]
@@ -142,6 +146,7 @@ export default defineConfig({
           text: 'SDKs',
           items: [
             { text: 'Overview', link: '/integrations/overview' },
+            { text: 'Microsoft AGT', link: '/integrations/agt' },
             { text: 'Python SDK', link: '/integrations/python' },
             { text: 'JavaScript SDK', link: '/integrations/javascript' },
             { text: '.NET SDK', link: '/integrations/dotnet' },
@@ -173,6 +178,35 @@ export default defineConfig({
           ]
         }
       ],
+      '/concepts/': [
+        {
+          text: 'AGT Response',
+          items: [
+            { text: 'AGT Architecture', link: '/concepts/agt-architecture' },
+            { text: 'Streaming, Sidecar & Egress', link: '/concepts/streaming-sidecar-egress' },
+            { text: 'Federation', link: '/concepts/federation' },
+            { text: 'Cost Governance', link: '/concepts/cost-governance' },
+            { text: 'Data Lineage', link: '/concepts/data-lineage' },
+          ]
+        }
+      ],
+      '/strategy/': [
+        {
+          text: 'Execution',
+          items: [
+            { text: 'Open Decisions', link: '/strategy/open-decisions' },
+            { text: 'Phase Compression Plan', link: '/strategy/phase-compression-plan' },
+          ]
+        }
+      ],
+      '/blueprints/': [
+        {
+          text: 'Blueprints',
+          items: [
+            { text: 'Regulated Industries', link: '/blueprints/regulated-industries' },
+          ]
+        }
+      ],
       '/api/': [
         {
           text: 'API Reference',

docs/blueprints/regulated-industries.md

@@ -0,0 +1,16 @@
+# Regulated Industry Blueprints
+
+MeshGuard blueprints are deployment and evidence packages. They are not certification claims by themselves.
+
+| Blueprint | Primary evidence |
+|---|---|
+| HIPAA | PHI policies, access logs, audit controls, BAA workflow. |
+| FedRAMP Moderate | FIPS build, AU/AC/IA/SC/SI mappings, SSP skeleton. |
+| FINRA and SEC 17a-4 | Immutable retention, human approval, WORM-compatible export. |
+| SOC 2 | Security, availability, processing integrity, confidentiality, privacy evidence. |
+| PCI-DSS | Card-data exfiltration controls and audit export. |
+| ISO 27001 | Logging, access, incident, and supplier controls. |
+| GDPR / EU AI Act / DORA | Data residency, lineage, subject export, operational resilience. |
+
+Each blueprint should include reference architecture, Terraform/Helm values, policy pack, evidence mapping, and a validated runbook.
+

docs/concepts/agt-architecture.md

@@ -0,0 +1,48 @@
+# AGT And MeshGuard Architecture
+
+AGT and MeshGuard occupy different layers.
+
+| Layer | Responsibility | Owner |
+|---|---|---|
+| PEP | Intercept agent actions in process and ask for a decision. | AGT, LangChain adapters, Bedrock adapters, OpenAI Agents adapters, or custom code. |
+| PDP | Evaluate tenant policy against the request context. | MeshGuard control plane. |
+| Audit | Persist decisions and operator actions in a tamper-evident stream. | MeshGuard audit service. |
+| Operations | SSO, SCIM, RBAC, alerting, SIEM egress, deployment, evidence export. | MeshGuard operator surface. |
+
+## Request Flow
+
+```mermaid
+sequenceDiagram
+  participant Agent as AGT-instrumented agent
+  participant PEP as MeshGuard AGT adapter
+  participant PDP as MeshGuard PDP
+  participant Audit as MeshGuard Audit
+  participant SIEM as Customer SIEM
+
+  Agent->>PEP: action + context
+  PEP->>PDP: PolicyRequest
+  PDP-->>PEP: PolicyResponse
+  PEP->>Audit: decision event
+  Audit-->>PEP: audit anchor
+  Audit->>SIEM: normalized egress
+  PEP-->>Agent: allow, deny, require_approval, or error
+```
+
+## Boundary Principles
+
+- The PEP is pluggable. AGT is first-class, not exclusive.
+- The PDP contract is stable and framework-neutral.
+- Tenant ID is mandatory on every control-plane request.
+- Audit records are portable and exportable.
+- Self-hosted, sovereign, and air-gapped deployments use the same product surface as SaaS.
+
+## Deployment Modes
+
+| Mode | Control-plane location | Best fit |
+|---|---|---|
+| Managed SaaS | MeshGuard cloud | Default production fleet governance. |
+| Dedicated tenant | Single-tenant MeshGuard cloud | Mid-enterprise isolation and predictable capacity. |
+| Customer cloud | Customer AWS, Azure, GCP, OCI, or sovereign account | Regulated or procurement-constrained enterprises. |
+| Self-hosted Kubernetes | Customer cluster | Sovereign and high-control environments. |
+| Air-gapped | Offline install bundle | Defense and disconnected environments. |
+

docs/concepts/cost-governance.md

@@ -0,0 +1,44 @@
+# Cost And Token Governance
+
+MeshGuard attributes model spend to agents, teams, business units, projects, and customers.
+
+## Provider Coverage
+
+- OpenAI and Azure OpenAI.
+- Anthropic.
+- AWS Bedrock.
+- GCP Vertex AI.
+- Cohere.
+- Mistral.
+- Local or self-hosted models through token estimation.
+
+## Controls
+
+- Daily, weekly, monthly, and rolling-window budgets.
+- Soft threshold alerts.
+- Hard caps enforced as policy denials.
+- Spend anomaly detection.
+- Chargeback exports for finance.
+
+## Policy Example
+
+```yaml
+apiVersion: governance.toolkit/v1
+kind: Policy
+metadata:
+  name: monthly-token-budget
+spec:
+  defaultEffect: deny
+  rules:
+    - effect: deny
+      actions:
+        - model:invoke
+      when:
+        meshguard.app/v1:
+          budgetRemainingUsd:
+            lte: 0
+    - effect: allow
+      actions:
+        - model:invoke
+```
+

docs/concepts/data-lineage.md

@@ -0,0 +1,28 @@
+# Data Lineage And Provenance
+
+MeshGuard records which agent touched which data, where that data went, and what derived artifacts or downstream agents were involved.
+
+## Graph Entities
+
+- Agent.
+- Dataset or data class.
+- Destination.
+- Derived artifact.
+- Policy decision.
+- Trace.
+
+## Integrations
+
+- OpenLineage.
+- DataHub.
+- Atlan.
+- Collibra.
+- Alation.
+
+## Query Examples
+
+- Who touched dataset X in the last 30 days?
+- What did agent Y send outside the tenant?
+- Which downstream agents received data derived from this source?
+- What did agents do with this data subject's information?
+

docs/concepts/federation.md

@@ -0,0 +1,24 @@
+# Federation And Cross-Org Agent Trust
+
+Federation lets one tenant authorize and audit another tenant's agent without handing control to a single cloud vendor.
+
+## Handshake
+
+1. Tenants agree to a signed federation scope.
+2. Each tenant exchanges trust roots.
+3. Tenant A grants Tenant B's agents explicit actions and resources.
+4. Grants are time-bounded, revocable, and audited.
+
+## Cross-Linked Audit
+
+When a federated action occurs:
+
+- Tenant X receives an audit event for the outgoing action.
+- Tenant Y receives an audit event for the inbound action.
+- Both events contain Merkle proof links to the other tenant's event.
+- Redaction profiles control what each tenant can see.
+
+## Dispute Evidence
+
+Either tenant can export a signed evidence bundle that verifies offline against MeshGuard's signing key and witness proof.
+

docs/concepts/streaming-sidecar-egress.md

@@ -0,0 +1,30 @@
+# Streaming Inspection, Guardian Sidecar, And Egress Proxy
+
+MeshGuard uses three enforcement layers.
+
+| Layer | Purpose | Bypass resistance |
+|---|---|---|
+| In-process PEP | Low-latency policy checks inside AGT or framework adapter. | Depends on agent process integrity. |
+| Guardian sidecar | Last-known-good policy enforcement and WAL-backed audit when the gateway is unreachable. | Stronger in Kubernetes or VM placement. |
+| Egress proxy | Network-level enforcement for outbound traffic. | Strongest when paired with network policy. |
+
+## Streaming Inspection
+
+Supported protocols:
+
+- Server-Sent Events.
+- OpenAI streaming.
+- Anthropic streaming.
+- Bedrock response streams.
+- Vertex streaming.
+- gRPC bidirectional streaming.
+
+Enforcement modes:
+
+- log-only
+- redact
+- block-and-truncate
+- full-block
+
+Matched sensitive content is deterministically redacted before audit so the audit log does not become a secondary PII/PHI store.
+

docs/guide/deployment/multi-cloud-sovereign-airgap.md

@@ -0,0 +1,29 @@
+# Multi-Cloud, Sovereign, And Air-Gapped Deployment
+
+MeshGuard is one product across deployment modes. Feature differences should come from policy and operational constraints, not separate SKUs.
+
+| Mode | Substrate | Notes |
+|---|---|---|
+| Managed SaaS US | AWS US regions | Default deployment. |
+| Managed SaaS EU | AWS EU or Azure West Europe | EU data residency. |
+| Managed SaaS UK | AWS eu-west-2 | UK data residency. |
+| Dedicated tenant | Single-tenant MeshGuard cloud | Isolation for mid-enterprise. |
+| Customer cloud operated by MeshGuard | Customer AWS, Azure, GCP, OCI | Enterprise procurement and residency. |
+| Customer-operated cloud | Customer account | Regulated and sovereign operations. |
+| On-prem Kubernetes | Customer cluster | Sovereign and disconnected-preferred environments. |
+| Air-gapped | Offline bundle | Defense and disconnected environments. |
+
+## Required Artifacts
+
+- Single Helm chart with values profiles.
+- Terraform modules for AWS, Azure, GCP, and OCI.
+- Signed OCI image bundle.
+- Offline license activation.
+- Offline audit anchor verification.
+- Customer-managed key integration.
+- Region-pinning policy checks.
+
+## Acceptance Target
+
+An air-gapped install must complete from offline media in 60 minutes or less including data initialization.
+

docs/guide/migrating-from-agt-local.md

@@ -0,0 +1,71 @@
+# Migrating From AGT Local Policies
+
+This guide moves an AGT-governed agent from local YAML evaluation to MeshGuard-managed policy decisions without rewriting the agent.
+
+## 1. Preserve The AGT Policy File
+
+MeshGuard accepts AGT-compatible YAML as the first-class policy format:
+
+```yaml
+apiVersion: governance.toolkit/v1
+kind: Policy
+metadata:
+  name: support-agent-prod
+spec:
+  defaultEffect: deny
+  rules:
+    - effect: allow
+      actions:
+        - read:ticket
+        - write:ticket_note
+    - effect: deny
+      actions:
+        - admin:*
+```
+
+MeshGuard-specific extensions must be namespaced under `meshguard.app/v1`.
+
+## 2. Add The MeshGuard Adapter
+
+```bash
+pip install meshguard-agt
+```
+
+```python
+from meshguard_agt import configure_agt_with_meshguard
+
+kernel = configure_agt_with_meshguard(
+    gateway_url="https://gateway.meshguard.app",
+    tenant_id="acme-corp",
+    agent_token=os.environ["MESHGUARD_AGENT_TOKEN"],
+)
+```
+
+## 3. Lift The Policy
+
+```bash
+meshguard policy lint policies/support-agent.yaml
+meshguard policy lift policies/support-agent.yaml --tenant acme-corp
+meshguard policy plan
+meshguard policy apply
+```
+
+## 4. Dry-Run Against History
+
+Before production promotion, replay the policy against historical decisions:
+
+```bash
+meshguard policy test --against last-7d
+meshguard policy diff current staged
+```
+
+## 5. Canary The Rollout
+
+```bash
+meshguard policy apply --canary 10 --rollback-on "denial_rate > 0.05 for 10m"
+```
+
+## 6. Lock Local Evaluation To Break-Glass
+
+After the remote PDP is stable, keep local YAML evaluation only as a signed last-known-good fallback for sidecars and disconnected environments.
+