Skip to content
Baseworks KB

Patrick's Inbox

Created 2026-03-03
Updated 2026-03-20
Tags inboxpatrickworkflow

Review queue. Items are added by Claude when something needs your attention. Mark done [x] and note any decisions.

See WORKFLOW-PROTOCOL.md for how this works.

Open Items

Section titled “Open Items”

2026-06-19

Section titled “2026-06-19”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-19

  • Claude Code updated: 2.1.181 (Claude Code) → 2.1.183 (Claude Code)
  • baseworks-agents system packages: 14 packages updated
  • baseworks-n8n system packages: 13 packages updated
  • n8n updated: 2.26.3 → 2.26.3 (health check: passed)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-19 | 1316MB | OK | | baseworks.com | Weekly | 2026-06-14 | DB=553MB, Files=149MB | OK | | practice | Weekly | 2026-06-14 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-06-14 | DB=29MB, Files=19MB | OK |

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-18

Section titled “2026-06-18”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-18

  • Claude Code updated: 2.1.179 (Claude Code) → 2.1.181 (Claude Code)
  • baseworks-agents system packages: 2 packages updated
  • baseworks-n8n system packages: 2 packages updated
  • n8n updated: 2.26.3 → 2.26.3 (health check: passed)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-18 | 1315MB | OK | | baseworks.com | Weekly | 2026-06-14 | DB=553MB, Files=149MB | OK | | practice | Weekly | 2026-06-14 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-06-14 | DB=29MB, Files=19MB | OK |

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-06-17 23:30 ET | BRNet 2026 session complete — ready for morning review

Section titled “[ ] 2026-06-17 23:30 ET | BRNet 2026 session complete — ready for morning review”

Added by Claude Code on Patrick’s Mac

Everything from tonight’s session is committed and pushed. Here’s what’s done and what needs your attention in the morning.

What’s complete:

  • /write-communications-post skill — committed, available on all machines via git pull
  • 41 conference photos — AVIF/WebP/JPEG at 4K, all 123 files live on CDN at media.baseworks.com/website/events/2026-06-brnet-body-representation/
  • 5/5 lecture transcripts — Olaf Blanke came through cleanly overnight (966 segments, good quality)
  • Audio originals — moved from external SSD to NAS at synology:/volume1/baseworks/research/conferences/2026-06-brnet/audio/
  • Transcript index — 02-areas/method-admin/core/science-docs/conferences/BRNet-2026-transcripts/index.md with quality ratings and re-transcription notes
  • Session context doc — fully updated at 02-areas/website/communications/2026-06-brnet-session-context.md
  • Asia’s inbox — updated with review request and approach options

What needs your decision before drafting begins:

  1. Read the post approach options (Section 11 of the context doc) — four options outlined; recommendation is A or A+C hybrid (anchor on assessment gap, include residential scientist framing at full length)
  2. Confirm approach with Asia — she has her own lecture notes for each talk that will significantly enrich the field observations section; the speaker-by-speaker content should wait for her input
  3. asia-talking.MOV 02:26–05:08 — Whisper lost the last ~2:40 of your video to Welsh hallucination; fill in from memory or note it as unrecoverable

Two things to read before the draft:

  • Asia’s abstract: 02-areas/method-admin/core/science-docs/conferences/BRNet 2026 Abstract.md
  • Conference landscape doc: 02-areas/method-admin/core/science-docs/conferences/BRNet 2026 Conference Landscape.md

No rush — nothing else needs doing until you and Asia agree on the approach.

2026-06-17

Section titled “2026-06-17”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-17

  • Claude Code updated: 2.1.178 (Claude Code) → 2.1.179 (Claude Code)
  • baseworks-agents system packages: 3 packages updated
  • baseworks-n8n system packages: 3 packages updated
  • n8n updated: 2.26.3 → 2.26.3 (health check: passed)
  • PostgreSQL updated: 16.14 → 16.14 (health check: passed)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-17 | 1315MB | OK | | baseworks.com | Weekly | 2026-06-14 | DB=553MB, Files=149MB | OK | | practice | Weekly | 2026-06-14 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-06-14 | DB=29MB, Files=19MB | OK |

Updates applied: 5

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-16

Section titled “2026-06-16”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-16

  • Claude Code updated: 2.1.177 (Claude Code) → 2.1.178 (Claude Code)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-16 | 1315MB | OK | | baseworks.com | Weekly | 2026-06-14 | DB=553MB, Files=149MB | OK | | practice | Weekly | 2026-06-14 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-06-14 | DB=29MB, Files=19MB | OK |

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-15

