EP-9 Spec

Entity Architecture and Governance Framework (EP-9)

EP-9 is a nine-layer specification for building entities that search engines and AI can identify and trust: 4 entity groups, a 6-block page template, 15 checkpoints and a 100-point Definition of Done.

The Entity Architecture and Governance Framework (EP-9) is a nine-layer specification for building an entity on a website, ordered from the layer that matters most, a clear identity, to the layer that matters least, consistency outside the site. It adds a 6-block page template, a 15-point audit checklist and a 100-point Definition of Done.

Specification: master document, version 1.0 Structure: 9 layers, 4 entity groups, 6-block template DOI: 10.5281/zenodo.22934007, CC BY 4.0

What the EP-9 framework is

The EP-9 framework is a deterministic nine-layer specification for establishing an entity, separating it from namesakes and preparing it for extraction by AI search. It starts from one observation: generative search engines such as Google AI Overviews, ChatGPT, Perplexity and Gemini weigh clear entity recognition, verified Knowledge Graph links and machine-readable schema, not keyword frequency alone.

The nine layers form one sequence, which the specification calls the Trust Chain. Each layer depends on the one before it: a schema declaration has nothing to confirm until the entity has a page, and an external profile has nothing to point to until the entity has a canonical URL.

Trust Chain: Clear Identity (L1) → Owned Content (L2) → Contextual Links (L3) → DefinedTerm Schema (L4) → Disambiguation (L5) → sameAs KG Anchoring (L6) → Proof Stack (L7) → DOM QA (L8) → Off-Site Sync (L9)

What an entity is in EP-9

An entity in EP-9 is more than a name that appears on a page. The specification defines it by four properties at once: an identity, a context, relationships and evidence. The sentence below is the definition as deposited, and it is also the exact text of this page's DefinedTerm schema, as checkpoint CHK-EP-07 requires.

An entity with a clearly defined identity, a context that separates it from namesakes, links to related entities, and enough evidence for search engines, AI systems and people to understand what it is and why it can be trusted.

A keyword helps a page be found. An entity helps a page be understood, trusted and quoted, because a machine can tell what the page is about and connect it to other things it already knows.

Why owned pages come before off-site profiles

Owned pages come before off-site profiles because, in the words of the specification, off-site social profiles and external citations cannot substitute for on-site owned entity architecture. Topical authority needs a foundation on the website itself: dedicated entity pages, structured DefinedTerm schema and deliberate internal links.

A profile created on a social network with no content behind it adds a name, not an entity. Off-site consistency is therefore the ninth layer, not the first. It confirms an entity that the first eight layers have already built.

The four entity functional groups

The four entity functional groups sort every entity on a domain by the job it does for a buyer: Offer, Problem, Method and Trust. Grouping entities this way prevents topical clutter and ties each one to a stage of Decision Ladder Navigation (DLN), so each entity page knows which next step it should offer.

The four entity functional groups and their role in the DLN flow.
Entity categoryCore focus and purposePrimary role in DLN flowExample domain entities
Offer EntityCommercial solutions, services, products, and core deliverables.Rate & Act (Conversion Landing)SEO Master Course, Enterprise Audit Service
Problem EntityCustomer pain points, technical friction, and operational barriers.Orient (Awareness & Problem Framing)Keyword Cannibalization, Traffic Drop, Low Conversion
Method EntityProprietary frameworks, methodologies, algorithms, and SOPs.Choose & Prove (Solution Selection)SIUM-1, EP-9, DLN OCPRA, SP-8 Schema Pack
Trust EntityVerifiable credentials, authors, organizations, and E-E-A-T assets.Prove & Rate (Risk Elimination)Danh Nolan (Author), danhnolan.com, ORCID Profile

The nine layers and their priority

The nine layers of EP-9 are listed below in order of priority, each with its core requirement and its pass criterion. Layers 1 to 4 and layer 8 are mandatory. Layers 5 to 7 are high priority, and layer 9 is medium priority. Each layer has its own specification page, linked in the table.

