trails-derive-from-source

To prevent shadow data when introducing projections or metadata maps, identify the natural owner module and verify it exports typed data before aligning downstream consumers with that canonical source.

A canonical source is the authoritative owner export that provides typed data for framework facts, ensuring downstream surfaces avoid duplication and indirection caused by relying on non-authoritative local projections.

Align downstream consumers by invoking a derive-from-source workflow with your change proposal, confirming a single authoritative owner export exists and is discoverable before creating local lists or projections.

You should escalate to the owner package during framework fact derivation when ownership of a fact is unclear or missing, ensuring the rightful owner module exports typed data before you proceed.

Yes, deriving framework facts from a canonical source applies to changes that introduce Warden rules across core packages, requiring owner module exports to be discoverable and preferring narrow owner exports.

Local projections create shadow data in core packages because they rely on non-authoritative sources, causing duplication and confusion instead of aligning downstream consumers with a single canonical owner export.