source-manifest-builder

Generating a deterministic asset manifest requires walking the repository to discover files, computing SHA256 hashes, and writing the curated assets block to a .skaile-source.yaml file for reproducible catalog ingestion.

An asset manifest is a reproducible inventory of repository files with publisher mapping and hashes. You need one when submitting assets to a catalog to enforce versioning, ensure file integrity, and guard against drift during review workflows.

Computing SHA256 hashes and filtering files for a YAML manifest involves applying file filtering rules to exclude unwanted entries, calculating cryptographic hashes for the remaining assets, and mapping them to the correct publisher before writing the block.

Yes, manifest generation integrates with review and publishing workflows to guard against drift. This ensures that the generated .skaile-source.yaml assets block remains reproducible and clean when publishing to a public catalog or private library.

Repository asset inventory drift occurs when manifests are not deterministic. Enforcing explicit file entries, versioning constraints, and author-curated publisher mapping during manifest generation prevents drift and ensures reproducible catalog ingestion.

Yes, explicit versioning is required when building a source manifest. The process enforces versioning and explicit file entries to ensure the resulting .skaile-source.yaml block remains deterministic and reproducible for catalog ingestion.