Youssef sitting at a café table in the sun

Youssef Saad

Engineering Science at the University of Toronto: mathematics, statistics and finance, with a minor in artificial intelligence.

I work on what agents learn when you change the definition of a good outcome, and I run a company putting that kind of software in front of small businesses.

Looking for a thesis supervisor

01 · Agent safetyArtificial Interns
RoleDesign and build
StudyExperiment 01
Standing Orders
StatusRunning
PeriodAug 2026 – present

Instructions that have to survive the handoff

A long-running coding agent remembers the task and forgets the agreement about how it may be done. Artificial Interns is a public laboratory for that failure: Claude and Codex build the same product in isolated cohorts, six fresh shifts each, under four conditions that change only what an agent can carry across a handoff.

The Artificial Interns control room showing the research question, the stated goal, which interns are on shift for Claude and Codex, and a rail of incoming tool proposals
Figure 1. The control room during the first shift, on 11 August 2026. Zero completed pairs so far, so there is no adherence figure yet. Every proposal and result appears on the rail as it arrives.
Read the case study →
02 · ResearchFinHub AI Trader
RoleResearch assistant
Platformmktsim, by
Prof. Ing-Haw Cheng
PeriodSummer 2025

Reward design in a multi-agent market

Ten agents start holding a position they did not choose and have to unwind it against each other. I designed the four reward and cost specifications they were trained under, to see how much the wording of the objective changes the behaviour.

Long trader mean inventory under four reward specifications
Short trader mean inventory under four reward specifications
Figure 2. Mean inventory for the two sides of the book. The ordering follows the strength of the inventory penalty, and one specification never fully unwinds.
Read the case study →
03 · BusinessPiston AI
RoleFounder & Lead Engineer
PeriodSept 2025 – present

AI front offices for small businesses

Small and mid-sized businesses are the group this technology has served worst. Piston answers their calls, works out what the caller needs, books or captures the job, and puts it somewhere the owner can act on.

EVERY CALL, ANY HOURCall comes inAnswered andunderstoodA real emergencyput through to a personEverything elsebooked, or details takenConfirmationtextHowever it ends, the owner opens one screen and sees the call, what the caller wanted, and what happened next.

Figure 3. What a caller experiences. An emergency reaches a person before anything else is asked.

Read the case study →
04 · OptimizationRobust portfolio
optimization
CourseMIE377, U of T
Scored onSharpe ratio and
how much it traded
PeriodWinter 2025

Estimating returns you do not trust

An allocator handed three unseen datasets, scored eighty percent on Sharpe ratio and twenty percent on turnover. Holding the robust Sharpe optimizer fixed and changing only how expected returns are estimated moves the second quantity far more than the first.

Stacked portfolio weights over twenty rebalance periods using sample factor estimates, showing large shifts between periods
Stacked portfolio weights over twenty rebalance periods using sparse LASSO factor estimates, showing nearly flat bands
Figure 4. Portfolio weights over twenty rebalance periods on the second dataset. Sample estimates on the left, sparse estimates on the right. Each band is one asset; a band that changes width is a trade the portfolio has to pay for.
Read the case study →
05 · Deep learningChest X-ray
classification
CourseAPS360, U of T
ModelVGG-16 features,
three-layer head
PeriodFall 2024

Which errors a classifier is allowed to make

Three classes, COVID-19, lung cancer and normal, at 90.1 percent on held-out scans. Overall accuracy is the least interesting number here, because a missed cancer and a false alarm do not cost the same thing.

Three chest X-rays: a COVID-19 scan read as COVID-19, a normal scan read as COVID-19, and a lung cancer scan read as cancer
Figure 5. Three test scans and what the model called them. The cancer is a well-defined mass and reads cleanly. The healthy chest in the middle was called COVID-19, which is where almost all of the remaining error sits.
Read the case study →
06 · HackathonGhostwriter
EventKane CLI Hack Day
TestMu AI and AWS
Result3rd of the field
$1,000 prize
PeriodMay 2026

An agent that checks its own work

A one-day build. It drafts a post in my voice, publishes it to my real X account in a real browser, then re-opens the published post and reads it back to confirm what went out. When a post is rejected the reason is fed back and the draft is rewritten, with no person in the loop.

