P69 — AIEP — Static Site Generator Adapter Pattern
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 integration patterns for AIEP-compliant machine mirror page generation within static site generator build pipelines.
[0002] More particularly, the disclosure concerns a static site generator adapter pattern defining the required interface and behaviour for AIEP adapter plugins for Next.js, Astro, Hugo, and WordPress, enabling automatic mirror page generation, manifest updates, and schema validation as part of the standard site build process.
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] Static site generators produce human-readable HTML pages as build output. To publish AIEP-compliant machine mirror pages, publishers must generate corresponding .aiep.json files for each page, update the well-known manifest and site index, and validate schema compliance — all as deterministic build steps.
[0006] Without a standardised adapter pattern, each SSG integration is implemented inconsistently, producing non-deterministic mirror pages and omitting validation gates that would otherwise prevent non-compliant output from reaching production.
Summary of the Disclosure
[0011] A static site generator adapter pattern is disclosed defining the required interface and behaviour for AIEP adapter plugins.
[0012] Adapters are defined for four reference SSG platforms: Next.js, Astro, Hugo, and WordPress.
[0013] All adapters must implement three required behaviours:
(a) mirror page generation: for each source page produced by the build, the adapter generates a corresponding machine mirror page conforming to P60, canonicalises the data object, computes content_hash using P63 rules, and writes the mirror file to the build output;
(b) manifest update: after generating all mirror pages, the adapter generates or updates the well-known manifest at /.well-known/aiep-manifest.json conforming to P61, reflecting all supported schema versions; and
(c) schema validation gate: the adapter validates all generated mirror pages against their declared schemas before build completion. If validation fails for any mirror page, the build must halt with a non-zero exit code (fail-closed), preventing non-compliant output from being published.
[0014] An AdapterRunHash is computed as:
AdapterRunHash = H(SSGPlatformId || SchemaVersionId || MirrorPageCount || IndexHash || Timestamp)
[0015] The technical effect is provision of a standardised adapter interface enabling automatic, deterministic, fail-closed AIEP mirror page generation within standard SSG build pipelines.
Brief Description of the Drawings
[0016] Figure 1 illustrates the adapter integration point within the SSG build pipeline.
[0017] Figure 2 illustrates the three required adapter behaviours in sequence.
[0018] Figure 3 illustrates the schema validation gate and fail-closed build halt.
[0019] Figure 4 illustrates the AdapterRunHash computation for audit and replay.
ASCII Drawings
Figure 1 — Adapter Integration Point
SSG Build Pipeline
+------------------+
| Parse source |
| content |
+--------+---------+
|
v
+--------+---------+
| Generate HTML |
| pages |
+--------+---------+
|
v
+--------+---------+ <-- AIEP Adapter injects here
| AIEP Mirror |
| Generation |
| Manifest Update |
| Schema Validation|
+--------+---------+
|
+------+------+
PASS FAIL
| |
v v
Build HALT build
output non-zero exit
published fail-closed
Figure 2 — Three Required Adapter Behaviours
1. Mirror Page Generation
For each source page:
- Extract structured data
- Canonicalise (P63 rules)
- Compute content_hash
- Write /path.aiep.json
2. Manifest Update
After all mirrors generated:
- Generate /.well-known/aiep-manifest.json (P61)
- Declare supported schema versions
3. Schema Validation Gate
For each generated mirror:
- Validate against declared schema
- PASS: continue
- FAIL: halt build, non-zero exit
Figure 3 — Schema Validation Gate
Validate each mirror page
|
v
+------------------+
| All mirrors pass |
| schema check? |
+--------+---------+
|
+------+------+
All Pass Any Fail
| |
v v
Update HALT build
index Non-zero exit
Publish Fail-closed
output No output
published
Figure 4 — AdapterRunHash Computation
SSGPlatformId ----+
SchemaVersionId ----+
MirrorPageCount ----+--> H(SSGPlatformId ||
IndexHash ----+ SchemaVersionId ||
Timestamp ----+ MirrorPageCount ||
IndexHash || Timestamp)
|
v
+--------------------+
| AdapterRunHash |
| (audit + replay) |
+--------------------+
Detailed Description
1. Supported Platforms
[0020] Reference adapters are defined for Next.js, Astro, Hugo, and WordPress. The adapter pattern is applicable to any SSG platform exposing a build hook or plugin interface.
2. Mirror Page Generation
[0021] For each source page produced by the build, the adapter extracts structured content, canonicalises the data object using P63 rules, computes content_hash, and writes the mirror file conforming to P60 to the build output directory.
3. Manifest Update
[0022] After generating all mirror pages, the adapter generates or updates the well-known manifest at /.well-known/aiep-manifest.json conforming to P61, listing all supported schema versions.
4. Schema Validation Gate
[0023] Before build completion, the adapter validates all generated mirror pages against their declared schemas. If any mirror page fails validation, the build halts with a non-zero exit code and no output is published. This ensures non-compliant mirror pages cannot reach production.
5. AdapterRunHash
[0024] An AdapterRunHash is computed as H(SSGPlatformId || SchemaVersionId || MirrorPageCount || IndexHash || Timestamp) for build audit and replay.
Claims
-
A static site generator adapter pattern comprising: (a) mirror page generation producing a machine mirror page conforming to P60 for each source page, with content_hash computed using P63 canonicalisation rules; (b) manifest update generating or updating the well-known manifest at
/.well-known/aiep-manifest.jsonconforming to P61 after all mirror pages are generated; (c) a schema validation gate validating all generated mirror pages before build completion, halting the build with a non-zero exit code upon any validation failure in a fail-closed manner; and (d) an AdapterRunHash computed as H(SSGPlatformId || SchemaVersionId || MirrorPageCount || IndexHash || Timestamp) for build audit. -
The pattern of claim 1 applicable to Next.js, Astro, Hugo, and WordPress reference platforms.
-
A computing system implementing an SSG adapter conforming to the pattern of any of claims 1 to 2.
-
A non-transitory computer-readable medium storing instructions implementing an SSG adapter conforming to the pattern 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 static site generator adapter pattern is disclosed defining required interface and behaviour for AIEP adapter plugins for Next.js, Astro, Hugo, and WordPress. Three required behaviours are defined: mirror page generation producing P60-conforming .aiep.json files with content_hash computed per P63 for each source page; manifest update generating the P61 well-known manifest after all mirrors are generated; and a schema validation gate halting the build with a non-zero exit code upon any validation failure before publication. An AdapterRunHash is computed as H(SSGPlatformId || SchemaVersionId || MirrorPageCount || IndexHash || Timestamp). The pattern ensures automatic, deterministic, fail-closed AIEP mirror generation within standard SSG build pipelines.