Home / The model / The universes / The source bytes

U0: The source bytes

Owner nobody: the bytes are what they are. Centre of gravity the hash. Smallest node a byte range in a file that was fetched on a date. Level down. Status partial.

Every promoted file carries its source, its retrieval time and its content hash, and the build refuses to run if the bytes disagree with their manifest. Per file today; per node is the change.

Node types

A node type is a required pattern of paths, not a label. The ones marked yes are walked on every build and the count is what matched; the rest are the vocabulary this universe needs and does not have.

TypeFormulaExists todayNote
SourceFilea node with a -fetched_from-> [URL] and a -hashes_to-> [Digest]not yet
ByteRangea node -inside-> a [SourceFile] with a stated offset and lengthnot yet

Verbs

Each is a verb with a distinct inverse, a stated domain and range, and the sentence it reads as. The ones marked live are in the edge vocabulary today; the rest are proposed here, or declared by the universe's owner elsewhere, and say so.

EdgeReads asInverseReads asDomainRangeFromStatus
fetched_fromthis file was fetched from this address on this dateservesthis address served this fileSourceFileURLproposed hereproposed
hashes_tothis file hashes to this digestdigest_ofthis digest is the digest of this fileSourceFileDigestproposed hereproposed
hashed_fromthis node was read from these bytesgroundsthese bytes ground this nodeNodeByteRangeproposed here; the AIUC-1 vault calls its version anchorsproposed

What the map adds here

Today the provenance block sits on every data file and says the same thing for every row in it. The Regulation Graph ends every chain in a hash of the retrieved bytes, per node. The per row version is what riskmandate.ai asked for in its Lab 03, request three, and it belongs here: a row's evidence is a node in U3 that is hashed_from a byte range in U0.

All thirteen · U1: The grammar · This universe as JSON · The brief