I
The optimization engineCompletion Optimization for Partially Defined Boolean Functions
Question: Can the Boolean function itself be optimized before the circuit?
A PDBF represents a family of Fully Defined Boolean Functions. Completion Optimization searches the Opportunity Space and selects Legal Completions according to gate count, depth, fan-out, area, power, wiring, or another objective.
First optimize the Boolean function. Then optimize the circuit.
The next question: where do PDBFs come from in ordinary designs?
II
The RTL extensionContextual Partially Defined Boolean Functions
Question: Can a block that looks fully specified become partially defined inside a complete RTL design?
Yes. Surrounding circuitry prevents many local input terms from occurring. Contextual PDBF extraction preserves reachable local behavior and exposes all other local terms as hidden contextual don’t-cares.
First discover the Contextual PDBF. Then optimize the PDBF. Then optimize the circuit.
The deepest question: is partial definition exceptional—or intrinsic?
III
The sequential foundationGT AND Sequential Synthesis
Question: Why do sequential systems inherently contain PDBFs?
Only reachable state/input combinations determine observable behavior. The unreachable region is intrinsically unspecified and forms a Native Sequential Device PDBF.
ONLY reachable behavior defines correctness.
Unreachable behavior defines optimization freedom.
Beyond the trilogy: the next question is how directly semantic care domains can guide implementation search.
IV
Beyond the trilogyDesign from Semantics
Question: What circuit structures become available when synthesis is constrained directly by semantic care-domain compatibility?
Paper IV studies direct semantic synthesis across processor-control and protocol-oriented benchmarks and evaluates gates, depth, wiring, and fan-out under independent care-domain verification.
Semantic incompleteness can itself be an optimization resource.