Skip to content

Promote query-aware observability from analytic control to held-out evidence #339

Description

@FlorianPfaff

Scientific objective

Build the evidence required for a Prob4D-centered paper claim:

Partial gauge information is admitted only when it supports a declared physical query; complete-prior uncertainty is retained in unobserved directions; unsupported precision is rejected; otherwise the exact physical fallback is preserved.

The implementation is on science/query-aware-observability-v1. This issue tracks promotion beyond controlled mechanism evidence.

Stage 1 — implementation and analytic control

  • Query-aware implementation PR is green under focused and repository CI.
  • Analytic collinear control artifact is frozen with source revision.
  • On-support query is factor-supported.
  • Broad-prior off-axis query is fallback-unresolved.
  • Tight-prior off-axis query is prior-bounded.
  • Bogus full-rank completion is fallback-invalid-update despite sub-tolerance reported uncertainty.

Stage 2 — DLO-like controlled sweep

Freeze before running:

  • effective rank and geometry-thickness grid;
  • overlap/noise/prior-strength grid;
  • on-support, near-support, and off-support query families;
  • component-wise query tolerances;
  • rank, uncertainty, gain, information-mismatch, and unsupported-information thresholds;
  • sequence/trial seeds and artifact schema.

Required baselines:

  • reject all rank-deficient factors;
  • point transform with no covariance;
  • pseudoinverse covariance without query admission;
  • ridge/full-rank completion;
  • exact observable-subspace fusion without query admission;
  • query admission without provenance audit;
  • full proposed method.

Required outputs:

  • query RMSE/NLL/coverage/calibration;
  • false-admission and false-rejection rates;
  • fallback and harmful-update rates;
  • risk/coverage curves;
  • results conditional on rank and query-nullspace sensitivity;
  • runtime and route accounting.

Stage 3 — fresh-provider qualification

Coordinate with #333 and #49.

  • Reconcile the overlapping PointWorld persistent-point draft PRs into one minimal source contract; do not merge duplicates.
  • Freeze provider checkpoint/runtime/dataset hashes.
  • Pass camera synchronization and calibration gates.
  • Pass metric-coordinate and persistent point-identity gates.
  • Pass source-only overlap/support feasibility gates.
  • Preserve every terminal failure reason.

No target access is authorized merely because the adapter executes.

Stage 4 — held-out registration

Before opening target outputs:

  • freeze physical query definitions and tolerances;
  • freeze query-admission thresholds and whether prior-bounded is permitted;
  • freeze exact fallback and BayesianPhysTwin finite-group harm guard;
  • freeze grouping/bootstrap unit and primary endpoints;
  • freeze stopping and route-accounting rules;
  • commit registration in Prob4D and FlorianPfaff/BayesianPhysTwin-Paper.

Stage 5 — end-to-end evidence

Evaluate on identical held-out factors/queries:

  • exact physical fallback;
  • unguarded provider candidate;
  • exact observable-subspace fusion;
  • query-aware admission;
  • query-aware admission plus BayesianPhysTwin harm guard.

Primary evidence bar:

  • lower harmful-update rate than ridge completion and unguarded exact-factor fusion;
  • materially higher supported-query coverage than rejecting all rank-deficient factors;
  • calibrated complete posterior;
  • nontrivial fresh-provider factor yield;
  • sequence-level uncertainty intervals;
  • complete reporting of positive and terminal negative routes.

Claim boundary

Until Stages 3–5 pass, this work supports only a controlled method claim. It must not be described as fresh real-provider competence, a new benchmark result, or established downstream BayesianPhysTwin improvement.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions