Level 3, and the screen's own parts after the shell, the plate and three controls were taken out of it. 11 heads, 9 questions and 42 sections on 11 painted screens. Measured 2026-08-08 in a browser, at 390 and 1280.
The event head with its actions, the odds figure and the section it opens. 5 elements against 20 until 2026-08-09: the action tiles and the odds bar were not in the cell.
| Holds 320 YES | Side | Amount |
|---|---|---|
| You | YES | $4.94 |
| whale_07 | YES | $471 |
| hedge_hannah | NO | $588 |
| marketmaven | YES | $121 |
| polly_predicts | NO | $87 |
Your bet is highlighted. Bets update as the odds move.
Recent bets, largest first. Filter: over $5.
These always go to the wire. I am holding my position and adding if it dips.
The committee bloc looks firmer this time though.
Volume jumped right after the headline. Watching how it settles.
First bet here. The resolution source being official notices makes this easy to trust.
| Holds 320 YES | Side | Amount |
|---|---|---|
| You | YES | $4.94 |
| whale_07 | YES | $471 |
| hedge_hannah | NO | $588 |
| marketmaven | YES | $121 |
| polly_predicts | NO | $87 |
Your bet is highlighted. Bets update as the odds move.
Recent bets, largest first. Filter: over $5.
The level and its reason stay on the organisms page. What needs the room here is a cascade trap this file paid for twice in one afternoon, and one measurement that explains the whole layout of the head.
Politics · One-time event
38%
Background from the Yonder team to explain the odds. It plays no role in how this market resolves.
Politics · One-time event
38%
Background from the Yonder team to explain the odds. It plays no role in how this market resolves.
| at 390 | at 1280 | |
|---|---|---|
| the head | 350x273 to 350x309 | 630x177 |
| the question | 146x109 | 408x55 |
| the big odds figure | 146x48 to 146x60 | 408x30 |
| a section | 350 wide, 238 to 580 tall | 630 wide, 175 to 491 tall |
146px is the whole story of this head on a phone. The thumbnail keeps its size, so the question gets what is left of a 350px row and runs to three or four lines, and the head grows to 309 tall. At 1280 the same question is 408 wide and 55 tall. Nothing about the component changes; the row simply has 262px more to give away, and it gives all of it to the question.
The photograph on the specimen is a placeholder written on the element, and this file says so: one sample event image so the stand has a picture. The shipped page writes its own.
A section carries a label, and the column heads nested inside its blocks are not that label. The first attempt made the label rule a CHILD selector, which is wrong twice over: the label is a grandchild, so it lost its own rule, and a section whose label happened to be a direct child would still have caught a nested head. The distinction is not depth, it is which block the heading belongs to.
Then the fix was written and it was still short. The rule that promotes a nested head out-specifies the section label, but only for what it DECLARES: the label's uppercase, its tracking and its brass went on applying to a heading that had just been promoted into their reach. A heading that belongs to a nested block has to say so for every property the outer rule sets.
The same shape appears once more in the bets table, for the same reason and in the same afternoon.
The layout left: the two columns are a pattern, and the plate the main column stands on is in the page frame. Three controls left on 2026-08-06, the bookmark, the share and the alert over the head, and they are the icon button's tile face.
What this file may still say about them is exactly one thing: WHERE the row sits over the head. The ground, the corner, the ink, the mark, the hover, the press and the favourited state are all one file away.
A market that has settled replaces the bet panel with a resolved panel, and there is one placement of it. Inside it the state block takes its third skin: no ground, no edge, and the actions become a full-width column, because that panel is the width of a sidebar and two buttons side by side in 280px are two buttons nobody can read.
That paragraph was the whole of it until 2026-08-10. One placement is
the easiest thing in the product to describe and the hardest to picture, and this page described
it. It stands here now, from event-detail-resolved.html, and it closes two
components at once: .resolved-panel is this file's and
.rp-inner inside it is bet panel's, which is what a
panel that REPLACES another panel looks like in two stylesheets.
The cell declares the panel visible and holds it in a row, the bargain
bet panel states in full: a panel that is
display:none below 760 cannot otherwise be a specimen on a page read at both
widths.
Measured 2026-08-17 on the one screen that carries it: this panel sits
at y=167 on the desk and y=2,227 of a 4,566px document on a phone, so a reader holding a
phone met the odds explainer, a price-by-bet-size table and the rules before anything said the
market was over. ia/docs/pages/seo.md asks a resolved event for "outcome plus
at-close odds", and the head is where a reader already is: .ed-result is
y=344 on the phone now. The panel keeps its own job, which is a different sentence
- it is about YOUR bet, not about the market.
Politics · One-time event · Trading closed
Resolved YES on Jun 27, 2026
At close: YES 38% NO 62%
Resolved NO on Jun 27, 2026
Politics · One-time event · Trading closed
Resolved YES on Jun 27, 2026
At close: YES 38% NO 62%
Resolved NO on Jun 27, 2026
The NO face has no placement and it is drawn anyway, which is this
repository's own rule about the chosen NO. A rule that cannot be rendered cannot be checked
and will be wrong the day it first draws, and half of a symmetric control had gone unmeasured
here once already. The side takes --outcome-yes-text rather than
--result-won-text: the two are the same colour for different reasons, and this one
is which side of the MARKET won, not whether the reader's bet did. Measured from the render on
both engines: 10.00 in the Vault and 7.43 in Daylight for the side, 14.97 and 15.24 for
the line it stands in.
Five classes this file declares stood on 9 screens each and nowhere in the
kit until 2026-08-10: .ed-facts, .resolution,
.args and .arg-col, plus the resolved panel above. They are not
decoration. The resolution paragraph is the sentence the whole product is built to be trusted
for, the one that says what makes this market pay out, and the design system had no picture
of it.
Both panels, from event-detail.html, and the second is the one
the Background tab shows. The strip above them is
tabs' third family; what is shown here is what the strip switches.
Resolves YES if a federal funding gap causes a shutdown beginning before 00:00 ET on March 1, 2027. Resolves NO if funding is in place through that date.
Source: official US Office of Management and Budget notices. Resolved by the Yonder team.
YES is priced at 38%. Funding talks have stalled twice this quarter, but the last three deadlines were settled at the last minute. What is moving the number:
Background from the Yonder team to explain the odds. It plays no role in how this market resolves.
Resolves YES if a federal funding gap causes a shutdown beginning before 00:00 ET on March 1, 2027. Resolves NO if funding is in place through that date.
Source: official US Office of Management and Budget notices. Resolved by the Yonder team.
YES is priced at 38%. Funding talks have stalled twice this quarter, but the last three deadlines were settled at the last minute. What is moving the number:
Background from the Yonder team to explain the odds. It plays no role in how this market resolves.
The second panel ships with hidden on it and it is
unhidden here, which is the same difference the shut dialog taught: a specimen inside a hidden
box is 39 correct elements the browser never paints. Both panels stand open together so the two
can be compared, and on the screen only one is ever shown.
.rules-panel reaches no rule at all. 18
placements on 9 screens, and no selector in components/ matches it. What draws is
the paragraph inside it. Filed as backlog 85, with the other eight of its kind.
Its own width query: 640 DESK, 560 one-off. At DESK the two argument columns go from stacked to side by side, each taking half. The 560 below it is a one-off and says so: three 36px tiles 8 apart ask for 140px of clearance against 118 of padding, so the head takes 100px of right padding under it. 560 is not a rung and collapsing it up to DESK would take three controls from 36 to 28 on 79 widths that have room for them.
A screen file owns its own parts and nothing else. The shell is a pattern, the plate is the page, the controls are atoms, and what is left is a head, a facts row and a resolution block.
A heading belongs to a block, not to a depth. Selectors that reason about how deep something is will be wrong the first time the markup gains a wrapper.
Never out-specify a rule for one property and assume the rest are handled. Uppercase, tracking and brass all went on applying to a heading that had been promoted out of their reach on the property that mattered.
Never use depth to say what a thing belongs to. The label is a grandchild and the nested head is a child, and the child selector got both of them backwards.
Never let a screen file draw a control. Three of them stood here, and the only correct sentence left is where the row sits.
The level and its reason:
the organisms page. The stylesheet:
components/event-detail.css. The shell:
components/patterns/detail-shell.css. The three controls over the head:
icon button. The tabs below it: tabs. The bet
control beside it: bet panel. The odds bar in the head:
odds bar.
These always go to the wire. I am holding my position and adding if it dips.
The committee bloc looks firmer this time though.
Volume jumped right after the headline. Watching how it settles.
First bet here. The resolution source being official notices makes this easy to trust.