# Arrival perceptibility
#
# Cache — arrival is scheduled but not composed. 58 modules land on home in
# 17.3s and none of them announce themselves. Names the measured baseline and
# the axis that is still missing, so the next pass does not re-derive it.

#>arrival_perceptibility_2026_08
#:cache #!attention #!load #!progressive-enhancement
#:operation #!cache
#:fixity #!tending
#:layer #!pragmatics

@implicit_arcs: ~"./implicit-attention-arcs.spw"
@feature_wiring: ~"./feature-wiring-timing-2026-07.spw"
@interaction_microstates: ~"../conventions/interaction-microstates.spw"
@region_ecology: ~"../conventions/region-component-ecology.spw"
@folding_organelle: ~"../conventions/folding-chrome-organelle.spw"
@load_trace: ~"../../public/js/runtime/load-trace.js"
@familiarity_gate: ~"../../public/js/runtime/familiarity-gate.js"
@module_loader: ~"../../public/js/runtime/orchestration/loader.js"
@arrival_electrostatics: ~"../conventions/arrival-electrostatics.spw"
@wonder_doctrine: ~"../philosophy/wonder-doctrine.spw"
@page_reasons: ~"../../scripts/page-reasons.mjs"
@wonder_script: ~"../../scripts/wonder.mjs"
@arrival_shells: ~"../../public/js/runtime/arrival-shells.js"

operation = "cache"
fixity = "tending"

^"measured_baseline"{
  note: "Home page, local build, 2026-08-12, via __SPW_SITE__.loadTrace. Numbers are the point; re-measure rather than trust these after scheduling changes."
  modules_mounted = 58
  arrival_span_ms = 17287
  immediate_tier_span_ms = 4496
  immediate_count = 20
  region_enhancers = "12, in a 271ms burst at ~8.4s"
  catalog_total = 96
  gates_in_use = #[`IMMEDIATE`, `VISIBLE`, `IDLE`, `SETTLED`, `REGION`][reg=set]
  gates_on_familiarity_before_this_pass = 0
}

^"claim"{
  text: "Arrival is scheduled but not composed. `when=` decides ordering; nothing decides whether a landing is perceptible. 58 silent mounts over 17s is an undifferentiated wash — no feature gets a moment, so the reader cannot appreciate a feature's presence or learn that it exists."
  restated: "This is @interaction_microstates#reward_contract applied to arrival rather than to interaction: never silent absorption."
  bar: "As subtle as necessary to be tasteful, as noticeable as necessary to be seen. Both sides fail commonly — skeletons and spinners are noticeable but not tasteful; ordinary progressive enhancement is tasteful but imperceptible. The site currently sits hard on the second failure."
}

^"landed_this_pass"{
  familiarity_axis = "runtime/familiarity-gate.js. The ladder (fresh|familiar|practiced|fluent|habitual) already existed in cognitive-state.js and visited surfaces were already persisted; neither was ever spent on scheduling. Now consulted inside getEffectiveMountWhen."
  familiarity_rule = "Defer-only. May push an expert surface off a newcomer's first paint; may never pull work forward into it. IDLE is the floor, so nothing is withheld and no content sits behind a loyalty wall."
  load_trace = "runtime/load-trace.js. Joins spw:module-mounted with layout-shift attribution; stepTo() winds back via the loader's existing mountModule/unmountModule. Recording is ambient and trivial; highlight/step are opt-in."
  shell_chrome_fix = "REGION_ENHANCER_SELECTOR excludes shell chrome. region-enhancer::shell-0 was restyling the site header at ~8.4s — the measured cause of 'the navigation changes as the page loads'. @region_ecology already forbade it (chrome_field is not pack-local)."
}

^"still_missing"{
  axis: "Perceptibility. Distinct from scheduling (when) and from eligibility (familiarity, features, selector)."
  questions: #[
    `Does a landing get a moment, or does it only get a slot?`,
    `Which arrivals deserve to be noticed at all — most should stay silent, or the wash just becomes a louder wash`,
    `Is perceptibility a property of the module, the region it lands in, or the reader's familiarity with it?`,
    `First-encounter vs return: a feature probably announces once and then stops. That is the same shape as feature-discovery's encounter[novel|convergent|return], which describes encounters without being scheduled by them.`
  ][reg=set]
  refuse: "Do not give every module an entrance. Unconstrained announcement is the same failure as unconstrained rotation in @folding_organelle — the constraint is what teaches."
}

