aboutsummaryrefslogtreecommitdiff
path: root/working/notes-template-lint/notes.org.proposed
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-23 08:41:44 -0500
committerCraig Jennings <c@cjennings.net>2026-07-23 08:41:44 -0500
commit10ea44b6de3be1872f7f0bd4501ccf3878105bc4 (patch)
treec4165d496f153172702c8a5cb574e97be470c738 /working/notes-template-lint/notes.org.proposed
parent01356fa036847f9d216dd92a006049105c2d5461 (diff)
downloadrulesets-10ea44b6de3be1872f7f0bd4501ccf3878105bc4.tar.gz
rulesets-10ea44b6de3be1872f7f0bd4501ccf3878105bc4.zip
feat(workflows): clear temp/ at wrap, plus three rule and template fixes
Four proposals from other projects, reviewed and applied together. wrap-it-up gains a Clear temp/ step in Step 3. temp/ is gitignored everywhere, so nothing there survives deletion. The step confirms before removing anything that reads as in-progress rather than throwaway, and skips where temp/ isn't gitignored. This closes the last open clause of the working/temp work from 2026-07-20. interaction.md drops the fenced-code-block carve-out. Chat output carries no markup at all now, fences included. Fences don't invert the way inline spans do, but the carve-out kept pulling them back in. sentry.org folds in four notes from its first two live runs elsewhere. Two are traps for anyone reviewing a night by git log: archive-done touches .gitignore on its first run, and a mirror-only project's quiet fires leave no commits at all. The others make property sweeps sanctioned quiet-fire work and split the task audit into a mechanical hourly subset plus a nightly judgment half. The notes.org template now lints clean, down from four flags in every project on every sweep. Two of those were mechanical, so lint-org --fix anywhere would have rewritten the template and drifted it from canonical.
Diffstat (limited to 'working/notes-template-lint/notes.org.proposed')
-rw-r--r--working/notes-template-lint/notes.org.proposed86
1 files changed, 0 insertions, 86 deletions
diff --git a/working/notes-template-lint/notes.org.proposed b/working/notes-template-lint/notes.org.proposed
deleted file mode 100644
index 311a86f..0000000
--- a/working/notes-template-lint/notes.org.proposed
+++ /dev/null
@@ -1,86 +0,0 @@
-#+TITLE: Claude Code Notes - [Project Name]
-#+AUTHOR: Craig Jennings
-#+DATE: [Date]
-
-* About This File
-
-This file contains project-specific information for this project.
-
-- When to read this:
-- At the start of EVERY session (after reading protocols.org)
-- When needing project context or history
-- When checking reminders or pending decisions
-
-- What's in this file:
-- Project-specific context and goals
-- Pending decisions
-- Active reminders
-
-- Session history is NOT in this file. Each session's record lives in =.ai/sessions/YYYY-MM-DD-HH-MM-description.org= — one file per session. Catch-up reads the Summary sections of the most recent 5.
-
-- For protocols and conventions, see [[file:protocols.org][protocols.org]].
-
-* Project-Specific Context
-
-This is where context regarding this project is placed.
-
-Examples of what goes here:
-- Project overview and goals
-- People and their relationships to the user
-- Contact information for companies and people
-- Current state of the project
-- Status report
-- Links to important documents
-- Technical architecture notes
-- Key decisions and rationale
-
-** If this is the first session
-
-Run the first-session workflow: [[file:workflows/first-session.org][first-session.org]]. It walks through git/.ai policy, project orientation, and initializing this notes.org. Remove this heading once done.
-
-* PENDING DECISIONS
-
-This section tracks decisions that need Craig's input before work can proceed.
-
-**Instructions:**
-- Add pending decisions as they arise during sessions
-- Format: =** [Topic/Feature Name]=
-- Include: What needs to be decided, options available, why it matters
-- Remove decisions once resolved (the resolution is captured in the Session Log of the session where it was resolved)
-
-- Example format:
-#+begin_example
-,** Feature Name or Topic
-
-Craig needs to decide on [specific question].
-
-Options:
-1. Option A - [brief description, pros/cons]
-2. Option B - [brief description, pros/cons]
-
-Why this matters: [impact on project]
-
-Implementation is ready - just need Craig's preference.
-#+end_example
-
-** Current Pending Decisions
-
-(None currently - will be added as they arise)
-
-* Active Reminders
-
-** Current Reminders
-
-(None currently - will be added as needed)
-
-** Instructions for This Section
-
-When Craig says "remind me" about something:
-1. Add it here with timestamp and description
-2. If it's a TODO, also add to =/home/cjennings/org/roam/inbox.org= scheduled for today
-3. Check this section at start of every session
-4. Remove reminders once addressed
-
-Format:
-- =[YYYY-MM-DD]= Description of what to remind Craig about
-