Zorp source interpretation

Zorp Intelligence

Repo and state-jam monitoring context for separating current Nockchain authority from Zorp lineage, Jock authoring signals, NockApp runtime history, and metadata-only state artifacts.

Zorp API Monitor State Jams

Repos

Core Active

Lineage Archived

Nockchain

33ba97b1e206

Source Authority

protocol

canonical-protocol-authority

nockchain/nockchain

Use the canonical Nockchain monorepo and Tier 0 docs for protocol, runtime, wallet, fakenet, PMA, and release claims. Treat zorp-corp/nockchain as a legacy redirect, not a separate current repo.

lineage

lineage-and-authoring-signal

zorp-corp

Use Zorp repos to understand Nockchain lineage, Jock/Nock authoring, NockApp history, runtime persistence history, and proof-adjacent signals.

state

state-artifact-provenance

https://drive.google.com/drive/folders/1aEYZwmg4isTuYXWFn9gKPl92-pYndwUw

Use the Drive folder as external state-jam/checkpoint provenance only; never treat it as VESL collaboration material or store raw state artifacts.

canonicalRelocation

zorp-corp/nockchain redirects to nockchain/nockchain

legacyUrl

https://github.com/zorp-corp/nockchain

canonicalUrl

https://github.com/nockchain/nockchain

decisionRule

Use nockchain/nockchain Tier 0 docs for protocol claims.

decisionRule

Treat zorp-corp/nockchain as a legacy redirect to nockchain/nockchain.

decisionRule

Use Zorp repos for lineage, authoring, fixture, and ecosystem-direction signals.

decisionRule

Use the Drive folder only as metadata-backed state-jam provenance, not as VESL evidence.

decisionRule

Promote a source into receipts only after recording repo, commit/build, artifact identity, and network context.

Monitor Brief

Zorp is useful as Nockchain lineage, language-authoring signal, and state-artifact provenance. Current protocol and operational authority stays with nockchain/nockchain and its Tier 0 docs.

riskFlag

legacy-repos-are-lineage-not-authority

riskFlag

zorp-corp-nockchain-redirects-to-canonical-nockchain-org

riskFlag

state-jam-folder-is-metadata-only

riskFlag

forked-tooling-is-low-signal-until-used-by-nockchain

Priority Sources

source

zorp-corp/jock-lang

source

zorp-corp/nockapp

source

zorp-corp/sword

source

nockchain/nockchain

Drift Check

Compares the pinned Zorp org repository inventory against GitHub metadata while preserving the State Jam folder as metadata-only provenance.

command

npm run check:zorp-org-drift -- --json

testCommand

npm run test:zorp-org-drift-check

sourceUrls

https://api.github.com/orgs/zorp-corp/repos?per_page=100&sort=updated&type=public, https://github.com/zorp-corp, https://drive.google.com/drive/folders/1aEYZwmg4isTuYXWFn9gKPl92-pYndwUw

highlightedCompareField

defaultBranch

compareFields

name, url, description, archived, fork, language, updatedAt, pushedAt, stars, openIssues, defaultBranch

Source Notes

jock-language-preview

zorp-corp/jock-lang

Jock is a developer preview language for producing Nock programs. Treat it as an authoring and fixture-design signal, then verify any executable behavior against canonical Nockchain and NockApp sources.

sourcePath

README.md

sourceSha

c07a67bbf4f1352c3fafb6af6063a0bbc1641e50

sourceSignals

jock-compiles-to-nock, developer-preview-language, hoon-compiler-dependency, nockapp-architecture-dependency

targetSurfaces

nockupValidation, generatedLabReports, fixtureDocs

nockapp-poke-peek-lineage

zorp-corp/nockapp

The archived NockApp repo is archived lineage for pure state machines, persistence, and the poke/peek interface. Use it to explain concepts while current operational claims stay anchored to nockchain/nockchain.

sourcePath

README.md

sourceSha

