nx_const.nx

nx_const.nx -- meta source of truth for universal constants. license_tier: ORIGINAL genealogy_id: nishi-substrate/constant-registry CARDINAL: constants that are SHARED across multiple modules and are UNIVERSAL (not algorithm-specific or application-tunable) live in ONE place. Per user 2026-05-19: "lets get a meta source of truth or whatever its called for values that should be like pi and calculations and all that as we build bits up so that these values arent scattered everywhere" What belongs HERE (in nx_const.nx): - Mathematical constants: pi, e, ln(2), sqrt(2), golden ratio - Alphabet encodings: DNA 2-bit codes, ASCII for nucleotides - Universal sentinels: NEG_INF, POS_INF, sentinel bytes - Common ASCII: digits, whitespace, punctuation What stays LOCAL to its module (NOT in nx_const): - Algorithm-spec constants: SHA-256 K[64], ChaCha20 sigma, AES S-box, P-256 curve params. These are PART OF the algorithm spec; moving them away from the implementation obscures provenance (license_tier + genealogy_id audit). See feedback-defer-ethics + Cardinal 11. - Application-tunable values: default gap penalties, k-mer sizes, window widths. These are user choices per workload, not universals. - File-format magic: opcode tables, struct offsets, ISA codes. Floating-point policy: The substrate is no-float (Cardinal 6 + crypto modules). Math constants are stored at fixed-point scale 1e18 (suffix _x1e18). Callers divide by NX_FIXED_SCALE_1E18 or use the integer-arithmetic helpers to be added in nx_fixed_point (G3+). Scale 1e18 fits in i64 (max ~9.2e18) and preserves all 18 decimal digits of the underlying transcendental, which exceeds IEEE-754 double precision. Discovery: docs/NISHI_CONSTANT_REGISTRY.md explains the policy + how to propose new entries. Any new constant that appears in two modules belongs here; refactor pull both into an import of this