Notation and Claim-Label Guide

This book mixes three very different kinds of statement: mathematics that can be checked with a pencil, an operating method that can be adopted by a team, and interpretation that is the author's own. Confusing these is the fastest way to turn a useful analogy into a false claim. To keep them separate, every substantive statement in the book carries one of five labels. The labels appear inline in the text, set in small capitals, and in the electronic edition they are also encoded as semantic classes so that assistive technology can announce them.

CANON. A definition or rule that belongs to the Odisena method and does not change between chapters. Canon statements are fixed vocabulary. When you see CANON, the words mean exactly what they mean everywhere else in the book. The canonical expansions are: RFPA is Recover, Field, Principal, Assumption; AVPT is Attempt, Validate, Preserve, Track; the Infinity Engine is a set of repeated, governed, evidence-preserving cycles, never uncontrolled or literally endless execution.

FACT. A mathematical, scientific, or historical statement that is true independently of this book and can be verified against a cited external source. Facts are not the author's opinion and do not depend on Odisena doctrine. Every FACT that is not elementary carries a citation to a public source in the endnotes.

METHOD. An operational mapping: a place where a mathematical operation or a general engineering practice is put into correspondence with an Odisena method step. A METHOD statement says "here is how you would do this." It is a recommendation for practice, testable by whether it works, not a theorem.

INTERPRETATION. The author's philosophical, organizational, or design inference drawn from the material. Interpretation is honest opinion. It is meant to be argued with. Nothing labeled INTERPRETATION should be cited as fact or as canon.

CASE. A worked example or scenario used to illustrate a point. Cases in this book are either public and cited, or they are privacy-safe abstractions of real Odisena project work, stripped of any private, personal, or security-sensitive detail. A CASE is evidence for how the method behaves, not proof that the method is universally correct.

Mathematical notation follows standard conventions. The Fibonacci sequence is written $F_0,F_1,F_2,\dots$ with the base cases $F_0=0$ and $F_1=1$ unless a chapter explicitly declares a different convention. The recurrence is $F_n=F_{n-1}+F_{n-2}$ for $n\ge 2$. The golden ratio is written $\phi =\frac{1+\sqrt{5}}{2}$. Set membership, summation, and matrix notation are used in the usual way and defined at first use. Where an equation appears in the electronic edition, it is provided as accessible text with an equivalent verbal description.

A single sentence may combine a fact and an interpretation. When it does, the labels are applied to the clauses, and the boundary between them is stated in plain language. The book would rather be pedantic about this than let a metaphor pass as a proof.