Might as well float this idea here since this is supposed t…

Might as well float this idea here since this is supposed to be the test factory:
Should we have enumerated lock types?
i.e should a lock contract be redeployed to have a type field that the app optionally sets when setting locking amount and duration?
the question arises for general indexing vs specified purpose indexing:
0 lock2 unspecified signal (and all grandfathered locks under original contract)
1 lock2 weight information signal (user as target) exampled hodlocker
2 lock2 mint signal (minter as target)
3 lock2 rate 1-5 fixed polarized signal (user and code as target)
4 lock2 vote
>4 TBD extensible definition

Then somebody could use an enum-aware indexer for their app that has parsed out only the lock types they are interested in. worth it for long term? thoughts?