ENTITY Documentation Portal
Developer manual · ENTITY v3.4.3 · governed ingestion

Continuous Ingestion API

Version boundary: current runtime = ENTITY v3.4.3; BTDU component = 3.4.2 unchanged. BTDU object/repository ingestion behavior inherited unchanged into v3.4.3 may retain component-level 3.4.2 identifiers without making the full runtime v3.4.2.

Ingestion brings an artifact into governed ENTITY state while preserving source, controller, rights-holder, evidence and provenance boundaries. BTDU repository/object ingestion does not convert topology, storage or custody into ownership or authority.

Required concepts

Before ingesting, establish the acting Entity, the authorization scope, the source Entity, the controller, any explicit rights holder, the provenance reference and the media type. Do not infer those fields merely from filesystem ownership or the machine performing the ingest.

BTDU object ingestion

BlackmoreTechnologyDataUniverse.ingest_bytes() verifies a mutation authorization receipt, computes content SHA-256, creates evidence, produces an exact-byte compound, creates a governed BTDU object and bonds it to source/controller/rights/evidence/provenance references. Boundary metadata explicitly states that topology does not create ownership or economic entitlement.

Repository ingestion

The current v3.4.3 checkout exposes the unchanged BTDU ingest-repo operator command. Repository manifests record repository path, Git commit/tree where available, tracked-file count, aggregate SHA-256 and resulting atomic root. For release or qualification ingestion, use a pinned commit/tag in the provenance reference rather than a moving branch name.

git checkout v3.4.3
python tools/entity_btdu_cli.py --entity-state STATE --btdu-state BTDU --adam-root ADAM --git-bin git ingest-repo PATH --provenance git://owner/repo@COMMIT

Idempotence and history

Content-addressed atoms/compounds should be reused where canonical identity is identical. A changed artifact is a new state/derivation, not permission to mutate the historical record into pretending the old bytes never existed.

Continuous workflows

For directories, repositories or long-running pipelines, record checkpoints, source hashes, rejected/failed records and resulting state/evidence roots. If a later ingestion changes authoritative material, create a new derivation/event and preserve earlier evidence.

Inherited qualification boundary

The v3.4.3 release explicitly carries forward the previously closed v3.4.2 real-world BTDU training qualification because v3.4.3 does not modify that qualified component/path. That is inherited unchanged-scope evidence, not a claim that the qualification was re-executed as a v3.4.3 test run.

Historical reproduction

If reproducing a sealed v3.4.2 BTDU campaign, use the v3.4.2 tag and its exact hashes/evidence. For current integration work, use the v3.4.3 release while preserving BTDU's component version as 3.4.2.