Skip to content

docs: digest 2026 research-landscape survey + record LLM-layer position#41

Merged
PhysShell merged 2 commits into
mainfrom
claude/research-landscape-notes
Jun 19, 2026
Merged

docs: digest 2026 research-landscape survey + record LLM-layer position#41
PhysShell merged 2 commits into
mainfrom
claude/research-landscape-notes

Conversation

@PhysShell

@PhysShell PhysShell commented Jun 19, 2026

Copy link
Copy Markdown
Owner

Add docs/notes/research-landscape-2026.md, a companion to the consolidation-and-positioning note: that one covers form (naming, schema, splits); this one covers research positioning (landscape, gaps, LLM role).

Captures the external survey's thesis (external static contracts for .NET resource/lifetime bugs; resource-leak / specify-and-check family; hybrid LLM+static keeping the deterministic checker as decider; the missing public .NET lifetime/resource benchmark as the opening), then records the three places our reading diverges:

  • We already have a deterministic spec miner (contract-inference / _infer_param_effect), which the survey files under far-horizon LLM work.
  • Differentiation is already demonstrated (3-way oracle on WalletWasabi), so the benchmark ask is "formalize what we did", not net-new.
  • The LLM layer must be a falsifiable fix/refactor assistant downstream of the verifier, never a trusted spec source: an LLM fix is locally falsifiable (re-run checker + tests), an LLM spec is trusted-base and fails silently. Any spec miner must be validator-gated, not trust-the-source.

Records the implied backlog (SARIF exporter, benchmark corpus as first-class artifact, metamorphic robustness harness, validator-gated boundary-API spec miner) without scheduling it, and explicitly de-duplicates the SUB/DIS rename against the already-logged WPFxxx rename decision.

Claude-Session: https://claude.ai/code/session_01Rg8kSk1YT14x7A1vo5zgED

Summary by CodeRabbit

  • Documentation
    • Added new research documentation summarizing a 2026 .NET static-analysis landscape, highlighting gaps, aligning areas of progress, and outlining a prioritized research backlog for future work.

@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: debbf4d5-a695-4f4b-98ab-9dd0deaab7a3

📥 Commits

Reviewing files that changed from the base of the PR and between c227fac and a3476d6.

📒 Files selected for processing (1)
  • docs/notes/research-landscape-2026.md

📝 Walkthrough

Walkthrough

A new research notes file docs/notes/research-landscape-2026.md (169 lines) is added. It digests an external 2026 .NET static-analysis survey, maps it to Own.NET's current positioning, defines a "LLM strictly downstream of the verifier" stance, lists four concrete backlog artifacts, documents explicit non-adoptions, and restates the benchmark-corpus and metamorphic-harness priority.

Changes

Research Landscape 2026 Notes

