Public evidence summary
Historical hosted attach-and-fork test
- Record date
- 3 September 2026
- Scope
- Historical record; any production observation is limited to the dated test described below.
- Current deployment
- Not independently verified by this historical evidence. Current availability
Recorded result
On 3 September 2026, laboratory checks created owned fork branches, exercised terminal attachment and refused another account’s access. File-divergence checking was skipped because most branch networks were unreachable, and attachment used the stable parent. A separate production narrative reports successful owned forks and keyboard interaction through the hosted client after deployment. Final robustness changes could not be rerun on the damaged laboratory environment. The laboratory assertions and production narrative cover different scopes; neither resolves the recorded branch-network limitation.
The public summary as JSON. These are the same reviewed fields shown in Read.
{
"schemaVersion": 1,
"publicSummaryVersion": "2026-09-30",
"classification": "PUBLIC",
"title": "Historical hosted attach-and-fork test",
"summary": "On 3 September 2026, laboratory checks created owned fork branches, exercised terminal attachment and refused another account’s access. File-divergence checking was skipped because most branch networks were unreachable, and attachment used the stable parent. A separate production narrative reports successful owned forks and keyboard interaction through the hosted client after deployment. Final robustness changes could not be rerun on the damaged laboratory environment. The laboratory assertions and production narrative cover different scopes; neither resolves the recorded branch-network limitation.",
"date": "3 September 2026",
"scope": "Historical record; any production observation is limited to the dated test described below.",
"result": "On 3 September 2026, laboratory checks created owned fork branches, exercised terminal attachment and refused another account’s access. File-divergence checking was skipped because most branch networks were unreachable, and attachment used the stable parent. A separate production narrative reports successful owned forks and keyboard interaction through the hosted client after deployment. Final robustness changes could not be rerun on the damaged laboratory environment. The laboratory assertions and production narrative cover different scopes; neither resolves the recorded branch-network limitation.",
"sections": [],
"currentDeployment": "Not independently verified by this historical evidence.",
"canonical": "/evidence/phase-af-1"
}
Download this public summary
This derivative has its own digest. It is not the original transcript or a new test. Historical original records are preserved privately.
Download public JSON →SHA-256 58f778bbb7b374c2d95744cb02da09754eea0b8bf1c7c6cf668d1e7202f0abb7