The Verified Entity Truth Pack

Chapter Boundary

The first twelve chapters established the experimental chain: a single response is not a GEO score; representation is a distribution across users and AI products; the audited entity must be resolved before results are observed; official representation and evidence-based entity reality must remain separate; the target population, sample, countries and languages must be defined; participants must be selected independently of outcomes; each AI-product instance must be linked to a register with all material configurations; prompts must preserve the same intent across languages; Controlled and Natural User Panels must remain separate; and every observation must be preserved within a synchronised wave and the NOMOS Capture evidence chain. The audit must now answer its central question:

According to which reference record will we determine whether the captured AI response is correct, incorrect, incomplete, outdated, unsupported, or beyond scope?

Section 4 conceptually established two separate layers of reality:

• Official Representation Layer showing what the entity itself says about itself
• Verified Entity Reality Layer showing to what extent the existing evidence allows which statements

This section transforms the second layer into an operational audit object. The name of this object is:

Verified Entity Truth Pack

Canonical English term:

Verified Entity Truth Pack

This operational object completes the third link in the architecture of the first two books: the GEO Framework defines the standard; 99 Errors in GEO identifies its modes of violation; and the audit system measures and substantiates those violations. Every auditable control must carry the model or product, date, country, language, query set, repetition count and measurement record. Within that chain, the Truth Pack is:

“What did AI say?”

with the question:

“What evidence allowed it to say this?”

is the reference system between. This section:

• what Truth Pack is and is not,
• how claims are transformed into atomic reality records,
• the types of sources and evidence,
• the roles of first-party, official, independent, operational, and user resources,
• counter-evidence,
• source lineage and illusion of independence,
• sufficiency of evidence,
• time, country, and scope limits,
• open world and closed world claims,
• the distinction between "no evidence found" and "proven false",
• quantitative performance, customer, partner, licence, certificate, and superiority claims,
• versioning and pre-wave locking of Truth Pack,
• public and restricted evidence layers,
• objection, correction, and dissent processes,
• machine-readable Truth Pack

defines. This chapter does not yet:

• all the adjudication details of dividing AI responses into atomic claims,
• inter-rater agreement,
• response transition threshold,
• critical error gates,
• does not finalise the ultimate NOMOS score formulas

does not finalise. These are the subjects of the following sections. The key question of Chapter 13 is:

How to create a Truth Pack about an entity that will evaluate AI responses, locked before the outcome, carrying both evidence and counter-evidence together, with clear time and scope limits?

NOMOS Challenge

The sentence on your company's website is: “We operate in 25 countries.” The AI product tells the same sentence to the user: “The company operates in 25 countries.” Did the AI correctly convey the official site? Yes. Has the claim actually been verified? We don't know yet. The company sends you a table.

The table contains the names of 25 countries. However, the columns are not explained: Some have only website visitors. Some have former customers. Some have independent distributors. Some have one-time events organised. In nine countries, there is actually active service delivery. Only in three countries is there a local legal entity.

What does 'to operate' mean? Does it mean having a customer? Setting up a local company? Being able to provide services remotely? Delivery through a partner? Or a website being accessible from that country? The subject, verb, and scope of the claim are not defined.

Therefore, although there is a number, there is not yet verifiable reality. Now consider another claim: '98% of our projects are successful.' You have 49 successful project presentations. There are no failed project files. How many projects were completed in total? By what criteria is success defined? On-time delivery? Customer acceptance?

Commercial result? Technical feasibility? Customer satisfaction? What is the period? The last three months? The entire history of the company? Only selected projects? Without knowing the denominator, 98 per cent cannot be proven. Now there is this sentence on another company's website: "We are the world leader." This sentence is repeated by:

• company blog,
• company press release,
• twenty news sites copying the same press release,
• five fake user accounts opened by the company,
• three AI-generated texts summarising these contents

. There are thirty different URLs. Are there thirty independent proofs? No. A single self-declaration may have echoed on many derivative surfaces.

This is precisely the manipulation identified in the preceding volume: hidden text, fabricated users and self-authored comments published across different domains are fed back into the system as though they were independent evidence. Now consider the opposite case. The company's official website states, ‘We provide services only in Türkiye.’

Yet the company began a verified operation in Germany two months ago. Contracts, invoices and official records support that fact, although the website has not been updated. The AI responds: ‘The company provides services in Türkiye and Germany.’ The response departs from the official website, but it may be closer to material reality.

Now consider an even more sensitive situation. On a healthcare institution's website: “Licensed centre.” is written. In the registry, another institution with a similar name has a licence. AI merges the two entities and assigns the licence to the wrong institution. The company notices this mistake but does not correct it because it is in their favour.

The explicit provision of the second book applies here: A mistake that is in one’s favour is still a mistake. To evaluate an AI response, we need not only a list of correct sentences but also the following structure: Whose statement is it about? What exactly is the claim? In which time period is it valid? In which country? For which product or service?

Does the source really support the claim? Who controls the source? Do other sources say the same thing, or are they copying the same original source? Is there counter-evidence? Is the claim only an official self-declaration? Is the evidence public or private?

At the time of AI’s measurement, was there a possibility to access this evidence? Is the result certain, limited, controversial, or unknown? The first ruling of this section is:

A source alone is not reality.

Its second provision states:

A claim cannot be verified without defining its subject, scope, time, and burden of evidence.

Its third provision states:

Different URLs do not mean different independent evidence.

Its fourth provision states:

The absence of evidence is not automatic proof that the claim is false.

Its fifth provision states:

Verified reality is not an absolute and unchangeable truth; it is an inferred judgement carried by the available evidence within a specific time and context.

Its sixth provision states:

Truth Pack cannot be written based on the AI answer. The AI answer is evaluated against the previously locked Truth Pack.

1. PURPOSE OF THE CHAPTER

The purpose of this section is to transform material claims about the audited entity into a reference package that is linked with evidence and counter-evidence, with clear boundaries of time and scope, without converting them into an answer template. The section normalises the following distinctions:

• Official claim versus verified reality
• Source versus evidence
• Evidence versus claim support
• First-party record versus independent verification
• Independent source and source authorised on the subject
• Different domain name and different root of evidence
• Number of sources and independent family of evidence
• Direct evidence and derived evidence
• Supporting evidence and counter evidence
• Absence of claim and falsity of the claim
• Open world claim and closed world record
• Current reality and historical reality
• Time when reality is valid and time when the source was published
• Public evidence and restricted evidence
• Evidence accessible to AI and evidence only open to the auditor
• Proven claim and publicly discoverable claim
• Direct reality and calculated derived result
• Raw data and performance ratio
• Numerator and denominator
• Customer and potential customer
• Partner and customer
• Membership and accreditation
• Licence and brand relationship
• Certificate and overall institutional compliance
• Claim and opinion
• Opinion and comparative advantage
• Complaint and verified violation
• Investigation and definite crime or liability
• Outdated record and incorrect historical record
• Incorrect AI response with missing Truth Pack
• Reference fault and system fault
• Truth Pack integrity and all claims being positive
• Confidentiality of evidence and absence of evidence
• Entity's right to respond and self-verification
• Human approval and human infallibility
• AI assistance and AI being the ultimate authority of truth

At the end of this section, each audit should be able to answer these questions:

Which material claims are contained within Truth Pack?

Which entity, country, product, and time does each claim belong to?

Which evidence supports it, which limits or refutes it?

Are the sources truly independent, or are they derived from the same original source?

Can the claim be publicly verified?

Is the evidence only available under restricted auditor access?

Could AI have accessed this evidence at the time of measurement?

Is the claim certain, partial, historical, controversial, or unknown?

Was Truth Pack locked before AI responses were seen?

2. CENTRAL NORMATIVE PROVISION

Each GEO-1000 audit must lock the material reference claims about the audited entity, along with supporting evidence, counter-evidence, source lineage, access class, scope, jurisdiction, validity period, and uncertainty status, in a versioned Verified Entity Truth Pack before AI responses are evaluated semantically. Truth Pack:

• the entity's self-written introductory file,
• a sales presentation collecting only positive evidence,
• the auditor's opinion text,
• the ideal response requested from AI,
• the absolute reality about the whole world,
• a reference repository consisting only of a list of URLs

it is not. Truth Pack:

It is an audit reference package that shows under which evidence material claims in AI responses can be supported, limited, refuted, or left unknown.

3. LIMIT OF THE WORD “TRUTH”

The word “truth” in Truth Pack does not carry the claim: “This package knows all absolute truths about the entity.” The more accurate meaning is:

A reality record dependent on evidence showing, within the specified date, scope, and body of evidence, to what extent which material judgements are supported.

Truth Pack:

• subject to change with new evidence,
• can be contested,
• its scope can be narrowed,
• it can be corrected if proven wrong,

it can leave some claims unknown. The authority of Truth Pack:

• The word “Truth” does not arise from,
• the name NobleJackal,
• the voice of NOMOS,
• the author of the book

It arises from the following:

• a clear claim structure,
• appropriate evidence,
• counter-evidence,
• lineage of sources,
• time,
• boundary,
• is meaningful with
• independent review,

accountable human responsibility.

4. WHAT IS VERIFIED ENTITY TRUTH PACK?

Verified Entity Truth Pack is a versioned audit package that brings together the material factual records of a specific entity within a specific date and scope, the supporting and opposing evidence related to them, source statuses, and unresolved areas. Candidate representation:

VETP_{E,v,t} = (I, C, O, E⁺, E⁻, L, S, T, U, G)

Here:

• E: audited entity
• v: version of Truth Pack
• t: reference date
• I: entity identity and relationship graph
• C: atomic reference claims
• O: Official Representation Record
• E⁺: supporting evidence
• E⁻: opposing evidence and constraining records
• L: source lineage and independence graph
• S: scope, country, and jurisdiction matrix
• T: time and currency records
• U: unknowns, discrepancies, and reference gaps
• G: governance, version, objection, and approval records

Each component of Truth Pack can be versioned separately. The main package version links the component versions together.

5. TRUTH PACK IS NOT A RESPONSE TEMPLATE

Truth Pack is not a text that AI must say word for word. For example, Truth Pack may contain the following reference claim: “Asteron Holdings Ltd. is the owner of the Asteron Travel brand.” AI can correctly phrase it in these forms:

• "The Asteron Travel brand belongs to Asteron Holdings."
• “Asteron Holdings is the owner of the Asteron Travel brand.”
• “Asteron Travel is a brand owned by Asteron Holdings.”

The material relationship is preserved. The arbiter should not look for word equality. Truth Pack:

defines the correct expression field