bf9f4503ad4b50e76d89caa882115bab952d5a00

sourceSignals

pure-functional-state-machines, poke-peek-interface, automatic-persistence, choo-hoon-compiler-lineage

targetSurfaces

nockchainNockappAtlas, nockchainNockappSourceTrace, fixtureDocs

sword-persistence-lineage

zorp-corp/sword

Sword is runtime persistence lineage. It can improve PMA/state-jam vocabulary, but current durability, recovery, and PMA behavior must come from the Nockchain monorepo.

sourcePath

README.md

sourceSha

9756a661f674c502e12a9140c3f865901fab02a6

sourceSignals

automatic-persistence-lineage, archived-runtime-reference, nock-runtime-history

targetSurfaces

stateJamRegistry, nockchainNockappAtlas, nockchainWatch

knock-formal-semantics

zorp-corp/knock

Knock is a K Framework implementation of the Nock virtual machine with run/prove examples. Use it as formal-semantics context for Nock reasoning, never as current Nockchain protocol authority.

sourcePath

README.md

sourceSha

e57ee1ff7fa7fbd7f0e7f85191dab5213be6938d

sourceSignals

k-framework-nock-semantics, symbolic-proof-examples, nock-vm-formal-evaluation, forked-formal-semantics-reference

targetSurfaces

nockchainKnowledgeSpine, nockchainProtocolTrace, docsResearch

sppark-proof-primitives

zorp-corp/sppark

sppark is proof-performance tooling for SNARK/STARK primitives such as MSM and NTT. Treat the Zorp fork as proof-adjacent ecosystem signal until canonical Nockchain or bridge code consumes it directly.

sourcePath

README.md

sourceSha

ca1648796550751efcfab335e5c12ecc35e3c1af

sourceSignals

zero-knowledge-performance-primitives, msm-ntt-accelerator-templates, cuda-rust-ffi-performance-context, forked-proof-tooling-reference

targetSurfaces

trustComputeBenchmarks, nockchainImpactQueue, docsResearch

Operator Actions

Treat zorp-corp/nockchain as a legacy URL that redirects to nockchain/nockchain before making protocol claims.

Promote Nockchain release, protocol-doc, fakenet, PMA, wallet, or libp2p changes into receipt fields before relying on test output.

Treat zorp-corp/jock-lang changes as fixture-authoring signals and zorp-corp/nockapp or zorp-corp/sword changes as historical context.

Inventory Drive state-jam artifacts by source URL, filename, size, hash, network, height or event boundary, and producing Nockchain build before trusting them.

Escalate new Zorp repos only when they affect Nock authoring, NockApp fixture generation, PMA/state, proofs, or Nockchain operations.

State Artifact Boundary

driveCorrection

state-jam folder, not a VESL folder

classification

Zorp/Nockchain state-jam folder, not a VESL folder. Treat as chain/runtime bootstrap metadata only.

artifactPolicy

metadata-only

driveFolder

https://drive.google.com/drive/folders/1aEYZwmg4isTuYXWFn9gKPl92-pYndwUw

Watch Matrix

canonical-runtime

Refresh upstream commit, release, protocol, PMA, fakenet, wallet, and bridge receipt fields before treating new evidence as comparable.

canonical-runtime

Canonical runtime

escalation: immediate

nockchain/nockchain

trigger

nockchain release/build tag change

trigger

Tier 0 protocol, architecture, workflow, or decision doc change

trigger

PMA, state-jam, checkpoint, fakenet, mining, wallet, libp2p, or bridge change

action

Refresh upstream commit, release, protocol, PMA, fakenet, wallet, and bridge receipt fields before treating new evidence as comparable.

action

Run Nockchain watch, release asset, protocol trace, operations, wallet, sync/gossip, and state-jam checks.

fields: nockchainCommit, nockchainBuild, protocolTrack, stateJamFingerprint, walletEndpointMode

authoring-fixtures

Authoring fixtures

