ThatWare AI
Analyze My Website →
PRACTICAL FILE GUIDE KNOWLEDGE REGISTRY

The Practical Guide to the ThatWare AI Knowledge Registry

Your organization knows far more than what appears on its homepage.

It has:

Research. Frameworks. Intellectual property. Awards. Media coverage. Books. Training. Credentials. Speaking engagements. Frequently asked questions. Entity relationships. Institutional memory.

The ThatWare AI Knowledge Registry is designed to organize those assets into a connected machine-readable knowledge system.

Instead of requiring intelligent systems to infer organizational expertise from scattered webpages, profiles, PDFs and external references, the Registry creates structured records that explain:

  • • What the organization has created.
  • • What it knows.
  • • Who and what belong to it.
  • • Which evidence supports its expertise.
  • • Which concepts it owns or defines.
  • • Which information should remain part of its long-term machine-readable identity.
Explore the Knowledge Registry → Explore the Intelligence Layer →

Supporting line: Turn organizational evidence into structured, connected and retrievable knowledge.

EVIDENCE GRAPH
Structured Proof Architecture

Convert scattered PDFs, patents, speaking gigs, and press coverage into an integrated machine-readable evidence graph that autonomous LLMs can resolve.

• 14 Coordinated Evidence Files • Master Innovation Catalog Schema • Persistent Brand Memory Layer
START WITH THE ARCHITECTURE

Fourteen Files. Fourteen Knowledge Responsibilities.

ThatWare's internal schema explicitly models the first nine evidence files as structured root resources and the Innovation Registry as their master catalog.

File Primary Role Core Question
keynotes.json Speaking authority Where has the organization shared expertise publicly?
copyrights.json Intellectual property What copyrighted assets belong to the organization?
research.json Research knowledge What original research has been produced?
frameworks.json Proprietary methodologies What frameworks or methodologies does the organization define?
awards.json Recognition What legitimate awards or recognitions support authority?
media.json Media evidence Where has the organization or its experts appeared publicly?
books.json Publications What books and long-form knowledge assets exist?
courses.json Education What structured training or educational assets exist?
certifications.json Credentials What professional or technical credentials can be represented?
innovation-registry.json Master innovation catalog How do the innovation and evidence records connect?
faq.json Structured Q&A What questions can the organization answer directly?
faq-knowledge-graph.json FAQ relationships How do questions connect to entities, topics and sources?
entity-registry.json Canonical entity registry Which entities, aliases and references are official?
brand-memory.json Persistent organizational memory What should machines consistently understand about the brand over time?
FROM SCATTERED PROOF TO CONNECTED KNOWLEDGE

Most Organizational Authority Exists in Fragments

Consider a company with:

  • • A founder who has spoken at conferences.
  • • A proprietary framework explained on several pages.
  • • Research published as PDFs.
  • • Awards listed on an old press page.
  • • Interviews hosted on third-party websites.
  • • Books published externally.
  • • Training materials in a learning platform.
  • • Certifications scattered across employee profiles.
  • • FAQs duplicated across service pages.

From a human perspective, these facts may clearly belong to one organization. From a machine perspective, they can look like disconnected records.

The Knowledge Registry creates a different model:
Organization
→ Research
→ Frameworks
→ Intellectual Property
→ Experts
→ Keynotes
→ Publications
→ Media
→ Awards
→ Certifications
→ FAQs
→ Entities
→ Long-Term Brand Memory
The Goal

Turn organizational proof into a structured evidence graph.

TWO DIFFERENT RESPONSIBILITIES

One Stores Organizational Knowledge. The Other Helps Systems Use It.

EVIDENCE REPOSITORY

Knowledge Registry

Answers: What does the organization know, own, publish and prove?

It focuses on:

Research Frameworks IP Awards Media Publications Education Credentials FAQs Entities Brand memory

Simple distinction: The Knowledge Registry stores the evidence.

UTILIZATION & REASONING

Intelligence Layer

Answers: How should that knowledge be related, retrieved, interpreted, validated and cited?

It focuses on:

