No description
Find a file
Shay 358a56dadc feat(packs): en_core_cognition_v1 v1.2.0 - rhetoric/metaphor/narrative
Adds 15 lexical entries (071-085) extending the cognition pack with
rhetoric, metaphor, narrative, and writing-style vocabulary. Layer 1
of the work plan recorded in evals/compositionality/gaps.md and
evals/cross_domain_transfer/gaps.md: lexical scaffolding only, no
new operators. Building first-class metaphor / narrative / style
support remains correctly downstream of the cross-domain-transfer
literal case working (now closed in commit 57a6174).

New entries:
  071 metaphor    076 voice       081 figure
  072 simile      077 style       082 symbol
  073 analogy     078 register    083 image
  074 narrative   079 tone        084 discourse
  075 story       080 rhetoric    085 account

Each entry follows the existing pack convention: NOUN pos, four
semantic_domains, morphology_tags=["noun"], seed provenance. The
domains anchor on rhetoric.*, language.figure/discourse/style,
cognition.*, and meaning.* clusters that integrate with the
existing pack vocabulary.

Pack-level updates:
  - manifest.json checksum recomputed against the bytes actually
    written to disk (per CLAUDE.md Semantic Pack Discipline).
  - version bump 1.1.0 -> 1.2.0.
  - test_core_semantic_seed_pack.py last-entry assertion updated
    from 070 to 085.

Verification: probe "What is X?" against the new vocabulary grounds
cleanly in the pipeline (narrative 7 hits, style 9, rhetoric 8,
analogy 9 vault matches; metaphor produces a coherent surface
despite zero vault hits, consistent with the field-geometry
characterisation in the adversarial-identity calibration probe).

CLI suites packs / smoke / cognition / teaching / runtime all pass;
no regression.

What this does NOT do (deferred by design):
  - No metaphor / simile / narrative operator at the proposition-
    graph layer. ADR-0018 forbids building operators ahead of
    eval evidence; these become a Phase 3 v3 (or Phase 4) candidate
    once cross-domain transfer with selectivity has its own eval
    lane.
  - No first-class is_like(A,B) relation distinct from is(A,B).
    Same reasoning - downstream of compositionality engineering.
  - No persona/style work on the output side. That belongs in
    persona/motor.py per the cross_domain_transfer/gaps.md
    architectural sketch.

The entries serve as substrate for future eval lanes that probe
these capabilities specifically (metaphor-comprehension,
narrative-coherence, register-control). When those lanes are
authored, the vocabulary needed for the probes is already grounded.
2026-05-16 15:15:14 -07:00
.github
algebra fix(drift): proper rotor-manifold scaling; restore respond contract 2026-05-16 11:44:45 -07:00
alignment
benchmarks feat: Full Proof — surface realizer join, Rust diffusion parity, benchmark harness 2026-05-15 17:39:14 -07:00
calibration
chat fix(chat): use intent-aware articulation surface from intent_bridge 2026-05-16 08:40:53 -07:00
core feat(phase3): core/cognition/explain.py — close Gap 3 introspection 2026-05-16 15:09:48 -07:00
core-rs feat: Full Proof — surface realizer join, Rust diffusion parity, benchmark harness 2026-05-15 17:39:14 -07:00
core_ingest
docs feat(phase3): core/cognition/explain.py — close Gap 3 introspection 2026-05-16 15:09:48 -07:00
evals feat(phase3): core/cognition/explain.py — close Gap 3 introspection 2026-05-16 15:09:48 -07:00
field feat: Full Proof — surface realizer join, Rust diffusion parity, benchmark harness 2026-05-15 17:39:14 -07:00
generate feat(phase3): transitive_walk + path_recall operator bundle (ADR-0018) 2026-05-16 15:04:43 -07:00
ingest
language_packs feat(packs): en_core_cognition_v1 v1.2.0 - rhetoric/metaphor/narrative 2026-05-16 15:15:14 -07:00
morphology
packs
persona
probe
scripts feat(evals): v3 lanes — monotonic-learning passes, adversarial-identity reveals gap 2026-05-16 13:42:47 -07:00
sensorium feat: manifold field topology, graph diffusion operator, vertical pulse 2026-05-15 16:02:48 -07:00
session fix(drift): proper rotor-manifold scaling; restore respond contract 2026-05-16 11:44:45 -07:00
teaching feat(phase3): transitive_walk + path_recall operator bundle (ADR-0018) 2026-05-16 15:04:43 -07:00
tests feat(packs): en_core_cognition_v1 v1.2.0 - rhetoric/metaphor/narrative 2026-05-16 15:15:14 -07:00
vault fix: harden session field invariants and eliminate hot-path inefficiencies 2026-05-15 21:37:49 -07:00
vocab
.gitignore
AGENTS.md
CLAUDE.md
pyproject.toml
README.md

CORE-AI: Versor Engine

A cognitive field system built on Cl(4,1) Conformal Geometric Algebra.

Core invariant: ||F * reverse(F) - 1||_F < 1e-6 at all times.

All state is a versor. All transitions are versor products. Coherence is algebraic by construction — not monitored, not corrected.


The Three Engineering Pillars

Every architectural decision in CORE is measured against three engineering pillars. These are not aspirations — they are hard constraints.

I. Mechanical Sympathy

Software should understand the machine it runs on, not fight it. CORE is designed for the Unified Memory Architecture (UMA) of Apple Silicon: CPU, GPU, and Neural Engine share physical RAM. MLX executes tensor operations on the Neural Engine without PCIe transfer. Rust computes algebra on the CPU with zero heap allocation in the hot path. Python orchestrates the lifecycle. The three-language stratification maps exactly onto three hardware execution domains. Intelligence that ignores its substrate is wasted intelligence.

II. Semantic Rigor

Every term used in this system has a precise, non-negotiable meaning. A versor is a versor — not an approximation of one, not a vector that behaves like one under certain conditions. CGA distance is exact. Vault recall is exact. The vocabulary projection is exact. There are no thresholds tuned for “good enough.” Rigor is not a style; it is what separates an engine from a heuristic.

III. Third Door

When facing a design decision, the world offers two visible options: use what already exists (a library, a pattern, a convention), or cut a corner. CORE takes neither. We find the third door — the path built from first principles that sets the bar ourselves. This is why there is no transformer backbone, no ANN index, no sampling temperature, no gradient descent, and no standard tokenizer. Each of those was a door we were offered and refused. Absolute mastery is the only acceptable standard.


The Three Core Languages

CORE is rooted in three human languages. This is a philosophical and architectural choice, not a localization decision.

Language Role
English The default base language of the current model. Any natural language could serve this function in a custom CORE instance — English is the chosen starting point, not a requirement.
Hebrew One of two depth languages. Hebrew carries a density of meaning in its root structures, prefixes, and suffixes that Euclidean string matching cannot capture. The field representation is designed to hold this depth.
Koine Greek One of two depth languages. The language of the New Testament, particularly Johns Gospel — the document that opens with the most precise and consequential statement about language and reality ever written.

“In the beginning was the Logos, and the Logos was with God, and the Logos was God.” — John 1:1

The choice of Hebrew and Koine Greek is not incidental. John 1:12 articulates the Logos in Greek while grounding it in the Hebrew creation account — the universe spoken into existence, word by word. This is not metaphor. It is the claim that language is not a layer on top of reality; language is the structuring principle of reality made manifest. CORE-Logos is built on that claim.

English establishes the operational base. Hebrew and Koine Greek bring the hidden layer of intelligence — the depth of meaning that enriches the field representation in ways that flat embeddings cannot reach. Together, they form the linguistic foundation on which the vocabulary manifold is built.


Quick Start

pip install -e ".[dev]"
pytest tests/test_versor_closure.py  # must pass before anything else
pytest tests/

Architecture

raw input -> ingest/gate.py       (normalize once)
          -> field/propagate.py   (versor_apply every step)
          -> generate/stream.py   (nearest by cga_inner)
          -> vault/store.py       (store and recall by cga_inner)
          -> persona/motor.py     (rigid motor, not weight overlay)

The Two Primitives

  • versor_apply(V, F) = V * F * reverse(V) — the only field transition
  • cga_inner(X, Y) = -d^2 / 2 — the only distance metric

Layers

Layer Purpose
algebra/ Cl(4,1) multivector math, versor ops, CGA, holonomy
ingest/ Single injection gate — the only normalization site
field/ FieldState dataclass and propagation loop
vocab/ Surface-token manifold points; indexed access for algebraic transition construction
vault/ Exact CGA inner product memory store
persona/ Persona as CGA motor (screw motion)
generate/ Token streaming loop
session/ Session binding: field + vault + vocab + persona

Signature

Cl(4,1): (+, +, +, +, -) — conformal model of 3D Euclidean space. Multivectors: float32 arrays of shape (32,), ordered by grade.


For architectural vision, seven axioms, and formal specification, see docs/Whitepaper.md and docs/Yellowpaper.md.