Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

organisation vs MS regulations #192

Open
erolm-a opened this issue Jan 31, 2022 · 0 comments
Open

organisation vs MS regulations #192

erolm-a opened this issue Jan 31, 2022 · 0 comments
Labels
enhancement New feature or request low-priority Low priority issues

Comments

@erolm-a
Copy link
Collaborator

erolm-a commented Jan 31, 2022

The flowchart is better explained here.

Basically:

  • every agent can only perform 2 breaches in cumulative enforcement.
  • if the lice count goes beyond 6.0 (suggested by CoGP) then a treatment is to be performed.
    • If a treatment is performed within 4 weeks and the level goes below 6.0 then it does not count towards the 1st of 2 breaches. By reading between the lines, it means that if an infraction has already been recorded this will count towards a second breach
    • Otherwise, if a treatment was performed but the count ratio did not go below the 6.0 suggested threshold since the first reporting, then it will be counted as a 1 of 2 breaches in cumulative enforcement. If the threshold is not met after 4 more weeks an enforcement notice will be issued.
  • Instead, if no treatment is performed within 6 weeks an enforcement notice will be issued (equivalent to two "strikes")
  • if at any point two strikes are reached an enforcement notice will be issued to the offending farm

What happens when an enforcement notice is issued? Not clear, but we believe a "game over" scenario could be achieved by forced fallowing of all cages.

What do you think @magicicada @anthonyohare ? I believe it would be interesting to support this before implementing policies (#161 ) - as long as we remove the inability to defect.

@erolm-a erolm-a added the enhancement New feature or request label Jan 31, 2022
@erolm-a erolm-a added the low-priority Low priority issues label Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low-priority Low priority issues
Projects
None yet
Development

No branches or pull requests

1 participant