Observation evidence boundary · Core20
Read-only provenance boundary for future real observation evidence. Nothing on this page feeds archive timestamps, published periods, or file values into Core20 authority.
WALLFLOWER PLACARD · WHAT DO I DO HERE?
There is nothing to operate here at present.
The observation archive landing area is currently empty, and no public archive inspector is connected to Core20.
When real observation evidence is added later, this page may expose provenance, fingerprints and bounded read-only inspection. INSPECT will mean LOOK, not IMPORT.
Nothing listed or inspected here automatically becomes clock authority. A source file crosses the observation boundary only after its physical columns are understood and a deterministic reduction is verified.
Nature first → source encoding second → verified reduction → native A8 representation → recovery last.
Separation rule
Archive inspection may contain conventional source timestamps, published periods and other source metadata. Those values remain source evidence and do not become defining Core20 timing authority merely because they are present in an archive.
A source file crosses the observation boundary only after its physical columns are understood and a deterministic reduction is verified. A three-column mutual-event light curve is not called an apparent x-position stream unless a documented physical reduction creates one.
Observation archive status
No observation files are currently loaded in the public archive landing area. This status is informational; the archive is not a Core20 control surface.
Future archive inspection contract
When real source evidence is present, a future read-only inspector may expose filename, source classification, file size, SHA-256 fingerprint and a bounded source sample.
Inspection does not grant authority. Listing, hashing or viewing a file does not make that file part of the Core20 timing chain.
Original evidence remains preserved. Any later reduction or adapter must be separately documented and verified.