Generate and confirm candidates

Penrose can generate hypotheses from registered searches, but generation is optional and default-off.

Generate candidates for the referee. Two modes: claims broad prose hypotheses the referee routes and tests (P3-P9). Gate: PENROSE_GENERATIVE_LAYER=1 specs executable, corpus-grounded formulaic_signal specs. Gate: that + a configured confirmation reserve Claims writes questions for the referee to answer; specs writes answers for the referee to check.

mode	input	output	gate	when to use
`claims`	Broad prose-hypothesis generation grounded in referee evidence	Registered hypotheses, optionally routed through P3-P9	`PENROSE_GENERATIVE_LAYER=1`	Ask the referee new testable questions
`specs`	Provenance-safe corpus concepts and executable capabilities	Registered, corpus-grounded `formulaic_signal` specs	Generative layer plus an adequate confirmation reserve	Produce executable answers for blind confirmation

Enable deliberately

penrose generate
PENROSE_GENERATIVE_LAYER=1 penrose generate claims -n 10
PENROSE_GENERATIVE_LAYER=1 penrose generate specs -n 10

The bare command reports both modes and their live readiness. Each mode's budget is preregistered; failed or discarded slots still count toward the search denominator.

Admission

Candidates are checked against the current executor and data capability snapshot. Bounded repair may normalize names or mechanically supported syntax; it cannot invent a missing series, semantic, or economic assumption.

Discovery cap

An unanchored generated candidate cannot become research-supported from discovery alone. A distinct, frozen survivor must enter confirmation.

Confirmation

Confirmation checks power before touching its reserve, executes the candidate's own frozen signal, and preserves the original registered denominator. A reserve is consumed once for that distinct claim.

Stop condition

Even after confirmation, P9 remains human. Candidate generation never authorizes trading or corpus promotion.