thad/journal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

for the day

Browse Source
This commit is contained in:
thad-w541
2025-10-28 21:12:05 -05:00
parent 11a08221f5
commit 104bc12bd5
13 changed files with 212 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
stockcropper/SC-PUNCHLIST.md
View File

@@ -22,7 +22,7 @@
# MISC
- [ ] Call riley
- [ ]
- [ ] Test solar charging circuitry in the suuuun
# VENDORS
- Motors

8
stockcropper/SC-SOPS.md
View File

@@ -1,18 +1,18 @@
---
Revision Date: 07OCT2025
Revision Date: 28OCT2025
Approved By: TJH
---
Rules are for the obedience of fools and the guidance of wise men.
> Rules are for the obedience of fools and the guidance of wise men.
- Douglas Bader
Often documents like these are very formal and militaristic. We ought to adhere to this document. However, we will not let it hamstring us. If there are things that it doesn't allow us to do, and we need to do them, we will revise this document wisely. We will not simply deviate from this document without addressing the problem with the process that led us to the deviation. It's OK to do things that deviate from this document for a while and see how they go. It's not OK to put anything into production or push to `main` without first discussing those changes and incorporating them into this document.
Often documents like these are very formal and militaristic. We ought to adhere to this document. However, we will not let it hamstring us. If there are things that it doesn't allow us to do, and we need to do them, we will revise this document wisely. We will not simply deviate from this document without addressing the problem with the process that led us to the deviation. It's OK to do things that deviate from this document "offline" for a while and see how they go - as long as you know that's what you're doing, and it's in the context of development, not production. It's not OK to put anything into production or push to `main` without first discussing those changes and incorporating them into this document.
# Component Types and Numbering
Components are given unique numbers. Why numbers? Numbers are cheap, succinct, clean, and consistent. The descriptions of parts may change over time, but the number stays the same.
## Parts (SC-xxxx)
Parts are individual items that aren't meant to be broken down further. Parts may be assembled (or even permanently assembled). This includes both custom and off the shelf components.
Parts are individual items that aren't meant to be broken down further. Parts may be assembled (or even permanently assembled, e.g. welded or glued). This includes both custom and off the shelf components.
Parts are numbered: `SC-xxxx`