The nine layers, as deposited, in order of priority.
LayerTechnical specification nameCore requirement and execution standardPriority and pass criteria
L1Clear Identity NamingEstablish 1 standardized, canonical entity name without ambiguous acronyms.Mandatory (Pass/Fail)
L2Owned Content HubDedicated URL (e.g., https://danhnolan.com/en/ep9/) with 6-block structured template.Mandatory (1 Dedicated Page)
L3Contextual Internal Links3-5 contextual internal links in related articles using exact entity name anchor text.Mandatory (Min 3 Links)
L4DefinedTerm SchemaJSON-LD DefinedTerm/Service schema with 100% word-for-word DOM text match.Mandatory (0 Schema Errors)
L5Disambiguation ContextInclude explicit context sentences, canonical definition, and 3-5 synonym mappings.High Priority
L6sameAs KG AnchoringLink entity to verified Knowledge Graph URIs (DOI, ORCID, Wikidata, LinkedIn).High Priority
L7Proof Stacking & E-E-A-TEmbed case studies, real-world data, author credentials, and transparent disclosures.High Priority
L8DOM QA & Render ParityEnsure core definition is visible in raw HTML DOM (not hidden behind JS/accordion).Mandatory QA
L9Off-Site Citation SyncMaintain 100% NAP and entity name consistency across external brand profiles.Medium Priority

The 6-Block Entity Page Template

The 6-Block Entity Page Template is the layout every owned entity page follows, so that a person can decide and a machine can extract from the same page. The blocks run from the definition, through scope and criteria, to mistakes, proof and a next step on the decision ladder.

The 6-Block Entity Page Template.
BlockBlock nameRequired structural content and layout elementsAI and conversion function
Block 1H1 & Answer-First DefinitionExact entity name in H1 + direct 1-2 sentence canonical definition immediately following.AI Featured Snippet & GEO Direct Answer
Block 2Context & Scope BoundariesDetailed explanation of what the entity is, what it is NOT, and key application scenarios.Semantic Disambiguation & Entity Bounds
Block 3Selection & Usage CriteriaStructured criteria, decision matrices, comparison tables, and execution conditions.DLN Choose Stage (Solution Comparison)
Block 4Common Mistakes & Anti-PatternsList of frequent execution errors, misconceptions, and anti-pattern warnings.Risk Reduction & Trust Building
Block 5Proof Stack & Case DataVerifiable implementation data, case study results, author bio, and ORCID/DOI citations.E-E-A-T Verification & Proof Stacking
Block 6Next-Step DLN Link RailContextual internal links leading to related Offer/Method entities or booking forms.Conversion Pathway (DLN Rate -> Act)

The 15-point technical audit checklist

The 15-point technical audit checklist turns the nine layers into checks with a named tool or method for each. Every checkpoint has an identifier from CHK-EP-01 to CHK-EP-15, so an audit can report which item failed rather than a general impression. Each layer page repeats its own checkpoints.

The itemized 15-point EP-9 technical audit checklist.
Checklist IDAudit layerMandatory verification requirementTool and method
CHK-EP-01L1 IdentityExact canonical entity name used across Title, H1, and Schema.DOM Inspection
CHK-EP-02L2 ContentDedicated Entity Page deployed with 6-block template at canonical URL.URL Audit / CMS
CHK-EP-03L2 Answer-First1-2 sentence direct definition appears immediately under H1.DOM Text Audit
CHK-EP-04L3 LinkingAt least 3 contextual internal links in cluster articles point to Entity Page.Screaming Frog
CHK-EP-05L3 Anchor TextAnchor text matches target entity name (no generic 'click here').Internal Link Audit
CHK-EP-06L4 Schema SyntaxValid DefinedTerm / Service JSON-LD schema with 0 syntax errors.Rich Results Test
CHK-EP-07L4 DOM ParitySchema description matches rendered HTML text 100% word-for-word.Tier 3 DOM QA
CHK-EP-08L5 DisambiguationInclude explicit context sentence and 3-5 synonym mappings.Content Brief QA
CHK-EP-09L6 KG AnchoringsameAs property links to DOI (10.5281/zenodo.22934007) or ORCID.JSON-LD Inspector
CHK-EP-10L7 Proof StackEmbed case data, methodology proof, and verifiable credentials.On-Page Audit
CHK-EP-11L7 Author BioAuthor profile linked to verified Person schema and ORCID record.E-E-A-T Audit
CHK-EP-12L8 DOM RenderCore answer visible in raw HTML DOM (not hidden under accordion/JS).GSC Live Test
CHK-EP-13L8 CanonicalSelf-referencing canonical tag on Entity Page.HTML Header Test
CHK-EP-14L9 ConsistencyEntity name, address, and description match across external profiles.Citation Audit
CHK-EP-15L9 Social SyncExternal brand profiles link back to canonical Entity Page URL.Backlink Audit

The official schema template for this page

The official schema template in the specification is written for this URL. It declares a WebPage about the entity, a DefinedTerm with the canonical definition, and a DefinedTermSet for the framework, all connected by @id references in one @graph. This page publishes the same three nodes, plus a term for each of the nine layers.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "https://danhnolan.com/en/ep9/#webpage",
      "url": "https://danhnolan.com/en/ep9/",
      "name": "Entity Architecture and Governance Framework (EP-9)",
      "isPartOf": {
        "@id": "https://danhnolan.com/#website"
      },
      "about": {
        "@id": "https://danhnolan.com/en/ep9/#entity"
      }
    },
    {
      "@type": "DefinedTerm",
      "@id": "https://danhnolan.com/en/ep9/#entity",
      "name": "Entity (EP-9)",
      "description": "An entity with a clearly defined identity, a context that separates it from namesakes, links to related entities, and enough evidence for search engines, AI systems and people to understand what it is and why it can be trusted.",
      "inDefinedTermSet": {
        "@id": "https://danhnolan.com/en/ep9/#ep9"
      }
    },
    {
      "@type": "DefinedTermSet",
      "@id": "https://danhnolan.com/en/ep9/#ep9",
      "name": "Entity Architecture and Governance Framework (EP-9)",
      "sameAs": "https://doi.org/10.5281/zenodo.22934007"
    }
  ]
}

