Public Slice — 2026-07-25

This page presents a selected reading of public repository material visible by the end of 25 July 2026 in Taiwan time. The evidence boundary is 25 July 2026, 23:59:59, Asia/Taipei. The page was assembled after that boundary; a later retrieval time does not move it.

The sequence is bounded to the main branch of one public repository as it stood at that boundary. Other public branches existed. They fall outside this selection, and public branch state is not main-branch state.

The moments are ordered. The order does not explain them. Nothing below establishes that any one of these states caused another.

In two titles, a character stood where a dash belongs.

Two document titles in mwe-public-documents.json carry codepoints from the Unicode Private Use Area, a range with no assigned public meaning, in the position an en dash occupies.

Committed 2026-07-13T20:20:46+08:00
Commit 68304c3287fb1faefb4e57c5f462c91ab2f627a7

Files mwe-public-documents.json

The file contains the characters at this commit. It does not record their origin.

They also appeared in the file from which the view was drawn.

The same two codepoints appear in visualizations/public-surface-authority-map/data.json, the file the public interface renders.

Committed 2026-07-14T05:49:51+08:00
Commit cdbf3fefb85491ba2aa7aedde09e912598372483

Files visualizations/public-surface-authority-map/data.json

The characters are present in this file at this commit. The file does not establish that they were read, or that anything followed.

Eleven days later, the contents differed.

Both occurrences are replaced with en dashes. The same commit changes four lines across two files and nothing else.

Committed 2026-07-25T10:39:16+08:00
Commit 0479406cf2df032613fea9a2e7497065da72250d

Files mwe-public-documents.json visualizations/public-surface-authority-map/data.json

Eleven days is the interval between two commit timestamps. The interval is not a measure of attention, delay, or difficulty, and it does not describe the work that lies between them.

For a while the record of what the file was, and the file, disagreed.

At one commit the tracked file measures 92,903 bytes, while the constants recording its identity elsewhere in the same repository state 92,901, together with a different checksum.

Committed 2026-07-25T10:45:03+08:00
Commit 3219fa03149b4bf1a229f059b4912b632028422b

Files tests/test_public_surface_candidate_generator.py visualizations/public-surface-authority-map/data.json

Commit 8038fe1e2a525f377a3918cd7ba56feefda4ef29 sets the constants to the file's measured values later the same day. The file itself is unchanged. The commit above is one commit where the two can be compared.

Later commit 8038fe1e2a525f377a3918cd7ba56feefda4ef29 tests/test_public_surface_candidate_generator.py

Here, the view was fixed.

The generator's default and explicit historical modes read the tracked file, recompute its identity, compare it against a pinned specification, and write nothing. The public README states the same.

Committed 2026-07-25T21:38:59+08:00
Commit 886f671347e06954b15d658803093df4d9c48b09

Files visualizations/public-surface-authority-map/README.md scripts/build_public_surface_authority_map.py

The generator modes and the README state this at this commit. It is not a statement about policy, authority, or anything decided outside these files.

The view names its source. The source remains open-ended.

mwe-public-documents.json declares 59 records. The drawn file is unchanged from the commit above, and continues to declare 30 records and to name mwe-public-documents.json as its source.

Committed 2026-07-25T22:21:01+08:00
Commit 933274af9693d6d1d9fac36819aafdf56f9ab81d

Files mwe-public-documents.json visualizations/public-surface-authority-map/data.json

Both counts are fields the two files declare. No public file states that the two are required to agree.

Each reference is pinned to a fixed commit. The selection and sequence are specific to this reading, not to the repository.