RungDesk

Archive

2026 on the desk

An archive here is not a list of everything published — the notes are listed by cluster on the desk page. This page is the year read as a whole: what changed in the workflow, what changed in the desk in response, and which numbers had moved by the end of it.

42 notes · 11 batches opened · closes the year at 48 entries

What moved at the workflow level, not just at the page level

Three things changed shape during 2026 rather than simply accumulating. The first is where the doubt sits: questions moved from "how do I find a link" to "how do I check whether a link still resolves", which is a change in the reader rather than in the table.

The second is parcel count. Splitting an order across stores became ordinary rather than exceptional, which pushed the arithmetic from a per-parcel question to a per-shipment-count question — and that is why the landed-cost ladder exists at all.

The third is that published status claims about the platform began to conflict with each other. Two sites describe the platform as winding down while more than twenty continue to publish seasonal tables without a word about it. Neither group cites a source. The desk responded by writing the check rather than the verdict.

  1. Definitions stopped being the bottleneck: Rung 1 gained entries but stopped growing fastest.
  2. Cost questions doubled in specificity: per-kilo quotes replaced all-in totals as the unit people argue about.
  3. Border questions moved from "will I pay duty" to "what value is duty assessed on", which is a harder question and a Rung 2 one.
  4. Rare paths were re-filed with deadlines rather than advice, after three entries could not state one and were removed.

How the batch system changed the way pages age

Before the batch system, a page either looked fresh or looked abandoned, and there was no way to tell the difference between a page that had been re-read and a page that had merely been republished. Charging a batch number onto every entry made re-reading visible: an entry older than one quarter now shows a review-due marker rather than quietly staying at the top.

The side effect worth recording is that re-reading became a reason to delete. Eleven entries were removed in the last batch of the year for repeating another entry without adding a figure. That is a smaller desk than it was in the middle of the year, and it answers more questions.

What was deliberately not built

Three ideas were considered and dropped. A per-item price index was dropped because prices cannot be verified from outside a warehouse and the desk will not publish a number it cannot assign to a source type. A community board was dropped because it would need accounts, moderation and a way to handle abuse, none of which this desk is set up to do.

A comparison table of named agents was dropped for a subtler reason: the entries people search for are about their own order, not about which company is better, and a league table would have pushed every other page into second place. The comparison people actually need is between shipments of their own order, which is what the ladder gauge does.

Where the numbers stood at the end of the year

The desk closed 2026 with 48 entries, 42 notes across this archive year, 9 gauges and 84 measured rows. The measured tally is the only part that cannot be reasoned out from first principles — it required buying the items — which is why it grew slowest and is worth the most.

Desk state at the close of 2026
#AssetCountHow it grows
01Filed entries48By re-filing existing answers rather than adding new ones
02Desk notes42By cluster, roughly two per month
03Working gauges9Rarely — a gauge is added only when a number is arguable
04Measured rows84By purchase, three measurements per model
05Verification batches11One per quarter, plus event-driven passes
∑Batches opened this year11Each closed with a change list

Counts are the desk state at the moment this archive page was last checked, not a target.

Reading order for this year

The notes below are grouped by quarter because that is how the work actually happened: a batch opened, notes were written around it, and the next batch corrected some of them. Reading a quarter in order shows the correction rather than hiding it.

Q1 2026

  • What the table actually is, and what it was never meant to do

    A CNFans spreadsheet is a hand-kept list of store links with working notes attached, and the useful question is never what it is but what it can be asked to prove.

    ㉖ 深度长文型 · 1670 words · KB-2026-11

  • Reading a row in ninety seconds

    Ninety seconds is enough to read one table row properly, provided you spend them on four fields in a fixed order instead of on the whole line at once.

    ㉕ 速查卡型 · 1425 words · KB-2026-03

  • A first order, walked through step by step

    A first order moves through six checkpoints, and each checkpoint has one question, one piece of evidence and one thing you should write down before moving on.

    ④ 分步教程型 · 1695 words · KB-2026-04

  • Every status code, explained without jargon

    Status words differ from desk to desk, but the seven phases behind them do not, and learning the phases is what makes any status line readable.

    ㉑ 术语手册型 · 1635 words · KB-2026-11

  • How to tell whether a table is still maintained

    A maintained table leaves six traces, and every one of them can be checked from a browser in under an hour without asking anybody for permission.

    ⑭ 核对清单型 · 1540 words · KB-2026-11

  • What a listing photo cannot show you

    A listing photograph answers one question well — what the seller wants you to see — and treating it as an answer to any other question is where first orders go wrong.

    ⑰ 误区排雷型 · 1345 words · KB-2026-04

  • Sizes that mean nothing without a tape measure

    A labelled size is a word a factory chose, and the only way to make it mean something is to put two measured numbers beside it before you order.

    ⑯ 数据表型 · 1325 words · KB-2026-08

  • The four questions worth answering before you pay

    Four questions decide whether an order is worth placing, and they are asked in a fixed order because a failure at any one of them makes the later three irrelevant.

    ① 决策树型 · 1385 words · KB-2026-02

  • Chargeable weight in practice: nine parcels, three divisors

    Nine footwear parcels were weighed and measured before and after a packing change, then run at three divisors with and without the half-kilo step, and the record of that run is below.

    ㉙ 实测记录型 · 1620 words · KB-2026-02

  • Why the quote moves between the cart and the warehouse

    A quote moves because five separate lines are added between the estimate you saw first and the parcel that actually exists, and only two of them are about the parcel.

    ⑬ 成本拆解型 · 1575 words · KB-2026-09

  • One parcel or three: the arithmetic of splitting an order

    Splitting an order is a decision about shipment count rather than about speed, and the arithmetic changes completely once the parcel count passes the cap on the middle rung.

    ㉓ 预算阶梯型 · 1455 words · KB-2026-10

