The word lineage describes different questions
Data-pipeline lineage traces how data moves through datasets, transformations and applications. Contract evidence lineage explains how agreements, amendments, effective dates and operating records support a governing position. Both concern traceability, but the relationships and questions are different.
When evaluating a platform, name the question before comparing the category. “Which transformation produced this field?” is not the same as “Which amended fee applies to this service for this period?” A useful implementation can connect these concerns without treating them as interchangeable.
Compare source, question and output
Data-pipeline lineage
Question
Where did this data come from and how was it transformed?
Source
Datasets, jobs, transformations and applications.
Output
An inspectable technical path through the data environment.
Contract evidence lineage
Question
Which records support the position that applies to this relationship and date?
Source
Agreements, orders, amendments, dates, scope and operating records.
Output
A source-backed governing position with changes and unresolved dependencies.
Trace the meaning of a change
Illustrative example: an amendment changes the price of one service from a specified date. A technical pipeline may show how the invoice table was loaded. The commercial review must also establish which service the amendment affects, when the price applies and which provisions remain unchanged.
Preserve the document family and the reasoning path. A reviewer should be able to move from the stated position to its supporting records, distinguish signature from effective dates and understand whether scope is limited to an entity, product or transaction.
Keep gaps and historical positions visible
A missing schedule or uncertain entity mapping should remain a visible dependency. Do not convert it into an apparently complete current answer. Assign responsibility for obtaining evidence and preserve the reason for subsequent corrections.
Historical review matters too. A team may need the position that applied when an invoice was issued, not only today’s summary. Keeping relationship and change history helps reviewers reconstruct that context and inspect the supporting sources.
Use the right foundation for the question
LineageAI is PostSig’s shared foundation for entity resolution, relationship modeling, effective dates, scope and source evidence. It should not be presented as a generic ETL or technical data-catalog replacement. Its relevance is the business meaning of connected records.
MCP provides approved access to that context for assistants, tools and customer-built workflows. It does not authorize autonomous actions. Evaluate the evidence path, permission boundary and unresolved-record handling against a real question before deciding how the context should support a workflow.