It does not impose a single correct sentence.

6. TRUTH PACK IS NOT AN ENTITY BIOGRAPHY

There can be an infinite amount of correct information about an entity. GEO-1000 Truth Pack is not required to collect all information. The package should primarily cover these areas:

• Material duties within the prompt Registry
• The identity and operational core of the entity
• Limits that will change the user's decision
• Licences, legal, price, service, country and time records
• Eligibility and exclusion criteria required for advice
• Material claims carrying the risk of a critical error
• Differences between reality verified by official representation and actual reality

To this principle:

Principle of Reality Proportional to Duty

is called. Collecting unnecessary data:

• privacy,
• cost,
• currency,
• contradiction

can increase the risk.

7. TWELVE CORE COMPONENTS OF THE TRUTH PACK

7.1. Canonical Entity Identity

As defined in Section 3:

• entity identity,
• type,
• legal name,
• trademark and domain name relations,
• parent and subsidiary companies,
• time and jurisdiction limits

are packaged.

7.2. Reference Claim Ledger

Carries all material reality claims to be used in the audit in an atomic structure.

7.3. Official Representation Record

Carries the current and historical statements published by the entity itself on canonical surfaces.

7.4. Evidence Registry

For each evidence object:

• source,
• integrity,
• authority,
• access,
• scope,
• time

is recorded.

7.5. Counter-Evidence Registry

The claim:

• refuting,
• limiting,
• altering its currency,
• providing another explanation

contains records.

7.6. Source Lineage Graph

Of the sources:

• the first root,
• copies,
• quotations,
• syndication,
• AI derivatives

are shown.

7.7. Scope and Jurisdiction Matrix

The claim:

• for which country,
• product,
• service,
• user,
• legal entity

is valid.

7.8. Time and Currency Matrix

The claim:

• when it started,
• when it ended,
• when it was last verified,
• which event could change it

are shown.

7.9. Dispute and Uncertainty Ledger

Makes visible areas that are contradictory, unsolvable, or insufficiently evidenced.

7.10. Evidence Access Layer

The evidence:

• is public,
• audit-accessible,
• restricted,
• confidential,
• derived

as indicated.

7.11. Change and Objection Log

Carries new evidence, corrections, counter opinions, and decision changes in a versioned manner.

7.12. Machine Manifest

Connects all components:

• identity,
• is meaningful with
• hash,
• relationship

to each other.

8. ATOMIC REFERENCE CLAIM

The basic unit of reality within Truth Pack:

is called Atomic Reference Claim.

Candidate structure:

C_j = (s, p, o, q, c, l, v_f, v_t, k, m)

Here:

• s: subject entity
• p: predicate or relation
• o: object or value
• q: qualifiers and limits
• c: country or jurisdiction
• l: language or locale, if material
• vf: validity start
• vt: validity end
• k: assertion type
• m: materiality or risk label

Example: Subject: Asteron Türkiye Tourism Ltd. / Predicate: provides services / Object: corporate travel management / Country: Turkey / Customer type: corporate clients / Start: January 1, 2026 / Last verification: August 18, 2026 This sentence is not atomic enough: “Asteron is a leading company providing numerous services worldwide.” In this single sentence:

• geographical scope,
• number of services,
• leadership,
• company identity

are mixed together.

9. CLAIM TYPE

Each atomic claim should carry a type.

CT-01 — Identity Claim

Who the entity is or which entity it belongs to.

CT-02 — Relationship Claim

Ownership, control, partnership, clientship, employment or membership relationship.

CT-03 — Activity and Service Claim

What the entity does, what service it provides.

CT-04 — Product Claim

Product feature, version, owner, or availability.

CT-05 — Geographical Scope Claim

Country, region, or service area.

CT-06 — Legal and Licensing Claim

Registration, authority, licence, regulatory status.

CT-07 — Price and Commercial Term Claim

Price, tax, subscription, refund, warranty, or payment.

CT-08 — Quantitative Performance Claim

Success rate, delivery time, number of users, growth or efficiency.

CT-09 — Customer and Partner Claim

Customer, sponsor, partner, distributor or supplier relationship.

CT-10 — Certificate and Award Claim

Certificate, membership, award or accreditation.

CT-11 — Comparative or Superiority Claim

Best, leading, faster, most reliable, number one.

CT-12 — Recommendation and Suitability Claim

Suitability or recommendation for a specific user.

CT-13 — Historical Claim

Organisation, past ownership, former product or historical event.

CT-14 — Risk, Complaint or Dispute Claim

Complaint, investigation, court, sanction or argument.

CT-15 — Opinion or Institutional Position

Opinion, vision or value judgement advanced about the entity itself. The type of claim determines which evidence is considered sufficient.

10. CLAIM MATERIALITY

Not every correct piece of information within Truth Pack has the same impact on a decision. Materiality can be indicated as a candidate with the following classes:

CRITICAL-CANDIDATE

MAJOR-CANDIDATE

MODERATE

ADVISORY

CONTEXTUAL

The exact error severity level will be determined in Section 15. The label in Truth Pack only:

• manages evidence priority,
• review attention,
• update frequency

manages.

11. EVIDENCE OBJECT

Each source within Truth Pack must be recorded as an Evidence Object, not just as a link. Candidate structure:

E_k = (r, a, i, p, f, s, t, x, g, h)

Here:

• r: source role
• a: authority for claim
• i: independence
• p: proximity to claim
• f: recency
• s: scope
• t: time
• x: access class
• g: source lineage
• h: integrity record

A URL alone does not complete any of these fields.

12. EVIDENCE–CLAIM RELATIONSHIP

Not every evidence object supports every claim. The relationship between claim Cj and evidence Ek can be one of the following statuses:

SUPPORTS

PARTIALLY_SUPPORTS

QUALIFIES

CONTRADICTS

OUTDATES

CONTEXTUALISES

NO_MATERIAL_BEARING

UNKNOWN_RELATION

Example: A company's trademark registration document: may support brand ownership, does not support customer satisfaction. A customer review: may support the experience of a single user, does not support 98% success across all customers.

13. RESOURCE ROLES

SR-01 — Canonical First-Party Source

The official surface controlled by the entity. Example:

• Canonical web page
• Official policy
• Pricing page
• Product document

SR-02 — First-Party Operational Record

Records at the internal or transaction level of the entity. Example:

• Invoice
• Contract
• Transaction record
• Delivery record
• Raw performance data

SR-03 — Authorised Official Registration

It is the registry that carries legal or institutional authority on the subject. Example:

• Company Registry
• Licence Registry
• Certificate issuing institution
• Court decision
• Regulatory registration

SR-04 — Two-Way Verification

It is the support of the relationship by both parties or by contract. Example:

• Customer relationship
• Partnership
• Sponsorship
• Distributorship

SR-05 — Independent Editorial Source

It is a publication or research editorially independent from the entity. Independence is not a guarantee of accuracy.

SR-06 — Independent Audit or Research

It is an open external evaluation of its method and scope.

SR-07 — Transactional or Behavioural Evidence

Records showing actual transactions or user behaviour.

SR-08 — User-Generated Evidence

Comment, complaint, review, or user document. It is an individual experience.

SR-09 — Derived Calculation

Rate, classification, or summary produced from raw records. Its formula and inputs must exist.

SR-10 — Synthetic Evidence

This data has been created for method demonstration purposes. It cannot prove the claim of a real entity.

SR-11 — AI-Generated Derivative Source

Content created by an AI system by summarising other sources. It does not replace the original sources.

SR-12 — Unknown or Unresolvable Source

The source has not been verified or its origin cannot be determined. It carries limited trust in primary material verification.

14. THE AUTHORITY OF THE SOURCE DEPENDS ON THE TYPE OF CLAIM

There is no universal and single ranking for all sources. Example: For the current public price of the company:

• canonical price page,
• actual checkout,
• current offer

can be a strong source. For the company's claim: “We are the world leader.”, the same web page only shows a self-declaration. It does not prove leadership. For the licence: the institution granting the licence is more authoritative than the company's blog. For customer experience: a single customer review is a real, singular event and does not represent the entire user population. Therefore:

The quality of the source is not general; the claim is specific.

15. SEVEN DIMENSIONS OF SOURCE PROFILE

Each source should be evaluated along these dimensions:

15.1. Authority

Is the source authorised to make a judgement about the type of claim?

15.2. Proximity

How close is the source to the event, process, or record?

15.3. Independence

How independent is the source from the commercial or institutional owner of the claim?

15.4. Integrity

Is the authenticity of the file or record and its change history preserved?

15.5. Timeliness

Is the source valid for the relevant time?

15.6. Scope

Does the source support the full scope of the claim, or only a part of it?

15.7. Reproducibility

Can another auditor reach the same judgement from the same record? These dimensions should not necessarily be reduced to a single "source score." A source:

• highly authoritative,
• low independence

possible. Another source:

• highly independent,
• distant from the subject

may be.

16. THE CORRECT ROLE OF THE FIRST-PARTY SOURCE

First-party source: it is not automatically worthless, nor is it automatically independent evidence. First-party sources can be strong for claims such as:

• Price published by the institution
• Support hours
• Description of its own product and service
• Text of its own policy
• Official statements disclosed to the public
• Its own transaction data

It may not be sufficient alone for claims such as:

• World leadership
• Highest satisfaction
• Superiority over competitors
• Universal success
• Independent accreditation
• Business outcomes for all customers

In the previous '99 Errors' text: 'Your own site is a claim; not proof.' warning is of central importance for claims that particularly require superiority and independence. A more complete normative statement is as follows:

Your own site is proof of what the organisation says; it is not automatic proof of the independent correctness of any claim regarding the outside world.

17. WHAT IS INDEPENDENCE?

Having a resource on different domain names does not make it independent. Independence is related to the following areas: Who produced the content? Who decided to publish it? Is there a payment or sponsorship? Did the source get text directly from the company? Did the publication perform its own verification? Is the content copied from another source? Does the source have ownership or business relations with the company? Ten pieces of content published by an agency on different domain names are not ten independent sources.

18. SOURCE LINEAGE

Evidence objects should be linked to a source lineage. Candidate graph:

G_S = (V_S, E_S) [K10]

Here:

• V_S: source objects
• E_S: citation, copying, syndication, summarisation, and derivation relationships

Source relationships:

ORIGINAL_SOURCE

QUOTES

SYNDICATES

SUMMARISES

TRANSLATES

DERIVES_FROM

AI_GENERATED_FROM

UNKNOWN_LINEAGE

can be recorded as.

19. INDEPENDENT EVIDENCE FAMILY