escalation: review

zorp-corp/jock-lang

trigger

Jock language/compiler change

trigger

new Nock authoring example

trigger

fixture-shaping parser or codegen change

action

Review fixture authoring assumptions and decide whether Jock changes should become new NockApp lab templates.

action

Keep protocol claims anchored to nockchain/nockchain even when authoring examples come from Jock.

fields: sourceRepo, sourceRepoPushedAt, fixtureAuthoringSignal

lineage-runtime

Lineage runtime

escalation: context-only

zorp-corp/nockapp, zorp-corp/sword

trigger

archived NockApp doc or example clarification

trigger

runtime persistence lineage note

trigger

poke, peek, or state-machine semantic clarification

action

Use as explanatory lineage for receipts and docs, not as current operational authority.

action

Promote only clarifications that improve NockApp fixture language or PMA/state interpretation.

fields: lineageSource, lineageInterpretation

proof-and-semantics

Proof and semantics

escalation: watch

zorp-corp/knock, zorp-corp/sppark

trigger

formal Nock semantics change

trigger

proof or accelerator tooling change

trigger

benchmark or verification primitive change

action

Evaluate whether semantics or proof changes should become compute/proof benchmark evidence.

action

Keep any proof-adjacent claim separate from Nockchain protocol authority until upstream Nockchain uses it.

fields: proofSource, semanticSource, benchmarkContext

low-signal-tooling

Low-signal tooling

escalation: defer

zorp-corp/create-pull-request, zorp-corp/setup-bazel, zorp-corp/rust-cache, zorp-corp/criterion-compare-action, zorp-corp/mnist-hoon

trigger

automation fork update

trigger

CI or benchmark utility change

trigger

old Hoon example update

action

Ignore unless Nockchain or Zorp starts relying on the tooling for builds, benchmark evidence, or fixture generation.

action

Record as ecosystem context only when it changes reproducibility or reporting assumptions.

fields: toolingSource, reproducibilityContext

Monitor Review Contract

sourcePolicy

zorp-nockchain-source-authority

requiredEvidenceFields

upstreamSourceUrl, observedAt, sourceAuthority, repoFullName, commitShaOrArtifactHash, affectedPaths, receiptImpact, operatorAction, nocksperimentalSurface, verificationCommand

highlightedEvidenceField

nocksperimentalSurface

reviewRule

Every Zorp monitor finding must classify the source before recommending code, docs, receipt, or runbook updates.

reviewRule

Canonical Nockchain commits, releases, build tags, and Tier 0 docs outrank Zorp lineage or authoring repositories.

reviewRule

State-jam findings remain metadata-only until artifact identity, network context, and producing build are recorded.

reviewRule

Lineage and authoring findings can update fixtures or docs only after naming a target Nocksperimental surface and verification command.

canonical-nockchain

Canonical Nockchain

escalation: immediate

Current protocol, runtime, wallet, mining, bridge, or build evidence can become stale.

targetSurfaces

nockchainWatch, nockchainKnowledgeSpine, nockchainProtocolTrace, nockchainReleaseAssets

requiredAction

Refresh upstream commit/build provenance and rerun the affected Nockchain atlas or trace tests before accepting new receipts.

zorp-authoring

Zorp Authoring

escalation: review

Fixture generation or explanation can drift even when current Nockchain protocol is unchanged.

targetSurfaces

nockupValidation, generatedLabReports, fixtureDocs

requiredAction

Review fixture assumptions and promote only reusable Jock/NockApp authoring patterns into Nocksperimental tests.

zorp-lineage

Zorp Lineage

escalation: context-only

Historical runtime, persistence, or semantic notes can improve explanation but should not override canonical Nockchain sources.

targetSurfaces

zorpUpstream, nockchainWatch, docsResearch

requiredAction

Update lineage notes only when they clarify NockApp fixture language, PMA/state interpretation, or Nock semantics.

state-artifact-provenance

