Specification

Unified Fractalish Weighting Kernel

UFWK keeps significance typed instead of collapsing it into one score. Evidence remains immutable; interpretation remains revisable.

Status: SPECIFICATION. The public page describes the weight schema, uncertainty envelope, and governance role. It does not claim a fully qualified runtime.

Why words and embeddings are insufficient

A sentence or vector can preserve content while losing why an event mattered, under which target it mattered, what remained unresolved, and which future actions should still be impermissible.

  • the same wording can carry different authority and consequence
  • summary memory can flatten contradiction lineage
  • similarity alone does not preserve rights, caution, or residue
A structured WeightReceipt with eight weight families, uncertainty envelope, source evidence, and governance gates.
The task projection may be derived from the field; it is not the field.

Eight weight families

S / C

Structural and contextual weight. What is organized, and why it matters here.

A / P

Affective-significance and prospective weight. What mobilizes attention, and what may matter next.

Q / M

Consequential and mnemonic weight. What changed, and how future accessibility should change.

R / K

Residual and counterfactual weight. What stayed outside the fit, and what likely differed.

Immutable evidence, revisable interpretation

Receipts preserve source evidence, digests, versions, and provenance. Weight assignments and uncertainty can later change without rewriting the evidence that originally triggered them.

That separation is why a correction can supersede a prior interpretation instead of pretending the earlier state never existed.

HOLD and interaction gates

High novelty, urgency, rhetorical force, or projected usefulness does not silently bypass missing evidence, unresolved residue, countervailing rights, or target-contract failure.

HOLD is not another name for SENSE. It is a governed unresolved posture.

Entroresilience direction and inflation controls

Consequence accounting

Consequence must remain distinct from novelty, salience, or authority. A striking event is not automatically a justified action.

Weight inflation controls

Public runtime claims stay blocked until calibration, disagreement behavior, invalidation conditions, and replay identity are bound to evidence.

No universal score

Tasks may derive routing projections from the field, but the public architecture does not present a universal truth or value scalar.

Verification plan

  1. Bind source evidence.

    Every public numerical or status claim needs a public evidence ID, source, scope limit, and replayable artifact.

  2. Calibrate across evaluators.

    Test whether the same encounter receives stable typed weighting under declared targets, not just stable wording.

  3. Stress novelty conflicts.

    Check that learnable novelty can contribute without becoming execution authority.

  4. Replay reinterpretation.

    Corrections must update future accessibility while preserving the original evidence and earlier acceptance path.