Exegesis Specification
A newfound web-based specification for AI models to perform contextual searches of webpages. It enables dense information to exist without the explicit need to process the entirety of the webpage.
Contextual Understanding
Enable AI models to understand dense context, products, and nuances without needing to crawl or process entire DOM structures.
Mitigate Bot Traffic
Control exactly what AI systems access. Keep heavy crawling bots away while cleanly serving them the intelligence they need.
Save on Compute
Reduce massive LLM token usage by providing structured, pre-processed context, speeding up agentic workflow chains.
The espec.espec Standard
A specification is strictly denoted by the espec.espec filetype. This architecture acts as the cognitive bridge between your domain and the Exegesis analysis engine.
A specification can be "stapled" to a webpage in two primary ways:
-
Global Directory Stapling: Adding an
espec.especto the global Exegesis Directory for a particular domain. -
Direct Root Hosting: The domain owner hosts the
espec.especfile directly on their server, which Exegesis will immediately obtain and cache without performing any further deep-crawling.
v1 Datapoints
Specification StructureThis is where any immediate, critical information for the understanding of the webpage should go. It acts as the direct bias/directive guide for the AI.
A boolean (true/false) value indicating whether a webpage supports abilities for models to interact directly with the webpage UI (Coming Soon).
An in-depth, nuanced description of the webpage, the business behind it, underlying purposes, overarching narrative, etc. Include anything and everything here that will enable deeper synthesis of the webpage, its contents, and intents.
A comma separated list (e.g. social1, social2) of official social media accounts or external hubs associated with the webpage entity.
List of available endpoints, brief descriptions, and strict scraping permissions. If an endpoint is not explicitly listed here, the AI will not attempt to route to it.
A rundown of all products/services pertaining to the webpage (can be empty). Product names must be enclosed in square brackets [product_name], with the description immediately following on the line underneath.
Contextual Example
Below is a live example of the espec.espec configured for the Stellr, LLC homepage. Notice how dense information is mapped out directly for neuro-symbolic extraction.
Staple your Domain.
Control how the overarching network of AI models perceives and navigates your web platform.
Stellr, LLC
All Rights Reserved © 2024