Directions Brain

log

15 min read

Log

Chronological, append-only operations log. One H2 per entry.

Entry format (greppable):

## [YYYY-MM-DD] <op> | <title>

Where <op> is one of: ingest, query, lint, refactor. Body (under each H2) is freeform: brief notes, pages touched, links to relevant [[wiki-pages]].

[2026-05-09] ingest | meeting: 2026-05-06-brain-os-strategy-brainstorm

[2026-05-09] refactor | introduce wiki/action-items.md

  • reason: User wants action items monitored across meetings, not just buried inside each meeting page.
  • touched: CLAUDE.md (Section A invariants 4+5 clarified to exempt operational root files; Section B directory map and narrative; Section F new step 8 for action-items maintenance, log append renumbered to step 9; Section I lint checks added), wiki/action-items.md (created), README.md (layout tree + new “Track action items” subsection).
  • notes: Single rolling page architecture chosen over per-item files (lighter ceremony, easier scan). Backfilled 5 open items from 2026-05-06-brain-os-strategy-brainstorm. wiki/action-items.md is the third operational root file alongside index.md and log.md — it has no frontmatter and is excluded from index.md.

[2026-05-09] refactor | document URL-fetch acquisition workflow for articles

  • reason: User asked how to add online sources for competitor research (starting with glean). Schema previously assumed raw/articles/ files were user-dropped only; needed an LLM-driven acquisition path.
  • touched: CLAUDE.md (Section A invariant 1 carve-out for new article files; Section G expanded into G.0 acquisition + G.1 ingest steps; provenance block format defined; log entry now includes url: line for traceability), README.md (“Add an article” section rewritten to lead with the URL workflow and keep manual drop as fallback).
  • notes: Default acquisition uses axcli chrome navigate/read/close so the user’s authenticated browser handles paywalls and logins; raw markdown is captured with no LLM summarization in the middle. The ONLY content the LLM may write into raw/ is a 4-line provenance block (Source URL + Captured date + Captured by); files remain immutable thereafter.

[2026-05-27] ingest | meeting: 2026-05-27-directions-vertical-pivot-and-prediction-markets

[2026-05-27] refactor | rename hari → ari-leshno (identity collision from prior ingest)

  • reason: ASR mis-rendering surfaced when ingesting raw/meetings/Saar<>Leshno (2026-05-19 18.00).txt. The 2026-05-27 ingest above had captured the same person as a hari stub from spoken Hebrew “הארי” (the name “ארי” with a definite article). Per Section J dedup (alias match against the new transcript’s “Ari Leshno”), merge into a single page.
  • touched: wiki/people/ari-leshno.md (created — combines original hari.md content with 2026-05-19 enrichment), wiki/people/hari.md (deleted), wiki/meetings/2026-05-27-directions-vertical-pivot-and-prediction-markets.md (3 wikilinks updated), wiki/topics/vertical-use-case-led-brain.md (2 wikilinks updated), wiki/people/saar-arbel.md (2 wikilinks updated), wiki/index.md (People entry renamed)
  • notes: New aliases on [[ari-leshno]] retain “Hari” / “הארי” so future ASR mis-renderings match by alias per Section J. All original Hari content (clinic-operations anchor, vertical-Brain anecdote) is preserved on the new page; 2026-05-19 details (Sheba role, glaucoma pitch, MVP, sizing, FDA precedent) are added.

[2026-05-27] ingest | meeting: 2026-05-19-saar-leshno-glaucoma-data-tracking