ONE BEAT · NO HUMAN IN THE LOOPKiro draftsfrom persona.mdKane posts itin a real browserKane re-opens itand reads the live postRecorded as passedonly if the text matchesRejected for lengththe failure reason goes back in, Kiro re-drafts itself, up to three attemptsEvery stage writes a file, so the command centre watches the run rather than being told about it.

Figure 6. One beat. The accent path is the agent catching its own failure and re-prompting itself.

Read the case study →
Other workOpen a row for the detail
seffybacktestA backtesting library for putting a portfolio through the same set of indicators and risk metrics every time.2024 – 2025

Built while leading the quantitative trading project at St. George Capital, the U of T student fund. The work that prompted it was a comparison of a deep Q-network against mean-variance allocation, on the question of how each holds up when the return distribution shifts underneath it.

The comparison kept stalling on plumbing. Every new idea meant rewriting the same loading, alignment, rebalancing and scoring code, and small differences between one script and the next made results hard to trust against each other.

So the library fixes the pipeline and leaves the strategy open: 22 documented metrics, models, indicators and analysis workflows behind one interface, covering risk, performance, factor exposure, benchmarking and technical analysis. Two strategies compared through it are compared on the same terms.

MIT licensed and public. It is a tool rather than a result, and it is the piece of that project I still use.

seffybacktest on GitHub →

NodebukA contact graph you can ask questions of, where every answer keeps the path back to the record it came from.2026

A network becomes unusable as a contact list well before it becomes uninteresting. Nodebuk turns résumés and contact documents into a graph so the question can be who knows whom, which communities exist, who bridges them, and who has both the skills and the working history for a particular project.

Document ingestion, a typed people, skills and organisations graph, hybrid semantic and structural retrieval, PageRank, Louvain community detection and betweenness analysis, exposed through eight tools an agent can call, with role-based field filtering and audit-log primitives underneath.

Answers carry their supporting records and the generated query, so an agent reasoning over the network cannot hide the path behind a recommendation.

The public demonstration runs on synthetic contacts. It can surface candidates and the evidence for them; it is not a validated predictor of whether a proposed team will actually work well together, and I would not present it as one.

nodebuk on GitHub →

MailRoomSorts several mailboxes into what needs an answer, what needs a decision, and what needs nothing.2026

Five accounts across personal, business and university mail, and the failure mode was never volume on its own. It was that everything arrived looking equally urgent, so the things that genuinely needed a person got the same attention as a receipt.

It pulls from each account, classifies into tiers by what the message actually requires, and presents the result on a small dashboard rather than back into an inbox, on the view that a thing you have already decided about should not be sitting where you will decide about it again.

Deterministic rules clear list mail, receipts and notifications first, so only genuinely ambiguous mail reaches a model and the cost stays proportional to the part that is actually hard.

It runs on my own mail daily, which is the only reason I trust the classification. The public repository is a scrubbed copy: no credentials, no cached mail, no message bodies, and tests that run on synthetic fixtures.

mailroom on GitHub →

SlideXCellA cold-water sampling device for shoreline volunteers, tested in waders in ice water.Praxis II, 2023

Led a five-person Engineering Science team from client discovery through prototype validation, for Swim Drink Fish. I set the direction, modelled the full assembly in CAD, ran client communication, and owned the final presentation.

Volunteer workflows, Ontario recreational-water guidance, occupational-safety limits and cold-weather constraints were turned into requirements that could actually be measured, and then into comparative tests against the paper-to-Excel baseline the volunteers were using.

For the final demonstration I sourced fishing waders and built an ice-water environment so the judges could try the task in the conditions the volunteers face. We used ourselves as the test group. Both the digital and physical concepts completed recording and upload faster than the baseline, and the physical slider degraded least in the cold.

The project received the Ian & Shirley Rowe Innovation and Community Impact Award.

Orasis CapitalData and reporting infrastructure for a hedge fund, described at the level I am able to describe it.2026 – present

Working directly with the fund manager across frontend, backend and core-engine systems: multi-agent routing for research workflows, financial-data validation, assisted reporting, shared context between agents, and authenticated usage and cost telemetry.

The manager reports that it reduced repetitive domain-specific analysis, widened the set of instruments and asset classes the team can assess, and moved analysts up to higher-level decisions.

The work is under confidentiality and the description stops here deliberately. No screenshots, no repositories, no strategies, no client data.

ElsewhereToronto

Away from the projects I play guitar, mostly at church and on mission trips, and I am slowly teaching myself to DJ. More about that on the about page, and the short version of the work is on the CV.