HermitCrab synthesis: 98% of Mbugwe synthesis work goes to candidates whose root lookup hits but never match the surface

Đang mở
  • Có gì không ổn?
#607 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
52/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
csharp
Lĩnh vực
backend

Hướng nghiên cứu

Start with docs/hermitcrab-2026-10-21-search-cost-round.md, lines 319–330, then review the failure-reason trace from #534 and the related discussion in #560. Identify where synthesis failures are traced and determine how to classify candidates whose lexical lookup hits but whose surface does not match. Done means the failures are classified by rejecting rule in work steps; do not add pruning.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

Claude-drafted.

98% of Mbugwe's synthesis work goes to candidates whose lexical lookup hits but whose synthesis never matches the surface form. It is the largest unaddressed bucket on Mbugwe, and no sound prune is known. The same share was 86% on the private deletion variant, but that figure was measured before a port fix (fix B) that cut the variant's total work by 94.7%, so it does not describe the current port or hc.dll.

Status: open research lead, not started.

What we know (HC-Rust port, synthesis work in work steps):

  • 98% on Mbugwe; the record does not give the sample or the fix state for that figure.
  • 86% on the private deletion variant, before fix B (303,966,311 work steps then, 16,220,190 after).
  • A lexical oracle cannot prune these candidates: the root is reachable, so lexical-reachability pruning (ledger rows 10 and 11) cannot reach them.
  • The 2026-10-27 census on hc.dll attributes steps by failure reason (SurfaceFormMismatch is 27.2% of Mbugwe synthesis steps) but does not split root-reachable failures.

Not known: which rules reject these candidates, and whether a sound condition exists.

Proposed change: classify these failures by the rule that rejects them, in work steps. Do not add a prune until a sound condition is found.

Related: #534 (PR, closed, not merged), #560 (open). The failure-reason trace that would do the classification is #534's; the census harness (branch research/failure-reason-stats at af97348b) is test-only. PanGloss: sillsdev/PanGloss#109 (pointer, open), which depends on sillsdev/PanGloss#34 (open, ports #534).

Next: revive the #534 failure-reason trace, or extend the census harness, and report work steps per rejecting rule on Mbugwe.

Evidence -- what the record states
  • Open lead 4: 86% (deletion variant, before fix B) and 98% (Mbugwe) of synthesis work goes to candidates whose lookup hits but whose synthesis never matches the surface (L338-L341); the same sentence appears in the C1 verdict (L160-L162).
  • Fix B: a re-inserted segment-class node keeps its members on a featureless grammar. It was a bug in the Rust port; C# was already exact. Deletion variant, held list: 303,966,311 to 16,220,190 work steps, 94.7% less (L51).
  • Before fix B, a two-word profile of the deletion variant put synthesis at about 90% of parser work (L101-L103).
Sources -- pinned to 2eba2f50 (closed PR #490 record)
What would reopen this

A sound condition that rejects a root-reachable failure class before it is synthesised, with a work-step ceiling worth its cost.

Ngôn ngữ chính
C#
Star
29
Fork
16
Merge trung bình
6 ngày 7 giờ
Pull request đã merge (30 ngày)
14

Chuẩn bị môi trường

  • Không có Dockerfile hay tệp Docker Compose
  • Có mẫu pull request
  • Không có hướng dẫn đóng góp

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của sillsdev/machine

Tất cả issue của sillsdev/machine

Issue tương tự

Thêm issue về C#

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.