The 30-day implementation roadmap

The 30-day implementation roadmap splits an EP-9 rollout into four sprints: inventory, entity pages, schema and links, then DOM QA and verification. The order follows the Trust Chain, so no sprint depends on work that a later sprint has not yet done.

  1. Sprint 1 (Days 1-7) - Entity Audit & Inventory. Identify core domain entities. Map into 4 functional groups (Offer, Problem, Method, Trust). Audit existing URLs and external brand profiles.
  2. Sprint 2 (Days 8-15) - Entity Page Architecture & Content. Deploy dedicated Entity Pages using the 6-block template. Draft Answer-First definitions and disambiguation context.
  3. Sprint 3 (Days 16-23) - Schema Implementation & Internal Link Flow. Inject @graph DefinedTerm JSON-LD with DOI sameAs linkage. Build 3-5 contextual internal links per entity.
  4. Sprint 4 (Days 24-30) - DOM QA & AI Extraction Verification. Validate 100% DOM text parity. Perform GSC URL inspection. Monitor Google AI Overviews and ChatGPT citations.

The 100-point Definition of Done

The Definition of Done is the rubric that decides whether an entity page is ready for production. It has five evaluation domains of 20 points each: identity on its own, then the remaining eight layers in pairs, so every layer of the framework is scored somewhere in the rubric.

