C.18:4.3 - Generation And Downstream-Use Record

When loop-engineering practice generates many candidates—for example, agent prompts, harness variants, workflow variants, or framework seeds—use C.18 to record generation, archive, front, descriptors, telemetry, retained exploration value, lineage, and the next applicable pattern. This does not say that the loop improved. Use E.23 only when one retained object version is changed and re-evaluated through repeated passes under a declared object-under-improvement evaluation; use G.9 for parity between variants and G.5 when a selected-set result must be declared.

When the missing work is to change usable material and examine the resulting variation, C.40 supplies that development and warranted continuation, with or without an already selected contribution. C.40.CD constructs problems and obtaining ways together through target application when those operations are needed. The record below describes generation; filling it does not perform these operations.

OpenEndedVariantGenerationRecord@Project:
  problemCardRef?:
  generationMethodOrFamilyRef:
  sourceRefs?:
  evaluatorOrComparatorRef?:
  emitterPolicyRef?:
  insertionPolicyRef?:
  dedupThreshold?:
  deduplicationBasisRef?:
  deduplicationUnit?:
  variantSetRef:
  descriptorMapRef:
  characteristicOrDescriptorSetRef:
  archiveOrFrontRef?:
  architectureCandidateRefs?:
  culturalVariantRefs?:
  telemetryRefs?:
  projectLocality?:
    generationWorkOccurrenceRef:
    compositeProjectWorkOccurrenceRef:
    governingRelationPatternRef:
    exactGenerationToProjectRelationRef:
  workPlanOrMeasurementRef?:
  refreshRef?:
  currentnessAsOf:
  currentStatus:
  stopOrRefreshReason:
  nextGoverningRelation:

Across the archive, front, and generation records, currentnessAsOf names the replay date or window together with the relevant pinned editions; currentStatus states whether the recorded archive/front/generation relation is active, held, closed, or stale for its declared use; and stopOrRefreshReason names the condition that ended it or the exact trigger that would reopen its currentness. These fields record the boundary but do not perform refresh. When source, descriptor, comparator, policy, evidence, or edition currentness becomes the live question, nextGoverningRelation points to G.11 and refreshRef? may cite the separately governed refresh record.

Here @Project is a compatibility and retrieval cue, not a project kind or relation assertion. Fill projectLocality? only after both Work occurrences have been admitted independently and the cited relation actually obtains under its direct governor. generationWorkOccurrenceRef names the exact dated generation U.Work; compositeProjectWorkOccurrenceRef names the selected composite project U.Work; and exactGenerationToProjectRelationRef cites, rather than creates, the exact work-part, containing-work, decision-use, source-use, or other governed relation. Use work parthood only when the complete A.15.1 basis holds. Otherwise omit projectLocality?: the @Project suffix remains retrieval-only and establishes no project Work, parthood, authority, context, or viewpoint.

For example, a completed harness-generation run may state:

projectLocality:
  generationWorkOccurrenceRef: HarnessVariantGenerationRun-2026-07-31 : U.Work
  compositeProjectWorkOccurrenceRef: AgentHarnessProjectWork-2026 : U.Work
  governingRelationPatternRef: A.15.1
  exactGenerationToProjectRelationRef: OperationalPartOf_work(HarnessVariantGenerationRun-2026-07-31, AgentHarnessProjectWork-2026)

Every optional field whose name ends in Ref? points to a separately identified object, claim, policy profile, or measurement basis. dedupThreshold? is not a reference: it carries one declared scalar threshold value. deduplicationUnit? carries its unit literal. Fill emitterPolicyRef? and insertionPolicyRef? only when the cited C.19 profile or insertion policy applies to the current pool treatment. When a threshold is inherited, the cited profile supplies dedupThreshold, deduplicationBasisRef, and deduplicationUnit; when it is not inherited, carry the scalar in dedupThreshold? and its basis and unit in deduplicationBasisRef? and deduplicationUnit?. These references and scalars do not give C.19 a generation operation or change the archive and front relations stated through C.18. In particular, problemCardRef? may cite a C.22.2 problem-side episteme but creates neither an actual Problem nor a ProblematicForRelation under C.22.PFR. Naming a generated variant, archive entry, front membership, telemetry value, or retained-exploration claim alone establishes neither an improvement-result nor a work-result identity and creates no relation from generation Work to a result. nextGoverningRelation is a locator for the next applicable pattern; it does not itself make a choice, declare a selected-set result, authorize work, perform refresh, or make any relation obtain.

Use this record when generation is current. For architecture moves involving candidates named in architectureCandidateRefs, use C.30, C.30.ASV, or C.30.AD as applicable. Use C.36 for cultural-evolution cases involving variants named in culturalVariantRefs. Local choice uses C.11; work planning and performed work use the A.15 family; effect measurement uses its direct measurement and evaluation patterns; refresh uses G.11. P2W carry-through uses E.18.1 when an accepted problem-side distinction must be preserved into the next relation.