Ingest a File
File ingestion should preserve exact content evidence and the authority/provenance facts around the artifact. Filesystem possession is not ownership.
Before ingest
- Identify the acting Entity and authorization scope.
- Identify the source/origin Entity.
- Identify the controller and, if explicit, rights holder.
- Record a provenance reference meaningful outside the local path.
- Confirm the file's licence/handling rules permit the intended processing.
BTDU path
The BTDU runtime computes the content SHA-256, ingests an evidence object, creates an exact-byte compound and records a governed object linked to source, controller, optional rights holder and provenance.
For repository files, prefer repository ingestion so the commit/tree and aggregate manifest are preserved. For standalone files, use the applicable ingestion surface from the reference SDK/runtime and keep the resulting object/evidence identifiers.
After ingest
Record the source hash, resulting object reference, evidence object ID, resulting state/atomic root where applicable, rejected/error status and timestamp. Reconstruct and hash a deterministic sample when qualifying exact reconstruction.
Do not
- Infer ownership from the account performing the upload.
- Overwrite historical provenance when a file changes.
- Claim economic rights merely because the file is inside BTDU.
- Delete source licence evidence needed to justify the ingest.