Long
Only Trinity-owned execution and accounting domain. Every future value-moving action remains Captain-signed and currently unavailable.
Release disabledTrinity protocol V1
One program · one Ship · owner-signed Long
Trinity executes and accounts only for owner-signed Long. This V14 launch candidate exposes verified readiness evidence while every deployment, wallet, and value-moving path remains fail-closed.
Local evidence reader
This report is stored-evidence diagnostic only. It is not a PIT, permit, qualification proof, reward claim, transaction plan, or authority object.
Decoded facts
Caller-supplied ‘observed finalized’ values are labels. This offline parser does not contact RPC or prove finality.
Execution boundary
Only Trinity-owned execution and accounting domain. Every future value-moving action remains Captain-signed and currently unavailable.
Release disabledCaptain-managed external position. Trinity may eventually display finalized read-only context only.
Never Trinity-executedCaptain-managed external position. Trinity may eventually display finalized read-only context only.
Never Trinity-executedNeutral and Short are Captain-managed external positions. This client may display only finalized read-only context; Trinity does not execute, custody, size, settle, or account for them.
Local/private
Local/private search does not require Ping-In and is not made public by this shell.
Public visibility
Public Ping-visible observation requires live consent in the source evidence. Ping is visibility consent, not trading authority.
Eligibility
Self-discovery and searcher curve class are facts only. Founder eligibility policy is unresolved; neither proves or denies eligibility.
Offline cache
Checking static shell support…
V13 Long composition
Exactly one default Ship and at most one Augmentation may be selected per mission. The base safety envelope always applies; an Augmentation may only tighten it.
Scale in through the exact next source stage, then full exit. No automatic stop loss. Captain-signed cancel, reduction, and full-exit paths are mandatory launch requirements but remain unavailable until their sole-program implementation is qualified.
Evidence correction
The prior ELF embedded the superseded ten-Ship active commitment. The corrected V13 checkpoint is evidence only and cannot authorize deployment or prove a successful Long.
Activation register