Continuous context
Keep current sources distinct from the evidence used by earlier results.
Business meaning changes
Products appear, policies change, fields are added and accounts merge. A context engine must consider both new facts and changes in the model that explains them.
- Source changes
- Affected mappings
- Context updates
- Dependent relationships
- Ask / Run
Current update behavior
Upload a replacement file or reconnect a source. PatternLab saves a new snapshot, makes it current and executes every enabled Run in that Workspace. Paused Runs remain saved but do not execute.
External changes are not detected automatically. There is no polling, schema-drift detection, webhook ingestion or automatic remapping. Reconnecting is an explicit action.
Historical evidence
A prior result continues to point to the saved source version used for that execution. New questions use current snapshots. The connection timestamp records when PatternLab saved the source, not when the business event occurred.
Mapping is not copying
A mapping describes business meaning without changing the source system. Separately, this release stores uploaded files and readable snapshots so checks and evidence can use them. The architecture should not be read as a claim that source data is never copied.