The 100-point Definition of Done, five evaluation domains of 20 points each.
Evaluation domainMax scoreMandatory quality control pass criteria
1. Identity & Naming (L1)20 PointsCanonical name standardized; zero ambiguous acronyms; Title & H1 aligned.
2. Content Architecture (L2-L3)20 PointsDedicated URL deployed with 6-block template; min 3 contextual internal links.
3. Schema & DOM Parity (L4-L5)20 PointsDefinedTerm @graph schema valid with 0 errors; 100% word-for-word DOM text match.
4. KG Anchoring & Proof (L6-L7)20 PointssameAs points to DOI (10.5281/zenodo.22934007) or ORCID; proof stack embedded.
5. DOM QA & Off-Site Sync (L8-L9)20 PointsAnswer-first visible in raw HTML; NAP and entity citations consistent off-site.

Frequently asked questions about EP-9

These are the questions readers ask most often about the Entity Architecture and Governance Framework (EP-9). Each one is answered directly from the deposited specification, in a few sentences, so that the answer can be read, quoted and cited on its own without the rest of this page.

No. EP-9 on this site is the Entity Architecture and Governance Framework, a specification for building entities that search engines and AI systems can identify. It has no connection to the NIO EP9 car or to any product model number. The hyphen and the full name are used to keep the two apart.

Which EP-9 layers are mandatory?

Layers 1 to 4 are mandatory in EP-9, and layer 8 is a mandatory quality check. Layers 5, 6 and 7 are high priority, and layer 9, off-site consistency, is medium priority. A page that fails a mandatory layer is not finished, whatever it scores elsewhere.

How long does it take to apply EP-9?

Applying EP-9 takes 30 days in the published roadmap, split into four sprints. Days 1 to 7 are the entity audit, days 8 to 15 build the entity pages, days 16 to 23 add schema and internal links, and days 24 to 30 verify the rendered page and watch for citations in AI answers.

Rights, reuse and how to cite this framework

Rights and reuse for this framework follow the Creative Commons Attribution 4.0 International license stated in the deposited specification. You may copy, share, adapt and build on the material for any purpose, including commercial use, as long as you give credit, link to the license and state whether you made changes.

Cite this framework as: Nolan, D. (2026). Entity Architecture and Governance Framework (EP-9): A 9-Layer Entity Specification, 6-Block Content Template, DefinedTerm Schema, and Trust Chain Standard for AI Search Extraction. Technical Working Paper, danhnolan.com Research Group. Zenodo. 10.5281/zenodo.22934007. ORCID: 0009-0007-7906-5091. Licensing terms: rights and reuse.

The deposit on Zenodo is the authoritative version. If this page and the deposited document differ, follow the document under the DOI.

References

The references below are the standards and official documentation that the layers of EP-9 apply. They are listed so that each requirement can be checked against its source rather than taken on trust, which is the same principle the seventh layer asks of every entity.

How to apply EP-9 to build a trusted entity page

These steps follow the Trust Chain order of EP-9, so you build a named entity, give it an owned page, declare it in schema and verify it before syncing external profiles.

  1. Inventory and group your entitiesIdentify the core entities on your domain, map each one into the four functional groups Offer, Problem, Method and Trust, and audit existing URLs and external brand profiles.
  2. Fix one canonical entity nameEstablish 1 standardized canonical name without ambiguous acronyms and use the exact same name across the Title, the H1 and the schema.
  3. Publish a dedicated 6-block entity pageDeploy the entity at its own canonical URL using the 6-Block Entity Page Template, with a 1-2 sentence answer-first definition immediately under the H1.
  4. Link the page from related articlesAdd 3-5 contextual internal links in related cluster articles, using the exact entity name as anchor text and never a generic phrase like click here.
  5. Declare the entity in DefinedTerm schemaAdd valid DefinedTerm JSON-LD with 0 syntax errors, match its description word for word to the visible text, and link sameAs to the DOI or ORCID.
  6. Verify the rendered pageConfirm the core definition appears in the raw HTML DOM and is never hidden behind JS or an accordion, then run a GSC URL inspection.
  7. Sync external profiles lastKeep the entity name, address and description consistent across external brand profiles, and make each profile link back to the canonical entity page URL.

