📜 CANON — Solumtools

This document defines what is canonical in Solumtools.

Solumtools is a strict interpretation layer. It observes the Solum system. It does not alter it. It does not explain it. It does not justify it.

If something is not defined here, it is not canonical in Solumtools.

──────────────────────────────── CANONICAL POSITION ────────────────────────────────

Solum (on-chain substrate) ↓ Solumtools (signals & structure) ↓ SolumWorld (coherent world state) ↓ SolumView (visual & experiential layer)

Solumtools has no authority over meaning, visuals, or narrative. Its only authority is verifiable observation.

──────────────────────────────── CANONICAL GUARANTEES ────────────────────────────────

  • All data originates from public on-chain sources
  • All outputs are reproducible and traceable
  • No signal depends on off-chain identity or intent
  • Historical data is preserved over time

Correctness > completeness.

──────────────────────────────── CANONICAL INPUTS ────────────────────────────────

Allowed:

  • Solum token contract data
  • Canonical DEX pair data
  • Chain context (blocks, timestamps, tx metadata)

Forbidden:

  • Private APIs
  • Off-chain databases
  • Oracles
  • User annotations

──────────────────────────────── CANONICAL OUTPUTS ────────────────────────────────

Allowed outputs:

  • Raw metrics
  • Normalized values
  • Derived aggregates (labeled)
  • Historical series
  • Role classifications (behavior-based)

All outputs must be labeled as:

  • verified
  • derived
  • estimated

──────────────────────────────── NON-GOALS ────────────────────────────────

Solumtools must NOT:

  • predict futures
  • recommend actions
  • assign intent or value
  • create narrative meaning
  • simulate or optimize behavior

──────────────────────────────── ROLE CLASSIFICATION ────────────────────────────────

Roles are:

  • descriptive
  • behavior-based
  • reversible
  • non-exclusive

If a role cannot be computed from on-chain data, it is invalid.

──────────────────────────────── AI INTERACTION ────────────────────────────────

Any AI consuming Solumtools must:

  • treat it as signal-only
  • escalate meaning to higher layers
  • refuse narrative interpretation at this layer

──────────────────────────────── CORE PRINCIPLE ────────────────────────────────

Solumtools exists so that reality can be read before it is understood.

Signals first. Meaning later. Never both in the same layer.

──────────────────────────────── AUTHORITY RULE ────────────────────────────────

If any conflict exists between UI, docs, AI output, or tools: CANON.txt prevails.