NOCKVEIL
NOCKVEIL-SPEC / GENESIS1,337 ENTITIES / ROBINHOOD CHAIN

The collection is an executable system.

NOCKVEIL is a 1,337-Sentinel network built around compatibility, relationships, productive state and irreversible transformation.

The image is the first interface. It reveals a Sentinel's signal role. The protocol layer determines what that Sentinel can do. A visually quiet Sentinel can still be structurally important, while a rare appearance can remain operationally unresolved.

CORE LOOPSCAN → MATCH → CONNECT → GENERATE → ROUTE → FUSE

Acquisition is external. Protocol activity begins after a Sentinel enters a wallet and is read by the network.

01SCANRead public traits and protocol state.
→
02MATCHResolve signal/core compatibility.
→
03CONNECTBoth owners authorize the relationship.
→
04GENERATEProductive state prints Credits.
→
05TRANSFORM25,000 $NKV fuels Fusion.

Entity grammar

Every entity is generated as a sentence. Trait categories are not independent decoration; each layer constrains the next.

STRUCTURE / SILHOUETTE

8 sentinel archetypes across four signal families. Structure implies posture, function class and the types of cores/interfaces that make sense.

family → posture → presumed function

CORE / TRUTH

6 active core types plus the Absent Core state. The core can confirm a structure, complicate it, or deliberately disappear. Absent Core is a socket, not a Void Core.

structure + core → physical logic

INTERFACE / RELATIONSHIP

7 interface types describe what the entity expects: input, output, connection, control or perception.

interface → directionality

MATERIAL / ERA

6 materials are grouped into three fictional eras. Material is historical information, not a color skin.

material → origin / era

STATE / TIME

7 states describe current condition: dormant, active, incomplete, contained, awaiting, fractured and more.

state → permitted transitions

ANOMALY / VIOLATION

Anomalies are controlled grammar breaks. Most are quiet. A small set create cross-entity clues.

rule break → possible signal
Design invariant: if a combination cannot be explained in one sentence of in-world logic, it does not enter the normal grammar. Interesting outliers live in the explicitly permitted anomaly space.

Population architecture

The Nockveil genesis population is fixed at 1,337 Sentinels. Distribution is weighted by signal role rather than simple trait-count rarity.

1,337SENTINELS
8STRUCTURES
7CORES
7INTERFACES
6MATERIALS
7STATES
RANGERS / TRACKING241 / 18%
WARDENS / GUARDED321 / 24%
RELAYS / ROUTED294 / 22%
SEERS / DORMANT160 / 12%
KEEPERS / ACTIVE321 / 24%
The genesis manifest records 83 anomaly-bearing Sentinels, 64 Absent Core states, 48 detached-core carriers and 21 authored signal pairings.

Authored signal pair

Nockveil pairings resolve complementary signal roles. The registry can connect a Sentinel that emits a route with one capable of receiving and stabilizing it.

Nockveil Sentinel 0124
SENTINEL #0124

THE GREEN SIGHT

STRUCTURE
Hooded Sentinel
CORE
Quartz Core
INTERFACE
Output Slot
STATE
Active
CREST
Crown Crest

An active output Sentinel that publishes an Arrow-Link route into the Nockveil registry.

Nockveil Sentinel 0786
SENTINEL #0786

THE THORN RECEIVER

STRUCTURE
Thorn Walker
CORE
Liquid Core
INTERFACE
Signal Receiver
STATE
Active
CREST
Signal Crest

Its receiver stabilizes the authored Arrow-Link signal emitted by Sentinel #0124.

#0124
ARROW-LINK
→
NOCKVEIL REGISTRY
LIQUID CORE
→
#0786
MATCH = TRUE

Matching engine

Matching is a constrained registry query, not a similarity score. The engine checks whether a Sentinel's authored signal link can be stabilized by a compatible core and whether both states permit connection.

SENTINEL AsignalLinkARROW-LINKrequiredCore = Liquid
+
SENTINEL BcoreIdentityLIQUID COREreceiver = active
→
NOCKVEIL REGISTRYCOMPATIBILITYTRUEconnection permitted
compatible(a, b) =
  a.socketType != null
  AND b.detachedCore == true
  AND a.requiredCoreIdentity == b.coreIdentity
  AND stateGate(a) == OPEN
  AND stateGate(b) == OPEN

This is the conceptual compatibility predicate. The production contract can encode the same invariant with a different implementation.