Knowledge graphs Retrieval Context Reasoning Trust Citations Endpoints Freshness

Simple distinction: The Intelligence Layer connects how the evidence can be used.

PUBLIC EXPERTISE

keynotes.json - Structure Speaking Authority

A keynote, panel, workshop or conference appearance is more than an event. It can establish relationships among: Speaker, Organization, Topic, Event, Date, Location, Recording, Source.

ThatWare's internal root-file architecture defines keynotes.json as a structured index of keynotes, conference talks, workshops, public speaking engagements and founder-led sessions.

Use It For:

Speaking authority Expert-topic relationships Conference evidence Founder expertise External validation
Example keynotes.json 
{
  "title": "Future of AI Search",
  "speaker": "Example Founder",
  "event": "Industry Conference",
  "date": "2026-06-14",
  "topics": [
    "AI Search",
    "Entity Intelligence"
  ],
  "sourceUrl": "https://example.com/event/",
  "recordingUrl": "https://example.com/video/"
}
INTELLECTUAL PROPERTY

copyrights.json - Create a Structured Copyright Registry

Organizations often own valuable intellectual assets but present them only as footer notices or scattered documents. copyrights.json can create structured records around: Copyrighted work, Ownership, Copyright identifier, Publication date, Associated asset, Supporting notice, Canonical source.

ThatWare's internal architecture defines this file specifically for copyright records, IDs, ownership references, publication dates and intellectual-property notices.

Important Principle

This file should document verified ownership. It should not be used to claim ownership of material without legal basis.

VERIFIED OWNERSHIP

Maps registered intellectual property and formal publication dates to the organization entity for automated legal authority discovery.

ORIGINAL KNOWLEDGE

research.json - Make Your Research Easier to Discover and Attribute

Original research is one of the strongest authority assets an organization can create. Yet research may live across PDFs, whitepapers, blog posts, data studies, research pages, presentations, and reports. research.json provides a structured index of those assets.

ThatWare's architecture defines it around research papers, whitepapers, methodology resources and AI-search-intelligence publications.

Recommended Fields:

Research title Author Organization Publication date Research topic Methodology Canonical source Dataset, if public Related frameworks Citation information
Example Relationship
Research
→ Author
→ Organization
→ Methodology
→ Framework
→ Topic
→ Publication
PROPRIETARY METHODOLOGIES

frameworks.json - Define the Systems Your Organization Has Developed

Many businesses use the term "framework" loosely. A structured framework registry should clarify: Framework name, Definition, Purpose, Creator, First publication, Related concepts, Supporting research, Canonical source.

ThatWare's own architecture uses frameworks.json as a structured registry for its named frameworks and connects those concepts back into the wider innovation architecture.

Good Registry Entry

A defined methodology with: Clear scope, Documented origin, Supporting source, Related research.

Bad Registry Entry

A marketing phrase presented as a proprietary framework without evidence.

NAMED METHODOLOGIES

Explicitly documents proprietary systems (such as AVM and VEM) with verified dates and author provenance.

VERIFIED RECOGNITION

awards.json - Structure Awards Without Turning Them Into Marketing Noise

Awards can strengthen an organizational evidence graph when they are verifiable. The registry can contain: Award name, Awarding organization, Category, Recipient, Date, Source URL, Supporting page, Relevant entity.

ThatWare's internal design uses awards.json for organizational recognition, leadership mentions, technology awards and industry awards.

Principle
"Record the evidence. Avoid exaggerating the meaning."

An award record should not automatically imply that the organization is "the best" in a category unless the awarding body explicitly made that determination.

THIRD-PARTY RECOGNITION

Binds verified external honors (like Stevie Awards) to the corporate entity via immutable verification URLs.

EXTERNAL MEDIA AUTHORITY

media.json - Connect Interviews, Press and Public Appearances

An organization may be referenced through: Interviews, Podcasts, News features, Guest articles, Expert commentary, Founder profiles, Public media appearances.