Layer / File(s) Summary
Document intro and survey summary
docs/notes/research-landscape-2026.md
Introduces the working-notes digest and summarizes the external survey's thesis: static-contract layer as Rust-for-C# alternative, three technology currents, identified benchmark and lifetime-resource gap, and recommended priority shape.
Own.NET alignment and LLM integration stance
docs/notes/research-landscape-2026.md
Documents where Own.NET already leads the survey (deterministic spec mining, oracle and real-world mining differentiation), then defines LLMs as falsifiable assistants strictly downstream of the deterministic verifier, with validator-gated candidate spec handling and a fix-loop workflow tied to a metamorphic conformance harness.
Concrete backlog, non-adoptions, and restated priority
docs/notes/research-landscape-2026.md
Lists four backlog artifacts in priority order (SARIF exporter, benchmark corpus, metamorphic robustness harness, validator-gated boundary-API spec miner), explicitly excludes paper-roadmap deliverables and far-horizon items, and restates the benchmark corpus plus metamorphic harness as the key enabling brick.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐇 A note appeared, quite fresh and bright,
On .NET specs and static light.
The LLM hops downstream with care,
No trusted source—just verified fare.
Benchmark corpus, harness in hand,
The rabbit nods: a solid plan! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and accurately summarizes the main change: adding documentation that digests a 2026 research-landscape survey and records the project's LLM-layer positioning.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/research-landscape-notes

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/notes/research-landscape-2026.md`:
- Around line 142-145: The reference to `consolidation-and-positioning.md` in
the notes section cannot be verified because the file does not exist in the
repository. Search the repository for any existing consolidation or
positioning-related documentation files with similar names. If found, correct
the filename reference to match the actual file name. If no such file exists and
the deduplication claim is unverifiable, either remove the reference to the
non-existent file entirely, or update the text to explicitly state that the
consolidation decision ownership needs to be clarified or established in a
document that should be created.
- Around line 50-62: The research-landscape-2026.md document claims completed
3-way oracle work (Own.NET vs Infer# vs CodeQL) on WalletWasabi and references a
non-existent consolidation-and-positioning.md file. Either document the
WalletWasabi oracle results in oracle.md and real-world-mining.md with
supporting details about the subscription-leak findings, create the missing
consolidation-and-positioning.md file, or revise the claims in the
research-landscape-2026.md document to clearly indicate whether this work is
completed or planned rather than asserting it as accomplished fact.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5aa4f09f-40f2-41f0-a480-5924694d10c2

📥 Commits

Reviewing files that changed from the base of the PR and between 1679a91 and c227fac.

📒 Files selected for processing (1)
  • docs/notes/research-landscape-2026.md

Comment thread docs/notes/research-landscape-2026.md Outdated
Comment thread docs/notes/research-landscape-2026.md
claude added 2 commits June 19, 2026 12:26
Add docs/notes/research-landscape-2026.md, a companion to the
consolidation-and-positioning note: that one covers form (naming, schema,
splits); this one covers research positioning (landscape, gaps, LLM role).

Captures the external survey's thesis (external static contracts for .NET
resource/lifetime bugs; resource-leak / specify-and-check family; hybrid
LLM+static keeping the deterministic checker as decider; the missing public
.NET lifetime/resource benchmark as the opening), then records the three
places our reading diverges:

- We already have a *deterministic* spec miner (contract-inference /
  _infer_param_effect), which the survey files under far-horizon LLM work.
- Differentiation is already demonstrated (3-way oracle on WalletWasabi),
  so the benchmark ask is "formalize what we did", not net-new.
- The LLM layer must be a falsifiable fix/refactor assistant downstream of
  the verifier, never a trusted spec source: an LLM fix is locally
  falsifiable (re-run checker + tests), an LLM spec is trusted-base and
  fails silently. Any spec miner must be validator-gated, not trust-the-source.

Records the implied backlog (SARIF exporter, benchmark corpus as first-class
artifact, metamorphic robustness harness, validator-gated boundary-API spec
miner) without scheduling it, and explicitly de-duplicates the SUB/DIS rename
against the already-logged WPFxxx rename decision.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rg8kSk1YT14x7A1vo5zgED
…cle run

CodeRabbit (PR #41) correctly flagged that the note cited oracle.md /
real-world-mining.md as evidence for a WalletWasabi 3-way oracle run, but
those files document the ScreenToGif and Dapper runs — WalletWasabi is not
written up anywhere in docs/. The WalletWasabi mining/oracle happened in CI
but its result was never distilled into the repo, so the citation was broken.

Retarget the "differentiation is already demonstrated" claim to the
*documented* ScreenToGif oracle result (SystemEvents error + VideoSource
warnings, own-only; CodeQL has no "subscribed-never-unsubscribed" query,
Infer# misses it too — all in real-world-mining.md "Cross-tool validation"),
and label the larger WalletWasabi run honestly as "exercised in CI, not yet
distilled into a committed corpus artifact" — which is precisely the
benchmark-corpus backlog item, not a result to lean on. Same fix in the
backlog bullet.

The other flagged reference (consolidation-and-positioning.md) was a
merge-timing artifact: it lives in #38, which merged ~3 min after the review;
the branch is now rebased onto main, so the file is present.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rg8kSk1YT14x7A1vo5zgED
@PhysShell
PhysShell force-pushed the claude/research-landscape-notes branch from c227fac to a3476d6 Compare June 19, 2026 12:27
@PhysShell
PhysShell merged commit 9eacbaa into main Jun 19, 2026
17 checks passed
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