Skip to content

Source ledger and reproducibility ​

Last reviewed: September 30, 2026.

Revision ledger ​

SourceInspected revisionProvenance / scope
Sparkles sibling implementation24f3e533987f6e48f260fce0b6fa3870dcb19634Clean tracked tree; unpublished local revision, relevant exact files copied below
nix-on-droid local forkae506ea303c49d1866e92632d68b9a5bb7ce6d1aUnpublished app-ID/module changes; unrelated untracked screenshots excluded
nix-on-droid published baseline55b6449b4582a4ba3ce712543c973360a026db7dPublished upstream commit, used for original scope/README
nix-on-droid-appe87b6091bffa7b6eafb1b59cc7824f5692441cd0Local upstream clone; installer/service source inspected
NNS28d2229a664cbe29e55a051d648a789b6511f735Clean published source; launcher/kernel/bridge/tests inspected, custom VM harness not run
Contributor collector handoff1fa8d36707330435fd6e7ca8e34deec1229fe542Command set matches Pixel logs; executable revision is not embedded in the report
AOSP Virtualization main175a51b30123fa6b02b541f1969665708f7ec2c3Framework, native demo, permission, pvmfw/Microdroid source; main is not universally shipping firmware
AOSP Android 16 release46351de83cd509bc9a9fee8fc99b07fcc0cdd0bdandroid-16.0.0_r3 resolved to commit; custom image class checked in release tree
nixos-avfd0a62c3f64b45a39570fde31a3a490b214bf19eeGuest and image construction; default owner is Android Terminal
Podroidce0121896b2895637ab1f656cbb0d75fa2874489Independent managed app engine; private API use examined
Gunyah device guide61ac570c2d467274d1d7d73605dcc685af6945b8Rooted Lenovo demonstration, protected variant and networking
DroidVM5c896915789294e3dbb9af81d6a53ee5f436887bCurrent backend and device registry, not locally run
Termux PRootab2e3464d04483b98a0614b470f3f8950d5a6468Exact PRoot revision pinned by inspected nix-on-droid expression
Nix upstream1ed54a0fd62da96d4f5e9c806555861e46f65341Local chroot-store documentation and run.cc equal upstream files at this revision

External citations in the deep dives point at exact implementation paths. Official Android policy documentation is a living source, reviewed on the date above. The QEMU and Nix manuals provide adjacent concepts rather than tested Android implementations.

Exact local grounding ​

Copies preserve source headers and original contents; they are not maintained implementations or standalone CI examples. Use them to inspect the particular local revision rather than assume a moving sibling checkout still matches it.

Source path in original checkoutCatalog copy
apps/terminal/src/session.dSession snapshot
apps/terminal/src/android_app.dAndroid host snapshot
apps/terminal/android/AndroidManifest.xmlManifest snapshot
docs/apps/terminal/android.mdImplementation notes snapshot
docs/specs/terminal/android.mdSpecification snapshot
modules/build/config.nixPackage configuration
modules/environment/login/login.nixOuter login
modules/environment/login/login-inner.nixInner login
modules/environment/nix.nixNix settings
modules/environment/networking.nixResolver settings
pkgs/nix-directory.nixStore bootstrap
pkgs/bootstrap.nixBootstrap archive
pkgs/proot-termux/default.nixPRoot derivation

The source paths above are relative to the original checkout. All thirteen snapshots were checked for byte equality against their original files. Text suffixes protect them from code formatters; local snapshot links intentionally bypass VitePress page resolution because these are source artifacts.

Runnable evidence ​

ProgramDemonstratesCI / hardware boundary
ELF loader readerReal PT_INTERP parsing and loader pathsOrdinary Linux host
Namespace probeActual namespace syscall and unchanged parentCapability-dependent; skips on rejection
Device inventoryExplicitly selected hardware inventoryNo serial means no hardware contacted
App-domain probeReal UID, SELinux/seccomp state, namespace and socket attemptsLinux CI plus Bionic Android cross-build and UI execution

Device validation records the commands, privilege context, failures, cleanup and limitations. Documentation CI is not presented as an Android integration test.

The contributor collector adds packaged root-ADB AVF/NNS inventory with selected existing-process views, bounded commands/output, private report directories and capability-aware CLI presentation. It also skips without an explicit device selection. Its real-device reports remain dated evidence, not CI assertions that every Android host has NNS or AVF.

Contributor device provenance ​

The Pixel 7 Pro page records the collection month, 28-record manifest audit and publication transformations. Nine normalized complete logs, three logs with non-epoch file timestamps explicitly omitted and seven marked excerpts retain relevant device/AVF/NNS evidence. Generic 1970-01-01 timestamps are retained. Exact collection time, the private archive digest, transient resource usage, full private mount/process inventories, the original archive and its manifest are not published.

The installed NNS module reports 3.1.0, versionCode=4, and matching public/module launcher hashes. That is deployment metadata, not an exact source/kernel/policy revision. The source revision ledger above remains authoritative for inspected implementation code; it must not be substituted for missing device build provenance. The Pixel report captures existing app-UID Zsh, root Nix and runit processes, but not a newly executed guest, Nix workload or Sparkles session.

Sources ​