C.18:4 - Solution

Keep records for archive, front, telemetry, generation, and downstream relations separate.

C.18:4.1 - Archive Record

ExplorationArchiveRecord@Context:
  archiveRef:
  variantSetRef:
  descriptorMapRef:
  characteristicSpaceRef:
  distanceDefinitionRef?:
  retentionPolicyRef:
  retainedExplorationValue:
  steppingStoneUse?:
  lineageOrEditionPins:
  telemetryRefs?:
  currentnessAsOf:
  currentStatus:
  stopOrRefreshReason:
  nextGoverningRelation:

Use this record when the current question is about archive use—for example, retained exploration value, coverage, novelty, diversity, stepping-stone value, future reachability, curriculum expansion, lineage, or archive policy. Do not use the archive record as a selected-set result declaration or work permission.

C.18:4.2 - Front Record

FrontRecord@Context:
  frontRef:
  candidateSetRef:
  comparatorOrDominanceSetRef:
  admissibilityRef:
  descriptorMapRef?:
  characteristicSpaceRef?:
  relationTokenSetRef:
  excludedTelemetryRefs?:
  selectedSetResultRef?:
  currentnessAsOf:
  currentStatus:
  stopOrRefreshReason:
  nextGoverningRelation:

Use this record when the current question is about front use—for example, non-domination, Pareto relation, Q-front membership, comparator currentness, admissibility, or partial-order preservation. The front may feed a later G.5 use, but it is not itself a declared selected-set result; declare that result from the front through G.5 under its own basis.

C.18:4.2a - Filled Archive And Front Micro-Records

ExplorationArchiveRecord@Context:
  archiveRef: dance-lab-variant-archive-2026
  variantSetRef: choreography variants generated during a festival lab
  descriptorMapRef: timing, body vocabulary, risk, teachability, audience recognizability
  characteristicSpaceRef: festival style-engineering characteristic space
  distanceDefinitionRef: difference in timing and body-vocabulary descriptors
  retentionPolicyRef: keep rare but teachable variants and variants that open later combination work
  retainedExplorationValue: stepping stones for teaching and later style intervention
  steppingStoneUse: candidate material for C.36 cultural-evolution case work
  lineageOrEditionPins: lab session, teacher edit, platform-publication edition
  telemetryRefs: replay counts, class adoption counts, jury notes
  currentnessAsOf: lab records and platform-publication edition reviewed through 2026-07-31
  currentStatus: active for retained exploration and teaching use
  stopOrRefreshReason: reopen through G.11 if the teaching-use judgement, retention policy, lineage, or platform edition changes
  nextGoverningRelation: C.36

For this example’s current question, the field names C.36 as the next applicable pattern. If one of the stated changes makes refresh current, G.11 becomes the next applicable pattern instead; it is not a second simultaneous locator.

FrontRecord@Context:
  frontRef: cooling-module-maintainability-energy-front
  candidateSetRef: retained cooling-module architecture candidates
  comparatorOrDominanceSetRef: energy-use and maintainability comparator
  admissibilityRef: safety and manufacturing constraints already admitted by project policy
  descriptorMapRef: thermal performance, service access, part count, manufacturing tolerance
  characteristicSpaceRef: product-family architecture characteristic space
  relationTokenSetRef: comparison relation-token set supporting non-dominated candidates under current comparator
  excludedTelemetryRefs: tests outside the current temperature envelope
  currentnessAsOf: comparator, safety constraints, and test evidence reviewed through 2026-07-31
  currentStatus: active non-dominated front for the declared comparator
  stopOrRefreshReason: reopen if eligibility, comparator, dominance grounds, or evidence edition changes
  nextGoverningRelation: C.30

For this example’s current question, the field names C.30 as the next applicable pattern. Omit selectedSetResultRef? until an exact G.5 result exists. If declaring a selector outcome later becomes current, start a separate G.5 use; if the front’s basis changes, start G.11 refresh. Neither possible continuation belongs in the current locator.

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.

C.18:4.3a - Distinguish exploration inside a space from change to the space

Apply this branch only when whether the effective possibility space changed can alter retention, comparison, generation, architecture, or the next decision. Start by declaring the current space through the candidate grammar or type boundary, generator and operators, available building blocks, evaluator or comparator, retention or reproduction rule, goals or actions, and environment that matter for this case. The declaration may be ordinary domain content or a cited description; it does not create a universal PossibilitySpace kind.

Then state the smallest supported mode:

The first result is one ordinary C.2.1 claim naming the earlier and candidate space declarations, exact changed component, mode wording, counterfactual or trajectory evidence, uncertainty, blocked stronger claim, and next governing relation. Use C.28 for a causal claim that the component change produced the new reachability. Use C.11.CRC when a finite space-changing intervention must be compared with the current configuration, and C.11 for the later choice.

Stop at ordinary same-space exploration when no action depends on the stronger mode. Reopen only when the candidate grammar, generator, operator set, evaluator, retention/reproduction rule, goals/actions, environment, evidence, or receiving decision changes.

Worked micro-case. A cooling-module search previously admits only fixed rectangular layouts assembled by the same connection operators and evaluated under the same thermal/maintainability comparator. A new layout far from the archive remains exploratory if those rules still admit it. For this comparison, take a validated curved-channel building block and its construction operator as supplied inputs. Adding them is expansive only when the earlier generator could not express the resulting layouts and the comparison still uses a compatible higher-order regime. If the operator itself is missing, C.39.RO and the applicable subject Methods must supply its construction before that addition can be claimed. Replacing candidate admission and retention with a context-adaptive rule that changes which successors count is transformational only when the earlier/candidate rule mapping and observed reachability support that stronger claim. A higher novelty score alone establishes none of these transitions.

C.18:4.4 - Front And Archive Are Different Returns

• Start from one declared candidate or eligibility set.
• Return the non-dominated front from the relation-token set under the declared comparator or dominance set.
• Return the exploration archive separately when retained exploration value, coverage, novelty, diversity, stepping-stone value, or future reachability is current.
• Keep tie-breakers and telemetry explicit so diversity, illumination, or popularity signals do not rewrite front semantics.
• Before promoting telemetry or a popularity-like signal into the comparator, dominance set, or selected-set criteria, check which intended archive/front uses or values become worse or more fragile when that signal improves. State the affected uses or values, or the checked loci when none worsened, and cite the policy or decision authority that admits the promotion and any trade-off. If this basis or authority is missing, keep the signal as telemetry or an explicitly bounded tie-breaker rather than silently promoting it.
• Use RetentionIntent=steppingStone when retention exists for frontier expansion or later curriculum value rather than current dominance.
• If one source line keeps both returns, say that the front answers current non-domination while the archive answers retained exploration value.

C.18:4.5 - Cultural And Architecture Variant Boundaries

For architecture-candidate generation, C.18 records generation, archive, front, descriptor, telemetry, and retained exploration value. C.30 governs the architecture claim: ArchitectureOf@Context, selected structure or structure kind, affected characteristic, and next architecture move.

For cultural variants, C.18 records the generated or retained variant set and its descriptors, lineage, telemetry, and archive or front relation. Use C.36 for a cultural-evolution case when collective-holon or discipline-facing Method, Work, system-role kind or assignment, canon, memory, recognition, selection, mediation, style, tradition, or intervention relations are current. Use F.17, F.18, and F.9 for durable term and bridge work for labels such as style, tradition, genre, scene, school, and technique.