Skip to content

backlog(B-0196): extend Scale-free axis to include temporal scale-invariance (spatial + temporal both load-bearing) (Aaron 2026-05-05) #1628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AceHack merged 1 commit into from
May 5, 2026
Merged

backlog(B-0196): extend Scale-free axis to include temporal scale-invariance (spatial + temporal both load-bearing) (Aaron 2026-05-05) #1628

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/backlog/P2/B-0196-bigint-and-bignumber-integration-aaron-2026-05-05.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ Aaron 2026-05-05 added four load-bearing properties that any numeric-type additi

1. **DST-safe** -- deterministic simulation testing per Otto-272. Every operation is replayable, deterministic-on-fixed-seed.
2. **Lock-free** -- no mutual exclusion. Compatible with the lock-free runtime.
3. **Scale-free** -- works across scales, small to BigInteger / arbitrary-precision.
3. **Scale-free** -- works across scales, small to BigInteger / arbitrary-precision (SPATIAL axis) AND across timescales, per-tick to multi-decade (TEMPORAL axis). The temporal axis was implicit in the original framing; Aaron 2026-05-05 made it explicit (preserved at `docs/research/2026-05-05-claudeai-cs-is-not-cs-scale-free-in-time-ossified-framework-diagnosis-aaron-forwarded-preservation.md`, PR #1623). The same operation/discipline pattern must hold across both axes: bootstrap razor at conversation scale IS postmortems at project scale IS building codes at field scale IS constitutional reform at civilization scale; same shape, different time-resolutions. Per-tick instrumentation accumulates data normally only available at decades-of-failure scale (the load-bearing claim hidden in the tick-cadence discipline).
4. **DBSP-native** -- retraction-aware. Negative weights compose cleanly through the operation; the operation is consistent under signed-delta application. NOT all numeric types satisfy this trivially: BigInteger as weight type works (ring algebra holds); BigDecimal-with-rounding may NOT (rounding errors don't necessarily compose with negation); float arithmetic explicitly doesn't (commutative-but-not-associative under accumulation).

**Per-candidate acceptance scoring**: each numeric-type candidate (BigInteger, BigRational, BigDecimal, BigFloat) gets scored against all four. Failure on ANY axis means rejection or restriction-to-non-incremental-use. Score-against-the-conjunction is the binding test, not score-against-overflow-prevention-alone.
Expand Down
Loading