State Artifact Provenance

escalation: immediate

Bootstrap artifacts can change local replay boundaries, balances, peer state, and support-bundle interpretation.

targetSurfaces

stateJamRegistry, localFakenetEvidence, nockchainOperationsAtlas

requiredAction

Inventory source URL, filename, hash, size, network, height or event boundary, and producing build without storing raw artifacts.

low-signal-tooling

Low-Signal Tooling

escalation: defer

Tooling updates are ecosystem context unless they affect reproducibility, benchmark reports, or fixture generation.

targetSurfaces

docsResearch, nockchainWatch

requiredAction

Defer until Nockchain or a high-signal Zorp repo starts relying on the tooling for builds, tests, or evidence.

Collaboration Flywheel

cycleId

zorp-monitor-to-fixture-flywheel

cadence

six-hour monitor plus manual source-authority review before product changes

highlightedFlywheelId

zorp-monitor-to-fixture-flywheel

highlightedEvidenceFields

reviewDecision, collaborationNoteUrl

highlightedForbiddenField

rawStateJam

requiredEvidenceFields

upstreamSourceUrl, observedAt, sourceAuthority, repoFullName, commitShaOrArtifactHash, affectedPaths, reviewDecision, nocksperimentalSurface, verificationCommand, collaborationNoteUrl

forbiddenFields

rawStateJam, rawPmaSlab, walletSeedPhrase, privateSigningKey, tenderlyAccessKey, r2TestToken

Turn Zorp and canonical Nockchain upstream changes into reviewed Nocksperimental product slices, fixtures, receipts, and ecosystem collaboration notes.

observe-upstream

Observe upstream

output

zorpMonitorFinding

targetSurfaces

zorpMonitorRunbook, nockchainWatch

Capture source URL, pushed/updated timestamp, commit or artifact identity, and whether the source is canonical, lineage, authoring, or state-artifact provenance.

classify-authority

Classify authority

output

sourceAuthorityDecision

targetSurfaces

zorpUpstream, nockchainKnowledgeSpine

Apply the source-authority matrix before changing tests or receipts, with canonical Nockchain outranking Zorp lineage repos for protocol claims.

route-product-slice

Route product slice

output

nocksperimentalSurfacePlan

targetSurfaces

nockchainImpactQueue, nockchainRustSourceGuide, nockupValidation

Choose the smallest evidence surface that should change: watch board, Rust/source atlas, fakenet evidence, state-jam registry, nockup validation, or docs.

verify-receipts

Verify receipts

output

verificationEvidence

targetSurfaces

registryCheckpoint, verificationIndex

Run the targeted test, registry checkpoint check, lint/build gates when code changed, and keep raw keys or state artifacts out of public payloads.

share-collab-note

Share collaboration note

output

collaborationBrief

targetSurfaces

docsResearch, ecosystemAlignment, veslEvidenceBridge

Summarize what changed, what Nocksperimental learned, and what Zorp/Nockchain collaborators could reuse without leaking private artifacts.

canonical-runtime-refresh

nockchain/nockchain

authority

canonical-protocol-authority

targetSurfaces

nockchainWatch, nockchainProtocolTrace, nockchainRustSourceGuide, registryCheckpoint

Update current protocol, release, runtime, fakenet, mining, wallet, bridge, PMA, and receipt assumptions.

authoring-fixture-review

zorp-corp/jock-lang

authority

lineage-and-authoring-signal

targetSurfaces

nockupValidation, generatedLabReports, fixtureDocs

Review higher-level Nock authoring patterns that could become reusable NockApp fixtures.

lineage-language-review

zorp-corp/nockapp

authority

lineage-and-authoring-signal

targetSurfaces

nockchainNockappAtlas, nockchainNockappSourceTrace, docsResearch

Preserve historical poke, peek, pure state-machine, and persistence vocabulary without using archived code as current authority.

pma-runtime-vocabulary-review

zorp-corp/sword

