2y–BGCR
This became the project’s one surviving carry-style extension. It was retained only as a secondary interpretive overlay, not as a new core input.
Project 2 tested whether public carry and market-plumbing signals could sharpen interpretation of an existing Treasury conditions model. The answer was limited but useful: one carry overlay survived, a trimmed context layer survived, and stronger claims did not.
The earlier framework already separated instability from constraint. Project 2 existed to test whether public carry and plumbing data could make those readings easier to interpret without rewriting the model itself.
The earlier research established a two-axis framework for Treasury market conditions, built around instability and constraint. But it left open several harder questions: whether carry conditions were telling us anything useful, whether the model’s constraint readings reflected real funding strain, and whether public validation signals could make those readings easier to interpret.
Project 2 was built to test those questions without rewriting the original model. In simpler terms, this project asked a practical question: when Treasury market conditions look strained, can public carry and plumbing data help us understand what kind of strain we are looking at?
That is a narrower question than “did dealers lose money?” or “did we find a new stress regime?” The project did not set out to prove either of those, and it did not end up proving them.
Project 2 tested one main carry candidate, one internal comparator, and a trimmed set of context signals.
This became the project’s one surviving carry-style extension. It was retained only as a secondary interpretive overlay, not as a new core input.
This remained useful only as an internal sensitivity check because it overlapped too heavily with the existing funding family.
Repo volumes, SOMA lending, and surfaced fails were kept as descriptive context for funding, collateral, plumbing, and settlement conditions.
These were surfaced later as additional context, but they were not strong enough to reopen the project’s limits.
The strongest survivor was 2y–BGCR. It did not become a new stress classifier, but it did show some modest value as a secondary overlay, especially in quieter funding and plumbing episodes where the baseline instability story was not doing all the explanatory work on its own.
September 2019 and October 2025 were the clearest examples. In those windows, the overlay added interpretive value without becoming a lead signal, a universal stress meter, or a replacement for the baseline model.
Repo volume families, OFR repo segment volumes, SOMA lending, and surfaced fails help describe conditions as non-calm, funding-tight, collateral-active, or settlement-strained. Their value is texture, not classification.
The page is more credible if the failures stay visible. Project 2 did not find a clean leading indicator, did not preserve 2y–SOFR as a public-facing signal, and did not turn context into a classifier.
The surviving carry overlay did not behave like a disciplined early-warning signal. In some important windows it added useful context; in others it did not.
It was almost identical to 2y–BGCR and mainly reflected overlap with the same funding family, which left it useful for internal checking but not for public emphasis.
The context layer helped describe market plumbing, but it did not separate healthy strain from impaired stress on its own and did not reopen any path toward integration.
This was one of the clearest cases where the surviving overlay helped. Carry conditions were weak while instability remained relatively quiet, which made the episode look more like a funding and plumbing disturbance than a pure volatility event.
This was the warning case against overreading carry. The overlay deteriorated early, but then flipped while instability kept surging. That blocked any simple story like “negative carry means damage” or “positive carry means things are fine.”
Here the surviving context signals helped describe the market environment, but they still did not turn into a clean lead or a new classification rule. The episode was informative, not decisive.
This was another useful overlay case. The carry and context complex suggested a non-calm, plumbing-active backdrop even though the instability axis was not loudly signaling a classic dislocation.
Treasury markets matter far beyond trading desks. They influence borrowing costs, financial stability, and how smoothly the broader system absorbs stress. A model that can better distinguish simple volatility from funding and plumbing strain is useful, even when the improvement is modest.
Not every turbulent Treasury episode is the same kind of problem. Some are mostly about prices moving fast. Others involve the funding and settlement machinery underneath the market. This project helped make that distinction easier to read, but not easy enough to declare solved.
Project 2’s value is that it narrowed the story honestly. It tested a stronger carry idea, rejected the parts that did not survive, kept the parts that added real interpretive value, and clarified what stronger evidence would be needed before anyone could make bigger claims. That makes the broader research program more disciplined, not less.
That limitation is not a flaw in the page. It is one of the most important findings the project produced.
As the work progressed, the project became more selective, not broader. The final package locked in a baseline-unchanged result: 2y–BGCR stayed as a modest overlay, 2y–SOFR was demoted to QC, the surviving context layer stayed descriptive, and the narrow validator expansion slightly strengthened context without materially changing the final judgment.
Each stage reduced overclaim risk. The end result was smaller than the original ambition, but more defensible.
The project leaves a few narrow future branches open. These include out-of-sample tracking of the retained overlay and context set, archival Treasury fails tracking, and a cleaner public dealer-capacity branch. But all of those remain conditional. None of them reopen integration on the current record.
For readers who want the technical version, the underlying research documents contain the formal governance locks, screening results, red-team adjudication, feasibility review, narrow validator build, and final package memo.
This public page is written as a static explainer, not as a stage log. The supporting document set below governs the claim ceiling, wording discipline, and role assignments behind the page.