docs(questions): #36 — E0608 entry-export ratification asked #169

tvidal · 2026-07-15T09:30:00+02:00

tvidal commented

2026-07-15 09:30:00 +02:00

docs(questions): #36 — E0608 entry-export ratification asked

Along the way:

docs(questions): #37-39 — the 3b-general walls (handle across entry, boot ref capture, provider lifetime vs exit)
docs(questions): #35-39 RULED — truthful composition then the door; call surface is (b); roster position is the key; explicit-kill is the lifecycle

Touches 1 file: questions.md.

docs(questions): #36 — E0608 entry-export ratification asked Along the way: - docs(questions): #37-39 — the 3b-general walls (handle across entry, boot ref capture, provider lifetime vs exit) - docs(questions): #35-39 RULED — truthful composition then the door; call surface is (b); roster position is the key; explicit-kill is the lifecycle Touches 1 file: `questions.md`.

hkowalski requested changes

2026-07-15 11:25:11 +02:00

Dismissed

hkowalski left a comment

Two things inline. The one in questions.md is the one I care about.

Two things inline. The one in `questions.md` is the one I care about.

questions.md

					
				@ -446,0 +502,4 @@

				  From the 3b-general attempt (orchestrator, 2026-08-13 — three independent blockers, probe-proven, nothing edited):

				  37. ▲ How does the provider handle cross the entry? BootEntry's `sup` is a LOCAL of BootEntry::main, and Program::entry() expands to a no-argument

				  `Mod::main();`. Injecting a parameter into the app's fn main makes the E0608-required header a lie (the entry is public declared surface — landed

main reads, decides and writes in one function. The deciding part is the piece I would want to test on its own. Worth splitting?, at questions.md:505.

`main` reads, decides and writes in one function. The deciding part is the piece I would want to test on its own. Worth splitting?, at questions.md:505.