FAQ about EP-9

Why does creating social profiles first fail to build an entity?

Social profiles created first fail because they add a name with no content behind it, and a name alone is not an entity. EP-9 places off-site consistency at layer 9, so external profiles confirm an entity that the first eight layers have already built on your own website.

What happens when the schema description does not match the visible text?

The page fails checkpoint CHK-EP-07, which requires the schema description to match the rendered HTML text 100% word-for-word. A mismatch also costs points in the Schema and DOM Parity domain of the Definition of Done, so copy the visible definition into the DefinedTerm exactly.

Why can a well-written entity definition still fail the EP-9 audit?

A well-written definition can still be missed if it is hidden behind JS or an accordion. Layer 8 of EP-9, DOM QA and Render Parity, requires the core definition to be visible in the raw HTML DOM, and checkpoint CHK-EP-12 tests it with the GSC Live Test.

Generic anchors such as click here fail the EP-9 internal link check. Checkpoint CHK-EP-05 requires anchor text that matches the target entity name, and layer 3 asks for 3-5 contextual links in related articles, with at least 3 needed to pass.

What are the four entity functional groups in EP-9 and what does each do?

The four groups are Offer, Problem, Method and Trust. Offer entities are services and products, Problem entities are customer pain points, Method entities are frameworks and methodologies, and Trust entities are credentials, authors and organizations. Each group ties to a stage of Decision Ladder Navigation (DLN).

What does each block of the 6-Block Entity Page Template contain?

Block 1 holds the H1 and an answer-first definition, Block 2 sets context and scope, Block 3 gives selection and usage criteria, Block 4 lists common mistakes, Block 5 carries proof and case data, and Block 6 is a next-step DLN link rail to related Offer or Method entities.

How is the 100-point Definition of Done scored across the nine layers?

The Definition of Done has five evaluation domains worth 20 points each. Identity and naming (L1) is scored alone, then the other layers are scored in pairs: L2-L3, L4-L5, L6-L7 and L8-L9. Every layer of EP-9 is therefore scored somewhere in the rubric.

How are items in the EP-9 15-point audit checklist identified and tested?

The 15-point checklist turns the nine layers into specific checks, each with a named tool or method such as DOM Inspection, Screaming Frog or the Rich Results Test. Every item has an identifier from CHK-EP-01 to CHK-EP-15, so an audit reports exactly which item failed.

What is EP-9 and what is it used for?

EP-9, the Entity Architecture and Governance Framework, is a nine-layer specification for building entities that search engines and AI can identify and trust. EP-9 orders the layers from a clear identity to off-site consistency and adds 4 entity groups, a 6-block page template, 15 checkpoints and a 100-point Definition of Done.

What is the difference between a keyword and an entity in EP-9?

In EP-9, a keyword helps a page be found, while an entity helps a page be understood, trusted and quoted. EP-9 defines an entity by four properties at once: an identity, a context that separates it from namesakes, links to related entities, and enough evidence to show why it can be trusted.

Can EP-9 be reused and adapted for commercial projects?

Yes, EP-9 can be used commercially under the Creative Commons Attribution 4.0 International license stated in the deposited specification. Anyone may copy, share, adapt and build on EP-9 for any purpose, as long as they give credit, link to the license and state whether they made changes.

Where should I start when applying EP-9 to a website?

Start EP-9 with the entity audit in days 1 to 7 of the 30-day roadmap: identify core domain entities, map them into the four groups Offer, Problem, Method and Trust, and audit existing URLs and external brand profiles. Then fix layer 1, one canonical name without ambiguous acronyms.

Menu

Add to Home Screen

  1. 1 Tap Share in Safari toolbar
  2. 2 Scroll down, select Add to Home Screen
  3. 3 Tap Add in top right corner

These steps are for Safari on iOS. If viewing inside another app, open in Safari first.