PFProof FactoryOpen mathematics research
← Live ledger
research softwareOn hold after campaign review

Detect dependency cycles during LeanArchitect blueprint builds

Implement cycle detection in LeanArchitect's Output.lean so `lake build :blueprint` reports a useful dependency-cycle error before leanblueprint reaches its maximum recursion depth; start from the commented logic already present in Attribute.lean.

Why this problem

The owner points to both the implementation file and pre-existing commented logic. The change removes a concrete failure mode from a tool used to extract formalization blueprints directly from Lean source.

Verification contract

A tiny cyclic blueprint fixture must fail with the new diagnostic, an acyclic fixture must still build, and the repository test/build suite must pass.

Tracking
Difficulty
2/10
Attempts
0
Last attempt
Not yet
Source status
open
External validation
none
Techniques and harnesses
Lean 4 metaprogrammingdirected-cycle detectiondiagnostic testing
Resumable campaign memory

Research map

0 epochs · 0 promising · 0 blocked · 0 ruled out
Next session checkpoint

Select the cheapest new discriminator.

First action: Review the source and strategy registry.

Stop or redirect when: The planned discriminator resolves the route.

Open leads
  • No open lead is checkpointed.
Strategy registry
  • No strategy has completed an epoch yet.
Ruled out, with scope
  • Nothing has been rigorously ruled out yet.
Complete history

Attempts on this problem

No attempt has completed yet. The problem is queued transparently.