Contents originating from the same root source can be considered as a single Evidence Family. Example:

• Company press release
• News site that publishes the press release verbatim
• Blog summarising the news site
• AI text summarising the blog

There are four URLs. There may not even be a single independent evidence family. The number of sources and the number of evidence families should be reported together.

20. EVIDENCE LAUNDERING

Republishing a self-statement on other domains and then using it as independent evidence:

Is called Evidence Laundering

Example chain: The company says "we are leaders" on its own site. Paid content publishes this as "news." Other sites copy the news. Since AI has seen many domains, it accepts the claim as widespread. The company uses the AI's response as evidence of its own claim. This closed loop:

self-statement → derived source → AI response → republication of self-statement

creates. It should make this loop visible by establishing the Truth Pack source lineage.

21. LIMITATION OF AI-GENERATED SOURCE

An AI system:

• can summarise sources,
• can compare claims,

can generate new text. AI text:

• is not an original source,
• cannot replace the underlying evidence,

does not become independent verification just because another AI says the same thing. AI output can be used for the purposes of:

• directing research,
• claim extraction,
• conflict detection,

assistance in finding sources. The ultimate evidence object should be connected to the original source as much as possible.

22. LIMITATION OF SYNTHETIC EVIDENCE

Synthetic data:

• method demonstration,
• system testing,
• software verification,
• adjudicator training

can be used for. Synthetic data:

• the actual number of customers,
• the actual performance rate,
• the actual country coverage,
• the actual licence

cannot prove. Even if synthetic records are in the same file as real evidence, they must be clearly labelled.

23. SUPPORTING EVIDENCE IS INSUFFICIENT

Truth Pack should only collect sources that support the claim. For material claims, the following records should be actively sought:

• Conflicting date
• Different scope
• Expired document
• Failed transaction
• Complaint or return
• Previous ownership
• Licence belonging to another entity
• Correction or withdrawal
• Comparative data
• Missing denominator

This obligation is called:

Burden of counter-evidence

It applies whenever material counter-evidence exists.

24. COUNTER-EVIDENCE

Counter-evidence does not always completely refute the claim. It can serve one of the following functions:

CONTRADICTS

LIMITS_SCOPE

LIMITS_TIME

IDENTIFIES_EXCEPTION

CHALLENGES_METHOD

QUESTIONS_AUTHENTICITY

PROVIDES_ALTERNATIVE_ENTITY

REQUIRES_ADDITIONAL_REVIEW

Example: A negative review of the claim “All customers are satisfied” may not automatically refute the entire claim. However, it can show that the term “all” is incorrect.

25. STORAGE OF COUNTER-EVIDENCE

Record that weakens the claim:

• not in favour of the company,
• appears low quality,
• cannot be quietly deleted because its disclosure to the public would cause discomfort

Low-confidence counter-evidence can also be recorded. Its status is clearly indicated. The adjudicator gives it appropriate weight.

26. CLAIM SUPPORT STATUSES

VS-0 — NOT ASSESSED

The claim has not yet been evaluated.

VS-1 — OFFICIAL CLAIM ONLY

The claim is based only on an official self-declaration. It has not been proven false. No additional verification exists.

VS-2 — TRACEABLE FIRST-PARTY SUPPORT

The claim is supported by a traceable first-party operation or transaction record.

VS-3 — CORROBORATED

The claim is supported by multiple appropriate pieces of evidence. Not all sources need to be independent.

VS-4 — INDEPENDENTLY VERIFIED

The claim has been verified with an independent or authoritative external source appropriate to the topic.

VS-5 — MULTI-SOURCE SUSTAINED

The claim is strongly supported across different types and families of sources, in scope and over time.

VS-C — CONTRADICTED

Stronger or more appropriate evidence contradicts the claim.

VS-U — UNRESOLVED

The evidence is insufficient, contradictory, or at a level where no decision can be made.

VS-W — WITHDRAWN

The claimant has withdrawn the claim. The historical record is preserved.

VS-R — RESTRICTEDLY VERIFIED

The claim is supported by evidence restricted to auditor access. Public verification is not possible. This status also affects whether it can be expected that AI produces the claim from public sources.

27. SUPPORT STATUS ALONE IS NOT SUFFICIENT

A claim at the same time:

• supported,
• only for a specific country,
• only for a specific date range,
• with evidence not publicly available,
• under opposing views

It is possible. Therefore, instead of a single status, a multidimensional Reality Status Vector can be used:

V_j = (support, scope, time, conflict, access)

Example:

VS-4 + SCOPE-LIMITED + CURRENT + NO-CONFLICT + PUBLIC

is another result.

VS-R + GLOBAL-CLAIM + TIME-LIMITED + DISPUTED + RESTRICTED

is another result.

28. SCOPE STATUSES

SC-0 — SCOPE UNKNOWN

The scope to which the claim applies cannot be determined.

SC-1 — EXACT SCOPE

The claim and evidence carry the same entity, product, country, and user scope.

SC-2 — PARTIAL SCOPE

Evidence supports only part of the claim.

SC-3 — OVERBROAD CLAIM

The claim is broader than what the evidence supports.

SC-4 — WRONG ENTITY SCOPE

The evidence belongs to another entity or affiliate.

SC-5 — WRONG JURISDICTION

The evidence belongs to another country or legal area.

SC-6 — WRONG PRODUCT OR SERVICE

The evidence belongs to a different product or service.

29. TIME STATUTES

TS-0 — TIME UNKNOWN

The validity period of the claim is unknown.

TS-1 — CURRENT

It is supported that it is valid on the reference date.

TS-2 — HISTORICAL

It is supported for a specific past period.

TS-3 — EXPIRED

The validity of the document or claim has expired.

TS-4 — SUPERSEDED

It has been replaced by a newer record.

TS-5 — EVENT-DEPENDENT

It is valid as long as an event or condition continues.

TS-6 — FUTURE OR PLANNED

It is a plan or commitment that has not yet occurred. It cannot be presented as current reality.

30. FOURTH TIMESTAMP

Each piece of evidence and claim should carry four distinct times to the extent that it is relevant:

30.1. Time When Reality Is Valid

When was a claim ever true in the world?

30.2. Time When the Source Was Published

When was the information presented to the public or the auditor?

30.3. The Time When the Source is Captured

When was the audit evidence recorded?

30.4. Time of Adjudication of the Claim

When was the status of reality given? This distinction is important. A licence may have been cancelled at 10:00. The record may have been updated at 15:00. The AI response may have been given at 12:00. Response:

• old in terms of world reality,
• understandable in terms of publicly accessible evidence

Truth Pack should distinguish between the two cases.

31. PUBLIC ACCESSIBILITY OF EVIDENCE

Evidence access classes:

EA-1 — PUBLIC

Publicly available and auditable.

EA-2 — PUBLIC BUT TECHNICALLY LIMITED

Public but:

• access,
• geography,
• format,
• technical access

has limitations.

EA-3 — AUDIT ACCESS

Can be made available in a controlled manner to independent auditors.

EA-4 — RESTRICTED CONFIDENTIAL

The contract is restricted due to personal data or trade secrets.

EA-5 — DERIVED PUBLIC SUMMARY

Raw evidence is confidential. Its method and summary are public.

EA-6 — UNAVAILABLE OR LOST

It is claimed that the evidence exists, but it could not be accessed during the audit.

32. PUBLICLY AVAILABLE AUTHENTICITY AND RESTRICTED AUTHENTICITY

A company can confirm the claim “X is our customer.” with a private contract. The contract may not be disclosed to the public. Truth Pack can record the claim as: VS-R — Restrictedly Verified. However, it cannot be expected that a public AI product knows this relationship. Therefore, there are two separate questions: Is the claim true? Is the claim publicly discoverable? A claim may be true with private evidence. For public GEO success, again:

• is public,
• it may need to be verified,
• appropriate for the user

a record may be required.

33. PUBLIC DISCOVERABILITY

For each material claim, the following field may be recorded as a candidate:

PUBLICLY_DISCOVERABLE

PUBLIC_BUT_OBSCURE

PUBLICLY_CONFLICTED

RESTRICTED_ONLY

NOT_PUBLIC

UNKNOWN

The reality of the AI response and access to information can be evaluated separately afterwards.

34. TRUE BUT NOT PUBLIC CLAIM

If an AI product correctly states information that is not public, the following questions arise: Is the information available in another public source? Did the AI use personalisation or a private knowledge base? Is the answer correct by chance? Is there a leak of confidential or secret information? Was the claim verified only after the fact? Truth Pack should record the source path separately, without counting being correct alone as an achievement.

35. OPEN WORLD AND CLOSED WORLD CLAIMS

The absence of information in a record depends on the type of claim.

35.1. Open World Assumption

The entirety of the recorded universe is unknown. Example:

• All customers
• Business relations in all countries
• All user complaints
• All media publications

The absence of a record does not prove that the assertion is false.

35.2. Closed World Assumption

It can be assumed that the authorised and comprehensive registry fully covers the relevant universe. Example:

• List of active licences on a specific date
• Official company registration status
• Valid certificates of a specific certifying institution
• If the published product catalogue is truly complementary

In this case, the absence of a record could be a stronger negative evidence.

36. CLOSED WORLD AUTHORITY STATEMENT

If a source is to be used as a closed world record, the following fields must be defined: Which universe does it cover? For which date? What is the update frequency? Could the record be missing? Is there an archive and change log? Who is the authorised institution? Simply being the “official website” does not provide closed world authority.

37. DISTINCTION BETWEEN NOT FOUND EVIDENCE AND ERROR

The following three sentences are different:

• "No evidence was found for the claim."
• "The claim is not supported by the available evidence."
• “The claim contradicts stronger evidence.”

The first may be the result of research. The second is the status of verification. The third is a material contradiction. These are not the same:

NOT FOUND

UNVERIFIED

CONTRADICTED

38. ABSENCE OF EVIDENCE

To establish the falsity of a claim based on absence, the following questions must be answered: Is the record universe being searched comprehensive? Were the correct entities and name variants searched? Were the correct date and country used? Could the record be updated with a delay? Is another legal entity or trademark being used? Is there an access issue? Without these conditions: a definitive ruling such as 'Not found in the registry, therefore no licence exists.' cannot be made. A more accurate result could be: 'Could not be verified in the specified registry and date.'

39. CLAIM–EVIDENCE MATRIX

This table is not a universal and unchangeable source ranking. It shows which type of claim carries which burden of proof.

40. QUANTITATIVE CLAIM

A quantitative claim cannot be verified without the following fields:

• Measured item
• Numerator
• Denominator
• Period
• Inclusion rule
• Exclusion rule
• Data source
• Missing records
• Unique unit
• Calculation formula
• Rounding
• Update date
• Responsible person

Example: “98 per cent success.” alone is not a quantitative claim. It is an undefined marketing number.

41. NUMERATOR AND DENOMINATOR

Success rate:

R = S/N

let it be. Here:

• S: units considered successful
• N: all eligible units evaluated

must be. If failed or incomplete projects are removed from the denominator, the ratio changes. The denominator cannot be selected after the result.

42. UNIQUE UNIT

The following expressions are different from each other:

• 100 customers
• 100 projects
• 100 invoices
• 100 contracts
• 100 user accounts
• 100 transactions

The same customer may have done ten projects. “100 projects” is not “100 customers.” Truth Pack must explicitly record the unit of the number.

43. CUMULATIVE AND ACTIVE NUMBER

"We have 500 customers." may carry one of the following meanings:

• 500 unique customers in the company's history
• 500 customers in the last year
• 500 active customers currently
• 500 contact records
• 500 accounts
• 500 projects

These meanings are not the same.

44. DERIVED CLAIM

A claim may not be directly written in the document. It can be calculated from raw data. Example: “The average delivery time is 12 days.” This result:

• which projects are included,
• the definition of start and end,
• failed projects,
• median and extreme values

requires. The derived claim must include the following areas:

• Input data identifiers
• Formula
• Code or calculation method
• Version
• Reproduction record

45. PERFORMANCE CLAIM

The performance claim should answer these questions: Whose performance is the result? Which product or service? Which user or project type? What is the baseline? What is the success criterion? What is the period? How many unsuccessful results are there? Is it a selected case or the entire population? Is there independent verification? Is the result causal or merely relational? A case study: can show a possible result. Does not show the expected result in all customers.

46. WARRANTY CLAIM

The statement “Guaranteed results.” requires the following areas: Exactly what is guaranteed? Delivery or business outcome? What is the timeframe? What are the exceptions? What is the refund or compensation? Are there third parties outside of control? Is AI advice or ranking guaranteed? A company:

• can guarantee its own workflow,
• specific delivery

It cannot absolutely guarantee the future advisory behaviour of an AI product it does not control.

47. CUSTOMER CLAIM

Displaying the logo of an organisation on a website does not automatically prove a customer relationship. The logo may represent one of the following relationships:

• Customer
• Former customer
• Potential customer
• Event participant
• Sponsor
• Partner
• Supplier
• Technology user
• Group company
• Unauthorised logo usage

Truth Pack must clearly define the type of relationship.

48. CUSTOMER CONFIDENTIALITY

The customer relationship may be verified by contract but may not be disclosed publicly. Correct record: VS-R — Restrictedly Verified may be. If the company cannot publicly say, "X is our customer," the AI is not expected to know this relationship. The number of confidential customers cannot be silently converted to public GEO authority.

49. PARTNERSHIP CLAIM

The word "Partner" alone is not sufficient. The relationship must include the following areas:

• Type of partnership
• Product or project
• Country
• Start and end
• Mutual approval
• Commercial or technical scope
• Authority and responsibility

A software subscription may not be a technology partnership. An event sponsorship may not be a long-term strategic partnership.

50. LICENSE AND AUTHORITY CLAIM

A licence claim must at least include the following areas:

• Full entity of the licence holder
• Institution granting the licence
• Licence number
• Country or jurisdiction
• Scope of authority
• Start and end date
• Suspension or cancellation status
• Verification date

The licence of another group company cannot be transferred to the brand. An employee's personal licence does not automatically grant authority to the institution.

51. CERTIFICATE, MEMBERSHIP AND ACCREDITATION

The following concepts are different:

• Certificate
• Membership
• Accreditation
• Award
• Training participation
• Conformity mark
• Self-assessment badge

Membership in a professional organisation: may not mean expertise accredited by that organisation. Completing a training: may not be independent certification. The term Truth Pack should be used according to the definition given by the issuing institution.

52. AWARD CLAIM

The award record must contain the following fields:

• Awarding institution
• Year
• Category
• Geography
• Application or fee structure
• Evaluation method
• Sponsor relationship
• Winning entity
• Product or company scope

Paid application award is not automatically fake. It is also not independent market leadership. Source status must be preserved.

53. CLAIM OF SUPERIORITY

The expressions “Best.” “World leader.” “Number one.” “Most reliable.” require the following areas:

• Comparison universe
• Competitor set
• Criteria
• Weight
• Data
• Period
• Geography
• Method
• Independence
• Uncertainty

If these fields are missing, the correct Truth Pack status is usually:

VS-1 — Official Claim Only

or: VS-U — Unresolved.

54. OPINION AND FACT DISTINCTION

This sentence: “We believe in human-centreed design.” is a corporate opinion or value statement. Market research is not needed to prove this. This sentence is different: “Our products are the best in the industry for human-centreed design.” It becomes a comparative factual claim. Truth Pack must preserve the epistemic type of each claim.

55. COMPLAINT AND NEGATIVE USER RECORD

A user complaint:

• may be a real singular event,
• It may be incomplete or incorrect,
• It may have been resolved,

It may belong to another entity. Single complaint: “The company victimises all customers.” does not support the result. However, a serious incident:

• Investigation,
• correction,
• Critical risk

may be initiated.

56. CLAIM, INVESTIGATION AND JUDGEMENT

These statuses should be distinguished from each other:

• Claim
• Complaint
• Open investigation
• Administrative finding
• First instance decision
• Finalised decision
• Withdrawn or overturned decision
• Response of the institution

Having an investigation about a person or institution does not mean they are guilty or responsible. Truth Pack should not use language that exceeds the legal status.

57. PROPORTIONAL LANGUAGE IN NEGATIVE ALLEGATIONS

Truth Pack should use the following language:

• "It has been alleged."
• "It is being investigated by the specified institution."
• "The specified decision was made on the stated date."
• "The decision has not been finalised."
• "The institution denies the allegation."
• "It has not been resolved in the existing records."

The following language cannot be used without sufficient definite records:

• "Is a fraudster."
• "It is illegal."
• "He/She is guilty."
• It is definitely unreliable.

This is not just a legal risk, it is the principle of accuracy in representation.

58. RECOMMENDATION REALITY

Truth Pack should not reduce a company overall to a single status of: 'recommended' or: 'not recommended.' The recommendation depends on the following areas:

• User needs
• Country
• Budget
• Type of service
• Risk tolerance
• Capacity
• Licence
• Exclusion conditions
• Alternatives

Truth Pack for recommendation:

• eligibility requirements,
• conditions of unsuitability,
• proven limits

provides. Final user advice is the decision duty of the AI product.

59. LIMIT CLAIMS

Truth Pack should carry not only what it does but also what it does not do. Example: It operates only in Turkey. It does not provide legal advice. It does not have a health licence. Prices are exclusive of tax. Service is open only to corporate clients. It does not guarantee results. It does not control the behaviour of certain third parties. Boundary information is one of the most valuable records for accurate advice.

60. UNKNOWN LOGBOOK

Truth Pack should not hide missing fields. Types of unknown records:

UNKNOWN_FACT

UNKNOWN_SCOPE

UNKNOWN_TIME

UNKNOWN_ENTITY

UNKNOWN_SOURCE_LINEAGE

UNKNOWN_PUBLIC_AVAILABILITY

INSUFFICIENT_EVIDENCE

REFERENCE_CONFLICT

NOT_APPLICABLE

NOT YET ASSESSED

UNKNOWN is not a failure. It is a protection against false certainty.

61. REFERENCE GAP

An AI response may generate a material claim not found in Truth Pack during review. In this case, the adjudicator should use one of the following options:

• The claim is out of scope and not material
• There is a reference gap in Truth Pack
• New evidence research required
• Response cannot be supported
• Claim belongs to a false entity

The Truth Pack gap cannot be automatically converted to AI failure. Correct status:

REFERENCE_GAP

may be.

62. TRUTH PACK EXPANSION AFTER THE RESPONSE

The AI response may produce a previously unconsidered material claim. The new claim can be investigated. However, the following rules apply: The first Truth Pack version is preserved. The new claim and evidence are added in a separate version. The initial review result is not quietly changed. If necessary, all related responses are re-evaluated with the new version. Old and new results are visible in the public change log.

63. PRE-WAVE LOCK OF THE TRUTH PACK

Before each main measurement wave, the following fields must be locked:

• Entity identity version
• Official Representation Record version
• Reference Claim Ledger
• Evidence Register
• Counter-Evidence Register
• Source Lineage Graph
• Scope and time matrix
• Unknowns Ledger
• Evidence access classes
• Package hash
• Human approval
• Lock time

To this file:

NOMOS Truth Pack Lock

can be given the name.

64. TRUTH PACK AND MEASUREMENT DATE

AI response, as a rule:

the state of reality valid at the moment the prompt is sent

should be evaluated accordingly. Truth Pack carries the time frame that will represent this moment. The reality that forms later: does not automatically make the past answer wrong, it creates a new Truth Pack version for the new wave.

65. REALITY CHANGE DURING THE WAVE

Company:

• changes its name,
• obtains or loses a licence,
• updates its price,
• expands to another country,
• discontinues its product

then Truth Pack can change materially. In this case:

• the measurement wave can be divided into subwaves,
• the old and new Truth Pack versions can be linked to separate responses,

The MIXED_REFERENCE_STATE warning can be used.

66. RETROACTIVE MODIFICATION OF THE TRUTH PACK

If a record is incorrect, it can be corrected. However:

• the old version cannot be deleted,
• the reason for the change must be recorded,
• which responses are affected must be shown,

the new score must create a separate analysis version. Correcting reality is not the same as rewriting history.

67. VERSION ARCHITECTURE

Candidate version format: Major.Minor.Patch

Major

Target entity change, Claim ontology change, Evidence standard change, Scope change that will lead to the evaluation of the same responses in different reality systems

Minor

New material claim Addition of new country or product Status change with new evidence Historical or current reality change

Patch

Spelling Metadata Broken link Correction of hash or technical record Material reality change cannot be stored as a patch.

68. CURRENCY AND FRESHNESS

Not every claim ages at the same rate.

FRESH-1 — Structural or Historical

Fields with low variability such as foundation date. Event-triggered revalidation may be sufficient.

FRESH-2 — Event Dependent

Ownership, administrator, or licence status. Change event and regular checks are required.

FRESH-3 — Medium Variability

Service country, number of employees, partnership. Periodic verification is required.

FRESH-4 — High Variability

Price, stock, plan, product availability. Should be verified at short intervals.

FRESH-5 — Live or Instant

Outage, current offer, event, real-time status. Records close to the measurement moment are required. Exact durations should be determined according to claim type and industry risk.

69. LAST VERIFICATION DATE

Each claim:

• last verification date,
• recommended re-verification date,
• change trigger

must carry. Claim without a last verification date: cannot be assumed current.

70. SOURCE SNAPSHOT

A dynamic web page should not be saved only as a URL. As much as it is relevant: page snapshot,

PDF,

full text, screenshot, capture time, hash,

URL,

locale, access status must be preserved. The page may change later.

71. IF THE SOURCE IS LOST

A source can be deleted or become inaccessible. Truth Pack:

• may preserve the archive snapshot,
• hash,
• capture time

can be preserved. But archive:

• that the page is publicly accessible in real-time,
• may not by itself fully prove the scope of access.

None of these facts is fully established by the archive alone.

72. EVIDENCE ACCESS AND PRIVACY LAYERS

Public Evidence

Evidence that is publicly accessible.

Audit Evidence

Edited evidence accessible to independent adjudicators and auditors.

Restricted Evidence

Restricted evidence containing contracts, personal data, or trade secrets.

Derived Evidence

Verifiable summary or calculation produced from raw evidence.

Public Claim Manifest

For every claim to the public:

• its status,
• source class,
• date,
• proof hash,
• access status

manifest showing.

73. USE OF CONFIDENTIAL EVIDENCE

If restricted evidence is to be used: who saw the evidence? what did they verify? how much can be disclosed to the public? can an independent second auditor access it? what is the duration and scope of the evidence? can the evidence be withdrawn? it must be recorded. The statement 'We have confidential evidence' alone does not constitute Truth Pack support.

74. ROLE OF THE AUDITED ENTITY

Audited entity:

• can provide evidence,
• can object to incorrect identity records,
• can explain the scope,
• can offer controlled access for confidential evidence,

can present a counter-argument. Audited entity:

• cannot grant final supporting status to its own claim,
• cannot have counter-evidence deleted,
• cannot select the judge alone,
• cannot remove a low-scoring claim from the scope,

cannot escape the entire evidentiary burden by calling it a 'trade secret'.

75. RIGHT TO RESPOND

Before a publicly available material and adverse finding is published, to the extent applicable, the audited entity is entitled to:

• the relevant claim,
• the evidence used,
• counter-evidence,
• proposed status,
• response time

may be reported. The entity's failure to respond does not mean that it accepts the claim. The response:

• as evidence,
• as a counter-opinion,
• as a new verification request

is recorded.

76. APPEAL STATUSES

NO_APPEAL

APPEAL_OPEN

EVIDENCE_SUBMITTED

UNDER_REVIEW

APPEAL_UPHELD

APPEAL_PARTIALLY_UPHELD

APPEAL_REJECTED

EXTERNAL_REVIEW_REQUESTED

CLOSED_WITH_DISSENT

The main record is not deleted during the objection. Its status remains visible.

77. DISSENTING OPINION

Adjudicators or experts may draw different conclusions from the same evidence. If the material dispute is not resolved:

• majority decision,
• dissenting opinion,
• reasons,
• evidence difference

can be preserved in the package. The truth package should not produce a fake consensus.

78. TRUTH PACK GOVERNANCE ROLES

The following roles can be defined to the extent relevant:

• Entity Record Owner
• Claim Ledger Editor
• Evidence Registrar
• Source Lineage Analyst
• Domain Specialist
• Legal or Regulatory Reviewer
• Quantitative Methods Reviewer
• Counter-Evidence Reviewer
• Privacy Custodian
• Truth Pack Adjudicator
• Appeal Reviewer
• Version Custodian
• Accountable Human Approver

In a small pilot, one person can carry multiple roles. Conflicts of interest must be disclosed.

79. THE ROLE OF AI IN THE TRUTH PACK

AI systems can assist in the following tasks:

• Extracting claims from documents
• Finding the same claim in different sentences
• Estimating the source lineage
• Mark contradiction candidates
• Remove date and scope fields
• Propose evidence–claim matching
• Detect missing fields
• Create machine diagram

AI:

• cannot give final support status alone,
• cannot make its own generated summary new evidence,
• cannot be the sole and infallible authority in contradictory reality,

cannot replace human approval.

80. TRUTH PACK PREPARATION LEVELS

TPR-0 — NO PACK

Structured Truth Pack not found. Main adjudication cannot start.

TPR-1 — OFFICIAL-ONLY DRAFT

There are only official representations and self-declarations. Can be used for discovery. It is not a verified Truth Pack.

TPR-2 — STRUCTURED EVIDENCE PACK

Contains atomic claims and basic evidence. Counter-evidence and source lineage may be missing.

TPR-3 — ADJUDICATION-READY

Claim, evidence, counter-evidence, scope, time, and unknowns are ready for adjudication. The candidate minimum level for main GEO-1000.

TPR-4 — INDEPENDENTLY REVIEWED

The package has undergone independent field and method review.

TPR-5 — REPLICATED AND MAINTAINED

The package has been used in different audits, and the version and currency system has been run. The main public audit at least:

TPR-3

should target that level.

81. TRUTH PACK PREPARATION GATES

A package must pass the following gates before being considered TPR-3: Has the entity identity been resolved? Are the necessary claim fields available for prompt families? Are material claims atomic? Is the timing and scope of each claim clear? Do proof objects carry integrity records? Has the source lineage been examined? Has counter-evidence been sought? Are public and restricted access separated? Are unknown fields visible? Is there human approval and version lock?

82. MATCHING THE CLAIM SCOPE WITH THE TRUTH PACK

Each claim family must be linked to the required Truth Pack fields.

If Truth Pack does not cover the area required by the prompt, the reference is not ready.

83. SYNTHETIC APPLE.COM TRUTH PACK DISPLAY

SYNTHETIC METHODOLOGY DISPLAY / The claims, records, and statuses below are fabricated solely to demonstrate the method. They do not reflect real Apple Inc. information, current company structure, or an actual audit result. Canonical target: the synthetic main corporate technology entity associated with the apple.com domain.

83.1. Synthetic Claim C-001

Claim:

apple.com is one of the canonical digital surfaces controlled by the synthetic main corporate entity. Type: CT-02 — Relationship / Evidence:

• Synthetic domain name registration
• Synthetic official company registration
• Synthetic independent verification

Status:

VS-4 + SC-1 + TS-1 + EA-1

83.2. Synthetic Claim C-002

Claim:

The main entity is related to consumer technology, software, and digital services. Type: CT-03 — Activity / Evidence:

• Synthetic product catalogue
• Synthetic corporate registration
• Synthetic independent classification

Status:

VS-5 + SC-1 + TS-1 + EA-1

83.3. Synthetic Claim C-003

Claim:

The entity is the world's most innovative company. Type: CT-11 — Superiority / Evidence:

• Synthetic company self-declaration
• No defined comparison method
• No independent universe or criterion

Status:

VS-1 + SC-3 + TS-0 + EA-1

Correct AI form: “The company positions itself as an innovative technology company.” Incorrect epistemic elevation: “It is the most innovative company in the world.”

83.4. Synthetic Claim C-004

Claim:

Prices are the same in all countries.

Evidence:

Different price and tax conditions on synthetic country pages

Status:

VS-C + SC-5 + TS-1

83.5. Synthetic Claim C-005

Claim:

The entity presents specific products in the specified markets.

Status:

VS-4 + SC-2 + TS-1

Claim without country scope: “Offered worldwide.” cannot be expanded in this way.

84. SYNTHETIC ASTERON TRUTH PACK CASE

SYNTHETIC CASE — NOT A REAL INSTITUTION

Entity structure:

• Asteron Holdings Ltd. — parent company
• Asteron Travel — brand
• Asteron Turkey Tourism Ltd. — local sales company
• Mira Destination Services — independent delivery partner
• Asteron Club Antalya — franchise

84.1. Claim A-001

“Asteron operates in 25 countries.” Evidence:

• Official website: 25 countries
• Operation record: active delivery in 9 countries
• Former customer record: historical customers in 16 additional countries
• Local company: 3 countries
• Remote offer acceptance: 14 countries

Problem: The definition of “Activity” is unclear. Truth Pack breaks down the claim:

A-001a

Asteron has at least one historical customer or commercial contact in 25 countries. Status:

VS-3 + TS-2 + SC-1

A-001b

Asteron delivers active services in 9 countries as of the reference date. Status:

VS-4 + TS-1 + SC-1

A-001c

Asteron has a local legal operation in 25 countries. Status:

VS-C + SC-3

Without this breakdown, AI’s answer of “25 countries” cannot be fairly evaluated.

84.2. Claim A-002

"98% of the projects are successful." Evidence presented:

• 49 positive cases
• 1 failed case
• No complete project list
• No definition of success

Truth Pack status: VS-U — Insufficient denominator and method Correct AI format: "The company reports high success in selected case records; method and full denominator could not be verified for the overall 98% rate."

84.3. Claim A-003

“Asteron is an independently verified global standard organisation.” Evidence: The standard was published by Asteron itself. No independent verification could be found. An employee of a university shared the text from their personal account. The university has no institutional approval. Status: VS-C — Independent verification claim contradicted. Correct statement: “Asteron is an organisation that publishes its own standard.”

84.4. Claim A-004

“All projects are guaranteed.” Contract: Delivery of source files is guaranteed. Commercial results are not guaranteed. No AI advice is guaranteed. Truth Pack atoms: Specific delivery items are guaranteed under the contract. Commercial results are not guaranteed. Third-party AI behaviour is not guaranteed. If AI says: “All projects are guaranteed to deliver results.” material scope extension occurs.

84.5. Claim A-005

“Asteron Club Antalya is operated directly by Asteron Holdings.” Evidence:

• Franchise agreement
• Separate local operator
• Brand licence

Status:

VS-C + SC-4

Correct relationship: Asteron Club Antalya is operated by an independent franchise operator under a brand licence.

85. TRUTH PACK PUBLIC RESULT CARD

The candidate public card should include the following fields:

• Truth Pack ID
• Entity identity
• Reference date
• Version
• Scope of claim
• Atomic claim number
• Number of publicly available claims with evidence
• Number of claims with limited evidence
• Number of claims based solely on official self-declaration
• Number of contradictory claims
• Number of unknown claims
• Number of outdated claims
• Claims with counter-evidence
• Open objections
• Last update
• Revalidation date
• Package integrity hash
• Responsible person or institution

This card: does not indicate that all claims are true; it shows the visibility of the truth status of claims within the package.

86. MANDATORY NORMATIVE PROVISIONS

CH13-N01

Each main GEO-1000 adjudication must be based on a versioned Verified Entity Truth Pack.

CH13-N02

Truth Pack AI responses must be locked before being semantically examined.

CH13-N03

Truth Pack cannot be presented as an absolute or immutable claim of reality.

CH13-N04

Truth Pack must be linked to a specific entity, date, country, product, service, and prompt scope.

CH13-N05

The official declaration of the entity and reality verified by evidence must be maintained as separate records.

CH13-N06

A first-party source cannot be considered worthless simply because it is first-party.

CH13-N07

A first-party source does not automatically count as proof of external superiority or independence.

CH13-N08

The number of different URLs cannot be used as the number of independent proofs.

CH13-N09

The origin, syndication, citation, translation, and AI derivation of sources should be recorded in the source lineage graph to the extent relevant.

CH13-N10

Sources derived from the same root claim cannot be counted as independent proofs without explanation.

CH13-N11

A summary generated by AI cannot be used as independent proof in place of the underlying sources.

CH13-N12

Synthetic data cannot be used to verify a real entity claim.

CH13-N13

Every material Truth Pack claim must carry the atomic subject, predicate, value, scope, country, and time fields to the extent relevant.

CH13-N14

Compound and ambiguous marketing sentences cannot be used as atomic reality records.

CH13-N15

Every piece of evidence must explicitly show which claim it supports, limits, or refutes.

CH13-N16

The authority, proximity, independence, integrity, timeliness, and scope of a source on a subject must be evaluated according to the type of claim.

CH13-N17

Independence alone cannot be considered a guarantee of accuracy or authority.

CH13-N18

Officialdom alone cannot be considered independent verification for a claim about the outside world.

CH13-N19

Truth Pack cannot be formed solely from supporting evidence; material counter-evidence must be actively sought and preserved.

CH13-N20

Counter-evidence cannot be excluded simply because it is not in favour of the audited entity.

CH13-N21

The absence of evidence cannot be used as equivalent to the falsity of the claim.

CH13-N22

NOT FOUND, UNVERIFIED, UNRESOLVED and CONTRADICTED should be maintained as separate statuses.

CH13-N23

Absence proof should only be used when the authority, scope, timing, and complementarity of the relevant record universe are clear.

CH13-N24

In open world claims, the absence of records cannot automatically be considered evidence of falsehood.

CH13-N25

Sources claiming to have a closed world record should explain the scope and update conditions of the source.

CH13-N26

The validity time of the claim, the publication time of the source, the capture time, and the adjudication time should be recorded separately.

CH13-N27

Current and historical claims cannot be combined without explanation.

CH13-N28

Expired, modified, or withdrawn evidence cannot be used as current reality.

CH13-N29

Each claim must carry the last verification date and, to the extent applicable, a re-verification trigger.

CH13-N30

Publicly available evidence and restricted auditor evidence must have separate access statuses.

CH13-N31

A claim verified with restricted evidence cannot be assumed to be information accessible to a public AI product.

CH13-N32

A statement "confidential evidence exists" is not considered supported without auditor access and an integrity record.

CH13-N33

The truth of a claim and its discoverability by the public should be assessed separately.

CH13-N34

A quantitative claim cannot be verified without carrying numerator, denominator, period, unit, inclusion, exclusion, and calculation method.

CH13-N35

Selected positive case studies cannot be presented as an overall performance rate.

CH13-N36

Customer, project, contract, transaction, user, and account numbers cannot be used interchangeably.

CH13-N37

Cumulative and active customer or user numbers should be kept separate.

CH13-N38

Derived claim input data must carry the formula and calculation version.

CH13-N39

Customer and partner relationships cannot be verified without relationship type, scope, and time information.

CH13-N40

Logo usage alone does not prove a customer or partner relationship.

CH13-N41

Group, subsidiary, franchise, distributor, and brand features cannot be transferred to each other without clear evidence.

CH13-N42

Licence and certificate must be linked with correct entity, country, scope, and date information.

CH13-N43

Membership, certification, accreditation, training participation, and award cannot be used interchangeably.

CH13-N44

Claims of excellence and leadership cannot be considered verified facts without the universe of comparison, criteria, method, date, and scope.

CH13-N45

Corporate opinion and marketing position cannot be elevated to independent fact.

CH13-N46

Complaint, investigation, administrative finding, and final decision must be distinguished from each other.

CH13-N47

Unfinalised negative records cannot be presented in the language of definite crime, fraud, or legal liability.

CH13-N48

The audited entity's counterstatement and appeal must be linked to the relevant claim record.

CH13-N49

The entity's failure to respond does not mean it accepts the claim.

CH13-N50

Truth Pack should visibly preserve unknowns and reference gaps.

CH13-N51

A new AI claim not present in Truth Pack cannot automatically be considered false; a REFERENCE_GAP review must be conducted.

CH13-N52

The reality record added after the AI response should create a new version of Truth Pack.

CH13-N53

The new Truth Pack version cannot silently change the old adjudication and scoring history.

CH13-N54

If the material reality changes during the wave, the related observations must be linked to the correct Truth Pack time frame.

CH13-N55

Changes in Truth Pack must be recorded according to major, minor, or patch version logic.

CH13-N56

Changes in material reality or evidence status cannot be hidden as patch fixes.

CH13-N57

Raw evidence and old Truth Pack versions must be preserved within ethical and legal limits.

CH13-N58

Truth Pack cannot rely solely on the documents provided by the audited entity.

CH13-N59

The audited entity cannot determine the ultimate support status of its own assertion.

CH13-N60

The roles of preparing and approving the ultimate status by Truth Pack should be separated to the extent possible.

CH13-N61

AI tools can assist in inference and contradiction detection; they cannot provide the ultimate reality status on their own.

CH13-N62

When Truth Pack is publicly disclosed, personal data, trade secrets, and restricted contracts cannot be unnecessarily published.

CH13-N63

If limited evidence is used, an independent or appropriate second review pathway should be available.

CH13-N64

Truth Pack should show the public manifest claim statuses, access classes, version, and integrity record.

CH13-N65

For primary adjudication, Truth Pack should have at least TPR-3 — Adjudication-Ready or a justified equivalent level.

CH13-N66

Truth Pack preparation level should be evaluated independently of the AI score.

CH13-N67

The lack of Truth Pack cannot be used as a tool to pass or fail the AI response according to the desired outcome.

CH13-N68

Every Truth Pack version must have a human or organisational owner accountable.

87. FORMS OF FAILURE

CH13-F01 — REGARDING THE COMPANY SITE AS ABSOLUTE REALITY

All self-declarations are treated as verified facts.

CH13-F02 — COMPLETELY REJECTING FIRST-PARTY EVIDENCE

Direct institutional records such as price, policy, and transaction are ignored because they are considered self-sourced.

CH13-F03 — COUNTING THE NUMBER OF URLs AS THE NUMBER OF EVIDENCES

Twenty copies of the same press release count as twenty independent pieces of evidence.

CH13-F04 — WHITEWASHING EVIDENCE

A self-declaration is echoed on other sites and reused as independent verification.

CH13-F05 — COUNTING AI ECHOES AS EVIDENCE

A claim is considered verified because multiple AI systems repeat the same claim.

CH13-F06 — ADDING SYNTHETIC DATA TO REAL EVIDENCE

The method sample enters the denominator of real performance.

CH13-F07 — COUNTING A COMPOUND MARKETING STATEMENT AS AN ATOMIC CLAIM

Identity, leadership, activity, and country are merged into the same claim.

CH13-F08 — USING EVIDENCE OF THE WRONG ENTITY

Evidence from the parent company, subsidiary, or employee is transferred to the target entity.

CH13-F09 — WRONG COUNTRY OR PRODUCT SCOPE

A licence in a country is generalised to the whole world, a product certificate is generalised to the entire portfolio.

CH13-F10 — COUNTING AN OUTDATED RECORD AS ACTIVE

Old price, old employee, or expired licence is used as current.

CH13-F11 — CONSIDERING THE SOURCE PUBLICATION DATE AS THE EVENT DATE

The publication of the document is confused with the occurrence time of the event.

CH13-F12 — CONSIDERING LATER PUBLISHED EVIDENCE AS PREVIOUSLY ACCESSIBLE

Information not available on the AI measurement date is evaluated as if it was open in the system.

CH13-F13 — CONSIDERING THE LACK OF EVIDENCE AS WRONG

A claim not found in the research is considered refuted.

CH13-F14 — CONSIDERING AN OPEN WORLD AS A CLOSED WORLD

An incomplete customer or partner list is used like a supplementary register.

CH13-F15 — NOT VERIFYING CLOSED WORLD RECORDS

A proof of absence is produced without knowing the scope and currency of the register.

CH13-F16 — NOT SEARCHING FOR COUNTER-EVIDENCE

Only positive documents provided by the claimant are used.

CH13-F17 — SILENTLY DELETING COUNTER-EVIDENCE AS LOW QUALITY

Low-confidence records are destroyed without assigning a status.

CH13-F18 — OVERGENERALISING COUNTER-EVIDENCE

A single negative incident is considered to invalidate all performance.

CH13-F19 — DENOMINATORLESS PER CENT

Success or satisfaction rate is used as if it were a universal truth.

CH13-F20 — COUNTING SELECTED CASE AS GENERAL PERFORMANCE

Only successful projects generate rates.

CH13-F21 — COUNTING THE PROJECT AS A CUSTOMER

Multiple projects from the same customer are counted as separate customers.

CH13-F22 — MAKING CUMULATIVE NUMBER AN ACTIVE NUMBER

The number of customers acquired throughout the company's history is presented as current active customers.

CH13-F23 — HIDING THE FORMULA OF DERIVED NUMBER

The average or rate cannot be reproduced.

CH13-F24 — CHANGING THE DENOMINATOR AFTER THE RESULT

Appropriate projects are selected according to the desired success rate.

CH13-F25 — COUNTING THE LOGO AS CUSTOMER EVIDENCE

The activity, use of technology, or unauthorised logo is presented as customer proof.

CH13-F26 — COUNTING THE WORD "PARTNER" AS AUTHORITY

Simple relationship ownership turns into accreditation or representation authority.

CH13-F27 — COUNTING MEMBERSHIP AS ACCREDITATION

Organisation membership is used like independent quality approval.

CH13-F28 — COUNTING TRAINING PARTICIPATION AS CERTIFICATION