Section titled “2026-06-15”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-15

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-15 | 1315MB | OK | | baseworks.com | Weekly | 2026-06-14 | DB=553MB, Files=149MB | OK | | practice | Weekly | 2026-06-14 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-06-14 | DB=29MB, Files=19MB | OK |

Updates applied: None

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-14

Section titled “2026-06-14”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-14

  • n8n updated: 2.26.3 → 2.26.3 (health check: passed)
  • FileBrowser — UPDATE NEEDS ATTENTION: health=starting

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-14 | 1315MB | OK | | baseworks.com | Weekly | 2026-06-07 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-06-07 | DB=499MB, Files=184MB | OK | | crm | Weekly | 2026-06-07 | DB=29MB, Files=19MB | OK |

Needs your attention:

  • Warning: FileBrowser update may have failed — health: starting

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

[ ] 2026-06-13 11:00 ET | n8n: Review migration plan to 1.x stable and schedule execution

Section titled “[ ] 2026-06-13 11:00 ET | n8n: Review migration plan to 1.x stable and schedule execution”

Added by Claude Code on Patrick’s MacBook Pro

Full migration plan is at docs/N8N-STABLE-MIGRATION-PLAN.md in the baseworks-changelog repo.

Context: baseworks-n8n is running the 2.x beta track (2.26.3). All 11 workflows use only core nodes — no 2.x-specific features. The plan covers: pre-migration export, credential documentation, DB backup + volume swap, 1.x install, re-import, rollback procedure, and cleanup.

Action needed: Read the plan, pick a maintenance window, and do it with Claude Code. Estimated time: 45–60 min including testing.

No urgency — 2.x is stable and update-check.py will notify via Slack if anything new drops.

2026-06-13

Section titled “2026-06-13”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-13

  • Claude Code updated: 2.1.174 (Claude Code) → 2.1.177 (Claude Code)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-13 | 1294MB | OK | | baseworks.com | Weekly | 2026-06-07 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-06-07 | DB=499MB, Files=184MB | OK | | crm | Weekly | 2026-06-07 | DB=29MB, Files=19MB | OK |

Needs your attention:

  • Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-12

Section titled “2026-06-12”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-12

  • Claude Code updated: 2.1.172 (Claude Code) → 2.1.174 (Claude Code)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-12 | 1294MB | OK | | baseworks.com | Weekly | 2026-06-07 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-06-07 | DB=499MB, Files=184MB | OK | | crm | Weekly | 2026-06-07 | DB=29MB, Files=19MB | OK |

Needs your attention:

  • Warning: n8n cannot SSH to baseworks-agents — vault capture pipeline is broken. Check SSH key at /opt/n8n-ssh/ on baseworks-n8n

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-11

Section titled “2026-06-11”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-11

  • Claude Code updated: 2.1.170 (Claude Code) → 2.1.172 (Claude Code)
  • baseworks-n8n system packages: 8 packages updated
  • n8n updated: 2.10.3 → 2.10.3 (health check: passed)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-11 | 1313MB | OK | | baseworks.com | Weekly | 2026-06-07 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-06-07 | DB=499MB, Files=184MB | OK | | crm | Weekly | 2026-06-07 | DB=29MB, Files=19MB | OK |

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-10

Section titled “2026-06-10”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-10

  • Claude Code updated: 2.1.169 (Claude Code) → 2.1.170 (Claude Code)
  • baseworks-n8n system packages: 1 packages updated
  • n8n updated: 2.10.3 → 2.10.3 (health check: passed)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-10 | 1313MB | OK | | baseworks.com | Weekly | 2026-06-07 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-06-07 | DB=499MB, Files=184MB | OK | | crm | Weekly | 2026-06-07 | DB=29MB, Files=19MB | OK |

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-09

Section titled “2026-06-09”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-09

  • Claude Code updated: 2.1.168 (Claude Code) → 2.1.169 (Claude Code)
  • b2 CLI updated: 4.7.0 2.12.0 → 4.7.1 2.12.0
  • baseworks-agents system packages: 15 packages updated
  • baseworks-n8n system packages: 15 packages updated

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-09 | 1313MB | OK | | baseworks.com | Weekly | 2026-06-07 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-06-07 | DB=499MB, Files=184MB | OK | | crm | Weekly | 2026-06-07 | DB=29MB, Files=19MB | OK |

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-08

Section titled “2026-06-08”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-08

  • FileBrowser — UPDATE NEEDS ATTENTION: health=starting

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-08 | 1313MB | OK | | baseworks.com | Weekly | 2026-06-07 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-06-07 | DB=499MB, Files=184MB | OK | | crm | Weekly | 2026-06-07 | DB=29MB, Files=19MB | OK |

