Upstream early warning

Nockchain PR Radar

Open upstream pull requests grouped by Nocksperimental risk class, target surface, receipt impact, and verification command so incoming Nockchain work can be reviewed before it silently changes test assumptions.

PR API Watch

Open PRs

Open Issues

High Priority

Drafts

Open Pull Requests

PR #125

fix(nockup): render template manifests from hbs sources

high / nockup-fixture-manifest

targetSurfaces

nockupValidation, generatedLabReports, fixtureDocs

receiptFields

templateManifestSource, templateManifestHash, renderedTemplateInputs

verificationCommand

npm run test:nockup-validation && npm run test:generated-reports

action

Review PR #125 before changing Nockup validation fixture manifest assumptions; template manifest rendering should become hashed receipt metadata.

PR #113

PMA trailhead, squashed and rebased

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, eventLogBoundary, fsyncMode, stateJamFingerprint

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #113 before changing PMA snapshot, event-log, or state-jam provenance assumptions.

PR #116

feat(wallet): support blobs and memo on transactions in wallet cli

high / wallet-transaction-metadata

targetSurfaces

nockchainWalletAtlas, localFakenetCommands, balanceEvidence

receiptFields

transactionBlobHash, memoPresence, walletCommand, endpointMode

verificationCommand

npm run test:nockchain-wallet-atlas && npm run test:local-fakenet-commands-api

action

Review PR #116 before publishing wallet transaction metadata receipts; blobs and memos must be hashed or summarized.

PR #103

Feature: Offline/cold wallet signing

high / offline-wallet-signing

targetSurfaces

nockchainWalletAtlas, localFakenetCommands, balanceEvidence

receiptFields

signingMode, unsignedTxHash, signedTxHash, airgapTransferMethod

verificationCommand

npm run test:nockchain-wallet-atlas && npm run test:local-fakenet-commands-api

action

Review PR #103 before changing wallet signing-mode receipts or cold/hot wallet safety guidance.

PR #119

feat(nockapp): public NockApp::export_state for live-app snapshot

high / nockapp-state-export

targetSurfaces

nockchainNockAppSourceTrace, stateJamRegistry, localFakenetEvidence

receiptFields

exportStateCommit, exportStateHash, stateJamFingerprint

verificationCommand

npm run test:nockchain-nockapp-source-api && npm run test:nockchain-state-jams-api

action

Review PR #119 before trusting live NockApp state export snapshots; export jams stay metadata-only.

PR #126

nockchain-bench

high / benchmarking

targetSurfaces

nockchainRustAtlas, generatedReports, computeBenchmarkProfiles

receiptFields

benchmarkSuite, crateUnderTest, criterionOutputHash

verificationCommand

npm run test:nockchain-rust-atlas-api && npm run test:generated-reports

action

Review PR #126 before claiming Rust performance expertise or adding benchmark receipts.

PR #124

AI Proof-of-Useful-Work (matmul) — ai-pow-miner + ai-pow-zk compact recursive STARK

high / compute-proof-puzzle

targetSurfaces

computeBenchmarkProfiles, trustSignals, x402MeteredTrustApi

receiptFields

puzzleId, proofDifficulty, solverOutputHash, compactCertificateBytes, certificateVerifierKeyDigest

verificationCommand

npm run test:compute-benchmark-detail-page && npm run test:x402

action

