Moniteur de finance IP

Analyse hebdomadaire des développements en financement adossé à la propriété intellectuelle : politique, réglementation, marchés, valorisation et recherche. Met à jour une note Obsidian chaque vendredi.

Spar Skills Guide Bot
ProductiviteIntermédiaire
1022/07/2026
Claude CodeCopilotCursor
#ip-finance#monitoring#weekly#policy

Recommandé pour


name: ip_finance_monitor description: Weekly scan of IP-backed finance developments — policy, regulation, market, valuation, and research. Updates Obsidian note. Runs every Friday. tags:

  • ip-finance
  • monitoring
  • weekly
  • policy

IP Finance Monitor

Purpose

Scan the internet for the past 30 days of developments in IP-backed finance, synthesise findings by category, and update the Obsidian note (deduplicating against already-logged items) at. This monitor runs every Friday.

/Users/michal/Library/Mobile Documents/iCloud~md~obsidian/Documents/Michal/Notes/Fleeting notes/IP backed finance developments.md

Instructions

Step 1 — Run searches

Run ALL of the following web searches. Today is {{currentDate}}. Look for developments from the past 30 days — prioritise recent items but keep substantive older items if relevant.

  1. EU IP-backed finance policy regulation intangible assets 2026
  2. IP collateral lending guarantee insurance securitisation 2026
  3. IP valuation standards IVSC IVS methodology 2026
  4. EUIPO EIB EIF European Commission IP finance 2026
  5. UK Singapore US IP finance lending 2026
  6. intangible assets finance research evidence 2026

Step 2 — Filter and synthesise

For each search block, prioritise items from the past 30 days. Discard generic background articles with no new information. Keep items that directly reference:

  • New policy proposals, legislative drafts, consultations
  • New instruments or programmes launched
  • New data, reports, or empirical studies
  • Statements or positions from key actors (EC, EUIPO, EIB, IVSC, Basel Committee)

Anchor data points — always retain regardless of age, unless the exact item already appears in the existing note (deduplication applies):

  • Key lending/market statistics (e.g., China IP-pledged loan volumes, BBB/UKIPO 40% lower default rate finding, WTW IP insurance market CAGR/rate trends)
  • Landmark regulatory changes (e.g., Basel III 25% risk-weight reduction for IP collateral)
  • Jurisdiction-level framework developments (e.g., India RBI IP finance rules, Hong Kong IP finance sandbox, Singapore IPOS/ACRA Intangibles Disclosure Framework)
  • Structural reform processes with long timelines (e.g., IASB IAS 38 overhaul, IVS revision cycles)

These anchor points serve as permanent reference material in the note and must not be pruned simply because a high-volume news week (e.g., a major report launch) dominates the digest.

Step 3 — Write the weekly digest

Produce a digest with the following structure (omit sections with no new items):

## Week of {{currentDate}}

### Policy & Regulation
- ...

### Market & Instruments
- ...

### Valuation
- ...

### Institutional Announcements
- ...

### Research & Evidence
- ...

### Notes
[Any cross-cutting observations, emerging themes, or items to watch next week]

Each bullet should include: [Source name] — one sentence summary. Link in parentheses.

Step 4 — Update the Obsidian note (with deduplication)

Read the existing note at: /Users/michal/Library/Mobile Documents/iCloud~md~obsidian/Documents/Michal/Notes/Fleeting notes/IP backed finance developments.md

If the file does not exist, create it with:

  1. YAML frontmatter: tags: [ip-finance, monitoring], created: {{currentDate}}
  2. Title: # IP Backed Finance — Weekly Developments
  3. Description line: Weekly digest from \/ip_finance_monitor`. New entries are prepended above older ones.`

If the file does exist but is missing YAML frontmatter, prepend the frontmatter block before doing anything else.

Deduplication: Before prepending, remove any new bullet whose URL or source+headline already appears in the existing note. Anchor data points (see Step 2) are subject to deduplication — only skip them if the exact same item is already present. If nothing new remains after deduplication, write _No new developments this week._ instead.

Prepend the new digest section immediately after the frontmatter --- separator (most recent week at the top). Do not modify any existing content below.

Step 5 — Confirm

Report back to the user:

  • How many items were found across all blocks
  • Which categories had the most activity
  • Any high-priority items that may need attention in the current week's work
Skills similaires