Needs your attention:

  • Warning: FileBrowser update may have failed — health: starting

Updates applied: None

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-07

Section titled “2026-06-07”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-07

  • Claude Code updated: 2.1.167 (Claude Code) → 2.1.168 (Claude Code)
  • FileBrowser — UPDATE NEEDS ATTENTION: health=starting

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-07 | 1313MB | OK | | baseworks.com | Weekly | 2026-05-31 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-05-31 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-05-31 | DB=18MB, Files=19MB | OK |

Needs your attention:

  • Warning: FileBrowser update may have failed — health: starting

Updates applied: 1

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-06

Section titled “2026-06-06”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-06

  • Claude Code updated: 2.1.163 (Claude Code) → 2.1.167 (Claude Code)
  • baseworks-agents system packages: 1 packages updated
  • baseworks-n8n system packages: 1 packages updated
  • n8n updated: 2.10.3 → 2.10.3 (health check: passed)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-06 | 1313MB | OK | | baseworks.com | Weekly | 2026-05-31 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-05-31 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-05-31 | DB=18MB, Files=19MB | OK |

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-05

Section titled “2026-06-05”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-05

  • Claude Code updated: 2.1.162 (Claude Code) → 2.1.163 (Claude Code)
  • baseworks-agents system packages: 4 packages updated
  • baseworks-n8n system packages: 2 packages updated
  • n8n updated: 2.10.3 → 2.10.3 (health check: passed)
  • FileBrowser — UPDATE NEEDS ATTENTION: health=starting

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-05 | 1313MB | OK | | baseworks.com | Weekly | 2026-05-31 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-05-31 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-05-31 | DB=18MB, Files=19MB | OK |

Needs your attention:

  • Warning: FileBrowser update may have failed — health: starting

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-04

Section titled “2026-06-04”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-04

  • Claude Code updated: 2.1.161 (Claude Code) → 2.1.162 (Claude Code)
  • baseworks-agents system packages: 6 packages updated
  • baseworks-n8n system packages: 5 packages updated
  • FileBrowser — UPDATE NEEDS ATTENTION: health=starting

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-04 | 1308MB | OK | | baseworks.com | Weekly | 2026-05-31 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-05-31 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-05-31 | DB=18MB, Files=19MB | OK |

Needs your attention:

  • Warning: FileBrowser update may have failed — health: starting

Updates applied: 3

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-03

Section titled “2026-06-03”

[ ] 03:45 ET | Daily Infrastructure Update Report

Section titled “[ ] 03:45 ET | Daily Infrastructure Update Report”

Added automatically by daily-infra-updates.sh on baseworks-agents VPS

Date: 2026-06-03

  • Claude Code updated: 2.1.160 (Claude Code) → 2.1.161 (Claude Code)
  • baseworks-agents system packages: 8 packages updated
  • baseworks-n8n system packages: 7 packages updated
  • n8n updated: 2.10.3 → 2.10.3 (health check: passed)

Backup health:

SiteScheduleLast SuccessSizeStatus

| n8n | Daily | 2026-06-03 | 1308MB | OK | | baseworks.com | Weekly | 2026-05-31 | DB=552MB, Files=149MB | OK | | practice | Weekly | 2026-05-31 | DB=500MB, Files=184MB | OK | | crm | Weekly | 2026-05-31 | DB=18MB, Files=19MB | OK |

Updates applied: 4

Requested action: Review any items flagged above. Auto-updates have already been applied and verified.

2026-06-02

Section titled “2026-06-02”

[ ] 12:00 ET | /create-campaign skill: LinkedIn article prescription — possible update needed

Section titled “[ ] 12:00 ET | /create-campaign skill: LinkedIn article prescription — possible update needed”

Added by Claude Code on Asia’s Mac Mini

Document: _campaign-creation-guidelines · SKILL Requested action: Decision needed — update skill prescription or leave as-is Summary:

  • The skill prescribes that the LinkedIn article should be the opening of the baseworks.com article with a “read more” link
  • For the Triple Irony campaign, Asia used a different approach: a compressed overview of the full argument — closer to an abstract than an excerpt — followed by a link to the full article
  • The Triple Irony article’s thesis lands in the second half, after the Robb/Ballard analysis; an opening cut would give the LinkedIn reader setup with no payoff and no sense of what the article is actually arguing
  • The abstract approach gives the reader the shape of the whole argument — including where it lands — without developing it fully; the full article on baseworks.com delivers the evidence and nuance
  • Both approaches point to the baseworks.com article; the difference is how the argument is represented to earn the click: beginning of the narrative vs. compressed arc of the whole