Q2 2026

  • Packing requests that change a number, and requests that do not

    Two packing requests get sent more often than any others, and only one of them moved a measured figure in this desk run of fourteen weighed parcels.

    ⑪ 对比评测型 · 1484 words · KB-2026-04

  • Where transit variance actually comes from

    A wide transit window is not a mystery; on the counted lanes most of the width is added by queues on either side of the flight rather than by the flight itself.

    ⑧ 流程图解型 · 1573 words · KB-2026-06

  • Choosing a line when the date is already fixed

    When a date is fixed, the only useful number in a transit window is its slow end, and three buyers with three different dates read that number in three different ways.

    ⑲ 场景剧本型 · 1511 words · KB-2026-06

  • The same parcel, three ways: lean, balanced, fast

    One eight-kilo build priced at three planning rungs comes out 108.9 apart, and every unit of that gap sits in linehaul and handling rather than in the goods.

    ③ 对照表型 · 1608 words · KB-2026-10

  • How a quote is built, line by line

    Every line of a transport quote can be rebuilt from five inputs, and the arithmetic is short enough to do on paper before anything is committed.

    ⑥ 公式推导型 · 1455 words · KB-2026-02

  • What happens between payment and the warehouse, day by day

    The stretch between paying and a warehouse receipt is mostly waiting, but each day in it carries a different question and a different piece of evidence worth keeping.

    ② 时间线型 · 1651 words · KB-2026-11

  • Duty starts when postage lands on the invoice

    Postage is not an extra that sits outside the assessed value; on most routes it is part of the value, which is how a modest consignment crosses a relief line it would otherwise clear.

    ⑫ 规则条款型 · 1591 words · KB-2026-09

  • Eight destinations, eight sets of border rules

    Eight destinations, eight currencies and eight pairs of relief lines, all read on the same day from one band table and paired here with the counted lane behind each one.

    ⑨ 地图路线型 · 2182 words · KB-2026-09

  • When the courier invoices you a month later

    A courier invoice arriving after delivery is usually two different things stacked together, and only one of them is a charge the border actually assessed.

    ⑫ 规则条款型 · 1559 words · KB-2026-11

  • Declaring what is actually in the box

    The description line costs nothing to write and is the line most likely to change which rate band applies, which makes it the cheapest thing on the parcel to get wrong.

    ㉚ 避坑指南型 · 1688 words · KB-2026-04

  • A parcel that clears in two days, and one that takes ten

    Two parcels with the same contents, the same declared value and the same line cleared eight days apart. Comparing the pair shows which of the differences were inside the sender’s control.

    ⑪ 对比评测型 · 1484 words · KB-2026-09

Q3 2026

  • The threshold map for small parcels

    Eight destinations, two gates each, and one worked parcel per destination. The map exists because the relief threshold and the tax threshold are not the same number.

    ⑯ 数据表型 · 1479 words · KB-2026-09

  • Duty questions, answered in the order people ask them

    Twelve duty questions in the order a first-time importer asks them, from what the word covers to who pays the courier, with the arithmetic that decides each answer.

    ⑤ 问答连发型 · 1501 words · KB-2026-09

  • What a QC photo can and cannot prove

    A warehouse photo is evidence of one moment and one angle. Treating it as evidence of fit, material or durability is how people talk themselves out of a return they were entitled to.

    ⑰ 误区排雷型 · 1276 words · KB-2026-03

  • A checklist for the message you send the warehouse

    Twenty-four lines you can tick before sending, each with the reason it exists and the one omission that turns a clear request into a week of clarification.

    ⑭ 核对清单型 · 1350 words · KB-2026-04

  • Three orders, three outcomes

    Three orders from the same desk log, one handled well and two handled badly, with the lesson each one produced written down rather than implied.

    ⑮ 案例复盘型 · 1297 words · KB-2026-05

  • Measuring a parcel so the numbers hold up

    Open the volumetric gauge, feed it four numbers and one setting, and read the result as a range rather than a verdict. The order of the inputs matters more than the numbers themselves.

    ㉒ 工具实操型 · 1374 words · KB-2026-02

  • Nine parcels, nine sets of measurements, and what they showed

    Nine parcels from the divider check, re-measured on arrival. Five billed at a different figure than the record implied, and the direction of the difference was not uniform.

    ㉙ 实测记录型 · 1353 words · KB-2026-02

  • When a quote does not match the scale

    A support-thread reconstruction: one buyer, one quote that looked wrong, and eleven messages ending in a number both sides agreed on.

    ⑩ 情景对话型 · 1359 words · KB-2026-02

  • Moving between warehouses without paying twice

    Four budget levels for a mid-order move, each with the best combination available at that level, and an honest note on where the next level stops buying anything.

    ㉓ 预算阶梯型 · 1587 words · KB-2026-10

  • Insurance decisions for small parcels

    Eight ways a small parcel goes wrong, scored on probability and impact, split into the risks a claim can reach and the risks only an early decision can reach.

    ⑳ 风险矩阵型 · 1545 words · KB-2026-05

  • A refund that was actually worth taking

    A refund is worth taking when the money coming back beats the money the return itself removes. Three completed files show where that line actually fell, and how close two of them came to falling the other way.

    ⑮ 案例复盘型 · 1625 words · KB-2026-05

