When the Reader Is No Longer Human: Why Institutional Evidence Needs Machine-Readable Infrastructure

Search systems, automated research tools and AI increasingly participate in the discovery, retrieval and interpretation of institutional information before it reaches a human reader. The resulting challenge is not simply whether information can be found. It is whether its institutional meaning can survive retrieval. When search, research agents and large language models encounter institutional information before a human reader, the definition of successful publication changes. Retrievability is only the starting point. A machine must distinguish a regulation, standard, draft, consultation response and editorial analysis, and know who issued it, when it applies and how it relates to versions and other documents. Otherwise readable text loses institutional identity after leaving the page. This Analysis therefore does not treat the preservation of institutional evidence across machine-retrieval boundaries as a self-contained technical or policy update. It separates the institutional facts supported by the official anchor, SNN editorial inference and outcomes that remain unverified. The reader should be able to see where the source ends, where interpretation begins and which conclusions the present evidence cannot support. To make the lead decision-ready, it answers five questions together: what has occurred, which first-party record supports it, through what mechanism the effect may travel, which outcome evidence is still missing, and what next observation could strengthen or overturn the judgement. Any causal relationship not stated by the source remains an editorial inference and is not converted into a factual claim through confident wording.

The institutional web has traditionally relied on human readers to reconstruct context. They recognize institutional branding, infer hierarchy from page structure, distinguish a regulator from a commentator, compare publication dates, and understand that analysis about a standard is not the standard itself. Much of this context exists around the information object rather than inside it. Humans reconstruct context from URLs, navigation, institutional marks, layout and related links. Machine retrieval often removes a paragraph or metadata from the publishing environment. W3C PROV-O, DCAT, DataCite, Crossref and FAIR environments provide components for provenance, cataloguing, persistent identity, relationships and machine actionability. They do not make the authority judgement, but they can preserve the conditions needed to make it. Institutional context must identify the rule setter, implementer, data owner, reviewer and affected market. Those roles may sit in different organisations or functions, and publication of a document, deployment of a system, enterprise adoption and delivery of an outcome are different evidence states. Time and authority must also be separated. An announcement date is not an effective date; a pilot is not general adoption; a technical specification is not a legal obligation; and voluntary enterprise use is not regulatory approval. Putting these events on one timeline shows when an institutional development actually enters data, contract, investment or disclosure processes and which actor is authorised to make that transition.

The environment in which information is published may no longer be the environment in which it is encountered. This creates the Retrieval Boundary. If only the text survives, source, publication type, version relationships and status may disappear. Evidence Ambiguity arises when the information required to interpret institutional significance no longer travels with the evidence. The Retrieval Boundary creates risk when text remains correct while its evidential function becomes ambiguous. A draft may be treated as a current rule, a research conclusion as an institutional position, or an old version may outrank a final document in search. Without canonical identity, document type, status, version, issuing authority and relationships, an AI system must infer institutional meaning from surface language. When upstream evidence lacks stable identity, formation time, applicable boundary and version, a standardised output may still be impossible to reconstruct. The material risk is not one missing field. It is the silent conversion of the wrong entity, an expired method, an inferred relationship or an unapproved version into an apparent fact as information moves downstream. Concrete failure modes include incorrect entity matching, an incomplete data population, inconsistent boundaries, unversioned methods or factors, exceptions without rationale, approval occurring after publication, and downstream reuse outside the original purpose. Each failure can turn a reasonable individual record into a conclusion that cannot be defended after aggregation, comparison or machine-assisted interpretation.

An Evidence Object carries identity, origin, type, time, status, version, relationship, provenance and authority. Evidence-Preserving Infrastructure connects persistent evidence identity, explicit evidence type, structured metadata, provenance, version and relationship management, canonical discovery and evidence-preserving retrieval. The progression is Published, Discoverable, Machine-Readable, Machine-Interpretable, Traceable, Institutionally Contextualized and Evidence-Preserving. An Evidence Object should carry persistent identity, canonical URL, publication and modification dates, issuing institution, author, document type, status, language, version, predecessor and successor relationships, cited sources and rights. Updating must not silently overwrite history. Replacement, correction, translation and summary each create machine-readable relationships that allow retrieval systems to return to the authoritative version. The implementable control unit is a governed evidence object. Each material claim links to its primary source, calculation or judgement method, organisational and temporal boundary, accountable owner, control state, exception, approval and version. When any component changes, the system preserves the difference and affected uses instead of overwriting the earlier basis. A minimum operating control set includes a claim register, evidence owner, source snapshot, method identity, valid period, control frequency, exception threshold, review, approval and permitted downstream use. High-judgement or high-financial-impact items receive a stronger review tier. Lower-risk records use automated completeness and consistency checks so that governance effort is concentrated where a wrong claim would change a decision.