^"debut_placement"{
  claim: "A module's first encounter should happen where its anatomy justifies it, not on whichever page loads first. Home currently declares 12 feature tokens, the most of any route except /design/."
  probe: `compare data-spw-features per route against the anatomy each feature's modules actually select for`
  example: "media-publishing on home gates promo-wonder-cycle, whose element is genuinely present — but it also pulls a 10KB behavior bundle for one card, and that card (daily-keyed promo copy) is not page-aware. Verified: the feature claim is legitimate, the proportionality is not."
  caution: "First grep for this returned a false negative on the promo element. Check both the source route and dist/ before concluding a feature claim is phantom."
}

^"insight #ri-002"{
  status: "landed"
  supersedes: "still_missing.axis — perceptibility is now built, but not where this cache expected it"
  correction: "next_smallest said one feature arriving perceptibly, judged by eye. Measuring first said that was premature. `npm run reasons`: 153 routes, and 124 of them have one liminality band or none. An entrance on a page with no interior is a louder wash, which refuse already forbids. Potential has to exist before it can be spent, so the pass built the field rather than the flourish."
  finding: "No route on this site is the sole host of any anatomy. 31 feature tokens: 21 name no catalog module at all, and of the 10 that do, three (operators 145 routes, navigator 138, console 137) are declared nearly everywhere. Page differentiation is carried almost entirely by prose."
  model: "Arrival perceptibility as electrostatics — shells (liminality bands), walls (braces / region purposes), dielectric (image-bearing seats), potential across a wall, discharge grounded into encounter memory. Promoted to @arrival_electrostatics."
  landed: #[
    `scripts/page-reasons.mjs + npm run reasons — per-route charge, shells, walls, dielectric; splits phantom claims into unbacked vocabulary vs unhosted anatomy`,
    `public/js/runtime/arrival-shells.js — the perceptibility axis; refuses to discharge where no wall exists, so 124 flat routes stay silent by physics rather than by veto`,
    `public/css/systems/arrival-electrostatics.css — the discharge drawn on the wall, not the content; layout-inert, suppressed under reduced-motion and capture mode`,
    `.spw/conventions/arrival-electrostatics.spw — the model, reviewed against @wonder_doctrine's own five tests`
  ][reg=set]
  doctrine_result: "Passes structural, honest, inspectable and vocabulary. Fails earned — it spends on a stranger and grounds away from the regular, which is the inverse of what the doctrine wants. Left as a live disagreement in wonder_arrival_potential_5 rather than reconciled by fiat."
}

^"insight #ri-003"{
  status: "landed"
  claim: "The site had the doctrine for wondering and none of the apparatus. `npm run wonder` finds 34 questions across assets, graph and four philosophy surfaces; not one carried a `!probe{}`, a `#>` anchor, a hypothesis, or a measurement substrate. The workbench canon carries 176 that do. Questions lived here as prose and therefore could not be cited, run, or closed."
  landed: "scripts/wonder.mjs — harvests wonders, renders them as ornamented enclosures that preserve the form's contour in a second medium, and resolves each `$%[…]` substrate against the surfaces that actually produce it."
  substrate_as_contract: "A `$%[…]` list is a component spec: what a region must be able to show for its question to be answerable. 9 of 16 substrates resolve today; the 7 that do not are the inspection components the runtime cannot yet be asked about (seat.liminality, brace.handleCount, region.ornamentDensity, module.mountedAt, runtime.stage, surface.familiarity, route-side joins)."
  caution: "First resolver matched bare words and reported seat.liminality as satisfied because page-reasons says 'liminality' somewhere. A mention is not a producer — require a producing position or a backlog will report itself complete."
}

^"validation"{
  probe: `__SPW_SITE__.loadTrace.summary() on any route; byWhen, deferred, shifted, spanMs`
  probe_reasons: `npm run reasons — phantom claims, flat pages, exclusive holdings, feature spread`
  probe_field: `__SPW_SITE__.arrivalField.field() — why this page did or did not conduct`
  probe_wonder: `npm run wonder && npm run wonder:measures`
  probe_familiarity: `applyFamiliarityGate({familiarity:'practiced'}, MOUNT_WHEN, 'immediate', surface) returns 'idle' when fresh and null once earned`
  falsification: "A new feature ships with an entrance animation but no encounter memory, so it announces itself on every visit forever."
  next_smallest: "One feature arriving perceptibly, judged by eye in a browser. This is a taste call and does not want another abstraction in front of it."
}