poke-effects
Poke effects
State-changing NockApp input boundary where a poke can emit effects and mutate durable state.
Use this boundary for fakenet and Nockup receipts that need to explain which poke path, effect tag, and before/after state roots were observed.
receiptFields
pokePath, effectTag, stateRootBefore, stateRootAfter, kernel, nockchainCommit
riskPosture
A poke is not just a command transcript; bind it to kernel, commit/build, endpoint mode, state root, and effect evidence before publishing.
peek-reads
Peek reads
Read-only NockApp observation boundary for state inspection without claiming a transition occurred.
Use this boundary for balance, route-table, state, or app peeks where the receipt must separate observation from mutation.
receiptFields
peekPath, stateRootAtPeek, grpcEndpoint, kernel, nockchainBuild
riskPosture
Peek output must be tied to endpoint, block/tip context, state root, and Nockchain build before it becomes evidence.
pma-durability
PMA durability
Persistent-memory and state-artifact boundary for local durability, replay context, checkpointing, and state-jam provenance.
Use this boundary when a NockApp test depends on existing state, a state export, a checkpoint, or a Zorp state-jam source.
receiptFields
stateJamFingerprint, pmaBoundary, eventLogBoundary, stateRootBefore, stateRootAfter
riskPosture
Record PMA and state-jam metadata only. Do not store or redistribute raw PMA slabs, event logs, checkpoints, or state jams.
grpc-private-endpoint
gRPC private endpoint
Local/private NockApp interaction surface used by probes, wallets, fakenets, and future direct runtime tests.
Use this boundary to distinguish private local gRPC evidence from public API or explorer-derived evidence.
receiptFields
grpcEndpoint, endpointMode, nockchainCommit, nockchainBuild, networkId
riskPosture
Never imply an unauthenticated private endpoint is safe for public exposure; record endpoint mode and local network context.
nockup-fixture
Nockup fixture
Scaffold/build/run boundary for turning NockApp source, Hoon kernels, and Jam artifacts into reproducible fixtures.
Use this boundary to connect Nockup validation receipts, fixture provenance, and future Jock/NockApp authoring templates.
receiptFields
nockupTemplate, jamHash, sourceRepo, sourceRepoPushedAt, kernel
riskPosture
A successful scaffold run is fixture evidence, not protocol authority. Keep it tied to source hash, template, build command, and Nockchain commit.