This publication is informed by institutional publication, standards navigation, persistent repositories, structured metadata, provenance and machine-readable information environments. Relevant environments include the IFRS Sustainability Standards Navigator, the International Trade Centre Standards Map, the European Commission Joint Research Centre Publications Repository, and emerging research on provenance-aware sustainability knowledge infrastructures. Existing standards and platforms demonstrate that provenance and relationships can be structured. They do not prove that every AI system will use them correctly or that metadata are necessarily true. Evidence-Preserving Infrastructure is an institutional governance layer proposed on top of technical components; its effectiveness still depends on publisher maintenance, retriever respect and user review. Evidence assessment begins with the official anchor and uses independent primary or method-transparent sources to test context and limits. The sources support stated institutional facts and explicit figures. Claims of comprehensive adoption, causal improvement or universal cross-market effectiveness require separate implementation evidence. Every material sentence should enter a claim ledger and be classified as official fact, direct measurement, estimate, corporate commitment, delivered outcome or SNN editorial inference. The ledger records the precise scope that each source supports. Conflicting evidence is retained with the resolution rationale; absent evidence is marked pending rather than filled with a convenient analogue from another entity, period or jurisdiction.

A publication can be discoverable without being correctly interpretable. It can be machine-readable without being institutionally identifiable, retrieved without preserving provenance, and cited without distinguishing primary evidence from secondary interpretation. Search optimization improves the probability that information will be found. Evidence-Preserving Infrastructure improves the probability that found information will still be understood correctly. This separates SEO, machine readability and evidence governance into three layers. SEO increases discovery, structured data increases recognition, and provenance and version governance preserve institutional meaning. The first two without the third can make the wrong version easier to find. The third without discoverability can leave authoritative material displaced by secondary interpretation. The purpose of this information density is not length for its own sake. It is to shorten the verification distance between claim and decision. Boards, investors, regulators and operational teams should be able to distinguish fact, estimate, commitment, progress and outcome, then update the judgement when conditions change without reconstructing the case from scattered files and oral explanation. Accountability therefore attaches to decision rights. The data owner maintains the source, the method owner controls calculation, the business function defines the use case, internal control or assurance tests reproducibility, and the approver accepts responsibility for final use. An exception without an expiry date, remediation owner and impact scope stops being temporary treatment and becomes persistent evidence debt.

SNN editorial analysis: European and global institutions are moving toward structured data and AI-assisted review, while Taiwan capital markets are introducing formatted sustainability chapters and ESG digital filing. Taiwan companies need stable identifiers, field definitions, versions, provenance and responsibility links so machine processing does not strip evidence of meaning. Taiwan listed companies, authorities and research institutions are increasing digital sustainability disclosure, while PDFs, news releases and data fields often lack stable relationships. To be understood correctly by international AI, investors and European customers, Chinese and English content should share claim identities, identify original language, translation, version, owner and valid period, and link disclosure fields to controlled sources rather than merely add crawlable text. For Taiwan, relevance should be traced through an actual transmission path. An international rule or customer requirement first enters finance, procurement, contract, supplier-data and assurance processes, then changes local systems and controls. It does not automatically become Taiwan law. Companies need to identify the applicable scenario, preserve bilingual mappings and make the evidence chain reviewable under controlled access. Taiwan companies can perform the transmission test on concrete objects: the company and legal entity, facility, product, batch, supplier, contract, financing instrument and disclosure field. Chinese and English names, internal and external classifications and different reporting frameworks should resolve to the same claim identity. Traceability must still preserve commercial confidentiality, personal data and access boundaries; it does not require unrestricted publication.

The future institutional web may need to function as an Evidence Environment in which identity persists, provenance remains traceable, versions remain distinguishable, relationships remain reconstructable, evidence classes remain separate and institutional meaning survives retrieval. The next challenge may not be producing more content. It may be ensuring that evidence carries the conditions required to interpret it correctly. Maturity should not be measured by page or API count, but by whether a machine can distinguish authority from commentary, final from draft and current from historical. A low-regret action is to conduct a machine-retrieval red team on one important institutional document, tracing search results, API output and AI summary back to determine whether identity, status, version and sources remain reconstructable. Future monitoring should separate final text, technical guidance, adoption scope, operating controls, supervision and observable outcomes. A low-regret step is to select one high-risk claim for an end-to-end reconstruction test and record missing identity, source, method, accountability and version. That is governance preparation, not a compliance guarantee or forecast of results. Monitoring should be event-triggered as well as calendar-based. A final rule, amended technical guidance, expanded scope, supervisory action, adoption data or observed outcome creates a new version and a reassessment of the earlier judgement. The prior conclusion is not erased. It retains its original basis, identifies the new evidence that changed it and states which decisions or downstream uses now require review.