cientista

Cross-reference ingested documents by comparing them against Vault manifests and factory context to surface obsolescence, gaps, and opportunities. Apply the analysis across repository state, indices, and the skill catalog to generate an evolution delta and a mandatory checkpoint.

An evolution delta is an artifact detailing surgical improvements, required checkpoints, and new or updated skills. You need it when translating indexed and ingested knowledge into concrete architectural and product evolution artifacts to map each delta to the affected module.

Ingest a Vault document and trigger the cross-reference analysis to produce aurora_evolution_delta.md and evolution_checkpoint.json. The analysis applies across repository state, indices, and the skill catalog, citing the source material for every enhancement.

Yes, cross-referencing new knowledge requires existing factory context and Vault manifests to surface obsolescence and opportunities. The Skill translates indexed knowledge into evolution delta artifacts by cross-referencing across vaults, the Ozzmosis index, and the factory state.

The best way to map knowledge ingestion deltas is to cross-reference ingested documents with Vault manifests to generate an aurora_evolution_delta.md. This artifact cites the source material for every enhancement and clearly maps each delta to the affected module, skill, or area.

Cross-referencing vaults produces a mandatory evolution_checkpoint.json to serve as a structural checkpoint alongside the aurora_evolution_delta.md. This ensures that every surfaced obsolescence, gap, and opportunity for evolution is formally recorded before architectural changes are applied.