INFO: Staff make a determination recommendation to the DM for minor amendments
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
A minor amendment become immediately “legal” upon submission but staff may recommend that the DM review it and make a determination consistent with RPPR 21
**DETERMINATION RECOMMENDATION PACKAGE**
- [ ] background (a few paragraphs of text) — required
- [ ] recommendation (selection) — required
- [ ] rationale (a few paragraphs) — optional
**FILE ATTACHMENTS**
- [ ] map — required (until other map available)
- an additional map is not required if there is already a map available for this RUP
- may need to consider attachment organization — how do you distinguish previous/general attachments from those associated with THIS action/version
- map needs to always be visible — other documents may be relevant only to a specific submission
- [ ] other documentation — optional
**RECOMMENDATION OPTIONS**
- [ ] Stands
- [ ] Wrongly Made - Stands
- [ ] Wrongly Made - without effect
- [ ] Submit as Mandatory Amendment
In addition to one of the above recommendations the staff person may recommend that
- [ ] suspension of operations not authorized in the absence of this amendment
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing the existing minor-amendment submission and determination workflow, including how maps and version-specific attachments are represented. Done means staff can submit the required package, select one recommendation, optionally add rationale and supporting documents, and record the suspension-of-operations recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- backend-api-design, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100