Skip to content

Measure representative raw-feature envelopes before scale selection - #525

Merged
trissim merged 2 commits into
mainfrom
docs/raw-feature-envelope-20261003
Oct 3, 2026
Merged

trissim merged 2 commits into
mainfrom
docs/raw-feature-envelope-20261003

Conversation

@trissim

@trissim trissim commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator

Change

Use the existing measurement guide owner, not a new procedure: replace narrowest-width-only evidence with a distributed raw width/size/intensity envelope, positive and faint controls, and context/native-scale review. Inspect single-scale response tradeoffs before downstream thresholds; use multiscale only if the exact live callable contract supports it. No invented scale parameter, operation or assay settings. Link affected phenotype claims to the strategy owner introduced in #511 rather than duplicate its conclusions.

Ownership and immutable installation

Main-only documentation PR, two files; no production code. Reused the released isolated checkout, preserving foreign dirty submodules. Singer owns the separate producer-retirement guide correction; no viewer-guide edit here. Target04 already contains released511 guides and522 production retirement API. Its canonical viewer procedure remains generic520 wording;522 validation notes are not packaged knowledge. Direct installed guide byte comparisons and original PACKAGE09 qualification are recorded in docs/validation/raw-feature-envelope-guide-20261003.rst.

Evidence boundary

Source/link review and git diff --check pass. Complete use-openhcs and Diataxis skills read. No scientist contexts/reports/images/settings/answers consulted; no tests/imports/build/install/native/MCP/UI/provider launch, runtime replay, fresh environment/worktree or hot update. Existing target04/SCI505 and frozen evaluations remain unchanged. New measurement guidance is source-only, NOT inside target04 and NOT demonstrated autonomous biological improvement.

@trissim

trissim commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator Author

Normal current-main integration is now published at 4ced6eb, including merged526 main532b13f5f0f872590d2f9022b33b575126bd02f3. Clean merge, no overlapping526 paths: only the original measurement-interpretation guide and its original validation receipt differ from current main. Both525 files are byte-unchanged from reviewed05927; git diff --check PASS. Singer notified of the disjoint boundary. Seven foreign dirty gitlink worktrees preserved, no submodule reset/update, tests/import/build/install/runtime/SCI contact or hot sync. Parent95 tinyarchive/retirement receiving remains separate;511 catalog acceptance is serial only after fixture terminal.

@trissim
trissim marked this pull request as ready for review October 3, 2026 10:48
Copilot AI balanced review requested due to automatic review settings October 3, 2026 10:48
@trissim
trissim merged commit eea91cc into main Oct 3, 2026
7 of 40 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@trissim

trissim commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator Author

Owner release for parent merge NOW: exact reviewed head 4ced6eb. Local and remote PR head match; only the two reviewed documentation/validation files are in scope. No unpublished top-level hunks or untracked files, no competing own source changes, pending edits or declared source borrower. Same-user current process cwd/exe check found no checkout borrower (not a privileged full import-origin certification). Seven foreign dirty gitlinks remain protected and are outside this release. Singer and Planck notified. Parent may merge source-only without CI/full pytest; Planck07 derives the newly merged canonical asset and511 claim-specific section through its ordinary source integration. No frozen06 hot sync, new build/install/runtime or scientific contact by this owner.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants