ARKNET did not begin from a blank repository. It began from the StarNet v0.10.7 baseline and was forked, reverse-engineered, decoupled and substantially reworked into a separate Tauri desktop orchestration system. This page publishes that provenance and the current verification limits instead of hiding them.
Syntax validation for every changed JavaScript/MJS/CJS file present in the audit tree
JSON parse for package manifests and Tauri configuration
brand-wordmark-mask: 21 assertions
diagnostics-support-email: 15 assertions
website:stage:check
test:fast progressed through 72 steps before dependency availability stopped step 73
72 completed steps are not presented as a full-suite pass.
PUBLIC RELEASE BLOCKERS
WHAT IS NOT CLAIMED
Inherited StarNet Station artwork/sprites remain a redistribution blocker until replaced with ArkNet-owned assets.
No ArkNet public release repository, updater host, signing identity or installer feed is claimed.
Full clean dependency + test proof still requires the Windows development environment.
Some legacy starnet.* state/protocol identifiers remain intentionally for compatibility and require a migration plan.
02 / SUBSTANTIAL FORK WORKAUDITED AREAS
UPSTREAM COUPLINGDISABLED / DECOUPLED
Inherited managed billing/update/release dependencies were disabled rather than impersonated.
RUNTIMEDYNAMIC LOOPBACK SIDECAR
Tauri allocates a free local port and binds the sidecar lifetime to the desktop process.
SECRETSOS KEYCHAIN DIRECTION
BYOK provider credentials are designed for OS keychain storage and token-guarded sidecar updates.
MIGRATIONREAD-OLD / PRESERVE STATE
Legacy StarNet app-data roots are treated as migration sources to avoid silently losing existing workspace state.
03 / PROVENANCE + NATIVE RUNTIME PROOF
FORK LINEAGE YOU CAN TRACE.
Build 212 publishes the exact upstream anchor, current snapshot HEAD, baseline-to-working-tree delta and selected native-shell runtime code. Release blockers from the supplied audit remain visible.
Preserves the supplied audit’s verification record and unresolved release blockers instead of converting partial test progress into a full-suite claim.
PROVENANCE BOUNDARY: ArkNet is a substantial derivative fork, not a from-zero codebase. The working-tree snapshot is development evidence, not a signed public release.
ARKNET is a substantial development fork, not an original-from-zero codebase. Upstream license/notice obligations and compatibility identifiers are retained where required. The current state is development-ready for continued work, not represented here as a cleared public commercial release.