P68 — AIEP — Cloudflare Deployment Blueprint
Publication Date: 2026-02-26 Status: Open Source Prior Art Disclosure Licence: Apache License 2.0 Author/Organisation: Phatfella Ltd Schema: AIEP_OS_SPEC_TEMPLATE v1.0.1 — https://aiep.dev/schemas/aiep-os-spec-template/v1.0.1
Field of the Invention
[0001] The disclosure relates to reference deployment architectures for AIEP-compliant web infrastructure.
[0002] More particularly, the disclosure concerns a reference deployment blueprint using Cloudflare infrastructure components to host and serve AIEP machine mirror pages, well-known manifests, site indexes, and validation services in a deterministic, edge-distributed manner.
Framework Context
[0003] This invention operates within an Architected Instruction and Evidence Protocol (AIEP) environment as defined in United Kingdom patent application number GB2519711.2, filed 20 November 2025, the entire contents of which are incorporated herein by reference.
[0004] The present invention extends deterministic canonicalisation, governance, and execution integrity mechanisms defined in the AIEP environment while remaining independently implementable as described herein.
Background
[0005] Publishers deploying AIEP-compliant machine mirror pages require a reference deployment architecture that provides edge-distributed serving, deterministic validation, durable registry storage, and canonical manifest hosting.
[0006] Without a reference blueprint, publishers must independently design infrastructure, producing inconsistent and non-interoperable deployment patterns that may compromise deterministic serving guarantees.
Summary of the Disclosure
[0011] A Cloudflare deployment blueprint is disclosed defining reference infrastructure components for hosting AIEP-compliant web artefacts.
[0012] The four reference components are:
(a) Cloudflare Workers for edge-side mirror page validation: Workers intercept requests to .aiep.json endpoints, validate content_hash on delivery, and return non-admissible responses for hash mismatches without serving corrupted content;
(b) Cloudflare KV for manifest storage: the well-known manifest (/.well-known/aiep-manifest.json) and site index (/.well-known/aiep-index.json) are stored in Cloudflare KV as immutable versioned entries, with KV keys structured as manifest:{site}:{version} and index:{site}:{version};
(c) Cloudflare Durable Objects for schema registry: domain schema definitions and version records are stored in Durable Objects providing strongly consistent reads, with each Durable Object instance scoped to a schema namespace; and
(d) Edge caching for mirror endpoints: machine mirror pages are served with deterministic cache keys derived from schema_version and content_hash, ensuring cached copies are invalidated on content change.
[0013] A DeploymentConfigHash is computed as:
DeploymentConfigHash = H(WorkerConfig || KVNamespace || DurableObjectNamespace || CachePolicy || SchemaVersionId)
[0014] Workers must not serve mirror pages without first verifying content_hash. Hash verification failure must return an HTTP 422 response with a non-admissible status body.
[0015] The technical effect is provision of a reference edge-distributed deployment architecture enabling consistent, deterministic serving and validation of AIEP web artefacts at global scale.
Brief Description of the Drawings
[0016] Figure 1 illustrates the four component architecture and request flow for mirror page delivery.
[0017] Figure 2 illustrates Worker-side hash validation and fail-closed response on mismatch.
[0018] Figure 3 illustrates KV key structure for manifest and index storage.
[0019] Figure 4 illustrates cache key derivation and invalidation strategy.
ASCII Drawings
Figure 1 — Four Component Architecture
Agent Request
|
v
+------------------+
| Cloudflare |
| Workers |
| (validation) |
+--------+---------+
|
+------+------+
Valid Invalid
| |
v v
Serve from HTTP 422
Edge Cache Non-admissible
|
+------> KV (manifest / index)
|
+------> Durable Objects (schema registry)
Figure 2 — Worker Hash Validation
Request to /path.aiep.json
|
v
Worker fetches mirror page
|
v
Verify content_hash against
canonical data object
|
+---+---+
Match Mismatch
| |
v v
Serve HTTP 422
mirror non-admissible
page body
Figure 3 — KV Key Structure
Manifest: manifest:{site}:{version}
Index: index:{site}:{version}
Example:
manifest:example.com:1.0.0
index:example.com:1.0.0
KV entries are immutable once written.
New versions create new KV entries.
Figure 4 — Cache Key Derivation and Invalidation
Cache key = H(endpoint_path || schema_version || content_hash)
Content change -> new content_hash -> new cache key
-> automatic cache invalidation
-> stale cached content never served for new hash
Detailed Description
1. Workers for Validation
[0020] Cloudflare Workers intercept requests to .aiep.json mirror endpoints and validate content_hash before serving. Hash mismatch returns HTTP 422 with a non-admissible status body. No corrupted or unverified content is served.
2. KV for Manifest and Index Storage
[0021] Well-known manifest and site index documents are stored in Cloudflare KV as immutable versioned entries keyed by manifest:{site}:{version} and index:{site}:{version}. Existing KV entries are not overwritten. New versions create new entries.
3. Durable Objects for Schema Registry
[0022] Domain schema definitions and version records are stored in Cloudflare Durable Objects providing strongly consistent reads. Each Durable Object instance is scoped to a schema namespace. Registry entries are append-only.
4. Edge Caching
[0023] Mirror pages are cached with deterministic cache keys derived from endpoint_path, schema_version, and content_hash. Content changes produce new content_hash values and therefore new cache keys, ensuring stale cached content is never served for updated mirrors.
5. DeploymentConfigHash
[0024] A DeploymentConfigHash is computed as H(WorkerConfig || KVNamespace || DurableObjectNamespace || CachePolicy || SchemaVersionId) for deployment audit and reproducibility verification.
Claims
-
A Cloudflare deployment blueprint for AIEP-compliant web infrastructure comprising: (a) Cloudflare Workers intercepting mirror endpoint requests and verifying content_hash before serving, returning HTTP 422 on hash mismatch without serving unverified content; (b) Cloudflare KV storing well-known manifest and site index as immutable versioned entries keyed by site and version; (c) Cloudflare Durable Objects storing schema registry with strongly consistent reads and append-only entries; and (d) edge caching with deterministic cache keys derived from endpoint path, schema_version, and content_hash ensuring automatic invalidation on content change.
-
The blueprint of claim 1 wherein a DeploymentConfigHash is computed as H(WorkerConfig || KVNamespace || DurableObjectNamespace || CachePolicy || SchemaVersionId) for deployment audit.
-
A computing system implementing infrastructure conforming to the blueprint of any of claims 1 to 2.
-
A non-transitory computer-readable medium storing configuration instructions implementing infrastructure conforming to the blueprint of any of claims 1 to 2.
Licence
Any person is granted a perpetual, irrevocable, worldwide, royalty-free licence to make, use, implement, modify, or distribute any system or method described in this disclosure for any purpose, without restriction, under the Apache License 2.0.
A copy of the Apache License 2.0 is available at https://www.apache.org/licenses/LICENSE-2.0
Abstract
A Cloudflare deployment blueprint is disclosed for AIEP-compliant web infrastructure. Four reference components are defined: Cloudflare Workers for edge-side content_hash validation returning HTTP 422 on mismatch, Cloudflare KV for immutable versioned manifest and index storage, Cloudflare Durable Objects for schema registry with strongly consistent reads, and edge caching with deterministic cache keys derived from endpoint path, schema_version, and content_hash. A DeploymentConfigHash is computed as H(WorkerConfig || KVNamespace || DurableObjectNamespace || CachePolicy || SchemaVersionId). The blueprint provides a reference edge-distributed deployment architecture for consistent deterministic serving of AIEP web artefacts at global scale.