Examples

Concrete paths

Small examples with exact identities.

These bounded runs expose their inputs, retained reports and limitations. They are not performance, scale or production-readiness claims.

The five versioned archives contain MIT-licensed example source and notices, without AxolDB binaries. Reports retain the product builds they actually used. See official downloads for availability andrelease status for current package scope.

External integration

DEAP knapsack

Restore a complete generation-20 checkpoint, then continue two parameter paths in new Python processes.

Application-level provenance; not native Fork lineage.

Archive SHA-256

ddae83bd983ba6f586912254d86a87a1f9b7c287a557b157549955670ea1b95a

External integration

Mesa Schelling model

Restore stable agents and simulation state, then compare two continuations from the same saved step.

Application-level provenance; not native Fork lineage.

Archive SHA-256

12f9d6fff641b84cbaa79438496c038c99dc11cedf3d7c851a5b2131b494a439

Local qualification bundle

Native integer mutation

Import three integers, run the built-in increment operator and inspect persisted source, result and complete native lineage.

Retained Linux mutation and restart/reload evidence is bound to its original run bundle; consult release status for current package scope.

Archive SHA-256

91ce5e3f1d7009b545c94131e55ad7c8cdcefc2bc162aa9bd852f2f7290ebf47

Local qualification bundle

Native binary crossover

Run binary midpoint crossover and verify the child against the actual persisted order of its two parents.

Verified on the recorded linux-x64 bundle; consult release status for current package scope.

Archive SHA-256

fcd7a94f8a9fc7548d05f9f4d403d9a60fc44ccd746630b595123665347cdcfd

External analysis

Quanteda dictionary comparison

Compare two rule versions over one small GOV.UK benefit-guide corpus and trace the two changed sentence labels.

Quanteda analyzes text; AxolDB stores and links source, rules and results.

Archive SHA-256

2b936f9b0830637c33f2769251d82e5ba939c27a110968a84f4704f5beaf7bad

Operation boundary

Population → Generations → explicit continuation

  1. Create an empty Population from an owner-prepared Contract selection and retain its initial Generation ID.
  2. Insert a prepared typed Genotype. Insertion stores a value; it does not change membership.
  3. Submit one explicit Transaction containing the complete desired membership and exact expected parent.
  4. Retain the returned Generation ID, read that state and Query it with the required authority.
  5. Continue through a native Fork only when the supported Evolution lifecycle owns that transition. External integrations retain their source relationship in application manifests instead.