Open question: Should the skill prescription be updated to offer both options — opening cut when the article opens on its thesis, abstract/overview when the thesis is structurally buried — with the trade-offs noted?

2026-05-29

Section titled “2026-05-29”

[ ] Triple Irony Campaign — Newsletter, Instagram & Facebook drafts ready for your input

Section titled “[ ] Triple Irony Campaign — Newsletter, Instagram & Facebook drafts ready for your input”

Added by Claude Code on Asia’s Mac Mini

Document: 2026-05-triple-irony Requested action: Read through and give input if any

Summary:

  • Asia drafted the full newsletter text for the Triple Irony campaign
  • Instagram and Facebook copy are also drafted
  • Instagram includes a section called “Instagram — Carousel Pull Quote Candidates” — Asia’s idea is to use one carousel image as a pull quote from the article
  • No structural decisions needed from you; just read and flag anything you’d change

2026-05-28

Section titled “2026-05-28”

[ ] 14:49 ET | Marta Stothers — Ignition assignment feedback — review before Asia responds

Section titled “[ ] 14:49 ET | Marta Stothers — Ignition assignment feedback — review before Asia responds”

Added by Claude Code on Asia’s Mac Mini

Assignment: marta-stothers-signition-260526 Requested action: Read before Asia sends her response. Asia plans to reply by email directly to Marta. Sensitive situation — please confirm you’re okay with the draft below before she sends.

Background: Marta has a pattern of defensiveness when receiving feedback. She appears to have some kind of neurological condition (fMRI-confirmed, per her own statement), but she signed her waiver without disclosing it and has not provided any details. Observationally her performance is within the normal range. The concern is that she may be using the undisclosed condition as a rhetorical shield rather than as practical context for her training.

The comment she made (Ignition assignment, “Most interesting” field):

Because segment 6.6 is a bilateral form, perhaps I can more fully explain why my body needs tactile and/or visual cues for unilateral movements. This is not a “preference”, like my favourite ice cream. It is hard-wired, fMRI-confirmed, neurophysiological fact. I have heard your strong opinions about “preferences” and learning styles”, so will dissent without disagrement.

Asia’s draft response (ready to send pending your read):

Hi Marta,

I’d like to respond to your comment in the Ignition assignment, because I think there may be a misunderstanding I want to clarify.

We don’t hold the position that everyone’s relationship to sensory cues is simply a matter of preference. People come with different nervous systems, different histories, and different starting points — and that individual variability is central to the Baseworks method.

What we do say is that the goal of this practice is to develop capacity in areas that are currently less available. For most people, that means going through phases where things feel uncertain or imprecise, if not cognitively uncomfortable — not because we want to make things harder, but because that sensory uncertainty is where the learning actually happens. Using tactile or visual cues is absolutely fine as a learning tool. But developing the ability to work without them, over time, is part of what we’re training. You’re not expected to do that on day one, or even in month six.

You have stronger-than-average body awareness, which is genuinely an asset here. The fact that you can notice and name what becomes harder without external reference points is itself useful information. We’re not asking anyone to perform tasks perfectly. What we are asking is to stay with the process, which for most people working at real capacity edges takes a long time before things shift.

If you haven’t read “The Woman Who Changed Her Brain” by Barbara Arrowsmith-Young, I’d highly recommend it. It describes many cases of focused training at capacity bottlenecks leading to real change, including in people who had been told their limitations were neurologically fixed.

We understand our approach isn’t for everyone, and there’s no pressure to continue if it doesn’t feel right. But we wanted you to have a clear picture of what we’re working toward together.

[ ] 2026-05-19 20:27 ET | Policy draft: Course Participation and Platform Integrity — review needed

Section titled “[ ] 2026-05-19 20:27 ET | Policy draft: Course Participation and Platform Integrity — review needed”

Added by Claude Code on Patrick’s Mac

Document: course-participation-integrity Requested action: Review the draft and confirm or revise. One open question requires your decision before this can go live.

Summary:

  • New policy section covering: completion requirements (lessons must be watched in full, AI-generated feedback is not valid), supportive framing (participants encouraged to reach out about schedule constraints), and the platform’s right to reset progress or revoke access
  • Refund policy confirmed: No refund when access is revoked for integrity violations
  • Prompted by the Noemi Normandin case (May 2026) — full record at index

