Skip to content

Conversation

@ValentinBredemestre
Copy link
Contributor

Introduce a TopologicalDerivation structure recording anomaly cancellation conditions as linear, quadratic and cubic homogeneous forms arising from a formal derivation (e.g. triangle diagrams or index-theoretic methods).

Provide a canonical map from TopologicalDerivation to ACCSystem, together with basic simp lemmas, and update the document structure accordingly.

Introduce a `TopologicalDerivation` structure recording anomaly cancellation conditions
as linear, quadratic and cubic homogeneous forms arising from a formal derivation
(e.g. triangle diagrams or index-theoretic methods).

Provide a canonical map from `TopologicalDerivation` to `ACCSystem`, together with
basic simp lemmas, and update the document structure accordingly.
@ValentinBredemestre ValentinBredemestre requested a review from a team as a code owner January 10, 2026 22:01
@ValentinBredemestre ValentinBredemestre changed the title Add topological derivation interface for anomaly cancellation conditions TODO 6VZMW Add topological derivation interface for anomaly cancellation conditions Jan 10, 2026
@jstoobysmith
Copy link
Member

Is there a difference between ACCSystem and TopologicalDerivation here? If not, I'm not sure we need the latter.

Introduce `TopologicalDerivation` as a lightweight abbreviation for `ACCSystem`,
used to record the intended topological or perturbative origin of anomaly
cancellation conditions (e.g. via triangle diagrams or index-theoretic methods).

This avoids duplicating the structure of `ACCSystem` while addressing the
corresponding TODO item.
@ValentinBredemestre
Copy link
Contributor Author

Sorry for the late reply, I’ve been quite busy recently. : /

This is my first time handling a TODO in the project, so I’m still learning the conventions and best practices here. Thanks a lot for the comment and for pointing this out, I really appreciate it. = )

I’ve updated the code to avoid duplicating ACCSystem and instead introduced TopologicalDerivation as a lightweight abbreviation, whose purpose is only to record the intended origin of the anomaly cancellation conditions. I hope this aligns better with the overall design. = )

@jstoobysmith
Copy link
Member

No worries :). This is probably one of the harder TODOs one could have picked :). I think what is probably best, because the documentation you have included is nice is the following:

  1. Keep the TODO item in place, but add more detail based on your documentation for the "## J" subheading.
  2. Don't define TopologicalDerivation explicitly, but add some information to the documentation string of ACCSystem stating that it is what should be derived (etc.).

If this makes sense.

…tion

Expand the documentation of `ACCSystem` and the Open TODO section to clarify that
anomaly cancellation conditions are intended to arise from formal derivations
(e.g. via triangle Feynman diagrams or index-theoretic methods).

No new definitions are introduced; the corresponding TODO item is kept open.
@ValentinBredemestre
Copy link
Contributor Author

Thanks a lot, that makes sense. = )

Before working on TODO 6VZMW more concretely, I just wanted to check what level of formalization you would expect there. In particular, would you envision something like a lightweight abstract structure encoding “gauge data” together with a map producing an ACCSystem, or is the intention more to keep this purely at the level of documentation for now?

I want to make sure any further work aligns well with the intended scope of this file and the project. = )

@jstoobysmith
Copy link
Member

Awesome, thanks for your edits.

In particular, would you envision something like a lightweight abstract structure encoding “gauge data” together with a map producing an ACCSystem, or is the intention more to keep this purely at the level of documentation for now?

I think the former. Ideally one would have a data type corresponding to a gauge field, and then be able to construct the triangle diagrams or use the topological index theorems to get from that to the ACC conditions. There are likely easier intermediate steps that could be done here though and maybe a start would be to break this TODO down into smaller TODO items.

Copy link
Member

@jstoobysmith jstoobysmith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved - and will merge now :).

@jstoobysmith jstoobysmith merged commit e96fa6c into HEPLean:master Jan 14, 2026
3 checks passed
@jstoobysmith
Copy link
Member

More generally, in this direction is this GitHub issue #880 which involves refactoring all of the code around these anomaly cancellation conditions, to make them centered on a key data structure.

@ValentinBredemestre ValentinBredemestre deleted the 6VZMW branch January 14, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants