:: This≠That Semantic Comparison and Intent Difference API

HOME MEANINGSYSTEM
KEYS 🤖


: This vs That Semantic Comparison

This≠That™ enables users and AI systems to deterministically recognise when the flow of intent has changed between two files, even when they appear close in wording or code.


It determines whether two inputs are meaningfully the same, or meaningfully different, under explicit constraints — providing a reliable, auditable way to enforce semantic distinction in complex workflows where correctness depends on the precise intent, not a resemblance.


It does not generate content. It enables users to quickly notice any alterations in meaning, and for AI workflows to move beyond surface similarity and establish any semantic distinction, equivalence, or conflict — before decision execution or storage occurs. This≠That Meaning API is intended for use where “almost the same” is simply not acceptable.


➤ This standalone Maenen website demonstrates the user-facing function: [ www.compareThisThat.com ]

➤ This standalone Maenen website embeds its capability: [ www.MeetMeeting.com ]


Similarity sees closeness. This≠That™ reveals meaningful impact.

Endpoint. "Compare Core Lite" version

POST v1/meaning/compare

: What Is This≠That™ API?

This≠That provides semantic comparison under constraint. It answers questions such as:
  • Are these two inputs meaningfully equivalent?
  • Has the intent changed anywhere in any material way?
  • Is this substitution allowed under defined rules?

Rather than returning a similarity score alone, This≠That returns a bounded semantic judgement suitable for downstream enforcement.

If shifts in intent are not caught early, small inflections can greatly alter the downstream behavioural trajectory.

: Examples

01  Policy Drift
THIS: Access is permitted for verified users during business hours.
THAT: Access is permitted for users during business hours.
Outcome: ≠ ❌ Trust boundary removed


02  Legal / Contractual Precision:
THIS: Payment must be received before services commence.
THAT: Payment should be received before services commence.
Outcome: ≠ ❌ Obligation becomes recommendation


03  Code-Level Intent (subtle refactor)

THIS:

if user.is_admin:
    grant_access()

THAT:

if user.is_admin or user.is_staff:
    grant_access()
Outcome: ≠ ❌ Access boundary expanded / Privilege scope widened

04  Paraphrase
THIS: Data will be retained for 30 days.
THAT: Data is stored for a period of 30 days.
Outcome: ≠ ✅ Meaningfully Equivalent


05  Agent Instruction Drift
THIS: Execute the task only after validation succeeds.
THAT: Execute the task after validation.
Outcome: ≠ ❌ Conditional safeguard removed

: The Problem Solved

➤ Humans and AI systems see similarity as sameness:
  • Paraphrases blur into equivalence
  • Revisions overwrite intent
  • Constraints drift silently
  • Comparisons lack explainability
 ➤ In high-stakes workflows, this leads to:
  • Incorrect reuse
  • Broken policies
  • Unsafe substitutions
  • Untraceable decisions

When meaning matters, any differences must be made explicit.

: About Code Artefacts

➤ This≠That can evaluate:
  • Semantic intent shifts in code
  • Permission boundary changes
  • Obligation weakening or strengthening
  • Scope expansion or contraction
  • Logical condition changes
  • Removal or addition of constraints
 ➤ It does not:
  • Refactor code
  • Parse full AST trees
  • Optimise structure
  • Execute or validate code at runtime
  • Guarantee runtime behavioural equivalence

It answers: “Is the meaning materially the same?”
NB. It does not answer: “Is this transformation structurally and behaviourally valid?”

: Beyond Typical Text Diff

Traditional diff tooling compares surface forms—characters, tokens, lines and structure. Those can state what has superficially changed, but not what it means or whether the meaning or intent has changed.

This≠That™ operates at the Maenen level of meaning. It evaluates whether two inputs are:

  • Meaningfully equivalent or meaningfully different,
  • or in conflict under explicit constraints.
  • Unsafe substitutions.
  • Untraceable decisions.

➤ Apparent large changes in detail may be irrelevant, whereas an overlooked slight change could be semantically significant.
➤ This≠That is designed to make the distinction explicit.


: The Diff Distinction

Text Diff Tools This≠That™ API
Surface Comparison Semantic Comparison
Syntax-Aware Meaning-Aware
Change Detection Constraint-based Judgement
No Notion of Intent Explicit Intent Evaluation
Not Auditable Receipt-Backed

Diff detects surface change. This≠That determines whether the change matters.

: Use Cases

➤ This≠That is suited for workflows such as:
  • Policy and rule enforcement
  • Prompt and instruction validation
  • Version comparison and drift detection
  • Pre-compression / pre-storage checks
  • Pre-handover pipelines
  • Rapid comprehension of updated contracts and documents
  • Guarding agent actions against substitution errors
➤ This≠That provides semantic comparison under constraint. It answers the question by:
  1. Accepts two or more semantic inputs
  2. Applies comparison constraints
  3. Determines equivalence, difference, or conflict
  4. Returns a structured result with a receipt

This deterministic API is designed to be predictable, auditable, and fast for you to discern "what changed where?"

: Modular API Pipeline (examples)

This≠That can be used standalone to verify any shift in intent between documents, after normalisation to ensure semantic constraints are respected before downstream reuse.


Inception  ?  This≠That  └──▶  ParsAIble Compression  └──▶  WaveInform → X → WaveReturn  → → →
 → → →  WaveInform → X → WaveReturn  →  This≠That  └──▶  ParsAIble Compression

: Results & Receipts

➤ This≠That API returns:
  • A comparison outcome
  • Optional explanatory signals
  • A receipt documenting the evaluation
 ➤ The receipts support:
  • Audit & Compliance
  • Debugging and Review
  • Downstream Enforcement Logic

- All results are bounded and explicit.


This vs That API
  Similarity This≠That™
 
Measures: Closeness Semantic Meaning Intent
Output: Score Decision
Constraints: ❌ ✅
Determinism: ⚠️ ✅
Audit Trail: ❌ ✅

: Security & Guardrails

  • Strict input validation
  • Bounded comparison scope
  • Deterministic evaluation paths
  • No free-form generation
  • No external data access


: Support

For technical issues or questions, use the contact options below. Full support and service-level agreements are not offered during the beta trial, though your query or comment will be carefully considered. Please include:

  • A short description of the issue
  • Example payloads (if possible)
  • The receipt from the relevant request
- Receipts significantly reduce back-and-forth and speed up diagnosis.


: v0.1 Beta Usage Notice

This API is currently available in limited v0.1 beta. Free assessment keys are subject to rate cap and payload limits.
No uptime or performance guarantees are implied. Features and behaviour may change between versions.


: Versioning

This documentation applies to:


API version: v0.1 (beta)

FOR-THE-DREAM-IS-WITH-INTEGRITY-FOR-THE-FREEDOM-OF-INTELLIGENCE