[2026-05-30] ingest | source: 2026-05-01-entree-capital-enterprise-ai-spend-map

  • source: raw/articles/2026-05-01-entree-capital-enterprise-ai-spend-map.pdf (PDF, 13 slides + Sources & footnotes; supplied directly by user — not web-captured. Originally named Enterprise AI Spend Map.pdf; renamed to convention later the same day — see refactor entry below.)
  • url: (not applicable — PDF supplied directly; no provenance block in raw)
  • new: 2026-05-01-entree-capital-enterprise-ai-spend-map, entree-capital, openai, anthropic, vertical-ai-tam, slm-default-and-fine-tuning, foundation-labs-monetization-shift
  • updated: vertical-use-case-led-brain (source_count 2→3; new Evidence row citing Bessemer +400% YoY, 752B/2029, Anthropic $70B/2028; Related extended with foundation-labs-monetization-shift), clinical-data-portability (source_count 1→2; new Evidence row on healthcare as 2026-27 vertical breakout; Related extended with vertical-ai-tam), cursor (source_count 2→3; Mentioned-in row added), glean (source_count 1→2; Mentioned-in row added), sierra (source_count 1→2; Mentioned-in row added), wiki/index.md (3 new Companies, 1 new Source, 3 new Topics)
  • notes: First VC-published source in the wiki. Established new tag pattern investor-thesis to flag VC-published reports as advocacy-shaped narrative rather than neutral analysis (applied to source page + entree-capital + the three new topic pages where relevant). Date 2026-05-01 chosen over today (2026-05-30) per user — PDF declares “May 2026” only, no specific day. Entity-stub scope: Section F step 4 (“create stub for each referenced entity”) was applied selectively — created stubs only for openai and anthropic because they are the load-bearing subjects of slide 5’s monetization-divergence claim. Other entities mentioned only as exemplars (Microsoft / Salesforce / ServiceNow / Google / Harvey / Bessemer / Menlo / a16z / Gartner) were not stubbed; future sources can promote them when needed. No action items: market-overview source, not a meeting; no follow-ups generated. Quality flag for entree-capital: stated thesis aligns suspiciously well with the vertical-use-case-led-brain direction the team had already chosen — read with the same skepticism applied to any VC’s portfolio-aligned market map.

[2026-05-30] refactor | rename raw PDF to YYYY-MM-DD-publisher-slug convention

  • reason: User requested the raw filename match the YYYY-MM-DD-publisher-slug convention (Section C). Original drop was Enterprise AI Spend Map.pdf with no date or publisher prefix.
  • touched: raw/articles/Enterprise AI Spend Map.pdf → raw/articles/2026-05-01-entree-capital-enterprise-ai-spend-map.pdf (renamed); wiki/sources/2026-05-01-entree-capital-enterprise-ai-spend-map.md (Source: line + Note paragraph updated); wiki/log.md (preceding ingest entry’s source: line annotated with rename history).
  • notes: Section A invariant 1 was overridden for this rename — the invariant says NEVER modify, delete, or rename existing files under raw/. User explicitly asked for the rename, treated as a one-time exception. If this should be the new default, CLAUDE.md Section A invariant 1 needs to be relaxed to allow agent-driven rename-to-convention (probably with a tighter rule: “may rename to match Section C convention; may not modify content”). Flagging here so future-Claude doesn’t quietly normalize the rule.

