Skip to content

AC (complexity)

A circuit-complexity hierarchy of languages decidable by polynomial-size, polylogarithmic-depth Boolean circuits with unbounded-fan-in AND and OR gates.

Version
v1 · 2026-09-08 · History
Domain-specific #
3182
Origin domain
computational complexity
Subdomain
computational complexity

Core Idea

AC^i contains languages recognized by polynomial-size circuit families of depth O(log^i n) using NOT and unbounded-fan-in AND and OR gates, under a stated uniformity convention. Unbounded fan-in compresses large conjunctions and disjunctions into single layers, while the depth exponent stratifies parallel circuit resources. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of computational complexity. It is Changing the gate basis to majority or modular gates yields neighboring TC or ACC classes; omitting uniformity can change the class being asserted..

Scope of Application

AC (complexity) belongs to computational complexity and is useful where the analyst can specify families of Boolean circuits indexed by input length, with size, depth, fan-in, uniformity, and accepted languages, then evaluate the family obeys polynomial size, the declared polylogarithmic depth bound, allowed gate basis, and uniformity condition. The scope is broad within that domain but bounded by the need for the family obeys polynomial size, the declared polylogarithmic depth bound, allowed gate basis, and uniformity condition. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity

The abstraction clarifies a crowded vocabulary by making the family obeys polynomial size, the declared polylogarithmic depth bound, allowed gate basis, and uniformity condition the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name AC (complexity) can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to AC (complexity). AC (complexity) compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: families of Boolean circuits indexed by input length, with size, depth, fan-in, uniformity, and accepted languages. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the family obeys polynomial size, the declared polylogarithmic depth bound, allowed gate basis, and uniformity condition independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of computational complexity because they reuse families of Boolean circuits indexed by input length, with size, depth, fan-in, uniformity, and accepted languages, Unbounded fan-in compresses large conjunctions and disjunctions into single layers, while the depth exponent stratifies parallel circuit resources., and type the carrier, state every parameter and convention in the definition, test that the family obeys polynomial size, the declared polylogarithmic depth bound, allowed gate basis, and uniformity condition, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for AC (complexity)Parents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.AC (complexity)DOMAINPrime abstraction: Complexity — is a kind ofComplexityPRIME

Current abstraction AC (complexity) Domain-specific

Parents (1) — more general patterns this builds on

  • AC (complexity) is a kind of Complexity Prime

    The proposed strict upward parent is prime:complexity.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

AC (complexity) sits in a crowded region of the domain-specific corpus (36th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Computational Complexity Classes & Reductions (22 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08