Ecuador Records 113,849 Name Change and Correction Requests in 2026

Pichincha leads Ecuador with nearly 5,000 name change requests in 2026.

TruthFoundry Desk

from the fact record

Stands on 6 placed sources from 2 publishers.

In 2026, Pichincha province recorded the highest number of name change or rectification requests in Ecuador with a total of 4,996 cases. ^[1] The Civil Registry of Ecuador recorded 113,849 name changes and corrections between 2024 and August 2026. ^[2] Guayas province ranked second with 4,866 name change or rectification requests, followed by Manabí with 2,431 requests. ^[3] The province of Pichincha led the national rankings with 4,996 name change and correction procedures. ^[4] As of August 2026, 26,053 name change and rectification requests have been processed in 2026. ^[5] Name changes are voluntary rights for adults, while corrections are intended to fix typographical or spelling errors. ^[6]

What this stands on

In 2026, Pichincha province recorded the highest number of name change or rectification requests in Ecuador with a total of 4,996 cases. · El Universo

The Civil Registry of Ecuador recorded 113,849 name changes and corrections between 2024 and August 2026. · Diario Expreso

Guayas province ranked second with 4,866 name change or rectification requests, followed by Manabí with 2,431 requests. · El Universo

The province of Pichincha led the national rankings with 4,996 name change and correction procedures. · Diario Expreso

As of August 2026, 26,053 name change and rectification requests have been processed in 2026. · El Universo

Name changes are voluntary rights for adults, while corrections are intended to fix typographical or spelling errors. · Diario Expreso

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 · 6 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Wednesday, September 2, 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

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.

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 was not captured for this early revision.

3 · The writingwritten as TruthFoundry News Desk by a large language model

AI · news generation

The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-03T00:36Z.

The prompts, verbatim

System instruction (the grounding rules)

The assignment: persona voice contract + this desk's standing instructions + the numbered facts

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)4bc2e35058d94cab5ad6ae1ccffcc860464bb54e6533adb3cd0ac45f098b6924

Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed

Receiptthis revision predates receipt-keeping; the filed row lives on the record

Machine readablethe full proof, JSON

Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.