aboutsummaryrefslogtreecommitdiff
path: root/working/notes-template-lint
diff options
context:
space:
mode:
Diffstat (limited to 'working/notes-template-lint')
-rw-r--r--working/notes-template-lint/notes.org.proposed86
-rw-r--r--working/notes-template-lint/proposal-from-smoke.org5
-rw-r--r--working/notes-template-lint/proposed.diff38
3 files changed, 129 insertions, 0 deletions
diff --git a/working/notes-template-lint/notes.org.proposed b/working/notes-template-lint/notes.org.proposed
new file mode 100644
index 0000000..311a86f
--- /dev/null
+++ b/working/notes-template-lint/notes.org.proposed
@@ -0,0 +1,86 @@
+#+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
+
diff --git a/working/notes-template-lint/proposal-from-smoke.org b/working/notes-template-lint/proposal-from-smoke.org
new file mode 100644
index 0000000..26b458a
--- /dev/null
+++ b/working/notes-template-lint/proposal-from-smoke.org
@@ -0,0 +1,5 @@
+#+TITLE: Proposal: clean four lint-org flags in the notes.org templat
+#+SOURCE: from smoke
+#+DATE: 2026-07-21 06:49:22 -0500
+
+Proposal: clean four lint-org flags in the notes.org template (claude-templates/.ai/notes.org). A sentry pass over smoke's synced copy flagged: (1) two 'possibly misplaced heading' judgments on the boilerplate lines that open with org bold at column 0 ('**When to read this:**' and '**What's in this file:**' in the About This File section) — org can parse a line-initial ** as a level-2 heading; rephrasing (a list dash, or moving the bold off line start) would clear it everywhere. (2) two 'possible incomplete block' judgments around the Pending Decisions instructions' #+begin_example block that shows the entry format — likely the example content confusing block parsing; worth a look at whether the example should escape its own markers (e.g. a comma-escaped ,** or ,#+ inside the block). Both are cosmetic — no behavior breaks — but every project inherits the lint noise on each sweep, so one canonical fix beats N local ones. No local edit made in smoke; its copy stays template-faithful.
diff --git a/working/notes-template-lint/proposed.diff b/working/notes-template-lint/proposed.diff
new file mode 100644
index 0000000..627741f
--- /dev/null
+++ b/working/notes-template-lint/proposed.diff
@@ -0,0 +1,38 @@
+--- claude-templates/.ai/notes.org 2026-07-09 13:57:29.814830969 -0500
++++ /tmp/nt.org 2026-07-23 02:48:03.165968767 -0500
+@@ -6,19 +6,19 @@
+
+ This file contains project-specific information for this project.
+
+-**When to read this:**
++- 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:**
++- 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.
++- 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]]
++- For protocols and conventions, see [[file:protocols.org][protocols.org]].
+
+ * Project-Specific Context
+
+@@ -48,9 +48,9 @@
+ - 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:**
++- Example format:
+ #+begin_example
+-** Feature Name or Topic
++,** Feature Name or Topic
+
+ Craig needs to decide on [specific question].
+