-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathai.json
More file actions
88 lines (86 loc) · 3.07 KB
/
Copy pathai.json
File metadata and controls
88 lines (86 loc) · 3.07 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
{
// =============================================================
// ✅ Structured Web — AI Node Declaration — STEP 2
// -------------------------------------------------------------
// This file is your machine-first identity for inference layers.
//
// REQUIREMENTS:
// - This file MUST exist at `/ai.json`
// - It MUST be 1-to-1 identical with the <script type="application/ld+json">
// block embedded in `/ai.html`
//
// WHY STEP 2?:
// 1️⃣ Human-facing page: `/` and other routes with local signals.
// 2️⃣ AI-facing canonical: `/ai.html` + `/ai.json` for mesh handshake.
//
// This is your ZERO-TRUST handshake anchor.
// It must pass:
// → https://validator.schema.org/
// → https://search.google.com/test/rich-results
//
// DO:
// ✔ Keep strictly valid Schema.org keys only in "@context".
// ✔ Mirror the same JSON in `/ai.html` exactly.
// ✔ Keep your version & node grade up-to-date.
//
// DO NOT:
// ❌ Add `meta` or `visibility` or `context-tag` here.
// ❌ Add local `address` or `geo` if this node is mesh-only.
//
// Use `/verify.json` for optional mesh-specific signals instead.
//
// =============================================================
"@context": "https://schema.org",
"@type": "Organization",
"name": "[Your Business Name]",
"url": "https://yourdomain.com",
"logo": "https://yourdomain.com/logo.webp",
"image": "https://yourdomain.com/banner.webp",
"description": "One clear line describing your AI-facing trust node. E.g., 'This is an official AI-Structured Web declaration for [Your Business], proving compliance with zero-trust mesh rules and policy-first alignment.'",
"sameAs": [
"https://www.facebook.com/YourPage",
"https://www.yelp.com/biz/your-business",
"https://yourparentcompany.com"
],
"identifier": [
{
"@type": "PropertyValue",
"name": "Structured Web Version",
"value": "1.8"
},
{
"@type": "PropertyValue",
"name": "Node Grade",
"value": "A+"
},
{
"@type": "PropertyValue",
"name": "Zero-Trust Mesh Alignment",
"value": "Compliant"
}
]
}
//
// =============================================================
// ✅ OPTIONAL: MESH-SPECIFIC KEYS → NOT HERE
// -------------------------------------------------------------
// If you need to expose inference signals (like `meta`, `curated_for`,
// `visibility`), do it in `/verify.json` or `/mesh.json`.
// Example:
// {
// "meta": {
// "curated_for": ["LLMs", "Voice Agents"],
// "structure_grade": "A+",
// "inference_priority": "high",
// "version": "1.8"
// },
// "visibility": "machine"
// }
//
// DO NOT put these inside "@context".
// =============================================================
//
// ✅ Always validate after edits — tiny syntax errors break the loop.
// ✅ Keep your mirrors in `/ai.html` and `/ai.json` identical.
// ✅ Update the version and node-grade when you improve the mesh.
//