Skip to content

Target-Site Sampling or Proxy Validation

Diagnostic validation — instantiates Effective-Input Delivery Assurance

Measures what is actually present at the point of action — by sampling the target directly, or by validating an accessible proxy that provably tracks it.

A diagnostic that establishes the truth at the point of action itself — either by sampling the exact target site, or, when the target is inaccessible, by validating that an easier-to-measure proxy reliably tracks the real target value. Its defining move is refusing to accept an upstream or convenient measurement as a stand-in for the point of action unless the substitution has been proven: its deliverable is a trustworthy point-of-action reading and, where a proxy is used, the validation that earns the right to use it. It fixes exactly where "the target" is and what "usable form" means there. It does not map the path or measure every stage — it nails the terminal ground truth.

Example

A bridge deck is being poured, and the crew must know when the in-place concrete has reached the strength to strip formwork and post-tension — too early risks collapse, too late wastes schedule. The true target is the strength of the concrete inside the deck, which cannot be tested directly without destroying it. Target-Site Sampling or Proxy Validation solves this by validating a proxy: the maturity method (ASTM C1074) establishes, for this specific mix, a calibrated relationship between a temperature-time index (cheap to log with embedded sensors) and measured strength (from lab cylinder breaks).[^maturity] Once that proxy is validated for the mix, embedded sensors give a live, in-place strength estimate at the true point of action — the deck itself — rather than from a cylinder cured in a different environment.

The mechanism's work is precisely this: defining the point of action (in-place deck concrete, not a lab cylinder), stating the usable-form criterion (structural strength, not mere set), and proving the maturity proxy tracks it before anyone trusts a single reading.

How it works

  • Define the point of action precisely — the exact site and the usable-form criterion that matters there (in-place strength, free/active concentration, root-zone moisture), not a convenient surrogate site.
  • If the target is directly sampleable, sample it and measure against that criterion.
  • If not, pick a measurable proxy and validate it — establish, and periodically re-check, that the proxy tracks the true target value across the relevant range — then read the proxy in place of the target.
  • Bound the proxy's validity — the conditions under which the relationship holds — so it is never trusted outside them.

Tuning parameters

  • Directness — sample the true target (definitive, often destructive and costly) versus a validated proxy (cheap and live, but only as good as its validation).
  • Validation strength — how many paired target-versus-proxy points, and how wide a range the proxy is proven over; thin validation invites out-of-range failure.
  • Re-validation cadence — a one-time calibration versus periodic re-checks as conditions (mix, batch, environment) drift.
  • Point-of-action strictness — how literally "the target" is defined; a slightly-off site is an unvalidated proxy in disguise.
  • Usable-form criterion — total content versus the active/usable form measured at the site.

When it helps, and when it misleads

Its strength is being the ground-truth anchor for the whole archetype — the one reading taken where it actually matters — and a validated proxy makes that truth cheap and continuous instead of destructive and rare.

Its failure mode is a proxy validated under one condition and applied outside its validated range, which silently lies — a maturity curve calibrated on one mix used for another, or a blood-level proxy for a tissue that behaves differently. Its classic misuse is adopting a convenient proxy because it correlated once and never re-validating, or quietly redefining "the target" to whatever site is reachable. The discipline that keeps it honest is to state the proxy's validated range explicitly, re-validate as conditions change, and treat any measurement not taken at the defined point of action as a proxy that must earn its trust.

How it implements the components

Target-Site Sampling or Proxy Validation fills the point-of-action-truth side of the archetype — the components that define and pin down the target:

  • point_of_action_definition — it fixes exactly where the target is and what counts as reaching it; the reference the whole path is measured toward.
  • usable_form_criterion — it specifies the usable/active form that must be present at the target (structural strength, free concentration), not mere presence.

It does not map the delivery path or trace the journey (that is Tagged Input Tracing), measure the amount at every intermediate stage (Stagewise Availability Assay), or confirm the uptake event itself (Uptake Confirmation); this mechanism validates the ground truth at the point of action, it does not follow or tally the path.

Notes

The point-of-action definition and usable-form criterion this mechanism sets are consumed by others — the Stagewise Availability Assay measures against them, and the Availability Funnel Dashboard draws its bottom band from them — so it is definitional infrastructure as much as a measurement. It sits close to Uptake Confirmation but is distinct: Uptake Confirmation asks did the input cross into the target, while this mechanism validates how we can trust the measurement of what is there.