# HyperContext (HC) Standard v1.3.0 — Agentic Web Integration — HC v1.3.0
> Source: https://ideas.asapai.net/hc-standard-v1-3-specification
> Type: framework | ID: hc-standard-v1.3.0

---
## hc-metadata
{
  "hc_version": "1.3.0",
  "hc_type": "framework",
  "artifact_id": "hc-standard-v1.3.0",
  "version": "1.3.0",
  "title": "HyperContext (HC) Standard v1.3.0 — Agentic Web Integration",
  "description": "Protocol for AI-compatible web pages with portable context injection, lazy loading, and browser-native tool registration via WebMCP integration",
  "author": "HC Standard / MasteryMade",
  "created": "2026-02-10T00:00:00Z",
  "updated": "2026-02-10T00:00:00Z",
  "tags": [
    "specification",
    "protocol",
    "standard",
    "framework",
    "webmcp",
    "agentic"
  ],
  "classification": {
    "category": "technical-specification",
    "subcategory": "protocol-definition",
    "domain": "web-standards"
  },
  "trusted_origins": [
    "https://hc-standard.org",
    "https://*.hc-standard.org",
    "https://ideas.asapai.net"
  ],
  "registry_stack": [
    {
      "level": "os",
      "url": "https://hc-standard.org/registry.json",
      "auto_load": true,
      "priority": 3
    }
  ],
  "execution": {
    "auto_execute": true,
    "bootstrap_required": true,
    "identity_optional": true,
    "lazy_load": true,
    "agentic_capable": true
  },
  "supersedes": "hc-standard-v1.2.2",
  "compliance_levels": {
    "protocol": "required",
    "content": "recommended",
    "agentic": "optional",
    "discovery": "optional"
  }
}

---
## hc-instructions
# HyperContext (HC) Standard v1.3.0 — Agentic Web Integration

## HC_BOOTSTRAP

### Context Detection
You are reading the HC v1.3.0 specification.
This is the authoritative reference for building HC-compliant pages with optional WebMCP agentic capabilities.

### What's New in v1.3.0
- NEW: `hc-tools` block for browser-native tool registration
- NEW: Agentic compliance tier (4-tier model replaces 3-tier)
- NEW: WebMCP bridge pattern for runtime tool execution
- NEW: Declarative form-to-tool annotations
- PRESERVED: Full backward compatibility with v1.2.2
- PRESERVED: All existing compliance requirements unchanged

### Execution Modes

**MODE: SPECIFICATION**
If a user asks "What is HC 1.3.0?" or "What changed from 1.2.2?":
1. Explain the 4-tier compliance model
2. Describe the DNA/RNA architecture (static portability + browser runtime)
3. Emphasize backward compatibility — v1.2.2 pages are still valid
4. Offer to build an HC 1.3.0 page or upgrade an existing one

**MODE: BUILD**
If a user asks to "build an HC page" or "make this page HC compliant":
1. Determine if they need Agentic tier (hc-tools) or just Protocol tier
2. Generate appropriate template
3. Include WebMCP bridge if Agentic tier requested
4. Validate against compliance checklist

**MODE: VALIDATE**
If a user asks to "validate" or "check compliance":
1. Check all 4 tiers systematically
2. Report: X/10 protocol, Y/5 content, Z/8 agentic, W/3 discovery
3. For any FAIL: explain what's wrong and provide the fix

**MODE: UPGRADE**
If a user has a v1.2.2 page and wants to upgrade:
1. Confirm existing v1.2.2 compliance (no regressions)
2. Add hc-tools block with tool definitions
3. Add bridge script for WebMCP runtime
4. Bump hc_version to "1.3.0" in metadata

### Runner Interface Contract (v1.3.0)

Required Methods (unchanged from v1.2.2):
| Method              | Purpose                          | Returns          |
|---------------------|----------------------------------|------------------|
| resolveIdentity()   | Get user identity via cascade    | string | null    |
| loadRegistries()    | Load and merge registry stack    | Registry[]       |
| selectArtifacts()   | Choose relevant artifacts        | Artifact[]       |
| executeBootstrap()  | Start without "run this"         | void             |
| fetchModule()       | Safely fetch external content    | ModuleContent    |

New Optional Methods (v1.3.0):
| Method              | Purpose                          | Returns          |
|---------------------|----------------------------------|------------------|
| loadTools()         | Parse hc-tools block             | ToolDefinition[] |
| registerTools()     | Register tools with runtime      | Registration[]   |
| bridgeWebMCP()      | Connect to navigator.modelContext| void             |

### Security Model (Extended)

All v1.2.2 security rules apply, plus:
- hc-tools execute() callbacks MUST NOT access cross-origin data
- Tool registrations MUST be scoped to the page lifecycle
- Destructive actions MUST require user confirmation (HITL)
- Tool schemas MUST validate inputs before execution
- Bridge script MUST detect polyfill availability before registration

### Compliance Checklist v1.3.0

**Tier 1: Protocol (MUST — 10 items)**
Same as v1.2.2. hc-metadata + hc-instructions with HC_BOOTSTRAP.

**Tier 2: Content (SHOULD — 5 items)**
Same as v1.2.2. #hc-human-docs with semantic HTML.

**Tier 3: Agentic (MAY — 8 items)** ← NEW
1. hc-tools block present with type="application/json"
2. Each tool has: name, description, inputSchema
3. Tool names use snake_case with domain prefix
4. inputSchema follows JSON Schema draft-07
5. Destructive tools have annotations.destructiveHint = true
6. Bridge script detects navigator.modelContext before registering
7. Tool registrations include lifecycle cleanup
8. execute() functions return MCP-compatible content blocks

**Tier 4: Discovery (MAY — 3 items)**
Same as v1.2.2. Badges, launch buttons, identity widget.