QuantumComputinglib learn · inspect · formalize
Checked on this commit 2,822 public declarations commit 07559c3d051f Build record

ASPBE harness

Search, prove, validate, and retain evidence

The upper layer controls decomposition and budget; the middle layer maintains a diverse population and feedback; focused workers discharge bounded obligations. Tolerance is relaxed by an explicit schedule, not silently.

Candidate generation, scoring, verification, and acceptance editable Mermaid source
flowchart LR
  C["Candidate construction<br/>U"] --> F["Finite screen<br/>dimensions · unitarity · clean block"]
  F --> L{"Named Lean theorem"}
  L -- "closed" --> V["Certified construction"]
  V --> E["Optional Qiskit /<br/>OpenQASM export"]
  L -- "open" --> O["Explicit obstruction<br/>or missing proof leaf"]
  O --> R["Change construction route<br/>or one declared ε rung"]
  R --> C

  classDef math fill:#ffffff,stroke:#5b6670,color:#222222,stroke-width:1.25px;
  classDef proof fill:#ffffff,stroke:#2f7355,color:#18382b,stroke-width:1.6px;
  classDef fail fill:#ffffff,stroke:#8a5a4a,color:#4c332c,stroke-width:1.4px;
  class C,F,R math;
  class L,V,E proof;
  class O fail;

1. Formal target

Translate the mathematical request into a state-preparation or block-projection contract.

2. Memory retrieval

Retrieve compatible completed declarations, route cards, and known obstructions.

3. Candidate population

Generate distinct constructions and retain provenance, assumptions, and resource tuples.

4. Resource ranking

Apply the declared lexicographic score without promoting an invalid candidate.

5. Lean obligations

Split unitarity, dimensions, register order, projection, normalization, and approximation goals.

6. Adaptive exploration

The upper layer may add agents, recombine routes, or relax epsilon only from recorded feedback.

7. Acceptance gate

Require the Lean build, tests, no-new-proof-hole policy, and source-linked documentation.

8. Executable validation

Run applicable circuit or matrix exports, including Qiskit checks, after the formal certificate gate.

Evidence boundary. Harness declarations formalize controller data and acceptance policy. They do not prove that an external agent run was efficient. Run logs, token accounting, and Qiskit outputs remain engineering evidence attached after the Lean gate.