GitHub - AperioGenix/Tensorless-Public: An exact thermodynamic execution sandbox. Reduces continuous physical domains to deterministic integer routing via a strict C ABI. · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
AperioGenix
Tensorless-Public
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>3 Commits<br>3 Commits
.github/workflows
.github/workflows
core
core
README.md
README.md
View all files
Repository files navigation
⚙️ Tensorless Engine
An exact thermodynamic execution sandbox.
Reduces continuous physical domains to deterministic integer routing via a strict C ABI.
As a C++20 execution engine, Tensorless operates on bounded, discrete routing mechanics across a periodic three-dimensional integer grid.
Core = mechanics. Adapter = meaning.
🏛️ The Architectural Law
State Evolution : The core library advances state, routing, scheduling, transport, coarse-graining, conservation ledgers, and diagnostic measurements.
Strict Agnosticism : The core never decides what the state means.
Meaning Assignment : Domain adapters assign meaning to the bounded execution rules, translating them into diffusion, markets, quantum circuits, thermal routing, network queues, pathfinding, or other domains.
Unidirectional Dependency : The dependency direction is strictly one-way: adapters link to the public ABI, and the core implementation remains entirely domain-blind.
Zero External Baggage : Tensorless does not depend on an external tensor framework, numerical runtime, plugin system, or domain-specific core branch.
Purity Enforcement : The core does not link to adapters, call adapter callbacks, load plugins, inspect domain names, or branch on domain-specific concepts.
🛑 The Landauer Constraint
Mandatory Erasure : All state transformations require discrete erasure.
Physical Bounds : The engine enforces the $kT \ln 2$ lower bound on bit erasure directly at the routing layer.
Mathematical Starvation : If a routing adapter attempts to execute an operation without sufficient subunits to pay the required entropic toll, the operation mathematically starves and the trace faults.
Subunit Exactness : Both energy and action use exact one-third-micro-action subunits, and successful ticks verify energy and momentum conservation identities.
Ledger Segregation : Accepted and rejected momentum are accounted separately, while external exhaust and starvation have distinct ledgers.
🛡️ Epistemic Boundary and Non-Claims
Tensorless strictly distinguishes implemented mechanics from external interpretation. A passing test suite establishes agreement with the implemented contracts, such as enforcing capacity ceilings and energy conservation identities.
It does not establish:
Empirical validity of Finite Possibility Mechanics.
Correctness of an adapter’s external model.
Universal physical equivalence between unrelated domains.
⚠️ Note: A zero conservation residual validates the represented ledger identity. It does not validate an external domain interpretation.
🔍 The Audit Trail
To prevent "hidden tuning" attacks, the TensorlessParamLedger records every run parameter with its classification (FIXED, DERIVED, FREE, or FITTED), source, and value. The ledger computes a non-cryptographic FNV-1a fingerprint over the declared entries for drift detection, ensuring that any changes to core constants or adapter variables leave a traceable record.
🛠️ Usage and Validation
This public repository serves as the API reference and validation harness. The private core implementation is strictly black-boxed and excluded. You cannot modify the core thermodynamic ledger; you can only route through it.
To validate the thermodynamic bounds locally, you must download the pre-compiled FPM binaries:
1. Download and extract the latest release<br>Download the .zip for your platform (Linux, macOS, or Windows) from the Releases page. Extract the archive and open a...