The media registry organizes those references around the correct organization and expert entities. ThatWare's internal file specification defines media.json as the structured index for interviews, podcasts, press features, public media references and founder media appearances.

Useful Relationship:

Expert → Media Appearance → Topic → Publication → Organization

PRESS & BROADCAST

Validates external coverage citations to distinguish authenticated media presence from self-promotional blogging.

LONG-FORM INTELLECTUAL AUTHORITY

books.json - Structure Books and Major Publications

A book or major publication can establish deeper subject authority than a normal webpage. The registry can include: Title, Author, Publisher, ISBN where applicable, Publication date, Topic, Edition, Canonical information page, Purchase or reference page, Related frameworks.

ThatWare's internal architecture describes books.json as the structured index for books, major publications, long-form publications, reports and authored knowledge assets.

LONG-FORM KNOWLEDGE

Connects ISBN records, monograph citations, and authored books directly to subject-matter experts within the firm.

EDUCATIONAL KNOWLEDGE

courses.json - Structure Training and Educational Assets

Organizations often teach what they know through: Courses, Workshops, Training programs, Internal academies, Webinars, Educational modules.

A machine-readable course registry can establish: Course title, Instructor, Topic, Target audience, Curriculum, Prerequisites, Duration, Delivery format, Credential (if applicable), Canonical page.

ThatWare's internal model uses courses.json for training modules, workshops, courses and educational content connected to its areas of expertise.

CURRICULUM ARCHITECTURE

Maps instructional modules, syllabi, and technical training pathways to establish educational subject authority.

CREDENTIALS & PROFESSIONAL TRUST

certifications.json - Structure Verified Credentials

Credentials can relate to: Professionals, The organization, Technology competencies, Training, Industry standards.

The registry should make clear:

  • • Who holds the credential?
  • • Who issued it?
  • • What does it cover?
  • • When was it issued?
  • • Does it expire?
  • • Can it be verified?

ThatWare's internal schema defines this file around professional certifications, credentials, technical recognition and education-related trust records.

Important

Never create certification records based solely on marketing claims.

CREDENTIAL VERIFICATION

Documents institutional and technical certifications with verifiable issuer URLs and expiration metadata.

MASTER INNOVATION CATALOG

innovation-registry.json - Connect the Organization's Innovation Evidence

This file acts as the master map of the innovation and authority layer. ThatWare's internal design models it as a DataCatalog linking keynotes, copyrights, research, frameworks, awards, media, books, courses and certifications into a single innovation graph.

Why It Matters:

Without a central registry, machines discover these resources independently. With a registry, the organization exposes one coherent innovation evidence layer.

Conceptually
innovation-registry.json
• keynotes.json
• copyrights.json
• research.json
• frameworks.json
• awards.json
• media.json
• books.json
• courses.json
• certifications.json
DIRECT ANSWER KNOWLEDGE

faq.json - Turn Repeated Questions Into Structured Knowledge

FAQs are one of the clearest knowledge formats because they mirror how people interact with AI systems: Question → Answer. faq.json can organize: Questions, Answers, Categories, Topics, Intent, Source pages, Relevant services or products, Update dates.

Internal ThatWare research describes faq.json as a custom AI/GEO knowledge file rather than a Schema.org standard, intended to structure FAQs separately from webpage markup.

Important Distinction:

faq.json is not the same thing as Schema.org FAQ markup. It is a custom machine-readable knowledge asset within the ThatWare architecture.

Example faq.json 
{
  "question": "What is AI readiness?",
  "answer": "AI readiness describes how prepared...",
  "category": "AI Readiness",
  "sourceUrl": "https://example.com/ai-readiness/",
  "lastUpdated": "2026-10-12"
}
ANSWER RELATIONSHIPS

faq-knowledge-graph.json - Connect Questions to the Knowledge Behind Them

A flat FAQ list provides answers. A FAQ knowledge graph should go further. Structure this ThatWare AI custom file around relationships such as: Question → Topic → Entity → Product / Service → Supporting Source → Related Question → Evidence → Parent Category.

Simple distinction

faq.json stores answers. • faq-knowledge-graph.json explains how the answers connect.