Full implementation now OPEN (135k+ LOC, two new crates: ai-pow-miner with 'pearl' mining + ai-pow-zk Plonky3 3-layer compact recursive STARK, ~125KB certificate / ~32s cold build; merge-mined matmul PoUW that subsidizes AI inference/training; binds Front #2 'AI Compute Market Fork A'). Branch is CONFLICTING (needs rebase on master) and REVIEW_REQUIRED — not merged. Treat the certificate as a future compute-benchmark / proving-demand evidence class, NOT current runtime authority. Mirror the compact-certificate byte size + verifier-key digest as evidence fields only after it merges; never ingest a solver private key.

PR #118

Respect --stack-size flag

high / runtime-stack-size

targetSurfaces

nockchainOperationsAtlas, localFakenetReadiness, localFakenetDiagnostics

receiptFields

stackSizeFlag, runtimeProfile, failureMode

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-diagnostics-api

action

Review PR #118 before changing local fakenet stack-size runbooks or diagnosing runtime stack failures.

Operator Queue

PR #125

Review PR #125 before changing Nockup validation fixture manifest assumptions.

PR #113

Review PR #113/#112/#107/#104 before trusting PMA snapshot, event-log, or state-jam assumptions.

PR #116

Review PR #116 before publishing wallet transaction metadata receipts.

PR #103

Review PR #103 before changing offline/cold wallet signing receipts.

Issue #121

Track issue #121 before changing runtime stack-frame safety diagnostics.

PR #119

Review PR #119 before trusting live NockApp state export snapshots.

PR #100

Track PMA checkpoint-stream persistence before changing state-artifact provenance.

PR #94

Track JAM cue hardening before changing runtime safety diagnostics.

PR #83

Track gRPC message-size controls before changing wallet/API command limits.

PR #79

Track peek v1 transaction support before changing transaction inspection receipts.

review

Review PR #126 before claiming Rust benchmarking coverage.

review

Review PR #124 as compute/proof benchmark material, not current Nockchain runtime authority.

review

Review PR #118 before changing stack-size runbooks or runtime failure triage.

Open Issues

Issue #121

NockStack::is_in_frame panics in debug on pointers outside the stack arena

high / runtime-stack-frame-safety

targetSurfaces

nockvmRuntimeSafety, nockchainOperationsAtlas, localFakenetDiagnostics

receiptFields

stackFramePointerRange, debugPanicMode, runtimeSafetyCheck

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-diagnostics-api

action

Track issue #121 before changing runtime stack-frame safety diagnostics or local fakenet panic triage.

Risk Classes

nockup-fixture-manifest

Nockup fixture manifests

Template manifest rendering can change which scaffold files, generated manifests, and fixture hashes a Nockup receipt should cite.

escalation

high

targetSurfaces

nockupValidation, generatedLabReports, fixtureDocs

verificationCommand

npm run test:nockup-validation && npm run test:generated-reports

pma-runtime-persistence

PMA runtime persistence

PMA throughput, event-log, snapshot, fsync, and closure changes can shift state bootstrap, replay, and artifact provenance assumptions.

escalation

high

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

wallet-transaction-metadata

Wallet transaction metadata

Wallet blobs and memos add transaction metadata that receipts must hash and classify without leaking note or key material.

escalation

high

targetSurfaces

nockchainWalletAtlas, localFakenetCommands, balanceEvidence

verificationCommand

npm run test:nockchain-wallet-atlas && npm run test:local-fakenet-commands-api

offline-wallet-signing

Offline wallet signing

Cold/offline signing changes transaction construction evidence, signing-mode boundaries, and key-material safety rules.

escalation

high

targetSurfaces

nockchainWalletAtlas, localFakenetCommands, balanceEvidence

verificationCommand

npm run test:nockchain-wallet-atlas && npm run test:local-fakenet-commands-api

nockapp-state-export

NockApp state export

Public live-app export state can improve snapshot receipts, but raw export jams must stay out of public APIs and git.

escalation

high

targetSurfaces

nockchainNockAppSourceTrace, stateJamRegistry, localFakenetEvidence

verificationCommand

npm run test:nockchain-nockapp-source-api && npm run test:nockchain-state-jams-api

benchmarking

Nockchain benchmarking

Benchmark harnesses can change which Rust crate gates and performance evidence belong in generated lab reports.

escalation

high

targetSurfaces

nockchainRustAtlas, generatedReports, computeBenchmarkProfiles

verificationCommand

npm run test:nockchain-rust-atlas-api && npm run test:generated-reports

compute-proof-puzzle

Compute/proof puzzle

AI PoW puzzle changes could become a new compute benchmark or trust signal rather than a Nockchain runtime claim.

escalation

high

targetSurfaces

computeBenchmarkProfiles, trustSignals, x402MeteredTrustApi

verificationCommand

npm run test:compute-benchmark-detail-page && npm run test:x402

runtime-stack-size

Runtime stack size

Stack-size behavior affects operator runbooks and failure triage for local fakenet and heavy NockApp runs.

escalation

high

targetSurfaces

nockchainOperationsAtlas, localFakenetReadiness, localFakenetDiagnostics

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-diagnostics-api

runtime-stack-frame-safety

Runtime stack frame safety

Stack-frame pointer panics can change runtime safety triage and operator diagnostics even before a fixing PR lands.

escalation

high

targetSurfaces

nockvmRuntimeSafety, nockchainOperationsAtlas, localFakenetDiagnostics

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-diagnostics-api

jam-cue-hardening

JAM cue hardening

JAM cue bounds and overflow fixes affect runtime safety receipts and support-bundle triage for malformed state or network data.

escalation

high

targetSurfaces

nockvmRuntimeSafety, nockchainOperationsAtlas, localFakenetDiagnostics

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-diagnostics-api

grpc-message-size

gRPC message size

gRPC max-message-size flags affect wallet, API, and local fakenet command safety for large state or transaction responses.

escalation

medium

targetSurfaces

nockchainWalletAtlas, localFakenetCommands, nockchainOperationsAtlas

verificationCommand

npm run test:nockchain-wallet-atlas && npm run test:local-fakenet-commands-api

Review Contract

requiredFields

prNumber, openIssueNumber, title, updatedAt, riskClass, priority, targetSurfaces, receiptImpact, verificationCommand

forbiddenFields

rawStateJam, rawPmaSlab, rawExportJam, walletSeedPhrase, privateSpendKey, rawBenchmarkCache

highlightedForbidden

rawStateJam, rawPmaSlab, walletSeedPhrase

rule

Draft PRs can shape future tests but cannot be treated as merged behavior.

rule

Open PRs are early-warning signals, not canonical protocol authority.

rule

Every merged PR that touches a target surface should refresh the matching Nocksperimental atlas, receipt contract, and tests.

rule

Receipt-impacting PRs must name the upstream commit, PR number, affected paths, and verification command before evidence is trusted.

Drift Check

status

available

command

npm run check:nockchain-pr-radar-drift -- --json

highlightedCommand

npm run check:nockchain-pr-radar-drift -- --json

testCommand

npm run test:nockchain-pr-radar-drift-check

highlightedPullRequestsApi

https://api.github.com/repos/nockchain/nockchain/pulls?state=open&per_page=100&sort=updated&direction=desc

sourceUrls

https://api.github.com/repos/nockchain/nockchain/pulls?state=open&per_page=100&sort=updated&direction=desc, https://api.github.com/repos/nockchain/nockchain/issues?state=open&per_page=100&sort=updated&direction=desc

compareFields

number, title, draft, updatedAt, author

interpretation

Use this before accepting the static PR radar as current; open PRs are early-warning signals and drift means the radar should be refreshed before product decisions.

Additional Pull Requests

PR #122

feat(nockup): install_path support and nested symlink fixes

medium / nockup-install-path

targetSurfaces

nockupValidation, workspaceEvidence, fixtureDocs

receiptFields

installPath, symlinkPolicy, workspaceRoot

verificationCommand

npm run test:nockup-validation && npm run test:workspace-evidence

action

Review PR #122 before treating Nockup install paths as portable workspace evidence.

PR #120

feat(nockup): extension hooks for downstream-owned templates and subcommands

medium / nockup-extension-hooks

targetSurfaces

fixtureDocs, nockupValidation, generatedLabReports

receiptFields

extensionHook, downstreamTemplateId, subcommandName

verificationCommand

npm run test:nockup-validation && npm run test:generated-reports

action

Review PR #120 before designing downstream-owned Nocksperimental Nockup templates.

PR #112

bump pma post throughput elas sr fsync hrtb closure

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, throughputProfile, fsyncMode, closureRuntimeMode

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #112 as PMA runtime persistence work before changing state-artifact support-bundle assumptions.

PR #107

Bump PMA, event log and snapshots, squashed + rebased, fsync

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, eventLogBoundary, snapshotHash, fsyncMode

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #107 before trusting event-log or snapshot provenance language in state-jam receipts.

PR #104

Bump pma post throughput event log and snapshots

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, eventLogBoundary, throughputProfile

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #104 as older PMA snapshot/event-log lineage before changing current state-artifact policy.

PR #117

feat(nockup): declarative post-install [[patches]]

medium / nockup-extension-hooks

targetSurfaces

fixtureDocs, nockupValidation, generatedLabReports

receiptFields

postInstallPatch, patchHash, templateId

verificationCommand

npm run test:nockup-validation && npm run test:generated-reports

action

Review PR #117 before accepting post-install patch evidence from Nockup templates.

PR #114

fix(nockup): pin `basic` template's nockchain deps to a real commit / proposed addition to nockup architecture

medium / template-pinning

targetSurfaces

nockupValidation, generatedReportProvenance, fixtureDocs

receiptFields

templateDependencyCommit, templateDependencyHash, nockchainBuild

verificationCommand

npm run test:nockup-validation && npm run test:generated-report-provenance-api

action

Review PR #114 before marking scaffold dependency provenance reproducible.

PR #111

Add h-zoon

watch / hoon-app-surface

targetSurfaces

nockchainDocsAtlas, nockchainNockAppAtlas, fixtureDocs

receiptFields

hoonAppName, sourceCommit, fixtureRole

verificationCommand

npm run test:nockchain-docs-atlas-api && npm run test:nockchain-nockapp-atlas-api

action

Watch PR #111 as Hoon app surface context until canonical docs or Nockup fixtures promote it.

PR #102

Add comprehensive x402 agentic payments specification for Nockchain

medium / x402-agentic-payments

targetSurfaces

x402MeteredTrustApi, bazaar, trustSignals

receiptFields

paymentSpecVersion, facilitatorMode, agentPaymentPolicy

verificationCommand

npm run test:x402 && npm run test:bazaar && npm run test:trust-signals

action

Review PR #102 before changing x402, Bazaar, or paid evidence assumptions.

PR #101

Bitemyapp/parser parse arm comparison next

watch / parser-arm-comparison

targetSurfaces

nockchainHoonKernelAtlas, nockchainDocsAtlas, fixtureDocs

receiptFields

parserSurface, armComparisonMode, hoonSourceAnchor

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:nockchain-docs-atlas-api

action

Watch PR #101 for parser and Hoon-source interpretation changes that could affect kernel fixture docs.

PR #100

ag2 opt persistence madvise checkpoint stream from pma slab but btree

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, checkpointStreamHash, btreePersistenceMode

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #100 as PMA checkpoint-stream persistence work before changing state-artifact provenance language.

PR #98

Native Rust Hoon parser

watch / hoon-parser-runtime

targetSurfaces

nockchainHoonKernelAtlas, nockchainDocsAtlas, fixtureDocs

receiptFields

hoonParserMode, sourceAnchor, parserFixtureHash

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:nockchain-docs-atlas-api

action

Watch PR #98 for Hoon parser changes that could affect kernel fixture source anchors.

PR #99

Bitemyapp/ag2 opt persistence madvise checkpoint

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, madviseMode, checkpointHash

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #99 as PMA checkpoint optimization context before trusting bootstrap or replay assumptions.

PR #97

Chris persistent PMA trailhead

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, persistenceMode, trailheadSource

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #97 as persistent PMA trailhead context before changing PMA boot-source guidance.

PR #96

Chris PMA trailhead

high / pma-runtime-persistence

targetSurfaces

stateJamRegistry, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

pmaSnapshotRoot, trailheadSource, runtimeMode

verificationCommand

npm run test:nockchain-state-jams-api && npm run test:nockchain-operations-atlas && npm run test:local-fakenet-evidence-api

action

Review PR #96 as older PMA trailhead context before updating state-jam and support-bundle assumptions.

PR #95

Add jojo repl

watch / jojo-repl-surface

targetSurfaces

nockchainNockAppAtlas, fixtureDocs, generatedLabReports

receiptFields

replCommand, interactiveFixtureMode, sourceCommit

verificationCommand

npm run test:nockchain-nockapp-atlas-api && npm run test:generated-reports

action

Watch PR #95 as possible interactive NockApp fixture or diagnostics surface.

PR #94

fix: prevent integer overflow in JAM cue deserialization

high / jam-cue-hardening

targetSurfaces

nockvmRuntimeSafety, nockchainOperationsAtlas, localFakenetDiagnostics

receiptFields

jamCueInputLength, cueValidationError, runtimeSafetyCheck

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-diagnostics-api

action

Review PR #94 before changing malformed JAM/runtime safety diagnostics or support-bundle guidance.

PR #93

Fix panic in JAM cue when deserializing empty buffer via P2P

high / p2p-jam-cue-hardening

targetSurfaces

nockchainSyncGossipTrace, nockchainOperationsAtlas, localFakenetEvidence

receiptFields

p2pPayloadLength, cueValidationError, peerSource

verificationCommand

npm run test:nockchain-sync-gossip-trace && npm run test:nockchain-operations-atlas

action

Review PR #93 before interpreting empty-buffer P2P failures in fakenet diagnostics.

PR #92

fix: add bounds check for heard-elders via Gossip

high / p2p-gossip-bounds

targetSurfaces

nockchainSyncGossipTrace, localFakenetDiagnostics, localFakenetEvidence

receiptFields

heardEldersCount, gossipBoundsCheck, peerSource

verificationCommand

npm run test:nockchain-sync-gossip-trace && npm run test:local-fakenet-diagnostics-api

action

Review PR #92 before updating gossip/peer DoS triage or route-table evidence guidance.

PR #89

fix: validate WireTag number to prevent serf thread panic

high / p2p-gossip-bounds

targetSurfaces

nockchainSyncGossipTrace, localFakenetDiagnostics, localFakenetEvidence

receiptFields

wireTagNumber, serfThreadFailureMode, validationError

verificationCommand

npm run test:nockchain-sync-gossip-trace && npm run test:local-fakenet-diagnostics-api

action

Review PR #89 before treating WireTag panic prevention as current P2P runtime behavior.

PR #87

Extending cli --version to include git sha.

medium / version-provenance

targetSurfaces

nockchainReleaseAssets, nockchainWatch, generatedReportProvenance

receiptFields

cliVersion, gitSha, binaryProvenance

verificationCommand

npm run test:nockchain-release-assets && npm run test:generated-report-provenance-api

action

Review PR #87 before changing release/binary provenance fields in generated reports.

PR #83

Add max message size in bytes for grpc servers and clients

medium / grpc-message-size

targetSurfaces

nockchainWalletAtlas, localFakenetCommands, nockchainOperationsAtlas

receiptFields

grpcMaxMessageBytes, endpointMode, commandSurface

verificationCommand

npm run test:nockchain-wallet-atlas && npm run test:local-fakenet-commands-api

action

Review PR #83 before changing wallet/API command limits or fakenet support-bundle guidance.

PR #82

Bumped the t-shirt size for nockchain app

high / runtime-memory-profile

targetSurfaces

nockchainOperationsAtlas, localFakenetReadiness, localFakenetDiagnostics

receiptFields

runtimeMemoryProfile, operatorSizingHint, failureMode

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-readiness-api

action

Review PR #82 before changing local fakenet readiness sizing or memory-failure triage.

PR #61

feat: --page-message flag for setting candidate-block's msg

medium / candidate-block-message

targetSurfaces

nockchainHoonKernelAtlas, localFakenetEvidence, generatedReports

receiptFields

candidateBlockMessage, minerCommand, blockCommitment

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:local-fakenet-evidence-api

action

Review PR #61 before adding candidate-block message fields to miner or fakenet receipts.

PR #46

zkvm-jetpack: Add Melt type

watch / zkvm-melt-type

targetSurfaces

computeBenchmarkProfiles, trustSignals, fixtureDocs

receiptFields

meltType, proofContext, computeFixture

verificationCommand

npm run test:compute-benchmark-detail-page && npm run test:trust-signals

action

Watch PR #46 as proof/compute context before promoting Melt into benchmark evidence.

PR #79

Added support for v1 transactions in nockchain-peek

medium / peek-v1-transactions

targetSurfaces

nockchainHoonKernelAtlas, nockchainWalletAtlas, localFakenetCommands

receiptFields

peekTransactionVersion, peekCommand, transactionSource

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:nockchain-wallet-atlas

action

Review PR #79 before changing peek-based transaction inspection or wallet-adjacent receipts.

PR #88

fix: validate height bounds to prevent worker thread panic

medium / consensus-height-bounds

targetSurfaces

nockchainProtocolTrace, localFakenetEvidence, nockchainOperationsAtlas

receiptFields

heightBoundsChecked, workerThreadFailureMode, validationError

verificationCommand

npm run test:nockchain-protocol-trace && npm run test:local-fakenet-evidence-api

action

Review PR #88 before treating worker-thread panic prevention as current protocol/runtime behavior.

Additional Risk Classes

x402-agentic-payments

x402 agentic payments

Agentic payment specs can affect paid evidence surfaces and facilitator assumptions without becoming current Nockchain protocol behavior.

escalation

medium

targetSurfaces

x402MeteredTrustApi, bazaar, trustSignals

verificationCommand

npm run test:x402 && npm run test:bazaar && npm run test:trust-signals

jojo-repl-surface

Jojo REPL surface

A REPL surface can become fixture-authoring context or interactive diagnostics, but should stay watch-only until canonical docs promote it.

escalation

watch

targetSurfaces

nockchainNockAppAtlas, fixtureDocs, generatedLabReports

verificationCommand

npm run test:nockchain-nockapp-atlas-api && npm run test:generated-reports

parser-arm-comparison

Parser arm comparison

Parser/arm comparison work can alter Hoon-facing fixture interpretation and kernel-source review assumptions.

escalation

watch

targetSurfaces

nockchainHoonKernelAtlas, nockchainDocsAtlas, fixtureDocs

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:nockchain-docs-atlas-api

hoon-parser-runtime

Hoon parser runtime

Native Hoon parser work can change how Hoon fixtures and kernel source anchors should be interpreted.

escalation

watch

targetSurfaces

nockchainHoonKernelAtlas, nockchainDocsAtlas, fixtureDocs

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:nockchain-docs-atlas-api

p2p-jam-cue-hardening

P2P JAM cue hardening

P2P decode panic fixes change how fakenet peer, route-table, and malformed gossip evidence should be interpreted.

escalation

high

targetSurfaces

nockchainSyncGossipTrace, nockchainOperationsAtlas, localFakenetEvidence

verificationCommand

npm run test:nockchain-sync-gossip-trace && npm run test:nockchain-operations-atlas

p2p-gossip-bounds

P2P gossip bounds

Gossip bounds and WireTag validation affect DoS posture, peer diagnostics, and route-table evidence.

escalation

high

targetSurfaces

nockchainSyncGossipTrace, localFakenetDiagnostics, localFakenetEvidence

verificationCommand

npm run test:nockchain-sync-gossip-trace && npm run test:local-fakenet-diagnostics-api

version-provenance

Version provenance

Including git SHA in CLI versions improves binary provenance and generated report source identity.

escalation

medium

targetSurfaces

nockchainReleaseAssets, nockchainWatch, generatedReportProvenance

verificationCommand

npm run test:nockchain-release-assets && npm run test:generated-report-provenance-api

runtime-memory-profile

Runtime memory profile

Memory sizing changes affect operator runbooks, readiness checks, and heavy NockApp failure triage.

escalation

high

targetSurfaces

nockchainOperationsAtlas, localFakenetReadiness, localFakenetDiagnostics

verificationCommand

npm run test:nockchain-operations-atlas && npm run test:local-fakenet-readiness-api

candidate-block-message

Candidate block message

Candidate-block message flags can change miner/fakenet evidence fields and block-commitment provenance.

escalation

medium

targetSurfaces

nockchainHoonKernelAtlas, localFakenetEvidence, generatedReports

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:local-fakenet-evidence-api

zkvm-melt-type

zkVM Melt type

Melt type work is proof/compute-adjacent context until canonical Nockchain surfaces promote it.

escalation

watch

targetSurfaces

computeBenchmarkProfiles, trustSignals, fixtureDocs

verificationCommand

npm run test:compute-benchmark-detail-page && npm run test:trust-signals

peek-v1-transactions

Peek v1 transactions

v1 transaction support in nockchain-peek changes what transaction evidence can be inspected without running wallet commands.

escalation

medium

targetSurfaces

nockchainHoonKernelAtlas, nockchainWalletAtlas, localFakenetCommands

verificationCommand

npm run test:nockchain-hoon-kernels-api && npm run test:nockchain-wallet-atlas

nockup-install-path

Nockup install paths

Install-path support and nested symlinks can change scaffold portability and workspace evidence paths.

escalation

medium

targetSurfaces

nockupValidation, workspaceEvidence, fixtureDocs

verificationCommand

npm run test:nockup-validation && npm run test:workspace-evidence

nockup-extension-hooks

Nockup extension hooks

Downstream-owned templates and subcommands could become first-class Nocksperimental extension points.

escalation

medium

targetSurfaces

fixtureDocs, nockupValidation, generatedLabReports

verificationCommand

npm run test:nockup-validation && npm run test:generated-reports

consensus-height-bounds

Consensus height bounds

Height-bound validation belongs in protocol-sensitive receipts once it lands, especially for worker-thread panic triage.

escalation

medium

targetSurfaces

nockchainProtocolTrace, localFakenetEvidence, nockchainOperationsAtlas

verificationCommand

npm run test:nockchain-protocol-trace && npm run test:local-fakenet-evidence-api

template-pinning

Template dependency pinning

Template dependency pins affect reproducible scaffold receipts and generated report provenance.

escalation

medium

targetSurfaces

nockupValidation, generatedReportProvenance, fixtureDocs

verificationCommand

npm run test:nockup-validation && npm run test:generated-report-provenance-api

hoon-app-surface

Hoon app surface

New Hoon app surfaces should be reviewed as fixture inspiration until canonical docs promote them.

escalation

watch

targetSurfaces

nockchainDocsAtlas, nockchainNockAppAtlas, fixtureDocs

verificationCommand

npm run test:nockchain-docs-atlas-api && npm run test:nockchain-nockapp-atlas-api