These guides provide conceptual background on the key ideas behind Spock GOS. They explain the "why" behind the design decisions and how to think about geometric reasoning.

Understanding Geometric Reasoning

Why Hypervectors?

Traditional symbolic AI represents concepts as discrete symbols that must be exactly matched. Spock uses hypervectors – high-dimensional vectors (512+ dimensions) – to represent concepts as points in a continuous geometric space.

Key advantages:

The Subject–Verb–Object Pattern

Every Spock statement has exactly four tokens:

@varName subject verb object

This uniform structure is not a limitation – it's a feature that enables:

Theory Management

Theories as Knowledge Bases

A theory in Spock is a named collection of facts, rules, and verb definitions. Theories can be:

Think of theories as competing worldviews or knowledge domains that can be combined, compared, and evolved.

Sessions and Symbol Resolution

A session is a temporary working context. When you look up a symbol:

  1. Check local session scope
  2. Check overlaid theories (LIFO order – most recent first)
  3. Check global/default theories

This allows you to experiment with local modifications without affecting persisted theories.

Explainability and Traces

DSL Traces

Every Spock operation produces a DSL trace – a record of exactly what statements were executed. This trace can be:

Unlike neural networks where reasoning is opaque, Spock's geometric operations are fully transparent.

Determinism

Spock is deterministic by design. Given the same input and theories, the same output is always produced. This is essential for:

Numeric Integration

Measured Values with Units

Spock seamlessly combines geometric reasoning with physical quantities:

@massLit 10 HasNumericValue 10
@mass massLit AttachUnit kg
@gLit 9.8 HasNumericValue 9.8
@g gLit AttachUnit m_per_s2
@force mass MulNumeric g  # Results in 98 N

Units are checked for compatibility – you can't add kilograms to meters. This catches errors at reasoning time, not runtime.

Related Documentation