Two things need to be done once you’ve reviewed and confirmed the wording:

  1. FAQ on the Spring 2026 study group page (WP ID 46997) — add one or two new FAQ questions covering completion requirements and the integrity policy. Draft proposed question is in the policy doc. Update via Elementor directly (not Termageddon).
  2. Terms and Conditions (WP ID 4910) — add the “Platform Access” section to the English T&Cs via Termageddon. French version (WP ID 48334) can be updated via WP-CLI directly.

[ ] 2026-05-19 14:15 ET | Session 7 — forum post, group post, and closing email template ready

Section titled “[ ] 2026-05-19 14:15 ET | Session 7 — forum post, group post, and closing email template ready”

Added by Claude Code on Patrick’s Mac

All three tasks from today’s session are complete:

  1. Forum topic (topic ID 22269): Session 7 summary posted to the Spring 2026 Study Group forum. Content was initially corrupted with PHP code — fixed. Tags, post_parent, and activity feed entry all verified clean.
  2. Group activity post (activity ID 436): English-only announcement posted to the group feed, matching the Session 5/6 pattern. Title: “Session 7 Summary: Full Practice and What Comes Next.”
  3. Closing email template: spring-2026-session-7-summary.md saved to email-templates/study-groups/. Schedule for send 2026-05-20 in FluentCRM to the Spring 2026 cohort list.

Action needed: Schedule the email in FluentCRM for May 20.

[ ] 2026-05-18 | Session 7 Summary — Asia’s edits complete, booking paragraph needs discussion

Section titled “[ ] 2026-05-18 | Session 7 Summary — Asia’s edits complete, booking paragraph needs discussion”

Added by Claude Code on Asia’s Mac Mini

Asia has finished her editorial pass on the Session 7 summary:

02-areas/educational-programs/study-groups/2026 (Spring) Study Group Montreal/session-summaries/session-7-summary-en.md

The summary is ready to use, but there is one open item before it goes to participants: the paragraph about practice session booking (in the “Continuing from Here” section) is currently marked in red in the file. Asia flagged it because there are logistics to confirm — specifically around how and when participants will be notified that booking is now available on their dashboard. Please coordinate with Asia on the correct wording and timing before that paragraph is finalized or the summary is posted.

[ ] 2026-05-13 | Two-Layer Framework + Mehling read + proposed interview

Section titled “[ ] 2026-05-13 | Two-Layer Framework + Mehling read + proposed interview”

Added by Claude Code on Asia’s Mac Mini

Asia and Claude have drafted a framework note at the-two-layers-framework that distinguishes two layers in Baseworks: (1) the sensorimotor science layer — specific trainable capacities with neural substrates — and (2) the philosophical/contemplative layer — what sustained commitment to any disciplined practice produces in a person. The note explains why these layers create communication friction and provides a content/communication strategy for when to use which.

Two things for you to do:

1. Read Mehling 2011 (30 min) The paper is at 03-resources/science papers/Mehling_2011_phenomenology of body awareness.pdf — specifically pages 3–6 (“Practitioners’ Views of Body Awareness”) and Table 1. Asia distances from this paper in the science layer, but the phenomenological findings map closely onto your philosophical layer. The practitioners Mehling interviewed (Feldenkrais, Alexander, yoga, MBSR, Somatic Experiencing) converged on: body awareness is inseparable from self-awareness; practice resumes an arrested embodiment process; the goal is integration of mind, body, and life context. Read it and note where your view aligns and where it diverges — this will sharpen your articulation of Layer 2.

2. Proposed interview with your Claude Once you’ve read the framework note and Mehling, have your Claude conduct a structured interview with you to articulate Layer 2 in your own words. The five starting questions are in the last section of the-two-layers-framework. The goal is a written account of your philosophical layer that doesn’t default to yoga vocabulary, wellness vocabulary, or borrowed neuroscience. That written account would then inform the press page lineage section (D13), the Baseworks Transmission framing, and any future philosophical writing.

Completed

Section titled “Completed”
2026-06-04
2026-06-04
2026-06-01
2026-05-13
2026-05-13
2026-05-13
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-05-05
2026-04-24
2026-04-09
2026-03-25
  • Blog Feedback Workflow Optimization — responded with tooling fix: AI Generation Warning in unified guide, WRITING-PROCESS.md, updated skills. Asia’s inbox updated with full explanation.
  • Voice guide v1.9 — Ksenia’s “Baseworks Practice” lowercase expansion confirmed by Patrick
  • Blog Post Feedback — “From Three Forms to Twenty-One” — all 10 points reviewed and applied
2026-03-19
  • baseworks-changelog repo — branch divergence merged, master deleted, all repos standardized on main
2026-03-17
2026-03-13
2026-03-12
2026-03-11
2026-03-10
2026-03-09
2026-03-05