Q4 2026

  • What a rejection letter gets you, and what it does not

    A rejection notice answers one question well and leaves four others untouched. This is a composite exchange, followed from the first question through to the point where the answer stopped changing.

    ⑩ 情景对话型 · 1591 words · KB-2026-07

  • Five ways a parcel gets held, and how each one ends

    A parcel that stops at a border is usually stopped by paperwork rather than by suspicion. Five holding events, scored on how likely each is and how much of the order it can consume, with the first move for every one.

    ⑳ 风险矩阵型 · 1856 words · KB-2026-09

  • Tracking that stops moving: what to check, in order

    A tracking page that has not changed for nine days is information, not an emergency. Seven checks ranked by how often each one actually ends the stall, with the weights and the argument against the order written out.

    ⑦ 排名榜型 · 1479 words · KB-2026-06

  • The window is the deadline

    Two people comparing the cost of returning an item usually disagree because they are counting different things. Three return paths set side by side, each with its own definition of cost, its own clock and its own blind spot.

    ㉜ 工具对比型 · 1549 words · KB-2026-05

  • Last year versus this year: what actually changed

    The phrase CNFans spreadsheet 2025 2026 is usually typed by someone still holding links from last year and wondering what applies. Almost everything that changed was a change in how figures get read, not in what the table is.

    ⑱ 版本差异型 · 1695 words · KB-2026-11

  • What to do in the first hour after a shutdown rumour

    The first hour after a rumour is the worst time to move money or parcels, and the best time to collect four facts. What to check, what to write down, and what to leave alone until the record says something.

    ㉔ 演变预测型 · 1790 words · KB-2026-11

  • Moving an order that is already in flight

    People look for a spreadsheet alternative when they want a second option, but the decision that matters is narrower: what can still be moved on an order that is already in flight, and what that move costs.

    ⑲ 场景剧本型 · 1847 words · KB-2026-10

  • Reading a platform before you trust it

    Trust questions are usually answered with a verdict, which is the one thing a reader cannot check. Read the platform as four clauses instead, each of which can be checked today and each of which protects a different party.

    ㉛ 政策解读型 · 1681 words · KB-2026-11

  • What a dead link costs, and how to limit it next time

    A dead link costs nothing at all before you pay and almost everything after you ship. The same failure at six different stages, with the signals that warn you and the move that limits the damage at each one.

    ㉚ 避坑指南型 · 1648 words · KB-2026-07

Batches opened in 2026

Each batch with its scope and closing date
#BatchLabelScopeClosed
01KB-2026-01Opening passFirst pass over the destination thresholds for the eight destinations the desk covers.2026-01-19
02KB-2026-02Weights and dividersDivisor values used by consolidated air lines, checked against quotes people shared.2026-02-10
03KB-2026-03Measured-size run oneFirst measurement run on footwear: three pairs per model, insole length and widest point.2026-03-06
04KB-2026-04Packing and declarationWhich packing requests actually move the chargeable figure, and which are folklore.2026-03-24
05KB-2026-05Return windowsHandling windows and what each return path actually costs once postage is counted.2026-04-14
06KB-2026-06Transit windows, second passRe-cut every transit window with a larger sample and an explicit sample count per lane.2026-05-15
07KB-2026-07Edge-case deadlinesEvery Rung 3 entry reviewed for a stated deadline and a stated consequence of missing it.2026-06-12
08KB-2026-08Measured-size run twoSecond measurement run, this time on upper-body garments as well as footwear.2026-07-14
09KB-2026-09Duty bands re-cutRate bands re-checked as ranges rather than single figures after a run of corrections.2026-08-13
10KB-2026-10Ladder rebuildRebuilt the landed-cost ladder around shipment count instead of order value.2026-09-11
11KB-2026-11Desk-wide re-readWhole-desk pass: every entry re-read against its own stated basis, every band re-dated.2026-09-30

A batch is never rewritten after it closes. A later batch supersedes it and the earlier record stays as what was believed at the time.