Reading Public Surfaces: Support, Limits, and Return
This page consolidates existing public reading boundaries and return routes. It does not create new authority, classification, relation status, or currentness claims.
It is not a Registry, complete authority map, canonical definition, or source of new classification decisions.
What this guide is for
Public pages here are entry points, not a complete system. A reader arriving at any single page may need to recover four things:
- which public surface is being read;
- what that surface supports;
- what it does not establish by itself;
- where to return for source, stated limits, or verification context.
This guide restates boundaries that the public pages already declare. Where a public page states its own limits, that page’s own statement remains the relevant public source for how its scope is represented here.
The public surface types
The Public Surface Map groups public pages into four types. This guide adds no further type.
Orientation surfaces
About the System, Entry Surfaces, Public Boundary, Public Site Notes, and Public Version Notes.
They support identity, scope, and inclusion questions: what this is, what the public website covers, what it does not cover. They do not establish corpus completeness, methodology, or internal structure.
Traversal surfaces
AI Reading Guide, AI-Readable Knowledge Architecture, Model Atlas, GitHub-Visible Model and Navigation Index, and Document Types.
They support navigation between public materials and machine-assisted reading. Navigation adjacency is a routing convenience; it is not a confirmed conceptual relation.
Record surfaces
Publications and DOI Records, Public Record Anchors, Citation Guide, and Platforms.
They support citation, record identification, and checking against the named public record. They do not establish validity or validate any other public surface.
Narrative surface
Fiction pages are readable as fiction. Their motifs may be adjacent to Meta-Writing Ecology, but they do not function as formal model evidence, corpus-completeness claims, or system validation.
What a public surface does not establish on its own
No single public page establishes:
- that the public materials are the complete archive or corpus;
- that a navigation link, adjacency edge, or shared page is a confirmed conceptual relation;
- that a mention, placement, navigation link, or adjacency edge establishes formal classification, authority status, or Registry state unless the cited public source explicitly declares it;
- that any other surface is correct, complete, current, or authorized.
Where a public source has not stated something, this guide records it only as not publicly confirmed. Public omission does not establish absence, falsity, or nonexistence elsewhere.
Currentness
This guide makes no currentness claim. Source status extends only as far as the cited public source or stated verification context.
Where a page or record states its own verification context, that statement — not this guide — is what carries the claim.
Return routes
From any public page:
- to the source or record it cites, follow that page’s own citation or record link;
- to what the public website includes and excludes, see Public Boundary;
- to how the public surfaces relate as entry points, see Public Surface Map;
- to how to read a given page type, see Document Types;
- to citation, record identification, and checking against named public records, see Citation Guide and Publications and DOI Records;
- to machine-assisted reading, see AI Reading Guide.
Boundary
This page describes existing public reading boundaries. It does not acquire interpretive position over the surfaces it describes, does not rank them, and authorizes nothing.
Models, records, and fiction return to their own stated source, function, and limits. Repository states return to the repository.