- replace real keys/passwords/tokens/connection strings with {{SECRET_*}}
placeholders across 24 files (review-named 12 + noise-audit finds:
WAQI/Dovecot/GPS/VPN subscriptions/Work runbooks/Plane API key)
- widen verifier: OPENSSH/RSA key headers, hyphenated sk-/prefixed sk-,
credential assignments & table cells, telegram bot tokens, conn strings
- placeholder/default-value/config-name exemptions to kill doc FPs
- skip .obsidian plugin code and frozen Inbox-Clippings from value scan
- GIT_WORKFLOW: no git add ., verifier before commit, force-push exception
- final regression: 0 flagged in tracked scope (was 43)
created
| created |
|---|
| 2025-09-13 |
Projects
Purpose: Time-bound initiatives with clear completion criteria.
What is a Project?
A project has:
- A specific goal or deliverable
- A clear end date or completion criteria
- Multiple tasks or actions
Examples: Writing a paper, launching a product, planning an event, learning a new skill
Recommended Structure
For each project folder, create:
Research/- Source materials and referencesDrafts/- Work in progressOutput/- Final deliverablesREADME.md- Project objectives, timeline, and status
Project Lifecycle
- Start: Create folder with subfolders and README
- During: Keep all related materials in the project folder
- Complete: Create summary note, then move to
04_Archive/
Active Project Folders
Tips
- Link to relevant Areas and Resources
- Commit regularly to track progress with git
- Review weekly to check status and next actions