Import, history and data quality
Imports reconstruct source records and relationships from preserved history. They retain external identifiers and provenance so later reconciliation can compare identity, relationships and values. Source offers remain distinct from accepted agreements. Import operations use their owning runbook and do not authorize a new operational transition.
Preserved sources and identifiers
Section titled “Preserved sources and identifiers”Bygglet imports use preserved source material and exact external identifiers. A source project, offer working copy and sent offer version can have different identities. Import previews keep these relationships visible for review. Document originals and imported source records have distinct preservation contracts; neither should be replaced by an unexplained derived value.
Import source identity and versions explains the detailed rules, examples and evidence limits.
Historical replay and side effects
Section titled “Historical replay and side effects”The import contract treats a replay as a fact that already happened. Transaction-local import mode permits specific historical writes and suppresses defined forward-looking effects. It is not a general bypass for every immutable record. Notification intent must not be created merely because an old acceptance is reconstructed.
Historical replay and forward effects explains the detailed rules, examples and evidence limits.
Identity, relation and value checks
Section titled “Identity, relation and value checks”Import reconciliation compares source identity, relationships and values. Matching record counts alone cannot prove that an offer is linked to the correct project or that invoice amounts retain their meaning. Financial authority requires its own agreement evidence. Historical exceptions remain explicit rather than being silently promoted to native operational facts.
Import reconciliation rules explains the detailed rules, examples and evidence limits.
Operational transition
Section titled “Operational transition”Operational cutover is the point after which new operational records and changes are made in Toolora. The replaced system may remain a historical reference. Data cleanup, replacement imports and retained configuration require their own agreed transition scope. Release and acceptance status must distinguish technical delivery from operational approval.
Operational transition and source ownership explains the detailed rules, examples and evidence limits.