STRUCTURE / SILHOUETTE
24 structural archetypes across five silhouette families. Structure implies posture, function class and the types of cores/interfaces that make sense.
family → posture → presumed functionP4096-SPEC / GENESIS4,096 ENTITIES / ROBINHOOD CHAIN
The collection is an executable system.
Protocol 4096 is a 4,096-entity network built around compatibility, relationships, productive state and irreversible transformation.
The image is the first interface. It tells you what the machine looks like. The protocol layer determines what the machine can do. A specimen can be visually ordinary and still be structurally important. Another can be spectacular and have no immediate relationship at all.
CORE LOOPSCAN → MATCH → CONNECT → GENERATE → ROUTE → FUSE
Acquisition is external. Protocol activity begins after an entity enters a wallet and is read by the network.
01SCANRead public traits and protocol state.
→02MATCHResolve socket/core compatibility.
→03CONNECTBoth owners authorize the relationship.
→04GENERATEProductive state prints Credits.
→05TRANSFORM100,000 $P4096 fuels Fusion.
Entity grammar
Every entity is generated as a sentence. Trait categories are not independent decoration; each layer constrains the next.
CORE / TRUTH
16 core types. The core can confirm a structure, complicate it, or deliberately disappear. Absent Core is a socket, not a Void Core.
structure + core → physical logicINTERFACE / RELATIONSHIP
18 interface types describe what the entity expects: input, output, connection, control or perception.
interface → directionalityMATERIAL / ERA
15 materials are grouped into three fictional eras. Material is historical information, not a color skin.
material → origin / eraSTATE / TIME
15 states describe current condition: dormant, active, incomplete, contained, awaiting, fractured and more.
state → permitted transitionsANOMALY / VIOLATION
Anomalies are controlled grammar breaks. Most are quiet. A small set create cross-entity clues.
rule break → possible signalDesign 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 genesis population is fixed at 4,096. The distribution is weighted by structural family and grammar rather than simple trait-count rarity.
4,096ENTITIES
24STRUCTURES
16CORES
18INTERFACES
15MATERIALS
15STATES
FAMILY A / AUTHORITY737 / 18%
FAMILY B / CONTAINED983 / 24%
FAMILY C / KINETIC901 / 22%
FAMILY D / SUSPENDED492 / 12%
FAMILY E / INSTRUMENTED983 / 24%
The supplied genesis manifest also records 205 anomaly-bearing entities, 123 Absent Core entities, 90 detached-core carriers and 30 authored fusion pairings.
Worked matches from the genesis registry
These are not invented examples. They are authored pairings in the supplied internal registry. They demonstrate exactly what a compatibility relationship looks like.
ENTITY #0124
THE EMPTY TERMINAL
- STRUCTURE
- Terminal
- CORE
- Absent Core
- INTERFACE
- Signal Receiver
- STATE
- Contained
- SOCKET
- Rect-Slot
- REQUIRED
- Geometric Core
Its socket is the query key. The machine is complete enough to exist, but incomplete enough to require something external.
ENTITY #2786
THE DETACHED CORE
- STRUCTURE
- Cube
- CORE
- Crystal
- INTERFACE
- Ports
- STATE
- Active
- SOCKET
- Rect-Slot
- CORE ID
- Geometric Core
Its detached component carries the exact core identity requested by #0124. The pair is therefore an authored exact match.
#0124
RECT-SLOT
RECT-SLOT
→
REGISTRY QUERY
GEOMETRIC CORE
GEOMETRIC CORE
→
#2786
MATCH = TRUE
MATCH = TRUE
ENTITY #0256
HEX SOCKET
- STRUCTURE
- Chassis
- CORE
- Absent Core
- INTERFACE
- Ports
- STATE
- Contained
- SOCKET
- Hex
- REQUIRED
- Liquid Core
ENTITY #3071
LIQUID-CORE CARRIER
- STRUCTURE
- Crawler
- CORE
- Geometric Core
- INTERFACE
- Scanner
- STATE
- Sealed
- SOCKET
- Hex
- CORE ID
- Liquid Core
ENTITY #0358
CIRCULAR-SMALL SOCKET
- STRUCTURE
- Capsule
- CORE
- Absent Core
- INTERFACE
- Control Wheel
- STATE
- Incomplete
- SOCKET
- Circular-Small
- REQUIRED
- Rotating Core
ENTITY #2381
ROTATING-CORE CARRIER
- STRUCTURE
- Chassis
- CORE
- Reactor
- INTERFACE
- Switches
- STATE
- Awaiting
- SOCKET
- Circular-Small
- CORE ID
- Rotating Core
A public viewer does not need to know every hidden identifier. The protocol can expose a match only when the registry determines that the relationship is executable.
Matching engine
Matching is a constrained registry query, not a similarity score. The engine checks whether an entity's required core identity can be satisfied by a compatible detached carrier and whether both states permit connection.
ENTITY AsocketTypeRECT-SLOTrequiredCore = Geometric
+ENTITY BcoreIdentityGEOMETRIC COREdetachedCore = true
→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#2786
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 100,000 $P4096. The burn is the fuel required to make the relationship permanent enough to become something new.
ENTITY A
+ENTITY B
↓100,000 $P4096
↓COMPOSITE ENTITY
FUEL100,000 $P4096
INPUTone executable connection
OUTPUTnew Composite Entity state
ARTderived from both parents
DESIGN PRINCIPLE$P4096 IS THE FUEL. CREDITS ARE THE OUTPUT.
The token and the reward unit therefore have different jobs. Credits measure productive state; $P4096 pays the irreversible cost of changing state.
Anomalies are signals, not cosmetics.
The genesis registry contains 205 anomaly-bearing entities. 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$P4096 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 4,096 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 $P4096?
$P4096 is the transformation fuel. A production Fusion requires a permanent burn of 100,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.