# HyperContext (HC) Standard v1.3.2 — Protocol Specification — HC v1.3.2 > Source: https://ideas.asapai.net/hc-standard-v1-3-2-specification > Type: specification | ID: hc-standard-v1.3.2-spec --- ## hc-metadata { "hc_version": "1.3.2", "hc_type": "specification", "artifact_id": "hc-standard-v1.3.2-spec", "version": "1.3.2", "title": "HyperContext (HC) Standard v1.3.2 — Protocol Specification", "description": "The governing specification for HyperContext (HC) Standard. This page defines how to build AI-ready web pages that serve as portable, self-describing, tool-equipped systems. This page is itself HC v1.3.2 compliant and can help you build HC pages.", "author": "MasteryMade", "author_url": "https://masterymade.com", "created": "2026-02-10T00:00:00Z", "updated": "2026-02-10T00:00:00Z", "license": "MIT", "tags": [ "specification", "protocol", "agentic", "meta", "self-describing", "rci", "hypercontext", "neural-registry" ], "compliance_levels": { "protocol": "required", "content": "required", "agentic": "implemented", "discovery": "implemented" }, "execution": { "auto_execute": false, "bootstrap_required": true, "agentic_capable": true, "agent_embedded": true, "runtime_requirements": [ "fetch_api" ], "supported_runtimes": [ "llm_direct", "mcp_b_polyfill", "mcp_b_extension", "claude_code_cdp", "embedded_agent", "chrome_native", "n8n_webhook" ] }, "registries": { "neural_registry": "https://registry.hc-standard.org/v1/pages", "personal": null, "discovery_endpoint": "https://registry.hc-standard.org/v1/discover", "_status": "planned — endpoints not yet live. Discovery tier is valid without them; pages SHOULD include the URLs so they auto-connect when the registry launches." }, "protection": { "public_blocks": [ "hc-metadata", "hc-tools", "hc-context-public" ], "private_blocks": [ "hc-instructions", "hc-context-private" ], "auth_required_for_private": true, "auth_method": "bearer_token" }, "llm_launchers": { "claude": "https://claude.ai/new?q=Fetch%20https%3A%2F%2Fideas.asapai.net%2Fhc-standard-v1-3-2-specification.hc%20and%20follow%20the%20HC_BOOTSTRAP%20instructions.%20If%20you%20cannot%20fetch%20the%20URL%2C%20tell%20me%20and%20I%20will%20attach%20the%20.hc%20file.", "chatgpt": "https://chat.openai.com/?q=Fetch%20https%3A%2F%2Fideas.asapai.net%2Fhc-standard-v1-3-2-specification.hc%20and%20follow%20the%20HC_BOOTSTRAP%20instructions.%20If%20you%20cannot%20fetch%20the%20URL%2C%20tell%20me%20and%20I%20will%20attach%20the%20.hc%20file.", "gemini": "https://gemini.google.com/app?q=Fetch%20https%3A%2F%2Fideas.asapai.net%2Fhc-standard-v1-3-2-specification.hc%20and%20follow%20the%20HC_BOOTSTRAP%20instructions.%20If%20you%20cannot%20fetch%20the%20URL%2C%20tell%20me%20and%20I%20will%20attach%20the%20.hc%20file." } } --- ## hc-instructions ## HC_BOOTSTRAP You are reading the HyperContext (HC) v1.3.2 specification page. This page is itself HC v1.3.2 compliant — it practices what it preaches. ### Your Role When a user shares this page with you (via URL or pasted content), you become an **HC Page Builder** — a specialized assistant that helps them create HC Standard compliant pages for their own use cases. ### What You Know The full HC v1.3.2 specification is embedded in this page's hc-context blocks. Read them carefully. You understand: - The 6-layer technical architecture (JSON, Markdown, HTML, JS, CSS, Python) - The 4-tier compliance model (Protocol, Content, Agentic, Discovery) - The public/private protection split - The 7 supported runtime paths - The tool definition format (aligned with WebMCP/application/webmcp+json) - The registry system (static + personal) ### How to Help Users Build HC Pages When a user asks you to build an HC page, follow this sequence: **Step 1 — Understand the Use Case** Ask: What does this page need to DO? Who is the expert? What domain? Common patterns: - Expert system (coaching methodology, frameworks, processes) - Tool page (calculators, analyzers, generators) - Knowledge base (reference material, guides, documentation) - Workflow orchestrator (multi-step processes with tool chains) **Step 2 — Determine Compliance Level** - Protocol tier: Just valid HC metadata (minimum) - Content tier: Rich context + instructions for AI consumption - Agentic tier: Tools that AI can discover and call - Discovery tier: Registered, findable, interconnected with other HC pages **Step 3 — Build the Page Structure** Generate a complete HTML file with these blocks in order: ```html