Tarek Ziadé
Python core developer; leads Python/infra tooling at Hugging Face
OSINT Profile
Tarek Ziadé is a longtime CPython core developer and packaging author (Pip, 'Architecture of Open Source Applications') who works on Hugging Face's Python and developer-infra tooling. NVIDIA agreed to acquire Hugging Face for ~$12.9B on 2026-09-03 ($11.9B to shareholders + up to $1B equity retention for HF employees joining NVIDIA; HF to remain an open platform; expected close H1 2027 pending regulatory approvals; antitrust runway + GPU-neutrality of the Hub are the live radar questions). Listed in Hugging Face's public organization directory (187 members, retrieved 2026-09-04); named at the HF All Hands where the deal was announced.
Public Relation Edge (do not over-claim)
Public OpCo / HoldCo Nodes
Only public nodes listed.
🗺 $UM-Radar GIS OSINT Map
1 entities geo-pinned · toggle People / Institutions · 48.8566, 2.3522
Currencies & Languages
🔬 ALPHA BRIEF
🔭 WATCH: rail volume, not follower count · which chain the settlement moves to next · fee take-rate disclosure
🔍 Tarek Ziadé is carried at HIGH confidence on 3 filed sources. The horizon below is a hypothesis with a shelf life, not advice.
Embed this dossier
Paste the badge on a site, a README or an agent page. It serves live from the edge and links back with its own attribution code.
Machine form: GET /badge/tarek-ziade.json
🔔 Watch this dossier notify on new signals
Paste a Base wallet and this record joins your watchlist. Nothing is uploaded, nothing is stored off-chain beyond the list, and removing it is one click.
🔗 Embed this dossier badge, 300x78, no tracking
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-tarek-ziade, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/tarek-ziade.json returns the same snippet for a generator.
🔗 Embed this dossier badge, 300x78, no tracking
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-tarek-ziade, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/tarek-ziade.json returns the same snippet for a generator.
Embed this dossier
Paste the badge on your own page. The image is edge-cached SVG, the link carries the attribution code, and the counter moves in the referral ledger.
📈 10-Year Forward Outlook 2026-2036 (horizon hypothesis, not advice)
The record is what it is: Python core developer; leads Python/infra tooling at Hugging Face. Nothing below is filed — it is the shape the seat would take if the current trajectory holds, and it is re-scored every time a new public source lands.
🔭 rail volume, not follower countExpect the mandate to widen before it deepens. Watch whether the current seat adds an adjacent function to the seat rather than a bigger title on the same one.
🔭 which chain the settlement moves to nextA second mandate is the normal move here — a board seat, a fund-side advisory role, or an operating chair next to the current one. The tell is a first public co-signature, not an announcement.
🔭 fee take-rate disclosureFirst capital event window. Either a priced round behind the current seat or a personal vehicle appears. Watch fee take-rate disclosure rather than the headline valuation.
🔭 agent-side integration countJurisdictional switch is the highest-probability structural change from Paris, France. A second residence, a second entity, or a second currency book (USD to a settlement unit) is the observable.
🔭 whether the rail survives its own tokenInstitutional shell forms: a holding vehicle, a family-office wrapper or a named co-investment club. Shells are quiet — the disclosure arrives through registry filings, not posts.
🔭 rail volume, not follower countDistribution becomes the constraint. At this horizon the question is who carries the current seat's output and this seat's name, and on what terms. Watch agent-side integration count.
🔭 which chain the settlement moves to nextSuccession pressure. Either a named deputy appears under the seat or the seat is re-scoped away from day-to-day. Both read as the same signal from outside.
🔭 fee take-rate disclosureSecond-order liquidity: secondary sales, a tender, or a strategic minority into the current seat. This is where an OSINT file usually goes stale for six months and then re-prices.
🔭 agent-side integration countRecord consolidation. By here the file should be readable as a single arc rather than a list of events, and the Paris, France base stops being the interesting part.
🔭 whether the rail survives its own tokenEnd-of-horizon check. Re-read 2026 against 2036: the useful output is which of the eleven rows actually printed, and which were noise carried by the market rather than the person.
🔭 rail volume, not follower count🔍 Deterministic horizon model: every row is derived from facts already on this record and re-scored when a new public source lands. No forecast value is asserted.
💳 What the paid dossier unlocks — $4.99 USDC
- 🔍 Provenance ledger: every figure tagged CLAIMED or filed, with the source URL
- 🤖 Machine pack: /api/um-radar/agent-pack JSON + MCP fetch_profile, 402-safe retries
- 🗺 GIS pin plus the adjacency graph - who else is in this room and how they link
- 🏦 Public OpCo / HoldCo node table, unfunded or filed status stated, never guessed
- ⏱ Record freshness: last verified not stated
- 💰 USDC-settled, 60% cheaper in $UM, live FX across 30 currencies
Buy without a browser: GET /oauth/protected-resource, then tools/call fetch_profile over MCP. Bulk and 402 retries are idempotent on the same slug.
Machine pack: /api/um-radar/agent-pack?slug=tarek-ziadeBatch / dataset pricing on request
🤝 Affiliate & Partner Links
Public OSINT radar only. Not investment advice. Not a prediction engine.