Skip to content
Astera Technology

Regenerate a rendition whose source master differs from its declared revision

Verify recorded derivation rather than trusting a refreshed filename.

Read expected source master

Synthetic placement requires rendition from master M2. File R34 is labelled “M2-square” but build record says derived from M1; R35 is labelled “M2-wide” and derived from M2. Local acceptance requires actual source M2. There is no authorised equivalence between masters and no image is generated here.

Rendition derivation worksheet
RenditionDeclared/derived sourceAction
R34 squareM2/M1Regenerate from M2
R35 wideM2/M2Keep source evidence
Download editable CSV ↓

Compare derivation evidence

  1. Match placement requirement to M2
  2. Read build source for each rendition
  3. Reject R34 relabelling
  4. Request M2 regeneration and new evidence

If derivation evidence is absent, source lineage remains unknown even with an M2 filename.

How many renditions require regeneration?

Show the worked answer

One, R34. R35 already has the supplied M2 derivation evidence.

Request actual regeneration

Filled campaign-operation checks
CaseDecision or resultReason
Rename R34 onlyRejectBuild source stays M1
New R34 built from M2Candidate eligibleActual source matches
Download editable CSV ↓

Keep old rendition and new derivation identities distinct. Compare the regenerated content with the placement brief before closing.

Related resources