Redesign Agent Guard launch website

docs/WEBSITE-CONTENT-MANIFEST.md

@@ -0,0 +1,64 @@
+# Agent Guard website content preservation manifest
+
+This manifest records the public content and behavior present before the 2026 launch-experience redesign and where each item remains afterward. It is a regression contract for `https://cairo.sh/AgentGuard`.
+
+## Route, metadata, and brand
+
+| Before | Preserved after | Implementation |
+| --- | --- | --- |
+| Production route `/AgentGuard` | Yes | `website/next.config.ts` base path |
+| Cairo Agent Guard name and Cairo logo | Yes | Header, hero security boundary, runtime, Edge, final CTA, footer |
+| Product description covering Identity, AGP, Runtime, and Edge | Yes, expanded | Metadata, hero, pillars, documentation |
+| Open Graph and X/Twitter preview | Yes | `website/app/layout.tsx` and `website/public/og.png` |
+| GitHub repository URL | Yes | Hero/open-source, integrations, docs, footer |
+| Apache-2.0 open-source statement | Yes | Open foundation and FAQ |
+
+## Sections and claims
+
+| Existing section | Preserved after | Notes |
+| --- | --- | --- |
+| Hero: intelligence is not authority | Yes | New identity-led headline; invariant retained verbatim |
+| Identify / Control / Defend / Prove outcomes | Yes | Proof strip retained |
+| Agent Identity | Yes | Lifecycle, signed claim, principal binding, validity, revocation, V0.1 HMAC/federation boundary retained |
+| Agent Guard Protocol | Yes | Request example, object model, ten decision effects, default-deny and delegation invariants retained |
+| Agent Guard Edge | Yes | Discover/verify/classify/authorize/enforce/record pipeline, trust states, targets, and managed-platform boundary retained |
+| Runtime | Yes | Non-bypassable Guardian, executor targets, six controls, and reference contract retained |
+| Deployment architecture | Yes | Data plane, control plane, and non-bypassability requirement retained |
+| Cairo Super Agent | Yes | Security context, mandatory gateway, and protected surfaces retained |
+| Certification | Yes | AGP-L1 through AGP-L4 and AGP-P, six-step flow, caveat, and application form retained |
+| Documentation | Yes | All ten topics, code examples, GitHub links; search added |
+| Open foundation | Yes | Repository tree, open-core scope, GitHub/docs CTAs retained |
+| Final CTA and footer | Yes | Integration, certification, brand, version, ownership, GitHub/docs links retained |
+
+## Certification application contract
+
+The form continues to submit JSON to `/AgentGuard/api/certification/applications` and preserves every field and constraint:
+
+- `organization`: required, 160 characters maximum.
+- `email`: required work email, 254 characters maximum.
+- `target`: AI Agent, Agent Runtime / Harness, Platform / API, MCP Server, or Physical AI System.
+- `level`: AGP-L1, AGP-L2, AGP-L3, AGP-L4, or AGP-P.
+- `summary`: required architecture/security boundary, 40–4,000 characters.
+- `companyWebsite`: inaccessible honeypot for automated abuse.
+
+The D1 storage binding, schema, migration, validation, success response, error response, and certification caveat are unchanged. The redesign adds recoverable draft persistence in `sessionStorage`, prevents duplicate submission while a request is in flight, and clears the draft only after success.
+
+## New launch content
+
+- Identity-led hero: “Every AI Agent Needs an Identity.”
+- “Why Agent Guard / Why now” threat narrative.
+- Five-pillar system model: Identity, Runtime, Policy, Certification, Platform Defense.
+- Integration and ecosystem matrix.
+- Searchable documentation navigation.
+- Product-boundary FAQ.
+- Active-section navigation and responsive/mobile refinements.
+
+## Technical boundaries retained
+
+- Identity is not permission.
+- V0.1 uses locally pinned symmetric HMAC and is not a cross-organization federation system.
+- Proof-of-possession and signed approval consumption remain next-protocol work.
+- V0.1 Edge is architecture and reference primitives, not a managed distributed service.
+- Non-bypassability requires deployment isolation and removal of alternate execution paths.
+- AGP-P does not replace an independent physical safety controller or emergency stop.
+

docs/WEBSITE-REDESIGN-REPORT.md

@@ -0,0 +1,40 @@
+# Agent Guard website redesign report
+
+## Objective
+
+Upgrade the existing Agent Guard site into a launch-quality product and documentation experience while preserving its technical fidelity, production route, certification intake, integrations, metadata, and open-source links.
+
+## Before
+
+The site already contained a sophisticated one-page technical presentation of Agent Identity, AGP, Edge, Runtime, deployment architecture, Cairo integration, certification, embedded documentation, and the open repository. Its dominant narrative began with generic security infrastructure and organized the experience around three product components. Documentation was browsable but not searchable, the certification form had no recoverable local draft, and the site did not yet include a dedicated threat narrative, ecosystem matrix, or FAQ.
+
+## After
+
+The redesigned journey is organized for both executive evaluation and technical implementation:
+
+1. Identity-led launch promise and live authorization visualization.
+2. Why-now threat model and independent-boundary design rule.
+3. Five trust pillars with direct paths into the deeper system.
+4. Identity, AGP policy, Edge, Runtime, architecture, and Cairo implementation detail.
+5. Integration and ecosystem patterns with explicit maturity labels.
+6. Evidence-based certification levels and durable application workflow.
+7. Searchable embedded documentation and open-source adoption path.
+8. Product-boundary FAQ and decisive integration/certification calls to action.
+
+## Interaction and accessibility upgrades
+
+- Raised the site-wide minimum type scale and contrast for navigation, lifecycle steps, trust records, diagrams, documentation, forms, and footer content so product information remains readable without browser zoom.
+- Semantic landmarks and heading hierarchy remain intact.
+- Skip navigation, visible keyboard focus, reduced-motion behavior, accessible form labels, live form status, and native FAQ disclosure controls are preserved or added.
+- Navigation now identifies the current section with `aria-current`.
+- Documentation search is keyboard-native and reports available topic count.
+- Certification application data survives recoverable navigation or request failures for the current tab and is removed after successful submission.
+- Desktop, tablet, and mobile layouts receive explicit grid transitions without horizontal overflow.
+
+## Fidelity and security decisions
+
+No technical boundary was softened for marketing. Integration cards distinguish a reference integration, reference adapter, architecture pattern, and protocol profile. The certification application remains an intake for scoping and evidence review—not a conformance claim. The Edge managed-platform boundary, V0.1 HMAC limitation, proof-of-possession gap, signed approval limitation, non-bypassability requirement, and physical safety boundary remain visible.
+
+## Deployment status
+
+This redesign is prepared as a focused reviewable pull request. It is not directly deployed to production by this change set.