# Crucible Mode (용광로모드) — Total-Immersion Absorption with an Unmeltable Core

> **Not a skill — a named absorption *stance*** that composes existing FH skills under one identity.
> Stands to absorption as `goal-quench` stands to `/goal`: it does not add a new capability, it names and
> chains capabilities FH already has, and supplies the identity principle that says *why* they chain.

## The distinction it names

FH's default absorption (sister-asset protocol, `frontier-digest`, selective import) is **cherry-pick**:
scan a source, keep the 1–2 worthy increments, reject the rest, done. Efficient, and correct for most
intake.

Crucible mode is the **opposite stance, used deliberately**: throw the *whole* corpus into the forge —
including the parts you would normally reject — melt it under adversarial heat, and let only what *bonds
to the identity core* survive into a re-forged asset. The output is not "a few imported items"; it is a
**re-tempered identity** plus, as a byproduct, a sharper boundary.

**Why total-immersion beats cherry-pick here — the rejections are load-bearing.** In cherry-pick, a
rejected item is waste. In the crucible, a rejected item is a *boundary-defining contrast*: melting the
whole 19736 corpus (Redis state-bus, tmux teams — plus cross-source over-claims like RTK 63.1% [347754])
did not just leave the decision-table behind — rejecting the Redis bus *re-confirmed and sharpened the
wording of* the boundary "FH is a quality harness, not an ops/speed runtime." Total-immersion mostly
re-states and sharpens a boundary that was implicit; occasionally it surfaces one that was not.
Cherry-pick rarely does either, because it never holds the rejected matter against the core long enough to
feel where the boundary is.

## The adamantium core (심지) — what the crucible cannot melt

Everything is meltable in the forge **except the identity invariants**. If these melted, the output would
no longer be FH — it would be a different tool wearing the name. They are the fixed point the melt is
defined *around*:

- Quality/governance over speed/ops ("a harness is a means, not an end").
- No judge-only path — a judged verdict is always paired with adversarial re-verification.
- Import-list-first + bidirectionality (no one-way export, no clone-and-own).
- HITL — AI proposes, the operator commits; no autonomous commit to shared repos.
- Verification before completion-claim (`harness_6axis_framework.md` Axis 5).

## The one sharpening (governor increment over the raw metaphor)

The metaphor says the core *"never melts."* Precisely: **unmeltable by absorption ≠ unchangeable by the
operator.** The two are different forces:

- **Crucible heat (absorption pressure)** — every external pattern, every frontier showcase, every sister
  asset. The core is *immune to this* **by construction**: the identity-bonding test that decides what
  survives is *defined by the core*, so absorption can never dissolve the thing doing the deciding. This
  is the virtue — the frontier cannot drift FH no matter how shiny (the anti-bubble / anti-FOMO guarantee,
  see `feedback_frontier_expectation_anchoring`).
- **The forge-master's deliberate hand (operator + maturity evolution)** — the core *can* be reforged, but
  only by a higher-authority, deliberate act (operator decision, `verify-bidirectional` baseline update,
  Phase II→III maturity, the v1-define / v2-complete / v3-expand arc). This is what keeps "never melts"
  from becoming dogma / stagnation (the farmer failure-mode): the core is unmeltable *by heat*, not frozen
  *forever*. **Anvil signal (concrete, so the escape hatch is not theoretical):** when the *same* rejected
  pattern recurs across **N≥3 distinct sister-corpus melts** and the operator concurs it is no longer drift
  but a genuine gap, that is the cue to reforge the core — route to `verify-bidirectional` (reusing the N=3
  recurrence-escalation threshold in `operations.md`). Absent that signal, repeated rejection is correct,
  not stubbornness — that distinction is what keeps the asymmetry falsifiable instead of self-sealing.

So: **adamantium against the crucible, reforgeable only at the operator's anvil.** That asymmetry is what
makes self-forging safe rather than self-destroying.

## The chain (composes existing skills — no reinvention)

| Stage | Existing FH asset(s) | Role in the metaphor |
|---|---|---|
| Total ingest | `frontier-digest`, sister-asset protocol, live-surface ingest | charge the whole corpus into the forge |
| Melt (heat) | `steel-quench` / `quench-challenger`, `phantom-quench` | adversarial heat — burn off the unsound |
| Identity-bonding test | governor source-close (`multi_model_sidecar_strategy.md` §Debate Circulation Loop), check-class taxonomy | does this bond to the adamantium core? |
| Reforge at tier | `sim-conductor`, `hub-persona-auditor`, target-tier blind sim | re-temper at the strength it must survive on |
| Rebirth (HITL) | `field-harvest` → FH-origin PR | identity-preserving + positively-expanded asset |
| Boundary record | `tracks/_audit/` cross-audit, documented rejections | rejections kept as boundary, never discarded |

## Self-forging (FH throws itself in — Mode D)

The crucible is recursive: FH subjects its *own* assets to the same forge it subjects external matter to.
A self-authored asset is not exempt — it goes in and only its sound core survives. (Worked instance, this
session, recorded in the `wikidocs-deep-sweep` audit + the lens-doc's own provenance block: the
`harness_design_decision_lens.md` draft was put through adversarial review; material the governor ruled
ALREADY-HAVE was demoted to honest restatement, an over-precise external stat was corrected to its
verified form, and only the orthogonal-bets framing survived as net-new. **This very doc was forged the
same way** — its S1–S3 defects, including a phantom "worked instance" claim, were caught by its own
quench pass before commit.) The unmeltable core is what makes this safe — self-forging tempers FH without
risking its identity.

## When to use crucible mode vs cherry-pick

- **Cherry-pick (default)** — routine intake, a source with one obvious increment, low identity stakes.
- **Crucible** — a *whole* corpus on a core FH axis; a frontier showcase that risks bubble/FOMO anchoring;
  any time the *boundary itself* is worth re-forging; FH self-development on identity-level assets.

## Check class & guards

- **Check class: judged**, paired with the melt itself (`steel-quench`/`quench-challenger`) + governor
  source-close — the stance has no judge-only path, consistent with the core it protects.
- **Guard — totality is not indiscriminate import.** Total-*immersion* (take everything into the melt) is
  not total-*absorption* (keep everything). The default-import remains zero; the forge decides.
- **Guard — the core list is operator-owned.** Adding/removing an adamantium invariant is a forge-master
  act (HITL), never an absorption byproduct.

## Provenance

Operator insight, 2026-06-14 (verbatim seed: *"포지하네스는 자기자신도 용광로에 빠뜨려서 단련해나갈 수
있다. 그러나 그 심지는 극도로 단련된 아다만티움과도 같아서 결코 녹지 않는다."*). Independently
operationalizes the same session's worked instances (wikidocs deep-sweep + the lens-doc self-forge). The
named stance + the unmeltable-by-absorption / reforgeable-by-operator distinction are the net-new
increment; the chained skills are all ALREADY-HAVE.

## Related
- `harness_6axis_framework.md` — Axis 5 (the heat) + Axis 6 (the rebirth); Core principle (the core)
- `harness_design_decision_lens.md` — harness-thickness bet (how thick the unmeltable core should be)
- `feedback_frontier_expectation_anchoring` (memory) — the anti-bubble anchoring the core enforces
- `knowledge/shared/rules/operational_adaptation.md` — reforge-by-operator channel (verify-bidirectional)