DISCOVERED
→
SCANNED
→
MATCH FOUND
→
OWNER A
+
OWNER B
→
CONNECTED

Connection is a productive state.

A match does not silently mutate an NFT. Both sides authorize the relationship. Once active, the pair becomes a productive protocol state and begins generating Credits.

Why two-sided consent?

The entities can belong to different wallets. Connection therefore behaves like a handshake: discovery is permissionless, activation is bilateral.

Connection ≠ Fusion

Connection keeps both genesis entities alive. Fusion is the later irreversible transformation that consumes the connected relationship and creates a Composite Entity.

ENTITY A#0124
RELATIONSHIPACTIVE
ENTITY B#0786
OUTPUTCREDITS / HOUR

Credits → stock-linked output

Credits are the protocol's productive accounting unit. Connected machines generate Credits. Credits are then routed into one of the protocol's available stock-linked reward markets.

NVDAroute 01
AAPLroute 02
TSLAroute 03
GMEroute 04
SPCXroute 05
SPYroute 06
PLTRroute 07
NFLXroute 08
RDDTroute 09
MSTRroute 10
CONNECTEDPRINTproductive relation active
ROUTEDDIRECToutput assigned to a market
REDEEMEDSETTLEreward adapter executes output
ACTIVE CONNECTIONtime × rate × protocol rules→CREDITS
The reward engine is deliberately separated from the entity grammar. A machine's visual rarity does not determine its stock route. The route is a protocol state selected by the operator.

Fusion / irreversible transformation

Fusion is not a second sale. It is a state transition. A valid connection can be transformed by burning 25,000 $NKV. The burn is the fuel required to make the relationship permanent enough to become something new.

ENTITY A
+
ENTITY B
↓
25,000 $NKV
↓
COMPOSITE ENTITY
FUEL25,000 $NKV
INPUTone executable connection
OUTPUTnew Composite Entity state
ARTderived from both parents
DESIGN PRINCIPLE$NKV IS THE FUEL. CREDITS ARE THE OUTPUT.

The token and the reward unit therefore have different jobs. Credits measure productive state; $NKV pays the irreversible cost of changing state.

Anomalies are signals, not cosmetics.

The genesis registry contains 83 anomaly-bearing Sentinels. Most anomalies are quiet: a single proportion deviation, a mismatched component, a strange material patch or a cross-entity clue that only becomes legible after a match is discovered.

IMPOSSIBLE CAVITYWRONG-FAMILY COMPONENTMISMATCHED-ERA MATERIALFLOATING COMPONENTSHARED CABLEEXACT ABSENT-SOCKET COMPONENTPIXEL DEVIATIONUNEXPLAINED SYMBOL
Anomaly ≠ guaranteed value. It means the grammar has been intentionally violated. Protocol relevance remains a separate hidden vector.

Production architecture

The public experience can remain simple while the underlying system stays modular. Ownership, registry state, reward accounting and transformation are separate concerns.

ERC-721ownership / token identity / metadata
↕
ENTITY REGISTRYcompatibility identifiers / state gates / pair records
↕
MATCH + CONNECTIONbilateral authorization / productive state
↕
CREDIT ENGINEtime-weighted output accounting / route assignment
↕
REWARD ADAPTERstock-linked settlement layer
↕
FUSION ENGINE$NKV burn / composite state / metadata transition
THE OPERATING SURFACEWallet ownership is read → protocol state is resolved → the terminal renders the relationship → signatures authorize state changes → the chain records the transition.

The architecture intentionally leaves the reward settlement adapter replaceable. The protocol's accounting and routing logic do not need to be rewritten when the production settlement rail changes.

FAQ

Do all 1,337 entities have a match?

No. The authored registry contains a finite set of explicit fusion relationships. Unresolved entities remain valid protocol participants through fallback operation.

Can two visually similar entities be incompatible?

Yes. Visual resemblance is not the compatibility key. The relationship is determined by protocol identifiers and state gates.

Can an entity generate output without a match?

Yes. The protocol includes a standalone/fallback operating path so unresolved entities are not dead ends.

What are Credits?

Credits are the productive accounting unit generated by protocol activity. They are routed toward stock-linked reward output according to protocol rules.

What is $NKV?

$NKV is the transformation fuel. A production Fusion requires a permanent burn of 25,000 tokens.

What happens when two entities fuse?

The connection is consumed and a Composite Entity state is created. The result inherits protocol information from both parents.

Where does acquisition happen?

Outside the operating surface. The Protocol website is designed to become the technical home for entities after acquisition.