code wiki / (root) / nx_autoformalize_cap_probe.nx

nx_autoformalize_cap_probe.nx

buildroot/runtime/nx_autoformalize_cap_probe.nx

2184 B46 linesdepth 8pulls 8 transitivereach 0 importersview sourcekind probe
docsdependenciesstructsconstsfunctions

about

nx_autoformalize_cap_probe.nx -- what does the 8-token cap in af_parse ACTUALLY do? Debt 1785521261 claimed it produces a WELL-FORMED FORMALIZATION OF A WEAKER STATEMENT (silently dropping trailing constraints). Reading the consumer suggests otherwise: it accepts ONLY nt==3 or nt==5 and returns 0 for anything else, so a 9+ token sentence truncated to 8 should match NEITHER shape and REFUSE. This probe settles which is true by RUNNING it, because a wrong debt is worse than no debt -- it sends the next person to fix something that is not broken. expect_exit: 0 license_tier: ORIGINAL

dependencies 2 imports · 0 importers

nx_syscalls.nx nx_autoformalize_lib.nx nx_autoformalize_cap_probe.nx

imports: nx_syscalls.nxnx_autoformalize_lib.nx

imported by: nobody (leaf or entry point)

call flow from main pre-order; caps 40 nodes / depth 6 declared; ↻ = already shown

main sys_mmap af_parse af_tok_num af_streq af_tok_plus af_streq ↻ af_tok_times af_streq ↻ af_tok_le af_streq ↻ af_tok_lt af_streq ↻ af_tok_unknown af_streq ↻ af_tok_eqw af_streq ↻ ac_w sys_write

structs

none

consts

none

functions

13func ac_w(s: *u8) -> i64
called by 1: main calls 1: sys_write
20func main() -> i64