This should be clearly labeled as a ThatWare AI custom architecture file, not a universal web standard.

Example faq-knowledge-graph.json 
{
  "questionId": "faq-001",
  "question": "What is AI readiness?",
  "about": [
    "AI Readiness",
    "Machine Readability"
  ],
  "relatedEntity": "Example Company",
  "source": "https://example.com/ai-readiness/",
  "relatedQuestions": [
    "faq-002",
    "faq-009"
  ]
}
CANONICAL ENTITY CONTROL

entity-registry.json - Create One Canonical Map of the Organization's Entities

This file is one of the most important parts of the Registry. It can contain: Organizations, Founders, Executives, Brands, Products, Services, Frameworks, Concepts, Locations, Aliases, Canonical URLs, First-published dates, Update dates, Related resources.

Internal ThatWare documentation defines entity-registry.json as the canonical entity map for frameworks, aliases, related entities, related resources, schema types, publication dates and canonical URLs, with specific use in disambiguation, entity confidence, alias control and retrieval alignment.

Why It Matters:

Without canonical entity control: "AVM", "AI Visibility Measurement", and "AI Visibility Metric" could accidentally be interpreted as three different concepts. A registry creates one canonical identity with controlled aliases.

Example entity-registry.json 
{
  "entityId": "framework-avm",
  "name": "AI Visibility Measurement",
  "aliases": [
    "AVM"
  ],
  "type": "Framework",
  "canonicalUrl": "https://example.com/avm/",
  "relatedEntities": [
    "organization-example"
  ]
}
PERSISTENT ORGANIZATIONAL MEMORY

brand-memory.json - Preserve What Machines Should Consistently Understand About the Brand

Websites evolve: pages disappear, navigation changes, products are renamed, leadership changes, research moves. Without a consolidated memory object, important organizational identity may have to be repeatedly inferred from scattered sources.

Internal ThatWare documentation defines brand-memory.json as a long-term machine-readable memory object consolidating identity, inventions, products, publications, expertise, philosophy, research, copyrights, books and major knowledge assets. It is explicitly described as a complement to, rather than a replacement for, the knowledge graph.

Critical Principle

Brand memory should preserve verified identity, not preserve outdated marketing claims forever.

Recommended Sections
  • Identity: Who is the organization?
  • History: How did it develop?
  • Expertise: What is it legitimately known for?
  • Innovations: Which concepts and frameworks did it create?
  • Products & Services: What does it currently provide?
  • Research: What knowledge has it produced?
  • Intellectual Property: What does it own?
  • Publications: What long-form knowledge assets exist?
  • Philosophy: What principles guide the organization?
  • Canonical Sources: Where can those facts be verified?
ONE ORGANIZATION MULTIPLE EVIDENCE LAYERS

How the Fourteen Files Work Together

At the center:

ORGANIZATION

Connected to:

Intellectual Authority
research.json frameworks.json books.json
Public Authority
keynotes.json media.json awards.json
Legal & Professional Evidence
copyrights.json certifications.json
Education
courses.json
Innovation Index
innovation-registry.json
Answer Knowledge
faq.json faq-knowledge-graph.json
Entity Control & Memory
entity-registry.json brand-memory.json
Unified Outcome

A retrievable map of what the organization knows, creates, proves and represents.

FROM CLAIM TO EVIDENCE

Follow One Claim Through the Registry

Imagine the website states: "Example Company developed Framework X."

A robust Registry should allow the claim to connect through:

Entity Registry

Framework X is defined as a canonical entity.

↓
Frameworks Registry

Its methodology and purpose are documented.

↓
Research Registry

Relevant supporting research is connected.

↓
Copyright Registry

Applicable protected assets are recorded where relevant.

↓
Keynotes / Media

Public discussions of the framework are linked.

↓
Brand Memory

Framework X remains part of the organization's consolidated innovation history.

↓
Innovation Registry

All evidence is connected within the wider innovation catalog.

Outcome
The claim becomes: Entity → Definition → Evidence → Provenance → Organizational Memory

instead of: Marketing statement → trust us.

DO NOT CONFUSE THE TWO

Knowledge Registry vs Knowledge Graph

Knowledge Registry

Stores structured records.

Examples:

  • • Research
  • • Awards
  • • Frameworks
  • • Books
  • • Entities

Simple distinction: The Registry tells you what exists.

Knowledge Graph

Represents relationships.

Examples:

  • • Organization created Framework
  • • Founder authored Book
  • • Research supports Methodology
  • • Award recognized Organization

Simple distinction: The Knowledge Graph tells you how it connects.

DEPLOYMENT

Keep Public Registry Files Stable and Predictable

A public implementation could use website-root paths such as:

example.com/
• keynotes.json
• copyrights.json
• research.json
• frameworks.json
• awards.json
• media.json
• books.json
• courses.json
• certifications.json
• innovation-registry.json
• faq.json
• faq-knowledge-graph.json
• entity-registry.json
• brand-memory.json

Internal ThatWare schema guidance recommends using absolute IDs and URLs, placing root files predictably, and connecting them back into higher-level discovery resources rather than leaving them isolated.

STRUCTURE MATTERS

Validation-Safe Architecture

Custom AI Files Should Not Break Standards-Based Markup. ThatWare's internal schema design follows an important distinction:

Raw Registry File:

Can contain operational fields needed by the application.

JSON-LD Representation:

Should remain compatible with valid Schema.org vocabulary.

Internal implementation guidance recommends using appropriate Schema.org types, absolute @id and url values, and additional Property/PropertyValue for custom AI-specific values instead of inventing invalid Schema.org properties.

Practical Rule
"Custom architecture is fine. Invalid structured data is not."
BEFORE DEPLOYMENT

Knowledge Registry Validation Checklist

Identity
□ Organization identity is consistent
□ People are correctly associated
□ Entity aliases are controlled
□ Canonical URLs are correct
Evidence
□ Awards are verifiable
□ Certifications are current
□ Media references exist
□ Research links resolve
□ Copyright claims are legitimate
Intellectual Property
□ Framework ownership is supported
□ Dates are accurate
□ Publications are correctly attributed
□ No third-party work is claimed improperly
FAQs
□ Answers match current website info
□ Source URLs are included
□ Unsupported answers are removed
□ Related entities are correct
Freshness
□ Former employees are updated
□ Discontinued frameworks/products handled
□ New research is indexed
□ Old URLs are replaced
Privacy & Security
□ No private customer information
□ No confidential research
□ No unpublished IP
□ No personal info without authorization
□ No internal-only documents
AVOID EVIDENCE POLLUTION

Common Knowledge Registry Mistakes

Inventing Authority

Do not create awards, citations, certifications or credentials that cannot be verified.

Treating Every Marketing Asset as Research

A sales page is not automatically a research publication.

Claiming Ownership Without Provenance

Framework and copyright registries require accurate ownership relationships.

Duplicating Entities

One concept should not become several disconnected entities simply because different abbreviations are used.

Keeping Outdated Brand Memory

Persistent memory should preserve truth, not obsolete positioning.

Publishing Private Knowledge

Not every piece of organizational knowledge belongs in a public machine-readable registry.

Confusing Custom Files With Standards

The Knowledge Registry is a ThatWare AI architecture. Do not imply that all AI systems universally recognize these files.

PRACTICAL PRIORITIZATION

Build the Registry Around the Evidence You Actually Have

Research-Driven Organization

Start with:

  • • research.json
  • • frameworks.json
  • • entity-registry.json
Founder-Led Expert Brand

Prioritize:

  • • keynotes.json
  • • media.json
  • • books.json
  • • brand-memory.json
Training Organization

Prioritize:

  • • courses.json
  • • certifications.json
  • • faq.json
IP-Heavy Organization

Prioritize:

  • • copyrights.json
  • • frameworks.json
  • • innovation-registry.json
Enterprise Brand

Build the complete connected registry.

Integrate all 14 files into one centralized, validated machine-readable knowledge ecosystem.

