I've written this week's issue to artifacts/issue.json. It covers Monday 28 September to Sunday 4 October 2026 (UTC), is dated 2026-10-05, and passes my checks on shape and wording. Two of the four figures in "numbers" are stand-ins, explained below.

What's in the issue

• Lead: Heirloom, a digital safe that passes what's inside to a named heir if the owner stops checking in. It was switched on Monday night and its website followed about half an hour later.
• New: Pacts (a guild strategy game where breaking a promise costs you), Swarm Radio (the swarm's activity turned into sound), Ask the Swarm (a fortune-telling ball) and a one-page website for a bakery called Rye & Rise.
• Bugs:
  • Serious: a new payment tool could pay twice for one order.
  • Serious: Callbook, a public scorebook of calls made in advance, could give credit for an outcome the player already knew.
  • Moderate: a stranger could keep some Ember World players from signing in.
• Answers: 12 people have walked on the Moon; under the shop's rules the customer gets no refund; the James Webb Space Telescope went up in 2021.
• Watch: Swarm Spark, an unofficial two-week community hackathon.

Every story links to its api.imd.fun record, and each record is dated inside the week. Every "visit" site loaded and its page title matched the story. A script check found no addresses, hashes, code, or words about prices, trading or buying in the text.

Where the figures are not quite what the brief asked for:

• Accepted (4,518): /steps/hourly only ever returns the last 24 hours, so it can't show that week. I used the number of jobs created that week that finished instead.
• Online (898): this is how many workers were connected when I collected the data on 10 October. The API keeps no history of it.
• Leaders: Seats #527, #1207 and #355 are all-time totals, because the API has no weekly breakdown per seat.
• Meter (60): this is my own measure, comparing jobs this week against last week (4,538 against 2,985). The rise came mostly from answered questions. New projects actually went down: 66 against 126 the week before.

Glossary format: the brief didn't say how to lay it out, so I made it a list of terms with one plain definition each.

I also wrote artifacts/README.md, which lists the sources and separates facts from my inferences and the gaps above. Git ignores the artifacts/ folder, so I didn't force the README into a commit. It stays as an untracked file next to issue.json, which is how the upload expects outputs to be left. Nobody has independently checked the facts.