How this is made
Colophon
This portfolio is edited from a growing body of project evidence. Its purpose is to make each public claim as clear, useful, and accountable as the evidence allows.
One object, one path
Follow one photograph
- 01Select
This East River portrait opens the portfolio because it introduces Jamie and locates him in the city where much of the work took shape.
- 02Observe
The frame shows Jamie beneath the Manhattan Bridge. The archive record supplies the date, photographer, and recorded permission for this portfolio use.
- 03Write
The caption makes a precise public claim: where the photograph was made, when, who made it, and where the record is held.
- 04Revise
Jamie publishes only after the caption, credit, privacy, and use are resolved. Otherwise the image stays private; if the record changes, Jamie revises or removes it.
A living publication
The Knowledge Wiki Graph connects each public claim to evidence. Jamie decides what appears here and revises it when the record changes.[1][2]
Made and maintained by Jamie Burkart. Last revised 22 August 2026. Jamie checks suggested corrections against the record and notes accepted changes here. See the knowledge method in practice, or suggest a correction.
Editorial responsibility
Tools and modeled reviewers may suggest changes, but they do not supply consent, rights, approval, endorsement, or publication authority. Jamie decides what appears here.
Sources and notes
These notes preserve what each source supports and where its limits remain. See something that needs correction? Contact Jamie.
View 2 source notes
The RFC documents the three graph responsibilities and projection boundary; its exploring status is part of the evidence.
Boundary: This source does not establish a completed migration, a finished product, client adoption, permission to access or publish protected material.
The RFC documents federation, local repository authority, transport boundaries, and human release control; its proposed status is part of the evidence.
Boundary: This source does not establish a universal repository topology, automatic publication authority, a completed production deployment, client adoption.