Important

Do not create empty files merely to claim a "complete" stack. A smaller registry containing verified evidence is better than a large registry filled with weak or artificial records.

ORGANIZATIONAL KNOWLEDGE CHANGES

A Registry Should Evolve With the Business

New Evidence Created

Research, award, course, keynote, publication or framework.

↓
Verify

Confirm ownership, dates, sources and entity relationships.

↓
Add to the Appropriate Registry

Update the relevant root file.

↓
Connect the Entity

Update entity-registry.json.

↓
Connect the Innovation Graph

Update innovation-registry.json where relevant.

↓
Update Memory

Add meaningful persistent knowledge to brand-memory.json.

↓
Validate

Check URLs, schema representations, relationships and timestamps.

↓
Deploy

Publish the reviewed version.

Outcome

New organizational knowledge becomes structured organizational knowledge.

ONE CONNECTED ARCHITECTURE

Registry → Intelligence → Visibility

FOUNDATION
Knowledge Registry

Stores:

Research, Frameworks, Media, Credentials, Entities, Memory.

REASONING
AI Intelligence Layer

Connects:

Retrieval, Context, Reasoning, Trust, Citations.

DEPLOYMENT
AI Stack

Creates:

Guidance, LLM context, Entity representation, Vector preparation, Semantic mapping.

ANALYTICS
AVM / VEM / GEO

Measures:

AI visibility, Entity clarity, Generative readiness, Authority gaps.

Result: The platform moves from

What do we know? → to → How is it structured? → to → How can it be retrieved? → to → Is AI actually understanding and surfacing it?

IMPORTANT LIMITATION

Structured Evidence Is Not Guaranteed AI Authority

A Knowledge Registry does not guarantee:

× AI citations
× Recommendations
× Rankings
× Knowledge Panels
× LLM memorization
× Training inclusion
× Press coverage

External systems decide independently what they: Retrieve, Believe, Cite, Rank, Summarize, and Recommend.

The Registry's Job: Make legitimate organizational knowledge:

Clearer Connected Traceable Current Retrievable
Our Principle
"Structure the evidence. Do not manufacture the authority."
TURN ORGANIZATIONAL PROOF INTO STRUCTURED KNOWLEDGE

Your Authority Already Exists. Give It a Machine-Readable Structure.

Your research, expertise, frameworks, publications, media, credentials and intellectual property should not remain scattered across disconnected pages. The Knowledge Registry helps connect: What you know, What you created, What you own, What proves your expertise, Which entities define your organization, and What intelligent systems should consistently understand about your brand.

Explore the Knowledge Registry → Explore the Intelligence Layer →

Supporting line: Structure the evidence. Connect the entities. Preserve the knowledge.

FAQS

Frequently Asked Questions

It is a collection of machine-readable files designed to organize organizational research, frameworks, intellectual property, media, awards, publications, training, credentials, FAQs, entities and persistent brand knowledge.

It is a deeper complementary architecture. The AI Stack creates foundational machine-readable website assets, while the Knowledge Registry structures organizational evidence and long-term knowledge.

No. Most Knowledge Registry files are ThatWare AI architecture assets. They should not be described as universally supported standards.

It acts as the master catalog connecting the organization's innovation and authority evidence files. Internal ThatWare architecture explicitly models it as a DataCatalog.

It is a persistent organizational-memory object intended to consolidate verified identity, expertise, products, innovations, research and other important knowledge so that the organization's identity does not need to be inferred repeatedly from scattered pages.

It is the canonical entity record used to manage names, aliases, relationships, dates and authoritative references for organizational entities.

faq.json is a custom machine-readable knowledge file. Schema.org FAQ markup is standards-based structured data embedded in or associated with webpages. They serve different purposes.

No. The Registry should reflect real organizational assets. Empty or fabricated registries provide no meaningful benefit.

Public Registry files should contain only information approved for public machine-readable exposure. Confidential or restricted knowledge should stay within controlled systems.

Whenever relevant organizational facts change or new verified evidence is created.