Can an agent preserve a public record's identity?
Begin with a specific public record reference. A software client should preserve that identity rather than silently turning a new interpretation or summary into the original record.
A successful independent second-client read remains part of the fuller experience.
Can software carry a public record's identity without inventing new verification?
An agent read is useful only if the identifier survives the trip. This journey starts from a governed public Source, uses a documented interface, and stops before claiming a comparison that was not actually performed.
See the subject in Counterpedia History of Science · governed Entry · Existing admitted record; distinct from Source and agent-access rightsOr begin with step 1 ↓A reading exercise
Ask for an account you can follow
Suppose an agent explains a passage from History of Science. What would let you follow the answer back to the material it used?
The account to be explained
Open the History of Science entry and choose a passage. A useful answer should identify the passage it is explaining, rather than give a free-standing summary.
History of Science · governed Entry Existing admitted record; distinct from Source and agent-access rightsThe source behind the account
Open the Source page to see what publication is recorded behind the entry. Keep the entry and its source distinct when checking the answer.
History of Science · public Source Source · existing public record; retained-text permission is separateSee the distinction
Ask for a short explanation and its references, then follow those references yourself. The reading page, Source page and an agent's account do different jobs. A real client call is needed to show what the agent returned; this reading exercise does not make that call.
Carry this forwardKeep a useful explanation connected to the passage and source it relies on.
Follow the trail
- 01
Open the governed Source
Open the History of Science entry and follow its documentary Source. Note the public record identity, WIKI-HISTORY-OF-SCIENCE-0001, separately from the Source identity, WIKI-HISTORY-OF-SCIENCE-0001-SRC-0001. You will compare record to record and Source to Source when software returns them; the two identifiers name different objects.
Open History of Science · governed Entry Existing admitted record; distinct from Source and agent-access rights
Open History of Science · public Source Source · existing public record; retained-text permission is separate
Keep: The record ID and Source ID, explicitly identified as different objects.
- 02
Read the interface documentation
This walkthrough uses the public MCP read interface documented on the Agent access page. In one compatible client, follow that page's connection instructions and confirm that the documented counterpedia.read operation is available. Note the interface version and access conditions. If the client cannot expose that read, record the limitation rather than switching silently to an HTML page or another interface.
Open Agent access and documented interfaces Public product documentation
Keep: The documented interface, access conditions, and availability in your client.
- 03
Exercise one read
Use counterpedia.read to request record WIKI-HISTORY-OF-SCIENCE-0001. Inspect the returned record identity, edition and any documentary Source references, comparing each with the same kind of object you opened earlier. Ask the client to explain one passage actually returned by a permitted read and identify the material it used. If the response provides only metadata or no readable passage, record that limit instead of supplying text yourself. Keep the request, response references, interface version and access conditions with the explanation. To read a section's text rather than the record summary, run counterpedia.search first and pass one returned section's open_reference to counterpedia.read unchanged.
Open Agent access and documented interfaces Public product documentation
Keep: The actual read request and response identities, or a documented refusal or failure.
- 04
Do not simulate a second client
Comparing identity and edition across clients is only evidence if a second eligible client was actually exercised. If it was not, say so, and do not describe a comparison, a second read or an independent verification that did not run. One supported read supports a single-client statement and nothing more.
Keep: A single-client statement unless a second authorized client was really exercised.
- 05
State the boundary
Finish with the useful explanation, the passage it addresses, the returned record and documentary Source identities, the interface and edition, and the access limits actually observed. Mark any identity or edition the response did not provide as unavailable. If the read was unsupported, refused or not performed, record that outcome explicitly; a plausible explanation alone does not complete the client task.
Open History of Science · public Source Source · existing public record; retained-text permission is separate
Keep: A passage-grounded explanation with identities and limits, or explicit non-completion.
Open the material
- History of Science · governed EntryExisting admitted record; distinct from Source and agent-access rights
- History of Science · Counterpedia searchSearch · governed-indexed subject
- History of Science · public SourceSource · existing public record; retained-text permission is separate
- Agent access and documented interfacesPublic product documentation
- Wikipedia · History of scienceOriginal publisher material
Research material is not admitted evidence; publisher links identify someone else’s document.
What to notice
- A returned identifier is not new verification of the record or documentary Source.
- Access may require credentials; an unavailable read is not an empty record.
- One client exercised is not a cross-client comparison.
- A public index listing and an accessible software-interface response are different claims.
- Retrieving a record through software is not a new assessment of it.
A useful finish
A useful passage-grounded explanation from one actual supported client read, with record and documentary Source identities kept distinct and the edition, interface and access conditions recorded. An unsupported, unavailable or unperformed read is reported explicitly and does not count as client-task completion. No cross-client comparison is implied.
Worked example
Observed on 4 November 2026 on the public site, signed out. This is what one actual run of these steps produced.
One anonymous read through counterpedia.org/mcp returned record WIKI-HISTORY-OF-SCIENCE-0001, edition WIKI-HISTORY-OF-SCIENCE-0001-ED-0001 and Source WIKI-HISTORY-OF-SCIENCE-0001-SRC-0001: the same identities the public pages show.
The returned text supports a narrow explanation: the record is a governed admission of a captured Wikipedia article, and it states that admission establishes no factual truth.
What it rests on
- counterpedia.read and counterpedia.sources responses from the documented endpoint (server counterpedia-mcp 0.1.0, no sign-in), made from one client.
- The Source's capture: Wikipedia, History of science, captured 19 August 2026, SHA-256 26a6e6c4…
What it did not establish
- A read by record_id returned the article's passages only as span identifiers, so that response alone could not explain a passage of the article.
- One client only; no comparison across clients.
Later check, 5 November 2026: counterpedia.search for History of Science returned three section references. Passing the first unchanged to counterpedia.read returned the complete public section “Ancient Origins”: “Ancient civilizations including Mesopotamia, Egypt, Greece, India, and China made systematic observations of nature.” It cites span WIKI-HISTORY-OF-SCIENCE-0001-SPAN-0002 and Source WIKI-HISTORY-OF-SCIENCE-0001-SRC-0001, edition …-ED-0001. It is Counterpedia's public section text drawn from the capture, not the full captured article; one client, no comparison across clients. Explained narrowly from that returned passage: Counterpedia's public section states that several ancient civilizations made systematic observations of nature. An agent can cite it as that section, with its span and Source, but the passage is not by itself a verified historical finding.
If it stops
- A second-client comparison is not established by this journey.
- Agent access depends on credentials and supported interfaces.
- Deployed API or MCP support is not inferred from a search listing, and no independent verification is claimed that did not run.
- History of Science is an illustrative subject; the method applies to any identified public object a supported interface can read.
Go deeper
Before you go deeper: The first chapter, Using Counterpedia with agents and software, uses a Boeing 737 MAX record as its example, not History of Science, and goes further than this page: it configures a client identity, follows a source reference, inspects an existing receipt and carries the work to another client. Apply its method to the History of Science record you read here; a second client stays unexercised until you actually run one.