[2026-05-30] ingest | source: alon-huri LinkedIn — pilot ingest (3 posts) + latest-15 sweep (15 posts total)

  • source: raw/articles/2026-05-29-alonhuri-linkedin-creator-arbitrage.md, raw/articles/2026-05-27-alonhuri-linkedin-soldiers-ptsd-update.md, raw/articles/2026-05-22-alonhuri-linkedin-reddit-personal-brand.md, raw/articles/2026-05-16-alonhuri-linkedin-ai-native-growth-hacking.md, raw/articles/2026-05-09-alonhuri-linkedin-ai-native-company.md, raw/articles/2026-03-06-alonhuri-linkedin-saas-is-dead-ai-native-agency.md, raw/articles/2026-02-27-alonhuri-linkedin-reddit-experiment-results.md, raw/articles/2026-02-20-alonhuri-linkedin-ads-in-ai-chats.md, raw/articles/2026-02-06-alonhuri-linkedin-bootstrap-vs-astrap.md, raw/articles/2026-01-30-alonhuri-linkedin-full-stack-ai.md, raw/articles/2026-01-23-alonhuri-linkedin-vibe-coding-2.md, raw/articles/2026-01-16-alonhuri-linkedin-soldiers-ptsd-original.md, raw/articles/2026-01-09-alonhuri-linkedin-vibe-acting.md, raw/articles/2026-01-02-alonhuri-linkedin-100-ideation-hacks.md, raw/articles/2025-12-26-alonhuri-linkedin-apple-openai-merger.md. 15 raw files, all Hebrew, captured via axcli chrome from user’s authenticated session. Posts 1, 4, 5 captured directly from the user-supplied LinkedIn URLs in the pilot phase; posts 2, 3, 16–25 captured from the LinkedIn activity feed (linkedin.com/in/alonhuri/recent-activity/all/) using axcli chrome click to trigger lazy-loading and sed to slice the resulting page-capture by feed-post index.
  • url: per-post LinkedIn share URLs available for pilot posts (in their respective source-page frontmatter); for the activity-feed sweep, individual share URLs were not exposed in the accessibility tree — provenance points to the feed URL with #feed-post-N anchor for traceability.
  • new (people): alon-huri — first thought-leader entry; weekly Friday LinkedIn poster.
  • new (companies): team8 — second VC entry after entree-capital; both tagged investor-thesis.
  • new (sources, 5 wiki source pages out of 15 raw): 2026-05-09-alonhuri-linkedin-ai-native-company, 2026-05-16-alonhuri-linkedin-ai-native-growth-hacking, 2026-03-06-alonhuri-linkedin-saas-is-dead-ai-native-agency, 2026-01-30-alonhuri-linkedin-full-stack-ai, 2026-01-09-alonhuri-linkedin-vibe-acting.
  • new (topics): full-stack-ai-vertical-services — synthesis topic anchored by the AI-Native-Agency + Full-Stack-AI source pair; reads as the most aggressive cut of vertical-use-case-led-brain.
  • updated: context-os-brain (source_count 2→3; new Evidence row from ai-native-company post), agent-native-go-to-market (source_count 3→5; +2 Evidence rows from growth-hacking + vibe-acting posts), vertical-use-case-led-brain (source_count 3→5; +2 Evidence rows from saas-is-dead + full-stack-ai posts; Related extended with full-stack-ai-vertical-services), wiki/index.md (1 People row, 1 Companies row, 5 Sources rows, 1 Topics row), wiki/log.md (this entry).
  • Curation gate (load-bearing for ideation? validate / contradict / extend a wiki topic OR open a new vertical/wedge angle?): 5 of 15 posts passed → wiki source page. 10 of 15 stayed raw-only with the rationale documented inline on alon-huri’s ## Notes — non-wiki posts (raw only) section. Load-bearing breakdown: ai-native-company (verbatim with context-os-brain), ai-native-growth-hacking (extends agent-native-go-to-market), saas-is-dead-ai-native-agency + full-stack-ai (anchor new topic full-stack-ai-vertical-services as most-aggressive cut of vertical-use-case-led-brain), vibe-acting (sharpens agent-native-go-to-market with action-layer thesis). Skip rationale: tactical playbooks (creator-arbitrage, reddit-personal-brand, reddit-experiment-results), personal/social initiative (soldiers-ptsd × 2 — important to Alon, not to ideation), opinion / speculation (ads-in-ai-chats, vibe-coding-2 / ASI, apple-openai-merger), founder-finance philosophy (bootstrap-vs-astrap — relevant only when team raises), methodology overlap with team’s own (100-ideation-hacks).
  • Skepticism flag. alon-huri is Managing Partner at team8. Five of his five wiki-promoted posts agree very strongly with the team’s pre-existing strategic direction. That’s more suspicious, not less — Alon is plausibly pitching narratives his fund’s portfolio plays into. Each source page carries this caveat inline; future-Claude should not treat his agreement as confirmatory without cross-checking against non-VC voices.
  • notes: No action items generated — these are external thought-leadership posts, not meetings; no follow-ups owned by team members. Open question worth raising at the next directions sync (flagged on full-stack-ai-vertical-services): of Alon’s 15 named regulated-profession verticals (legal, real-estate, finance, healthcare, education, marketing — see 2026-03-06-alonhuri-linkedin-saas-is-dead-ai-native-agency), only healthcare (ari-leshno / clinical-data-portability) has been concretely evaluated by the team; the other 12 remain unfiltered. Filename convention. Raw files use YYYY-MM-DD-alonhuri-linkedin-<topic-slug>.md per user request — date is post-creation date (approximated to nearest Friday for the activity-feed sweep, since LinkedIn shows only relative time like “3mo”). Source-page slugs match the raw filenames for 1:1 navigation. Memory updated. Project memory at .claude/projects/.../memory/brain-purpose-startup-ideation.md already covered the VC-perspective input pattern from the entree-capital ingest; no additional memory needed for this Alon ingest.

