ASHLIGHT FOCUS v31.9F3H · Technical Topology

F3E adds a client-side repository preflight layer on top of the existing AIP/Focus acquisition engine. It does not create a second privileged execution engine.

Research preflight

Research intent
  → Repository Atlas selection
  → FIXTURE_SUITE | CUSTOM_QUERY | CUSTOM_SET
  → bounded candidate pool (20 / 50 / 100 / 200 per query)
  → RabbitRankV2 query-alignment features
  → dedupe
  → per-source promotion
  → QUERY FITNESS comparison
  → global promoted candidates
  → RabbitPreflightReceiptV1
  → operational source handoff / later Rabbit deep acquisition

Fitness boundary

QUERY FITNESS measures alignment and acquisition usefulness only. It is not a hidden credibility, trust, authority or truth score.

Workspace ownership

Default: no workspace mutation
Optional projection ON
  → metadata-only PROBE preview windows
  → ownerSource = PROBE_LAB
  → AUTO CLEAR PREVIOUS PROBE / CLEAR LAST PROBE
  → CLEAR_ALL sanitation removes Probe transient state

Execution authority

AIP V2 Agent, Director OS, MCP, one-shot capabilities, hard stop, Command Audit JSON and named mounts remain as in F3D. F3E introduces no new privileged server verb; Probe V2 is currently a connected browser-side research preflight surface.

Machine receipts

RepoProbeMacroV2, RepoProbeReceiptV2, CandidateVettingV1 and RabbitPreflightReceiptV1 are designed so future agents/Rabbit workers can consume the same bounded selection evidence without scraping the UI.

F3F · Curated Rabbit Gate

Probe broad pool
  → per-source vetting
  → cross-source policy
     SOURCE_NORMALIZED | BALANCED_SOURCES | PURE_RELEVANCE
  → RabbitPreflightReceiptV1
  → PROMOTE → RABBIT
  → operational candidates only
  → VETTED main-gate queue
  → ADD VETTED / configurable ADD GREEN gate pass
  → deep acquisition

Probe metadata previews are client-owned reconnaissance. By default they are cleared after successful handoff while the preflight receipt and lineage remain. Non-operational sources remain metadata evidence until a dedicated acquisition adapter exists.

F3F · Theme ownership contract

Theme tokens are owned only by body[data-theme]. Child controls may carry theme-related metadata without instantiating an accidental nested token scope. This closes the low-contrast Theme-menu defect and becomes the contract for new Director, Probe, export and OS UI surfaces.