odh traffic today --type bike --include-stale --limit 20000 returns 19 events, every one active: true, the oldest starting 2019-04-05. They are formatted identically to good data, and several no longer appear in the live Content API bulletin.
The freshness warning that would save the reader is third of four.
This is the worst-placed instance of a general problem: bike is the one category name that exactly matches a plausible user question ("is any cycle route closed?"), so it is the most discoverable path, and it leads to the frozen feed. An agent that skims the warnings answers confidently and wrongly. In a field test of v0.5.0 the agent only escaped by checking the newest-row date itself.
--type bike is rejected under --source content (correctly — announcements carry no cycle tag, so a tag filter would drop real matches), which leaves the category with no live path at all.
Options
- Order warnings by severity, so a feed whose newest row is ~11 months old leads rather than trails.
- Have
--type bike name the live route in its output, the way the --source content rejection already suggests --search radroute.
- Both.
Not proposing to remove the category: the historical rows are legitimate as history, and --include-stale is the documented way to ask for them. The defect is that they are presented with active: true and a quiet caveat.
Done when
- A
--type bike answer from the frozen feed cannot be read as current without the reader having seen the age.
odh traffic today --type bike --include-stale --limit 20000returns 19 events, every oneactive: true, the oldest starting 2019-04-05. They are formatted identically to good data, and several no longer appear in the live Content API bulletin.The freshness warning that would save the reader is third of four.
This is the worst-placed instance of a general problem:
bikeis the one category name that exactly matches a plausible user question ("is any cycle route closed?"), so it is the most discoverable path, and it leads to the frozen feed. An agent that skims the warnings answers confidently and wrongly. In a field test of v0.5.0 the agent only escaped by checking the newest-row date itself.--type bikeis rejected under--source content(correctly — announcements carry no cycle tag, so a tag filter would drop real matches), which leaves the category with no live path at all.Options
--type bikename the live route in its output, the way the--source contentrejection already suggests--search radroute.Not proposing to remove the category: the historical rows are legitimate as history, and
--include-staleis the documented way to ask for them. The defect is that they are presented withactive: trueand a quiet caveat.Done when
--type bikeanswer from the frozen feed cannot be read as current without the reader having seen the age.