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
- source:
raw/meetings/notetaker/2026-05-06-meeting-13-30.json(Hebrew ASR transcript, ~88 min; first ~10 min off-topic chitchat dropped) - new: 2026-05-06-brain-os-strategy-brainstorm, saar-arbel, guy-barkat, nizan-shifman, yoni, tubel, monday, etoro, harmony, glean, sierra, wonderful, cursor, context-os-brain, vitamin-vs-painkiller-framing, top-down-bottom-up-alignment, agent-native-go-to-market
- updated: index.md (populated all six categories from empty)
- notes: first ingest into a fresh wiki — every entity treated as CREATE per Section F step 0. Hebrew names use English-transliteration slugs with Hebrew aliases per repo convention. Two person pages (yoni, tubel) carry
_(unknown — needs source)_for surnames pending future sources. No decision pages created — meeting was exploratory, not commitment-bearing.
[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.mdis the third operational root file alongsideindex.mdandlog.md— it has no frontmatter and is excluded fromindex.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 includesurl: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/closeso 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 intoraw/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
- source:
raw/meetings/notetaker/2026-05-27-directions-05-30.json(Hebrew ASR transcript, ~75 min; first ~4 min off-topic football chitchat dropped) - new: 2026-05-27-directions-vertical-pivot-and-prediction-markets, tomer-shalom, maor-naksh, inbar-markovich, yuval-ovadia, amit-frishberg, shiran-navi,
hari(later merged into ari-leshno — see refactor entry below), notch, alta, winner-toto, polymarket, kalshi, axonius, brm, antara, vertical-use-case-led-brain, prediction-markets-regulatory-play, monday-agents-month - updated: saar-arbel, guy-barkat, nizan-shifman, etoro, monday, wonderful, cursor (source_count +1; meeting back-references), context-os-brain, agent-native-go-to-market, vitamin-vs-painkiller-framing (source_count +1; strategic-direction notes pointing to vertical-use-case-led-brain),
wiki/index.md(12 new entries across People/Companies/Meetings/Topics),wiki/action-items.md(8 new open items; no prior items closed — none of the 2026-05-06 open items were addressed in this sync) - notes: Two main threads in this meeting. (1) guy-barkat surfaced a regulation-grade sports prediction-markets thesis from a Tomer-Shalom + Toto-chairman conversation — captured as exploratory (prediction-markets-regulatory-play); two-thirds of the team is skeptical, gating triage on the upcoming Toto-chairman follow-up. (2) Strategic reframe of the Brain: shift from horizontal context-OS to vertical use-case-led product with the Brain as moat (vertical-use-case-led-brain) — this is the team’s first concrete answer to the prior 2026-05-06 open question of “next two steps beyond Operating System.” No decision pages created — both threads are still exploratory directions, not commitments. Several new pages carry (unknown — needs source) markers for ASR-uncertain names (Tomer’s surname, Maor’s prior employer, Roni’s surname, Toto chairman’s name, Hari’s surname). [Note: the
haripage was retired and merged into ari-leshno in the same-day refactor entry below; mention preserved here for audit-trail accuracy.]
[2026-05-27] refactor | rename hari → ari-leshno (identity collision from prior ingest)
- reason: ASR mis-rendering surfaced when ingesting
raw/meetings/notetaker/2026-05-19-saar-leshno-15-00.json. The 2026-05-27 ingest above had captured the same person as aharistub 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 originalhari.mdcontent 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
- source:
raw/meetings/notetaker/2026-05-19-saar-leshno-15-00.json(Hebrew ASR transcript, ~62 min; first ~6 min off-topic chitchat dropped — football + Karpathy/Anthropic rumor + Google-Meet rant) - new: 2026-05-19-saar-leshno-glaucoma-data-tracking, yael, sheba, zeiss, kameleon, idx, clinical-data-portability
- updated: ari-leshno (source_count 1→2 via the rename refactor + this ingest; full body rewrite with the concrete glaucoma pitch), saar-arbel (source_count 2→3; new mentioned-in entry), guy-barkat (source_count 2→3; new mentioned-in entry), vertical-use-case-led-brain (source_count 1→2; new evidence row + clinical-data-portability added to Related),
wiki/index.md(People + Companies + Meetings + Topics),wiki/action-items.md(2 new open items; no prior items closed) - notes: Ingested out of chronological order — this 2026-05-19 meeting was the actual source of the ari-leshno anecdote in 2026-05-27-directions-vertical-pivot-and-prediction-markets but only digested today. Open question now flagged on vertical-use-case-led-brain: the visual-field-tracking wedge looks closer to a healthcare SaaS than a Brain-shaped product — that judgment should precede any Sheba partnership commitment. New people page yael carries
_(Surname unknown — needs source.)_per Section L. The kameleon page records spelling/identity uncertainty (real corporate identity not yet verified).
[2026-05-30] ingest | source: 2026-05-01-entree-capital-enterprise-ai-spend-map
- source:
raw/articles/vc-articles/2026-05-01-entree-capital-enterprise-ai-spend-map.pdf(PDF, 13 slides + Sources & footnotes; supplied directly by user — not web-captured. Originally namedEnterprise 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-thesisto 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-slugconvention (Section C). Original drop wasEnterprise AI Spend Map.pdfwith no date or publisher prefix. - touched:
raw/articles/Enterprise AI Spend Map.pdf→raw/articles/vc-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.mdSection 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/linkedin-posts/2026-05-29-alonhuri-linkedin-creator-arbitrage.md,raw/articles/linkedin-posts/2026-05-27-alonhuri-linkedin-soldiers-ptsd-update.md,raw/articles/linkedin-posts/2026-05-22-alonhuri-linkedin-reddit-personal-brand.md,raw/articles/linkedin-posts/2026-05-16-alonhuri-linkedin-ai-native-growth-hacking.md,raw/articles/linkedin-posts/2026-05-09-alonhuri-linkedin-ai-native-company.md,raw/articles/linkedin-posts/2026-03-06-alonhuri-linkedin-saas-is-dead-ai-native-agency.md,raw/articles/linkedin-posts/2026-02-27-alonhuri-linkedin-reddit-experiment-results.md,raw/articles/linkedin-posts/2026-02-20-alonhuri-linkedin-ads-in-ai-chats.md,raw/articles/linkedin-posts/2026-02-06-alonhuri-linkedin-bootstrap-vs-astrap.md,raw/articles/linkedin-posts/2026-01-30-alonhuri-linkedin-full-stack-ai.md,raw/articles/linkedin-posts/2026-01-23-alonhuri-linkedin-vibe-coding-2.md,raw/articles/linkedin-posts/2026-01-16-alonhuri-linkedin-soldiers-ptsd-original.md,raw/articles/linkedin-posts/2026-01-09-alonhuri-linkedin-vibe-acting.md,raw/articles/linkedin-posts/2026-01-02-alonhuri-linkedin-100-ideation-hacks.md,raw/articles/linkedin-posts/2025-12-26-alonhuri-linkedin-apple-openai-merger.md. 15 raw files, all Hebrew, captured viaaxcli chromefrom 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/) usingaxcli chrome clickto trigger lazy-loading andsedto 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-Nanchor 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>.mdper 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.mdalready 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/notetaker/2026-05-31-directions-starting-the-week-17-00.json(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-assiavsyoni-mondayrename).
[2026-06-04] ingest | meeting: 2026-06-04-directions-matan-construction
- source:
raw/meetings/notetaker/2026-06-04-directions-w-matan-construction-06-00.json(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
akrsteinwith aliases covering variants.
[2026-06-02] ingest | meeting: 2026-06-02-directions-account-management-vertical
- source:
raw/meetings/notetaker/2026-06-02-directions-brainstorm-17-30.json(Hebrew ASR transcript, ~55 min; opening ~3 min personal chitchat dropped) - new: 2026-06-02-directions-account-management-vertical, daniela, ofer-polivoda, 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-polivoda (AM benchmark + feedback target; originally captured as Ofer/Mixpanel before full name was known), 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:
topics/connect-businesses-multi-vertical-api.mdwas missing the required## Evidencesection — added with citation to 2026-05-31-directions-connect-businesses-and-brain-scaling and the supporting entities.[[deutsche-bank]]was referenced from 2026-05-31-directions-connect-businesses-and-brain-scaling + etoro + connect-businesses-multi-vertical-api but had no page — created stub atcompanies/deutsche-bank.mdand added to index.[[grab]]was referenced from 2026-05-31-directions-connect-businesses-and-brain-scaling + wolt + rami-levy + connect-businesses-multi-vertical-api but had no page — created stub atcompanies/grab.mdand added to index.
- pre-existing flagged (NOT auto-fixed; out of scope for this lint run):
[[pagaya]]referenced fromcompanies/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: createcompanies/pagaya.mdstub on next refactor.[[maccabi-netanya]]referenced frompeople/tomer-shalom.md— no page exists. Football club; lower priority. Suggested fix: create stub or unlink.[[decision-slug]]flagged frommeetings/2026-05-06-brain-os-strategy-brainstorm.mdandmeetings/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 fromindex.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.
[2026-06-08] ingest | source: 2026-06-08-contech-funnel-brief
- source: raw/articles/2026-06-08-contech-funnel-brief.md (user-uploaded brief, placed into raw/ on the user’s behalf — immutable thereafter)
- context: ConTech landscape/white-space brief ingested; web-verified competitive data (Buildots–Genda acquisition Oct ‘25; Planera ~54M Series B) folded into the synthesis.
- new: 2026-06-08-contech-funnel-brief, buildots, openspace, doxel, versatile, genda, planera, permitflow, contech-competitive-landscape, construction-margin-protection-wedge
- updated: construction-project-management (source_count 1→2; added competitive-context key points + evidence), index
- notes: no action-items added (article ingest; the relevant validation step — the tendering-dept call — is already an open item under 2026-06-04-directions-matan-construction).
[2026-06-11] query | Almogim construction-Brain POC design
- source: user conversation 2026-06-11 (Saar ↔ Almogim CEO; no raw transcript yet — flagged on the new pages)
- new: almogim, almogim-exec-visibility-poc
- updated: construction-margin-protection-wedge (second access path), construction-project-management (related link), index
- notes: exec-visibility POC scoped (M365/Outlook, concierge model, Hebrew chat) with week-4 pivot gate to the margin wedge based on CEO query-log classification. source_count: 0 on both new pages until a raw source (meeting summary or first working session) is captured.
[2026-06-14] ingest | meeting: 2026-06-13-directions-revenue-cycle-and-construction-poc
- source:
raw/meetings/notetaker/2026-06-13-directions-17-00.json(Hebrew ASR transcript, long in-person session at Guy’s house; off-topic sports / food / Iran-policy chatter excluded from synthesis) - new: 2026-06-13-directions-revenue-cycle-and-construction-poc, revenue-cycle-brain, discount-bank, meitav
- updated: saar-arbel, guy-barkat, nizan-shifman, daniela, nir-goldstein, ofer-polivoda, wonderful, notch, brm, monday, harmony, gong, mixpanel, almogim, 2026-05-16-alonhuri-linkedin-ai-native-growth-hacking, account-management-vertical, context-os-brain, vertical-use-case-led-brain, agent-native-go-to-market, construction-project-management, almogim-exec-visibility-poc, construction-margin-protection-wedge, vitamin-vs-painkiller-framing, index, action-items
- notes: New broad direction opened: revenue-cycle-brain — a closed-loop GTM/revenue Brain over marketing, sales, product, support, AM, and retention signals. The team did not decide a vertical; AM remains clearer and more bounded, revenue-cycle is bigger but integration-heavy, and construction has warm POC access via almogim-exec-visibility-poc. wonderful / discount-bank anchored the service-to-platform pattern. No decision pages created — still exploratory. Four new Open action items added for this week’s wedge choice, construction POC validation, AM operator validation, and revenue-cycle wedge pressure-test.
[2026-06-14] refactor | OKF-compatible wiki frontmatter
- reason: User requested support for Google’s Open Knowledge Format frontmatter structure.
- touched: all non-operational
wiki/**/*.mdconcept pages;AGENTS.md;CLAUDE.md; log - notes: Added OKF recommended
title,description, andtimestampfields to 98 wiki concept pages. Addedresourcefor meeting/source pages where a canonical raw path or source URL exists. Preserved existing repo fields (aliases,source_count,last_updated,status, etc.) as OKF producer-defined extension keys. Leftraw/immutable and left operational root files (wiki/index.md,wiki/log.md,wiki/action-items.md) without frontmatter.
[2026-06-15] ingest | meeting: 2026-06-15-directions-ofer-polivoda-am-operator-interview
- source:
raw/meetings/notetaker/2026-06-15-directions-w-ofer-polivoda-12-00.json - new: 2026-06-15-directions-ofer-polivoda-am-operator-interview
- updated: account-management-vertical, ofer-polivoda, mixpanel, gong, saar-arbel, guy-barkat, nizan-shifman,
wiki/index.md,wiki/action-items.md - notes: Operator validation for the AM/CS wedge. Ofer’s strongest input: current tools increasingly monitor the past/current account state, but they do not generate account-specific future plans or preserve relationship context across stakeholders and channels. Expanded account-management-vertical with an AM pain inventory, what works today, what does not work, and ideation hooks for later product exploration. Closed the ofer-polivoda intro action and added a follow-up action for deeper AM-pain discovery. Renamed the prior
ofer-mixpanelstub to ofer-polivoda now that the full name is known.
[2026-06-15] refactor | define local OKF profile
- reason: User approved the OKF-compatibility plan: keep
wiki/as the OKF bundle root, preserve repo-native wikilinks internally, and verify every concept page follows the local frontmatter profile. - touched:
AGENTS.md,CLAUDE.md,README.md,scripts/okf-profile-lint.rb, log - notes: Added explicit OKF bundle boundary, documented
wiki/action-items.mdas a local operational extension, kept strict Markdown-link conversion as an export-time concern, and addedruby scripts/okf-profile-lint.rb. Verification passed for 99 concept pages.
[2026-06-15] refactor | replace OKF profile lint with Python
- reason: User clarified that repo code should be Python-only.
- touched:
scripts/okf_profile_lint.py,scripts/okf-profile-lint.rb,AGENTS.md,CLAUDE.md,README.md,.gitignore, log - notes: Replaced the Ruby OKF-profile lint script with a Python/PyYAML implementation, ignored Python bytecode caches, and updated current docs to use
python3 scripts/okf_profile_lint.py. Verification passed for 99 concept pages.
[2026-06-16] ingest | meeting: 2026-06-16-directions-ran-levy-fiverr-cs-operator-interview
- source:
raw/meetings/notetaker/2026-06-16-directions-with-ran-06-00.json - new: 2026-06-16-directions-ran-levy-fiverr-cs-operator-interview, ran-levy, fiverr
- updated: account-management-vertical, vertical-use-case-led-brain, gong, saar-arbel, guy-barkat, nizan-shifman, index, action-items
- notes: Operator validation for AM/CS through a different model from Mixpanel: fiverr B2C seller success. ran-levy described ~300 sellers per CSM, a $49/month success subscription, six hours/day of reactive work, and current AI tooling via Zoom Revenue Accelerator plus internal VOC/report agents. Main synthesis: the AM wedge now splits into enterprise relationship AM vs scaled marketplace/customer success; generic call summaries/scorecards are table stakes, so the Brain has to own cross-tool context, proactive opportunity selection, and human/business judgment.
[2026-06-16] ingest | meeting: 2026-06-14-directions-from-home-strategy-brain-dogfooding
- source:
raw/meetings/notetaker/2026-06-14-directions-from-home-18-15.json - new: 2026-06-14-directions-from-home-strategy-brain-dogfooding
- updated: account-management-vertical, revenue-cycle-brain, context-os-brain, vertical-use-case-led-brain, agent-native-go-to-market, monday, harmony, saar-arbel, guy-barkat, nizan-shifman, index, action-items
- notes: Strategy session between the 2026-06-13 directions meeting and the AM operator interviews. Main outcome: no vertical decision; interview-first validation. AM remained the immediate validation lane, revenue-cycle-brain stayed the largest but least crisp vision, and Brain dogfooding was scoped as support work around proactive context quality rather than a standalone product. No decision pages created.
[2026-06-16] ingest | meeting: 2026-06-16-directions-ofri-avivi-renewals-operator-interview
- source:
raw/meetings/notetaker/2026-06-16-directions-w-ofri-avivi-09-00.json - new: 2026-06-16-directions-ofri-avivi-renewals-operator-interview, ofri-avivi, cymulate
- updated: account-management-vertical, vertical-use-case-led-brain, saar-arbel, guy-barkat, nizan-shifman, index, action-items
- notes: Operator validation for AM/CS through a renewals-manager lens. ofri-avivi described cymulate’s pre-renewal workflow: 90-day renewal reports, CS/support/product-health investigation, CISO/CIO/procurement outreach, regional differences, and the gap between dashboard telemetry and the real CS story. Main synthesis: the AM/CS wedge now has at least three archetypes — enterprise relationship AM, scaled CS/seller success, and SaaS renewals management. No new action items beyond updating the existing AM interview/digest tracking.
[2026-06-16] query | renewals-management-wedge synthesis
- source: 2026-06-16-directions-ofri-avivi-renewals-operator-interview
- new: renewals-management-wedge
- updated: account-management-vertical, vertical-use-case-led-brain, 2026-06-16-directions-ofri-avivi-renewals-operator-interview, ofri-avivi, cymulate, index, action-items
- notes: Promoted Ofri/Cymulate’s renewals-manager workflow into its own topic because it is a distinct AM/CS wedge: hard renewal deadline, customer-health truth gap, CS/support/sales coordination, and 90-day/six-month rescue timing.
[2026-06-20] ingest | notetaker enrichment: 2026-06-16-directions-ofri-avivi-renewals-operator-interview
- source:
raw/meetings/notetaker/2026-06-16-directions-w-ofri-avivi-09-00.json - updated: 2026-06-16-directions-ofri-avivi-renewals-operator-interview, renewals-management-wedge, account-management-vertical, ofri-avivi, cymulate
- notes: Enriched the existing Ofri/Cymulate renewals pages from monday Notetaker
summary+topics; no new independent source_count because this is the same meeting as the legacy raw transcript. Added sharper details on GRR vs NRR scope, Salesforce+Coda manual renewal workflow, BI removal during CRO/tool-stack change, CS joining late-stage sales calls, partner-mediated renewal signal loss, and technical fluency as a renewal-manager scaling constraint. No action items were captured by Notetaker.
[2026-06-20] lint | post-notetaker enrichment check
- counts: 107 concept pages
- result:
python3 scripts/okf_profile_lint.pypassed - flagged: none
[2026-06-21] ingest | meeting: 2026-06-20-directions-planning-the-week-18-30
- source:
raw/meetings/notetaker/2026-06-20-directions-planning-the-week-18-30.json - new: 2026-06-20-directions-planning-the-week-18-30, human-in-the-loop-accountability, user-discovery-cadence, 2026-06-20-vertical-product-over-generic-brain, 2026-06-20-run-high-cadence-user-discovery-sprint, user-interviews, sefi
- updated: context-os-brain, vertical-use-case-led-brain, account-management-vertical, construction-project-management, vitamin-vs-painkiller-framing, agent-native-go-to-market, guy-barkat, nizan-shifman, saar-arbel, monday, brm, index, action-items
- notes: Ingested the Notetaker planning meeting. Main synthesis: generic Brain is not the product wedge; the product should be vertical/use-case-led and use human accountability as the trust layer. Added a high-cadence user-discovery operating plan and six open action items for construction interviews, User Interviews setup, Founder-Market Fit table updates, and VC/YC ideation.
[2026-06-21] lint | post-planning-meeting ingest check
- counts: 114 concept pages
- result:
python3 scripts/okf_profile_lint.pypassed - flagged: none
[2026-06-21] ingest | source: 2026-03-23-a16z-two-paths-left-for-software
- source:
raw/articles/vc-articles/2026-03-23-a16z-two-paths-left-for-software.md - url: https://a16z.com/there-are-only-two-paths-left-for-software/
- new: 2026-03-23-a16z-two-paths-left-for-software, a16z, david-george, software-refounding-pressure
- updated: context-os-brain, agent-native-go-to-market, vertical-use-case-led-brain, index
- notes: Captured the public article via direct
curl+pandocfallback becauseaxcli chromegateway was unavailable. Main synthesis: public software companies face a forced choice between +10 points of AI-native growth and 40-50% true margins; the growth path requires living context layers, token/usage/outcome pricing, and products that move measurable revenue. Entity-stub scope followed the selective pattern from the Entrée ingest: created publisher/author pages only; Broadcom/VMware remain plain-text exemplars until a source makes them load-bearing. No action-items update because this is an external article, not a meeting.
[2026-06-21] lint | post-a16z-source ingest check
- counts: 118 concept pages
- result:
python3 scripts/okf_profile_lint.pypassed - flagged: no new ingest-introduced issues. A separate ad-hoc wikilink scan still surfaces pre-existing unresolved links already documented in earlier lint notes:
pagaya,maccabi-netanya, and template placeholders such asdecision-slug.
[2026-06-21] refactor | introduce VC hypothesis layer
- reason: User wants VC articles decomposed into broad topics plus falsifiable world assumptions that can later be used to evaluate startup ideas against VC market motion.
- touched: ai-native-products-must-move-company-growth, living-context-layers-become-ai-infrastructure, seat-based-saas-pricing-erodes, token-usage-outcome-pricing-captures-ai-growth, agents-weaken-software-moats, 2026-03-23-a16z-two-paths-left-for-software, software-refounding-pressure, context-os-brain, agent-native-go-to-market, vertical-use-case-led-brain, index
- notes: Added
wiki/hypotheses/as a first-class concept directory andtype: hypothesisto the local OKF profile inAGENTS.md/CLAUDE.md, with a template centered on claim, evidence, counter-evidence, implications, favored/weakened ideas, confidence, and disconfirming signals. Updatedscripts/okf_profile_lint.pyto validate hypothesis type, folder placement, required sections, and at least one evidence citation. Seeded five hypotheses from the a16z article; no raw files changed.
[2026-06-21] lint | post-hypothesis-layer refactor check
- counts: 123 concept pages
- result:
python3 scripts/okf_profile_lint.pypassed - flagged: none from the local OKF profile check.
[2026-06-21] ingest | source: 2026-03-05-sequoia-services-the-new-software
- source:
raw/articles/vc-articles/2026-03-05-sequoia-services-the-new-software.md - url: https://sequoiacap.com/article/services-the-new-software/
- new: 2026-03-05-sequoia-services-the-new-software, sequoia-capital, julien-bek, autopilots-capture-services-budget, outsourced-intelligence-work-is-best-autopilot-wedge, intelligence-heavy-work-automates-before-judgement-heavy-work, copilots-converge-into-autopilots
- updated: full-stack-ai-vertical-services, vertical-ai-tam, agent-native-go-to-market, vertical-use-case-led-brain, token-usage-outcome-pricing-captures-ai-growth, index
- notes: Captured the public article via direct
curl+pandocfallback becauseaxcli chromegateway was unavailable. Main synthesis: Sequoia’s services-as-new-software thesis says AI-native winners should sell completed work, start with outsourced intelligence-heavy tasks, and use services/labor budgets as the TAM denominator. Entity-stub scope stayed selective: created publisher/author pages only; named startups in the opportunity map remain examples inside the source page until a later source makes them load-bearing. No action-items update because this is an external article, not a meeting.
[2026-06-21] lint | post-Sequoia-source ingest check
- counts: 130 concept pages
- result:
python3 scripts/okf_profile_lint.pypassed - flagged: none from the local OKF profile check.
[2026-06-26] refactor | organize Notetaker state and gate digests
- reason: User asked to clarify the folder structure and digest only monday Notetaker meetings where at least two of Guy, Nizan, and Saar participated.
- touched:
AGENTS.md,CLAUDE.md,README.md,skills/fetch-notetaker-meetings/SKILL.md,skills/update-directions-brain-context/SKILL.md,skills/fetch-notetaker-meetings/scripts/fetch_notetaker_meetings.py,state/notetaker/processed.md - notes: Moved mutable Notetaker processing state from top-level
notetaker/processed.mdtostate/notetaker/processed.md; documentedraw/as immutable inputs,wiki/as synthesized knowledge, andstate/as mutable pipeline bookkeeping. The recurring Notetaker sync now fetches participant metadata, saves only meetings with at least two ofguybarkat2@gmail.com,nizanshifman@gmail.com, andsaararbel1@gmail.com, and records others asskipped-not-core-teamso they are not repeatedly digested.
[2026-06-26] refactor | organize raw sources
- reason: User asked to organize raw sources while the repo is still small, keep digested Notetaker meetings in the unified raw meeting store, and split raw articles by source type.
- touched:
raw/meetings/notetaker/,raw/articles/linkedin-posts/,raw/articles/vc-articles/, 2026-05-06-brain-os-strategy-brainstorm, 2026-05-19-saar-leshno-glaucoma-data-tracking, 2026-05-27-directions-vertical-pivot-and-prediction-markets, 2026-05-31-directions-connect-businesses-and-brain-scaling, 2026-06-02-directions-account-management-vertical, 2026-06-04-directions-matan-construction, 2026-06-13-directions-revenue-cycle-and-construction-poc, 2026-06-14-directions-from-home-strategy-brain-dogfooding, 2026-06-15-directions-ofer-polivoda-am-operator-interview, 2026-06-16-directions-ran-levy-fiverr-cs-operator-interview, 2026-06-16-directions-ofri-avivi-renewals-operator-interview, 2026-01-09-alonhuri-linkedin-vibe-acting, 2026-01-30-alonhuri-linkedin-full-stack-ai, 2026-03-06-alonhuri-linkedin-saas-is-dead-ai-native-agency, 2026-05-09-alonhuri-linkedin-ai-native-company, 2026-05-16-alonhuri-linkedin-ai-native-growth-hacking, 2026-03-05-sequoia-services-the-new-software, 2026-03-23-a16z-two-paths-left-for-software, 2026-05-01-entree-capital-enterprise-ai-spend-map,state/notetaker/processed.md,AGENTS.md,CLAUDE.md,README.md - notes: Backfilled and normalized Notetaker JSON for historical digested meetings and switched meeting pages to use those JSON files as their primary
resource. Two historical meetings had monday participant metadata showing only Saar, so they were saved by exact ID as historical backfills while the future sync gate remains strict. Moved older manual transcript files intoraw/meetings/legacy-transcripts/, Alon Huri LinkedIn raw posts intoraw/articles/linkedin-posts/, and VC/investor reports intoraw/articles/vc-articles/; left the internal ConTech brief atraw/articles/root because it is neither LinkedIn nor a VC article.
[2026-06-26] ingest | meeting: 2026-06-21-directions-roy-keren-salesforce-gtm-ai-interview
- source:
raw/meetings/notetaker/2026-06-21-directions-with-roy-09-00.json - new: 2026-06-21-directions-roy-keren-salesforce-gtm-ai-interview, roy-keren, salesforce
- updated: account-management-vertical, revenue-cycle-brain, user-discovery-cadence, guy-barkat, nizan-shifman, saar-arbel, sefi, index, action-items
- notes: Filled the only Notetaker raw meeting missing a
wiki/meetingspage. Main synthesis: Salesforce/Slack Bot is a serious incumbent benchmark for AM/revenue-team AI; generic account prep and email drafting are already close to solved in advanced GTM stacks, so the wedge must move toward relationship context, unusual customer acts, laggard AI transformation, or less-automated verticals such as construction.
[2026-06-26] lint | wiki profile check
- counts: 133 concept pages
- result:
python3 scripts/okf_profile_lint.pypassed - flagged: none