Import source identity and versions
An import preserves a source fact and the relationships that make it meaningful. Toolora assigns native identifiers while retaining source-system/external identities and version provenance. A matching customer name, invoice total or number of rows cannot replace that identity.
The Bygglet runbook owns operational fetch/import procedures. Its private preserved corpus and expiring source session are not handbook inputs. This reference describes source mapping from the reviewed code; it neither reads private exports nor authorizes a replacement import.
Identity reference
Section titled “Identity reference”| Source object | Identity that must survive | Common incorrect substitution |
|---|---|---|
| Tender / offer thread | Base tender external ID and native thread ID | Treat every version as a separate commercial offer |
| Working copy and locked sent version | Each version’s external ID and its own lines/details | Copy current working text/rows into a previously sent version |
| Project | Source project ID plus native project and explicit quote relationships | Infer accepted billing authority from a source-only offer link |
| Invoice and rows | Exact external document identity and original row amount semantics | Recompute a fixed-price row solely from quantity × unit price |
| Customer/person | Source identity plus company-local relationship/profile | Merge by display label or promote a contact into a customer |
| Imported event | Domain identity, event facts and stable normalized replay key | Use arrival time as the event’s business identity |
| Original attachment | Original/version identity and bytes/hash where provided | Treat extracted text or a model suggestion as the original |
Versions and evidence fields
Section titled “Versions and evidence fields”A Bygglet tender is its working copy; locked versions have their own IDs. A subresource sweep over only base tender records can therefore miss sent-version rows. The registered tender-row fetch expands version IDs. Descriptions and row values must come from the corresponding version record; missing historical detail remains missing rather than borrowing the working copy.
The numeric answer field describes the source response: 1 accepted, 2 declined, 4 no answer and 100 draft. A send-state label is not the customer answer. Even a valid numeric accepted value does not alone authorize creation of immutable Toolora acceptance evidence. The legacy acceptance-shaped path is refused before writes; supported reconstruction needs its own version/project/source checks and controlled RPC.
Likewise, a populated name is not necessarily a signature. Event-like target fields need consistent timestamps and surrounding evidence. Commercial authority and historical replay retain that distinction.
Amounts and replay keys
Section titled “Amounts and replay keys”Source price can carry a fixed-price row’s amount even when quantity and unit price are zero. The shared line-amount mapper preserves that fact and applicable discount semantics. Reconciliation compares what the mapper would write with the source, not merely the resulting table cardinality.
Imported approved time also retains its external origin; it cannot become a fresh payroll handoff merely by copying an approved status.
Imported event keys normalize equivalent timestamps and amount representations while retaining distinguishing business fields. A changed event body or source fact must not be collapsed merely because two events arrived in the same fetch. The exact key contract remains event-specific.
An import-job ID, external source ID, native primary key, content hash and checkpoint each answer different questions. The dispatcher tracks execution progress; it does not make every source fact interchangeable or certify complete reconstruction.
Synthetic source example
Section titled “Synthetic source example”A synthetic tender T has working copy T and sent versions V1 and V2. Staff later edit T. Importing V1 must preserve V1’s own text, rows and source ID. Missing V1 rows are a review gap; copying T’s current rows would create the right row count with the wrong historical offer.
A project referencing T as its source can be linked for provenance without asserting it accepted V2. An imported fixed-price invoice row with zero quantity and a source price of 2,000 retains that source amount rather than becoming zero.
Evidence limits
Section titled “Evidence limits”Synthetic key and acceptance-boundary tests specify replay normalization and refusal without writes. Corpus reconciliation needs its authorized private source/target pair and before/after evidence. The source review does not certify current import completeness, repaired historical exceptions or an operational cutover. Original preservation owns the separate archive contract.