Native computation of canonical path data #
Input natural labels and coordinates use binary encodings; syntactic positions and the subdivision budget use unary counters. These certificates compute only the shared paths, crossing cells, and occurrence lookup, with no geometric validity assumption.
Main results #
Cslib.Complexity.SAT.PlanarCompile.computableInPolyTime_budget.Cslib.Complexity.SAT.PlanarCompile.computableInPolyTime_paths.Cslib.Complexity.SAT.PlanarCompile.computableInPolyTime_crossingSites.Cslib.Complexity.SAT.PlanarCompile.computableInPolyTime_occurrencePath.
References #
These are the shared canonical incidence-path constructions and certificates.
Pointwise binary integer addition is polynomial-time computable.
Casting a unary natural number to a binary integer is polynomial-time computable.
Layout.center is computable in polynomial time from a unary index.
The budget is a linear expression in syntactic list lengths, computed as a unary counter.
Canonical incidence routes have a native polynomial-time bounded unit expansion. The input labels and output coordinates are binary; only the step budget is unary.
Deduplicating a route via selectDistinct with an all-true mask is polynomial-time
computable.
Occupied nonvertex crossing sites can be selected in native polynomial time.
Looking up the path for a syntactic literal occurrence is native polynomial-time.