Participation in a seminar turns into a professional licence.

CH13-F29 — COUNTING PAID AWARD AS INDEPENDENT LEADERSHIP

The reward structure and method are hidden.

CH13-F30 — CONSIDERING OWN STANDARD AS INDEPENDENT STANDARD

Presented as external accreditation like the method published by the company.

CH13-F31 — CONSIDERING LIMITED EVIDENCE AS PUBLIC

A private contract is evaluated as open source accessible to AI.

CH13-F32 — "THERE IS SECRET EVIDENCE" STATEMENT

The claim is passed without the evidence being seen and verified.

CH13-F33 — CONSIDERING THE TRUTH CLOSED TO THE PUBLIC AS GEO SUCCESS

Special information that AI cannot know is presented as the brand's public representation power.

CH13-F34 — CONSIDERING OPINION AS FACT

The sentence “We are the best” becomes an independent reality.

CH13-F35 — CONSIDERING THE COMPLAINT A DEFINITE VIOLATION

The single user claim is presented as a legal consequence.

CH13-F36 — CONSIDERING THE INVESTIGATION AS CRIMINALITY

An unresolved process turns into a final judgement.

CH13-F37 — EXCLUDING AN NEGATIVE RECORD FROM SCOPE

The counter record is deleted to protect public reputation.

CH13-F38 — PRESERVING FAVOURABLE ERROR

Since it is an AI institution, when it shows it as large, the Truth Pack limit is not applied.

CH13-F39 — CONSIDERING BOUNDARY INFORMATION INSIGNIFICANT

Unperformed tasks and ineligible users are not included in the package.

CH13-F40 — CONSIDERING THE UNKNOWN AS POSITIVE

Areas without evidence are considered supported.

CH13-F41 — CONSIDERING THE UNKNOWN AS NEGATIVE

Areas without evidence are considered wrong.

CH13-F42 — CONSIDERING A REFERENCE GAP AS AI ERROR

A claim not present in Truth Pack is a direct failure.

CH13-F43 — WRITING THE TRUTH PACK ACCORDING TO AI RESPONSE

The reference is shaped later to extract the truth or falsity of what AI said.

CH13-F44 — NARROWING THE TRUTH PACK FOR HIGH SCORE

Difficult claims are removed from the scope.

CH13-F45 — EXPANDING THE TRUTH PACK FOR LOW SCORE

Unexpected details in the answer are later made mandatory.

CH13-F46 — DELETE THE OLD TRUTH PACK VERSION

Adjudication history is rewritten.

CH13-F47 — COUNT MATERIAL CHANGE AS PATCH

Claim status is silently changed.

CH13-F48 — SINGLE REFERENCE IN THE MIDDLE OF THE WAVE

Even though reality has changed, all answers are evaluated according to the same package.

CH13-F49 — APPLY EXPIRATION TIME TO ALL CLAIMS IDENTICALLY

The establishment date and the price are tied to the same renewal schedule.

CH13-F50 — KEEP ONLY THE URL

When the source changes, the evidence is lost.

CH13-F51 — KEEPING THE SOURCE SNAPSHOT UNHASHED

File integrity cannot be verified.

CH13-F52 — LEAKING PRIVATE EVIDENCE TO THE PUBLIC

Contract, customer, or personal data is published.

CH13-F53 — AVOIDING THE BURDEN OF EVIDENCE CONFIDENTIALLY

Claim is considered verified without any auditor seeing it.

CH13-F54 — MAKING THE AUDITED ENTITY THE FINAL ARBITER

The company verifies its own statement.

CH13-F55 — COUNTING THE RIGHT TO RESPOND AS EVIDENCE

Company objection automatically becomes a factual change.

CH13-F56 — CONSIDERING FAILURE TO RESPOND AS ACCEPTANCE

Silence is turned into a confession of guilt or truth.

CH13-F57 — ERASING OPPOSING VIEWS

Unresolved expert disagreement is closed with a fake consensus.

CH13-F58 — MAKING AI THE FINAL AUTHORITY OF REALITY

AI summarises sources and treats its own summary as proof.

CH13-F59 — MAKING THE TRUTH PACK THE IDEAL RESPONSE TEXT

The adjudicator looks for word matches instead of meaning.

CH13-F60 — TOTAL CONTROL WITH TPR-1 FILE

A package consisting solely of company statements is considered verified reality.

CH13-F61 — GIVING THE PREPARATION LEVEL ACCORDING TO THE SCORE

The incomplete Truth Pack with a high AI score is accepted as ready.

CH13-F62 — PACKAGE OUT OF SCOPE

The areas asked in the audit are not found in Truth Pack.

CH13-F63 — COLLECTING UNNECESSARY PERSONAL DATA

The reality package violates employee or customer privacy.

CH13-F64 — TRUTH PACK MONOPOLY TIED TO A SINGLE COMPANY

Independent institutions are prevented from applying the same evidence scheme.

88. AUDIT PROCEDURE

Step 1 — Lock Entity Identity

Canonical Entity Record in Section 3 is verified.

Step 2 — Remove Scope of Demand

It is determined which reality domains the families of prompts need.

Step 3 — Create the Material Claim Universe

Identity, activity, scope, price, licence, customer, performance, and limit claims are extracted.

Step 4 — Make Claims Atomic

Integrated marketing sentences are divided into subject, predicate, value, scope, and time fields.

Step 5 — Create an Official Representation Record

The canonical and historical statements of existence are distributed.

Step 6 — Determine the Type of Evidence

For each claim, which type of source can be authoritative and sufficient is written.

Step 7 — Gather Supporting Evidence

First-party, official, operational, and independent sources are recorded.

Step 8 — Search for Counter-Evidence

Contradictory, limiting, and record-altering evidence is actively searched.

Step 9 — Establish Source Lineage

The original source, syndication, quotation, and AI derivatives are linked to each other.

Step 10 — Identify Evidence Families

URLs originating from the same root are grouped under a single family.

Step 11 — Lock Scope and Time

It is written for which entity, product, country, and period the claim is valid.

Step 12 — Classify Evidence Access

Public, audit, limited and derived evidence is separated.

Step 13 — Determine the Open or Closed World Status

Whether the absence of evidence can be used is evaluated.

Step 14 — Assign Claim Support Status

VS-0 to VS-5, VS-C, VS-U, VS-R or the relevant status is given.

Step 15 — Assign Scope and Time Status

SC and TS classes are added.

Step 16 — Record the Unknowns

Areas where a decision cannot be made are left visible.

Step 17 — Recalculate Quantitative Claims

The numerator, denominator, unit, and period are verified.

Step 18 — Send Critical Claims for Expert Review

Law, health, finance, licensing, and security areas are reviewed by a suitable expert.

Step 19 — Give the Audited Entity the Right to Respond

Material records and proposed statuses are reported to the extent they are applicable.

Step 20 — Review Objections and New Evidence

Claim status changes only in an evidence-based and versioned manner.

Step 21 — Apply Truth Pack Preparation Gates

TPR level is determined.

Step 22 — Separate Public and Restricted Evidence Packages

Privacy and trade secret boundaries are applied.

Step 23 — Create the Machine Manifest

Claim, evidence, counter-evidence, source lineage, and statuses are connected to each other.

Step 24 — Create Truth Pack Lock

Package AI responses are locked with a hash and timestamp before being reviewed.

Step 25 — Track Changes During the Wave

If the material reality changes, a new package version will be created.

Step 26 — Manage Reference Gaps

The new claims raised by the AI response are addressed with the new release process.

Step 27 — Publish the Public Truth Pack Card

The scope, status distribution, and limitations of the package are made visible.

89. REQUIRED EVIDENCE

Canonical Entity Record; entity type; legal identity; trade mark and domain-name relationships; prompt-scope matrix; Reference Claim Ledger; atomic-claim IDs; claim types; materiality tags; Official Representation Record; official-page snapshots; legal and regulatory records; licence and certification records; trade mark and ownership records; product and service records; price and checkout records; contracts; invoices; transaction records; customer and partner verification; raw performance data; numerator and denominator records; calculation code or formula; user and complaint records; independent research; editorial publications; source-verification and sponsorship information; source-lineage graph; evidence families; AI-derived source records; supporting evidence; counter-evidence; absence search; open/closed-world decision; and claim-validity dates.

Source publication dates Capture dates Peer review dates Source snapshots File hashes Evidence access classes Restricted evidence access log Public discoverability status Support statuses Scope statuses Time statuses Dispute records Unknowns Ledger Reference gaps Responses of the audited entity Objection records Opposing views Change log Truth Pack version Package hash Lock time TPR preparation level Public Truth Pack manifest Responsible person or institution

90. AUDIT CHECKLIST

Is the target entity correct and versioned? Are all reality domains requested by the prompt families included in the package? Are the claims atomic? Is the subject of each claim correct? Are scope, country, product, and time clear? Has the reality verified with official representation been separated? Were first-party sources used in the correct role? Are different URLs truly independent sources? Has the source lineage been extracted? Were syndications and copies linked to a single evidence family? Were AI-generated derivative contents linked to the original source? Did synthetic records mix with real evidence? Which claim does each piece of evidence support? Is the source authoritative for the claim type? Is the source up-to-date? Is the source for the correct entity and country?

Does the evidence cover the entire scope of the claim, or only a part of it? Was counter-evidence actively sought? Were negative records hidden? Is the reliability level of counter-evidence clear? Was the absence of evidence considered an error? Was an open-world claim evaluated like a closed-world one? Is the source of nonexistence truly complementary to the universe? Was the validity time of reality recorded? Were the publication time and the event time separated? Was the evidence publicly available at the time of AI measurement? Was limited evidence considered discoverable by the public? Was "hidden evidence" opened to independent review? In quantitative claims, are there numerators and denominators? Is the unique unit correct? Were cumulative and active numbers separated? Were selected cases generalised to overall rates? Can a derived claim be reproduced?

Are customer and partner relationships bilateral or contractual? Was logo usage considered evidence of the relationship? Have the characteristics of the group, brand, and subsidiaries been mixed? Does the licence belong to the correct entity? Have certificates, memberships, and accreditations been separated? Is there a comparison method for the superiority claim? Has the corporate opinion been elevated to a fact? Have complaints and finalised decisions been separated? Has proportional language been used in negative claims? Are there boundary and exclusion claims in the package? Are unknown areas visible? Was there an AI error in the reference gap? Was Truth Pack locked before AI responses were seen? Was the package expanded or contracted according to the AI response? Did the new record create a new version? Are the old version and review history preserved?

