# MIP102c2-SP34 Issues

## AVC References

| MIP | Line |
|--|--|
| 106 | 241 |
| 106 | 901-902 |
| 113 | 171 |
| 113 | 241 |
| 113 | 520 |

Gave up. Way too many references

## Numbering

| MIP | Line |
|--|--|
| 104 | 216 |
| 104 | 230 |
| 104 | Skipped fourth article |
| 104 | Skipped 5.2 article |
| 104 | Skipped sixth article |
| 104 | Skipped eight article |
| 104 | Skipped twelfth article |
| 104 | 538|
| 106 | Skipped 2.3 |
| 106 | Skipped 3.1 |
| 106 | 407 |
| 106 | 1368 (and not referenced from anywhere)|

Gave up. Way too many issues. This should be approached systematically with a clear objective

---

_Sometimes_ letters are introduced as part of article codes *along* numbers -- e.g.:

### 1.1

Content

### 1.1.1A

Content

(Versus `1.1A`)

## Misc

- Please see [CivicSage's comment](https://github.com/makerdao/mips/pull/1100#discussion_r1620592903) and my comment below it.
- Please see [CivicSage's comment](https://github.com/makerdao/mips/pull/1100#discussion_r1620880048). Sounds reasonable to be more specific
- Please see [CivicSage's comment](https://github.com/makerdao/mips/pull/1100#discussion_r1620823208)
- Letters in article codes are supposed to be semantic (A for lists/records, B for budgets, T for templates), but their use is not consistent. (Oh, reminder for myself that GFXLabs is introducing _C_ in their amendment, too)
-