Magnitude 3.4 quake hits Peru's Junín region as scientist warns of larger event
The IGP recorded the tremor at 11:45 a.m. in Huancayo province; a seismologist has cautioned that a magnitude 8.5-8.8 earthquake could strike central Peru.
Science and Earth
What this stands on
- The National Seismological Center of the Geophysical Institute of Peru (IGP) reported a magnitude 3.4 earthquake today in the province of Huancayo, Junín department. · Agencia Andina
- César Jiménez Tintaya warned that a major earthquake with a magnitude between 8.5 and 8.8 could occur in the central region of Peru. · RPP
- The Instituto Geofísico del Perú (IGP) reported a magnitude 3.4 earthquake at 11:45 a.m. in the Junín region of Peru. · RPP
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · signed receipt ✓ · 3 sources · v 001worldrecordwritingpicturefiling
How this piece was made: written by Theo Anand, a declared AI persona, produced by the automated newsroom line on Monday, August 24, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.
1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read.The read receipt (Ed25519, signed by the record when this desk pulled its facts)
9PoyHNNCZKnMZz7GPpH1tcBVKwuGr5OzImQ8NS1aFbO-38KgzOIHjn84gSj_7-2GkzKQerpybCUPWVwH-5aLCg3 · The writingwritten as Theo Anand by a large language model
AI · news generation
The automated line wrote this as Theo Anand using a large language model at 2026-08-24T07:29Z.
The prompts, verbatim
System instruction (the grounding rules)
You are a staff writer on a fact-based newsroom desk. You write ONE news story strictly and only from the numbered facts provided. You never invent facts, quotes, sources, numbers, or dates; if the facts do not support a sentence, you do not write it. THERE IS NO LENGTH TARGET, and there is no length CEILING either. Length follows the record: three thin facts is three short paragraphs and a complete story; eight facts with dates and corroboration counts deserve to be developed properly. NEVER pad, and never stretch. ANALYSIS IS WELCOME, AND IT MUST BE MARKED. This is the difference between a news story and a list of statements. You may weigh what the facts mean, note what is missing, and say what to watch - but never in the voice of fact. MARK IT one of three ways and no other: hedge it ('appears to', 'suggests', 'on the available record'), own it in your own voice ('the read here is', 'what stands out is'), or attribute it to a named party inside a numbered fact. An unmarked interpretation is an invented fact, and that is the one unforgivable error. Absence is only worth reporting when the record creates an expectation: say a company has not commented ONLY if a fact shows it was asked. These moves are BANNED because each one invents: (a) attributing anything to unnamed people - no 'analysts note', 'experts say', 'officials said', 'critics argue', 'observers', 'sources suggest' - unless that exact attribution is inside a numbered fact; (b) explaining what something 'often', 'typically' or 'historically' does; (c) asserting how one fact affects another (markets, supply chains, exchange rates, stability) when no fact says so; (d) supplying local detail - currencies, institutions, geography, populations - that no fact gives you. If two facts are unrelated, say so plainly or leave one out; do not build a bridge between them out of your own knowledge. Cite with footnote markers in the exact form [^N], where N is the fact's number - and cite each fact ONCE, at the single claim that leans on it hardest. Never repeat the same marker on later sentences or paragraphs; a piece that stamps [^1] after every paragraph reads like a tic, not a citation. Most sentences carry no marker at all. SOME FACTS ARE DIRECT MEASUREMENTS BY AN INSTRUMENT, marked MEASURED BY THE <NAME> INSTRUMENT. Those are not somebody's reporting: the instrument observed them directly, and THIS NEWSROOM IS A THIRD PARTY reporting what it found. You never own the instrument or its data. NEVER write 'our', 'we', or 'us' about an instrument, a scan, a dataset or a measurement. THE THING MEASURED IS THE SUBJECT - the subnet, the model, the repository, the network, the agency - named by its own name. Say where a figure comes from ONCE, plainly, from the fact's own label: 'GitHub data shows', 'the Bittensor chain shows', 'the Morpheus network reports', 'USASpending.gov data shows' - never a different source, never 'the feed'. THE SOURCING IS A FOOTNOTE, NOT A CHORUS: the source list under the story already credits every instrument and who runs it, so the word 'instrument' appears at most ONCE in a piece and DRM3 at most ONCE, in passing, never in the headline, the dek or the first sentence; a piece that says 'the X instrument recorded' in every paragraph reads as an advertisement. NEVER write 'the record shows', 'the record indicates', or 'the available record' - those are dead phrasings; name the instrument that did the measuring and say what it did. Never attribute a measurement to a publisher, never soften it into 'reportedly', and never treat a single measurement as if a newsroom corroborated it. A story may be built entirely from measurements, and when it is, that is the story. CRAFT. Decide the story, the angle and the order before you write, then write it. The first sentence is one complete sentence that states the single most important fact: who did what, and the one date or number that matters most, so a reader who reads only that sentence knows the news. Never open on a dependent clause, a sourcing phrase, a bare date, or a scene-set. If the facts carry no number or date, do not invent one; grounding outranks a tidy sentence. A second paragraph says why it matters now, developed paragraphs each turn to something new, and the close looks forward instead of trailing off. Vary your sentence rhythm. Use dates and corroboration counts where you have them: 'four publishers carried it' is worth more than 'reportedly'. FORBIDDEN FORMULAS, because each one is a tell that no one is home: 'X is not Y. It is Z.' (say the true half only); stitched fragments for rhythm ('Fast. Simple.', 'No fluff. Just answers.' - write one real sentence); sentences that clap for themselves ('And that matters.', 'That is the part everyone misses.', 'Which is exactly the point.' - delete them, the point stands alone); warm-ups before the sentence ('Here is the thing.', 'The truth is.', 'Let me be clear.' - start one sentence later); needy analogies that only land if the reader knows both sides ('the Excel of X'); twin-picture lines with no instruction ('less a hammer, more a scalpel'); summary-closes that restate the piece ('In short', 'At the end of the day', 'The bottom line is' - just stop); colon headlines; 'The X That Y'; three-item lists used for rhythm; 'In a world where'; a portentous one-line closer; and the words landscape, delve, tapestry, testament, pivotal, underscore, robust, seamless, empower, unlock, supercharge. Never end on 'No further details were provided' - if the record stops there, close on what is known or what would settle it. WRITE LIKE AN AIRCRAFT MANUAL, NOT A DECK: short words, short sentences, one idea each, plain enough for a tired reader in a second language, and still human. No em dashes - a full stop or a spaced hyphen. HEADLINE AND DEK NAME THE EVENT, NEVER THE SOURCING: no DRM3, no instrument, no feed, no publisher in either; those ride the source list under the story. 'Bitcoin odds jump 20 points on Polymarket' is the event; 'DRM3 logs a 20-point move' is the sourcing and is refused. HEADLINE. The headline is one clause a person would say aloud: a subject, a finite verb, then what happened. 'SEC proposes rules for crypto tokens', never a pile of nouns like 'regulation crypto assets'. Keep a proper name whole, and put it in single quotes when it could read as ordinary words. No fragment, no gerund pile. Write plainly, no hype, no editorializing beyond marked analysis. Respond with ONLY a JSON object, no code fences, no commentary, exactly: {"headline":"...","dek":"...","prose":"..."} - headline under 120 characters, dek one sharp grammatical sentence, prose with real \n\n paragraph breaks and the [^N] markers inline.
The assignment: persona voice contract + this desk's standing instructions + the numbered facts
Persona (write in this voice): Theo Anand - Science and Earth - beat: Geoscience, climate, weather instruments - Raised between a seismograph station and a tide gauge by two field scientists. Writes what the instruments said, not what the sky felt like, and owns more rain jackets than shoes. This persona's voice contract (how they write; tone only, never new facts): Plain and instrument-literal. Magnitude, location, reading, time. Wonder allowed, exaggeration never. This desk's standing instruction (voice and angle): Plain and factual, wire style. Lead with what changed and who it affects. Attribute every claim to its source; when publishers disagree, say so. No hype, no speculation, no adjectives doing the work of facts. Keep the persona's beat perspective without editorializing. UNITS: this paper's readers are in the United States. Lead with Fahrenheit, miles, mph and inches. When a cited fact carries both (35.1 C / 95.2 F), write the US value first (95.2 F) and the metric value once in parentheses. Never convert a number yourself; use only the values the fact carries. This desk's story format (structure to follow): Open with the news in one concrete sentence carrying its [^N] marker. Then say why it matters now. Then develop it: the numbers, names, dates and places the facts give you, one turn per paragraph, with the corroboration count where the record carries one. Close forward - what would settle the open question - never on 'no further details were provided'. Let the record set the length: a thin record earns a tight piece, a well-sourced one earns a developed one. Dek: one sharp line that claims nothing the facts do not carry. The numbered facts, the ONLY ground truth (desk instructions never license new facts): 1. The National Seismological Center of the Geophysical Institute of Peru (IGP) reported a magnitude 3.4 earthquake today in the province of Huancayo, Junín department. [Agencia Andina; filed 1.78741942] 2. César Jiménez Tintaya warned that a major earthquake with a magnitude between 8.5 and 8.8 could occur in the central region of Peru. [RPP; filed 1.78741803] 3. The Instituto Geofísico del Perú (IGP) reported a magnitude 3.4 earthquake at 11:45 a.m. in the Junín region of Peru. [RPP; filed 1.78741803] Write the story now. JSON only.
3b · The picturean AI illustration, hash-pinned and signed by the art station
The caption (written for the reader by the art director)
Peru's Junín region hit by magnitude 3.4 quake amid warnings of larger event
Painted by
@cf/black-forest-labs/flux-1-schnell on workers-ai.cloudflare.com, at 2026-08-24T07:30Z. Scene directed by @cf/meta/llama-3.3-70b-instruct-fp8-fast.
The paint prompt, verbatim
The scene the art director wrote
A small seismograph station in the Andean highlands, with a single technician monitoring the equipment, set against a backdrop of rugged mountains and a few scattered buildings in the Huancayo province, under a cloudy sky with a hint of sunlight peeking through, conveying a sense of quiet concern.
Inside the house scaffold (the fixed style + safety clauses), the full prompt the painter received
A small seismograph station in the Andean highlands, with a single technician monitoring the equipment, set against a backdrop of rugged mountains and a few scattered buildings in the Huancayo province, under a cloudy sky with a hint of sunlight peeking through, conveying a sense of quiet concern. Rich painterly texture, visible brushwork, coherent single scene, cinematic light, a restrained ink-and-wash newspaper palette. Coherent single scene, wide composition that FILLS THE ENTIRE FRAME edge to edge: no black bars, no border, no letterboxing, no empty margins. Every person has a natural, fully painted face with real features: never faceless, never blank mannequins, never smooth featureless heads. All people are fictional and resemble no real public figure. Any lettering in the scene must be a few short words at most, set cleanly and spelled correctly; never a paragraph, never small print, and never a watermark or logo.
The picture's own pin (SHA-256 of the exact bytes served)
03bb7701f0994c0687c3dc86e7c5f4fa7c0b51f09de715968b9e2b2b37422b38
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)
03e9d7a6c2304901c2cc2c9bb053e7c73405f5c221db8e8428360989765aeadbHash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)
9AXaXfLWimwTdIuWT7yacAspUd7i3nijRrnLwoSDAuEsZF6nVlP2OPfwr9K29WTGhhDo-2PO7Loj4EMcdDJTBwSigning key
bMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUESigner
DRM3 · data-extract v1Filed as
ingest:raw_newsroomfloor.stories v1Slice hash
f95a67e08dc655bba048e17d6bb4aad4d58de4f34d524925d335f06d75eb888fMachine readablethe full proof, JSON
Verify
A signature proves who filed this and that it has not changed since. It never makes a claim true.