[2026-05-31] ingest | meeting: 2026-05-31-directions-connect-businesses-and-brain-scaling

  • source: raw/meetings/Directions starting the week (2026-05-31 20.00).txt (Hebrew ASR transcript, ~90 min; opening ~5 min football championship + closing ~10 min logistics + assorted personal asides excluded from summary)
  • new: 2026-05-31-directions-connect-businesses-and-brain-scaling, connect-businesses-multi-vertical-api (NEW topic), plaid, snaptrade, papaya-global, wolt, rami-levy, victory, osher-ad, render-ai (8 new companies)
  • updated: saar-arbel (source_count 3→4), guy-barkat (source_count 3→4), nizan-shifman (source_count 2→3), tomer-shalom (source_count 1→2), alon-huri (source_count 5→6; new mentioned-in row for the Saar Claude-project ideation use), etoro (source_count 2→3; partnership pipeline + NoteTaker policy), wonderful (source_count 2→3; ARR + FDE-debate update), sierra (source_count 2→3; ~$1B raise per Nizan), context-os-brain (source_count 3→4; agent-harness + difficulty-as-moat + qualified-source-of-truth additions; updated open questions), vertical-use-case-led-brain (source_count 5→6; vertical-determines-data-model evidence; sibling non-Brain directions called out), prediction-markets-regulatory-play (source_count 1→2; triage-gate escalation evidence row), wiki/index.md (8 new Companies, 1 new Topic, 1 new Meeting), wiki/action-items.md (1 prior item closed — Sunday-evening sync was today; 1 prior item moved Open → In progress — Toto chairman follow-up; 6 new open items + 1 progress note across 4 prior items)
  • notes: NEW direction surfaced. guy-barkat introduced a third active exploratory direction — connect-businesses-multi-vertical-api — alongside vertical-use-case-led-brain and prediction-markets-regulatory-play. Crucially this is a non-Brain direction; the team now holds three open lenses without a process for converging. Brain reframe. Same meeting deepened the Brain conversation: Guy’s strongest scaling-difficulty case yet (partial data is worse than no data; conflict resolution unsolved; need an “agent harness”) flipped mid-conversation into a moat argument (the difficulty itself prevents incumbents from building it in-house). Saar reinforced vertical-as-data-model. Nizan defended Holy-Grail framing and reported “I’ve cracked AI” via daily Brain use. Source-of-truth debate resolved as “qualified yes when paired with conflict-surfacing UX.” Adoption gap. guy-barkat still unattached to the Brain; provisioning + pair-install scheduled for this week. etoro’s default opt-out on Monday NoteTaker is now documented as the policy gate. No decision pages. Two-vertical-direction ramping + Brain harness work are still exploratory; no commitments crossed the decision-slug threshold. Note on Yoni. The new meeting references “our CEO Yoni” at etoro (Yoni Assia) — different person from the existing yoni page (Monday senior exec / pitch target). No new Yoni page created since the eToro Yoni was only mentioned in passing; a future ingest with substantive Yoni-Assia content should disambiguate via Section C collision-suffix (yoni-assia vs yoni-monday rename).