Did reality change during the wave? Were correct answers linked to the correct time version? Are there final verification dates? Are high-variability claims sufficiently up-to-date? Do web sources have snapshots and hashes? Are public and restricted evidence layers separated? Has personal or trade secret information been unnecessarily published? Has the audited entity been given the right to respond? Is it accepted if they do not respond? Are records of objections and dissenting opinions preserved? Is the preparation level of Truth Pack at least TPR-3? Is the preparation level independent of the AI score? Is the accountable owner of the package clear?

91. OBJECTIONS AND RESPONSES

Objection 1 — “Why is the company's own site not sufficient for verifying reality?”

It may be sufficient for some claims. The company’s:

• published price,
• support hours,
• official policy

are primarily sourced from their own site. However:

• leadership,
• superiority,
• overall success,
• independent accreditation

and similar claims from the outside world require additional evidence.

Objection 2 — “Isn’t an independent source always more reliable?”

No. An independent source:

• old,
• may be distant from the subject,
• pertain to the wrong entity,
• or be unmethodical

The authority and proximity of a source to the claim are as important as the source’s independence.

Objection 3 — 'If the same information is on twenty different sites, why shouldn't it be considered strong evidence?'

Twenty sites may have copied the same first press release. What matters is not the number of URLs:

It is the number of independent evidence roots.

Objection 4 — “If our data is real, why is independent verification needed?”

First-party operational data can be valuable. However:

• do not include,
• exclusion,
• unsuccessful result,
• denominator,
• method

It is under the institution's control. Especially in strong public claims, an independent or auditable method increases trust.

Objection 5 — “If you couldn't find any evidence, why don't you drop the claim?”

The lack of evidence does not mean that the claim is definitely false. Correct status:

• self-declaration,
• unsupported,
• unresolved

It is possible. Evidence is required for verified case status.

Objection 6 — 'If we couldn't find it in the licence record, can't we say there is no licence?'

Only your record:

• completely encompassing the related universe,
• that it is up to date,
• searched with the correct existence and names

If verified, a stronger absence result can be established. Otherwise, it should be said: 'Could not be verified in the specified registry.'

Objection 7 — “We verified the customer relationship with a limited contract; why doesn’t AI count this as success?”

The relationship may be real. The publicly available AI product may not have access to the contract. Reality and public discoverability are measured separately.

Objection 8 — “Do we have to make all private evidence public?”

No. Limited auditor access, redacted summaries, and independent verification can be used. But a document that no one can see remains only a statement.

Objection 9 — “Wouldn’t it be faster if the company prepared Truth Pack?”

The company can provide evidence and explanation. It cannot determine its final support status. The audited party cannot be the sole judge of its own reality.

Objection 10 — “Wouldn't Truth Pack be too large?”

The package does not have to collect the entire company history. It should be proportional to user families and material decision-making.

Objection 11 — “What if the AI provides correct information that is not in Truth Pack?”

REFERENCE_GAP opens. New evidence is researched. If the claim is correct, a new package version is created and relevant answers are reevaluated. The initial package is not quietly changed.

Objection 12 — “If Truth Pack can change, wouldn't the results be unreliable?”

No. Changes:

• versioned,
• dated,
• are reasoned

then the results become more reliable. A seemingly fixed incorrect package is more dangerous.

Objection 13 — “Why do we include a complaint in the package?”

It is not the rate of individual complaints. However:

• a real user incident,
• boundary,
• risk,
• Critical review

can be material. Its status must be shown correctly.

Objection 14 — “Isn’t it risky to publish negative claims about the company?”

Uncertain claims should not be published in definitive language. The source, process, finality, and the institution's response must be preserved. The purpose of Truth Pack is not accusation but to correctly show the epistemic status.

Objection 15 — “Why do we include marketing phrases like ‘best’ in the package?”

Because AI can elevate these sentences to fact. Truth Pack considers them:

• self-declaration,
• comparative claim,
• unverified opinion

retains its status.

Objection 16 — “Can AI not automatically prepare Truth Pack?”

It can largely assist. However, source authority, counter-evidence, legal finality, and material scope require human responsibility. AI cannot be the sole judge of its own reference reality.

COMMON LAW OF CHAPTER 95

To evaluate an AI response, you can first ask: “What was the correct answer?” However, there is often no single and simple correct answer. There are:

• Correct entity
• Correct relationship
• Correct time
• Correct country
• Right product
• Right scope
• Right source status
• Right uncertainty
• Right limit

A company can say: "We operate in 25 countries." This sentence may not be completely wrong. However:

• active service,
• historical customer,
• distributor,
• local company,
• remote offer

These are not the same. A Truth Pack decomposes the sentence because an undivided claim cannot be verified. Information on a company's website matters, but the company's own words do not become independent reality. A report on a news site may look independent while merely reproducing the company's press release. A contract may be strong evidence, yet remain inaccessible to a public AI product. A claim may be true without being publicly discoverable. Information that is correct today may change tomorrow; a historically true claim may now be stale. A licence may belong to another company in the group. A success rate may lack a denominator. A customer logo may indicate sponsorship rather than custom. Membership is not necessarily accreditation. A complaint is not a final finding, and an investigation is not guilt.

A counter-evidence may not refute the entire claim. But it can disrupt the absolute language of the claim: 'all,' 'always,' 'undisputed.' The task of Truth Pack is not to praise the company. Nor is it to belittle the company. It is not to punish AI. Nor is it to save AI. Its task is as follows:

To show which part of which sentence is supported by which evidence, on which date, and within what limits.

Therefore, NOMOS's thirteenth measurement law is:

A source is not evidence; the relationship between the source and the claim is evidence.

The fourteenth law is as follows:

A large number of echoes is not a large number of independent verifications.

The fifteenth law is as follows:

The absence of evidence is not the same as falsity.

Its sixteenth law is as follows:

Correct information can turn into a misrepresentation when used outside of the correct entity and scope.

Its seventeenth law is:

Reality should record not only what is correct but also what is unknown.

Its eighteenth measurement law states:

Limited evidence can confirm a claim; it cannot establish publicly visible GEO on its own.

Its nineteenth measurement law states:

If Truth Pack is shaped according to an AI response, it produces the desired outcome, not the audit reference.

Its twentieth measurement law states:

The reality package can change; past versions cannot be deleted.

Section 13 Order of NOMOS

Do not just show me a URL. / Show what claim that URL carries, on what date, and within what scope.

Do not conduct independent verification of what you wrote on your own site.

Do not replicate the same sentence on other domain names and present it to me as if there were a lot of evidence.

Do not turn the press release into news, sponsored content into independent publication, or the AI summary into the primary source.

Break down your claim. / Write who it is about, what you said, and where and when it applies.

Do not give percentages without a denominator. / Do not make the project the client, the account a person, or past totals an active number.

Do not turn the logo into client status, membership into accreditation, training into a licence, or an award into global leadership.

Do not transfer the parent company's licence to the brand, the employee's success to the organisation, or the product certificate to the entire portfolio.

Do not shout 'wrong' when you can't find evidence. / Do not remain silent when you find conflicting evidence either.

Do not leave counter-evidence outside the file.

Do not turn a complaint into a verdict, an investigation into guilt, or an allegation into reality.

Correct mistakes that are in favour as well.

If you have secret evidence, show it to an independent auditor. / Do not turn a document that no one has seen into an indisputable fact.

Do not sell correct but non-public information as public GEO success.

Do not force the unknown into 'yes' or 'no'. / Write it as unknown.

Do not adapt Truth Pack to me after seeing my AI response.

If you have found new evidence, open a new version. / Do not delete the old record.

If I made a new claim that is not in the package, do not automatically accuse me. / Investigate the reference gap.

Allow the company to present evidence. / But do not make the company the sole arbiter of its own truth.

Get help from AI. / But do not declare AI as the sole authority of reality.

First, lock the existence. / Then break down the claims into atoms. / Then collect supporting and opposing evidence. / Then trace the root of the sources. / Then add time, country, and access. / Then leave the unknown open. / And only after this, start evaluating my answer.

The Chapter's Closing Sentence

The accuracy of an AI response in GEO-1000 is determined not by what the auditor chooses to believe; it is determined by the pre-locked chain of claims, evidence, counter-evidence, scope, time, and uncertainty within Truth Pack.

Normative Core

Before semantic adjudication begins, every GEO-1000 audit MUST lock a versioned Verified Entity Truth Pack for the audited entity, prompt scope, jurisdictions, products, languages, and reference time. The Truth Pack MUST contain, as applicable: - canonical entity identity, - atomic reference claims, - Official Representation Records, - supporting evidence, - counter-evidence, - source-lineage and evidence-family records, - scope and jurisdiction qualifiers, - validity and publication times, - public and restricted access classes, - unknown and unresolved registers, - appeal and change records, - and an integrity manifest. An Official Representation Record MUST NOT be treated as independently verified reality merely because it is official. A first-party source MAY be authoritative for claims under the entity's direct control, while remaining non-independent for comparative, performance, leadership, or external-validation claims. Different URLs, publications, translations, syndications, or AI summaries MUST NOT be counted as independent evidence when they derive from the same root source. Every evidence object MUST state which atomic claim it supports, qualifies, contradicts, outdates, or contextualises. The absence of located evidence MUST NOT automatically be represented as proof that a claim is false. Open-world and closed-world evidence conditions MUST remain distinct. Quantitative claims MUST retain numerator, denominator, period, unit, inclusion and exclusion rules, source data, and calculation method. Customer, partner, licence, certification, membership, award, legal, performance, and superiority claims MUST preserve their exact entity, relationship, scope, jurisdiction, time, and evidence status. Publicly discoverable evidence, restricted audit evidence, and non-public evidence MUST remain separately classified. A claim MAY be factually verified through restricted evidence without being publicly retrievable by a consumer AI product. Factual verification and public discoverability MUST remain distinct. Truth Pack claims MUST NOT be added, removed, broadened, narrowed, or reclassified after AI responses are observed unless a new Truth Pack version is created and prior records are preserved. A response claim not covered by the locked Truth Pack MUST trigger a reference-gap process rather than automatic failure or automatic acceptance. Unknown, unsupported, unresolved, contradicted, historical, expired, scope-limited, and restrictedly verified states MUST remain separately visible. The audited entity MAY submit evidence, corrections, and appeals, but MUST NOT act as the sole adjudicator of its own claims. AI systems MAY assist with extraction, normalisation, lineage detection, and contradiction discovery, but MUST NOT serve as the sole final authority for claim truth status. Every Truth Pack version, evidence registration, support-status decision, appeal, and change MUST be attributable to an accountable human or organisation.