authority

lineage-and-authoring-signal

targetSurfaces

stateJamRegistry, nockchainPmaSourceTrace, nockchainRuntimeSafety

Translate runtime persistence lineage into better PMA and state-jam explanation while validating behavior against current Nockchain.

state-jam-provenance-inventory

https://drive.google.com/drive/folders/1aEYZwmg4isTuYXWFn9gKPl92-pYndwUw

authority

state-artifact-provenance

targetSurfaces

stateJamRegistry, localFakenetEvidence, nockchainOperationsAtlas

Inventory state-jam metadata for reproducible fakenet/bootstrap work without storing raw artifacts.

Signal Layers

protocol-runtime

Protocol and runtime

Current Nockchain behavior belongs to the canonical Nockchain monorepo, not legacy Zorp repos.

nockchain/nockchain

language-authoring

Language authoring

Jock is the clearest public signal for higher-level Nock application authoring.

zorp-corp/jock-lang

nockapp-lineage

NockApp lineage

Archived NockApp material helps explain poke/peek/state-machine concepts but is not operational authority.

zorp-corp/nockapp

runtime-lineage

Runtime lineage

Sword is useful history for persistence and Nock runtime ideas; current PMA behavior lives in Nockchain.

zorp-corp/sword

formal-semantics

Formal semantics

Knock can inform Nock semantic reasoning but should not override Nockchain Tier 0 docs.

zorp-corp/knock

proof-tooling

Proof tooling

Proof-adjacent changes may matter later for compute/proof benchmarks and bridge evidence.

zorp-corp/sppark

Repository Watch

nockapp-lineage

zorp-corp/nockapp

NockApp runtime lineage for pure state machines, poke/peek interpretation, persistence boundaries, and receipt language.

updated 2026-06-05T18:09:10Z / pushed 2025-04-10T15:31:01Z

language-authoring

zorp-corp/jock-lang

Track high-level Nock application authoring and compiler-facing changes that may shape future NockApp fixtures.

updated 2026-04-05T19:51:30Z / pushed 2026-03-12T02:29:17Z

runtime-lineage

zorp-corp/sword

Historical runtime persistence context only; use current nockvm/Nockchain code for operational claims.

updated 2026-02-19T13:42:24Z / pushed 2025-01-29T02:09:46Z

formal-semantics

zorp-corp/knock

Formal-semantics reference for Nock reasoning; do not treat it as current Nockchain runtime authority.

updated 2025-12-09T12:01:03Z / pushed 2023-04-01T21:27:32Z

proof-tooling

zorp-corp/sppark

Watch for proof-system and accelerator-adjacent changes that could matter to future compute/proof benchmarks.

updated 2025-06-23T22:02:02Z / pushed 2025-06-06T10:32:46Z

build-tooling

zorp-corp/setup-bazel

Low signal unless Zorp build/deploy workflows begin to reuse Bazel action changes.

updated 2025-05-02T01:30:09Z / pushed 2025-04-28T00:44:58Z

automation-tooling

zorp-corp/create-pull-request

Low signal, but monitor for upstream automation patterns that affect repo sync or generated update PRs.

updated 2025-04-30T18:08:29Z / pushed 2025-04-29T12:41:35Z

hoon-examples

zorp-corp/mnist-hoon

Old Hoon example material; useful only as a fixture inspiration source, not protocol authority.

updated 2024-08-24T00:26:03Z / pushed 2024-05-31T12:31:35Z

ci-tooling

zorp-corp/rust-cache

Low signal unless Nockchain build cache behavior becomes relevant to reproducible evidence.

updated 2024-08-13T15:29:04Z / pushed 2024-08-13T13:51:30Z

benchmark-tooling

zorp-corp/criterion-compare-action

Potential lineage for benchmark diff reporting if Nocksperimental adds performance evidence receipts.

updated 2024-08-13T15:28:44Z / pushed 2024-08-13T14:23:16Z