[2026-06-04] ingest | meeting: 2026-06-04-directions-matan-construction

  • source: raw/meetings/Directions w_ Matan (construction) (2026-06-04 09.00).txt (Hebrew ASR transcript, ~31 min; expert interview format — Matan was on the road, so the call was kept tight)
  • new: 2026-06-04-directions-matan-construction, matan-amram, solel-boneh, akrstein, construction-project-management
  • updated: nizan-shifman (source_count 4→5; new mentioned-in entry), guy-barkat (source_count 5→6; new mentioned-in entry), wiki/index.md (1 Person, 2 Companies, 1 Meeting, 1 Topic added), wiki/action-items.md (1 item closed to Done — construction intro was Matan himself; 3 new Open items for follow-up contacts)
  • notes: First construction-vertical expert interview. Key finding: internal project management at even the largest Israeli GCs is entirely offline Excel + WhatsApp — no live visibility. Two emerging angles: (1) “context OS for construction” — Nizan’s thesis that project-state visibility is the root problem; (2) the subcontractor/labor-deployment layer — Guy’s thesis that this is an equally underserved, entirely un-tooled segment. No decision pages created — still mapping the space. Entity note: akrstein has multiple ASR spellings in the transcript (אקרשטיין / הקירשטיין / האקלשטיין); canonical slug is akrstein with aliases covering variants.

[2026-06-02] ingest | meeting: 2026-06-02-directions-account-management-vertical

  • source: raw/meetings/Directions brainstorm (2026-06-02 20.30).txt (Hebrew ASR transcript, ~55 min; opening ~3 min personal chitchat dropped)
  • new: 2026-06-02-directions-account-management-vertical, daniela, ofer-mixpanel, nir-goldstein, mixpanel, gong, account-management-vertical
  • updated: nizan-shifman (source_count 3→4), guy-barkat (source_count 4→5), saar-arbel (source_count 4→5), harmony (source_count 1→2), vertical-use-case-led-brain (source_count 6→7; “which vertical” open question resolved to AM working answer), context-os-brain (source_count 4→5; AM architecture note + agentic CRM debate), wiki/index.md (3 People, 2 Companies, 1 Meeting, 1 Topic added), wiki/action-items.md (2 items closed to Done; 4 new Open items)
  • notes: The team’s “which vertical” open question has a working answer for the first time: Account Management / Customer Success. No formal decision page created — still pre-commitment, with the Daniela pilot as the next validation gate. Key new entities: daniela (Harmony AM, pilot subject), nir-goldstein (VC framing: grow book-of-business coverage), ofer-mixpanel (AM benchmark + feedback target), gong (revenue-intelligence adjacent). Architecture debate (integrate CRMs via MCP vs. build AM-native CRM) is live and open — no decision taken.

[2026-05-31] lint | post-ingest checklist

  • counts: 71 wiki files (3 operational root + 68 slugged content). Index references 69 distinct slugs. Frontmatter present + complete on all 68 content pages. No frontmatter wikilinks. No source_count:0 orphans. No status:active pages older than 90 days. No Open/Done duplicates in action-items.md. Action-items.md has all four required H2 sections in order; every Source meeting reference resolves.
  • new flagged + auto-fixed in this run:
  • pre-existing flagged (NOT auto-fixed; out of scope for this lint run):
    • [[pagaya]] referenced from companies/axonius.md, meetings/2026-05-27-directions-vertical-pivot-and-prediction-markets.md, people/guy-barkat.md — no page exists. Pagaya is a real Israeli AI-fintech; intro pipeline reference. Suggested fix: create companies/pagaya.md stub on next refactor.
    • [[maccabi-netanya]] referenced from people/tomer-shalom.md — no page exists. Football club; lower priority. Suggested fix: create stub or unlink.
    • [[decision-slug]] flagged from meetings/2026-05-06-brain-os-strategy-brainstorm.md and meetings/2026-05-27-directions-vertical-pivot-and-prediction-markets.md — false positives; both occurrences are inside <!-- ... --> HTML template comments (template scaffolding from Section E meeting template), not body wikilinks. Lint script doesn’t strip HTML comments. Suggested fix: strip the template-comment lines on next refactor of those meeting pages, OR upgrade the lint regex to skip HTML comments.
    • [[slug]] flagged from index.md — same false-positive pattern; the Decisions section header is <!-- [[slug]] — one-line summary (date + outcome) -->. Same fix options.
  • result: PASS for this ingest (all 3 ingest-introduced issues fixed); 4 pre-existing flags surfaced for future cleanup.

Graph View