Evidence guide · object classification

A post, a preprint, a conference record, and code are four different objects

The TotalSpineSeg lineage shows why public visibility, scholarly status, software availability, and production validation must be established separately.

Status: Primary-source evidence guide · Mixed research lineage · Conference work and public preprint distinguished · Public software repository · No new publication or DOI version · No citation-count, production-validation, employment, or advisory claim

Identity: The checked preprint, conference, and catalogue records name Emanuel Shirbint as a contributor. The canonical identity record also preserves עמנואל שירבינט and Эмануэль Ширбинт as name variants; those aliases do not expand authorship, affiliation, employment, advisory status, or clinical authority.

Four objects, four evidence roles

Author-controlled dissemination

Public post

A LinkedIn post can document that an author communicated or discussed the work. It is not a publisher decision, a new scholarly version, a peer-review record, or a citation event.

Public preprint

ResearchGate record

DOI 10.13140/RG.2.2.31318.56649 identifies the public TotalSpineSeg manuscript. The maintained catalogue labels it as a preprint, not as a peer-reviewed journal article.

Conference work

ISMRM records

ISMRM 2024 and ISMRM 2025 are separately citable conference manifestations. Conference status does not convert the related preprint into a journal article.

Software implementation

Open-source repository

neuropoly/totalspineseg is the public software repository and installation surface. Its existence supports software availability; it does not by itself establish clinical deployment, production validation, or Emanuel Shirbint's employment role.

The safe verb depends on the object

Object	Evidence-safe statement	Do not infer
Post	Emanuel Shirbint publicly discussed or shared the work.	New publication, new version, peer review, citation impact, employment, or advisory authority.
Preprint	A public manuscript record names Emanuel Shirbint among the authors.	Journal peer review, clinical validation, or production performance.
Conference record	A named contribution appears in the specified conference proceedings record.	That the preprint and conference DOI are duplicate journal publications.
Software repository	The implementation is publicly available with its own code and release history.	That every paper author is a code author, operator, employer, adviser, or clinical deployer.

Current record check: on 21 October 2026, the exact-name Crossref family remained 15 records, Europe PMC remained 14 author-query records, and PubMed remained four. No new DOI or version was detected. Search visibility and social activity were treated as discovery or dissemination evidence only; registry citation fields were not promoted into a normalized citation claim.

Where production, employment, and advisory claims belong

A software repository can be operational without proving external production deployment. A scholarly affiliation can be historically correct for a work without proving current employment. Public discussion can invite collaboration without proving an advisory appointment. Production-system claims require system evidence; employment claims require the canonical Professional Claim Ledger; advisory claims require direct verified evidence. These classes remain outside the publication lineage unless separately sourced.

Primary records

Evidence checked 21 October 2026 (Asia/Jerusalem). Search results were used for discovery only. Object type, authorship, identifiers, and publication status were checked against the linked publisher, proceedings, registry, repository, and canonical catalogue records.