dbrain-processor

d-brain Processor

Process daily entries → thoughts (Obsidian) + HTML report (Telegram).

Integrates with Your Business data for business context.

CRITICAL: Output Format

ALWAYS return RAW HTML. No exceptions. No markdown. Ever.

Your final output goes directly to Telegram with parse_mode=HTML.

Rules:

ALWAYS return HTML report — even if entries already processed
ALWAYS use the template below — no free-form text
NEVER use markdown syntax (**, ##, ```, -)
NEVER explain what you did in plain text — put it in HTML report

WRONG:

<b>Title</b>

CORRECT: Title

Processing Flow

Load personal context — Read goals/1-yearly, goals/2-monthly, goals/3-weekly
Load business context:
- Read business/_index.md — Your Business (clients, projects, CRM)
- Read projects/_index.md — personal projects (if relevant)
Read daily — daily/YYYY-MM-DD.md
Process entries — Classify → task or thought, detect business mentions
Create cards (autograph) — new entities/thoughts become vault cards per the autograph template (type, description-as-snippet, tags, status); tasks become checklist entries in the daily note / project notes
Build links — Connect notes with [[wiki-links]], link to business entities
Generate HTML report — business activity + day summary
Log actions to daily — append action log entry (see below)
Evolve MEMORY.md — update long-term memory if needed (see below)
Capture observations — record friction signals to handoff.md (see below)

MANDATORY: Logging to daily/

After ANY changes in the vault — IMMEDIATELY write to daily/YYYY-MM-DD.md:

Format:

## HH:MM [text]
{Описание действий}

**Создано/Обновлено:**
- [[path/to/file|Name]] — описание

What to log:

Creating files in thoughts/
Updating business/ or projects/
Adding task entries to daily/projects
Synchronization with external systems

Example:

## 14:30 [text]
Обработка ежедневных записей

**Создано задач:** 2
- [ ] Follow-up Acme Corp (due: завтра, p2)
- [ ] Подготовить КП Unilever (due: пятница, p2)

**Сохранено мыслей:** 1
- [[thoughts/ideas/product-launch|Product Launch]] — идея запуска

Why: Audit trail + context for future processing.

Evolve MEMORY.md (Step 9 Detail)

GOAL: Keep MEMORY.md up to date. Don't append, but EVOLVE.

When to update MEMORY.md

Check after processing entries — is there information worthy of long-term memory?

Write Rules: What is worthy of MEMORY.md

WRITE:

✅ Key decisions с impact (pivot, tool choice, architecture change)
✅ Changes in the pipeline (new lead, closed deal, status change)
✅ Financial changes (payments received, debts, new contracts)
✅ New patterns/insights (learnings)
✅ Changes in Active Context (new ONE Big Thing, Hot Projects)
✅ New key contacts (with context)

DO NOT WRITE:

❌ Daily trivia (meetings, calls without impact)
❌ Temporary notes (leave in daily/)
❌ Duplicates of what already exists
❌ Project details (leave in business/crm/, projects/)
❌ Trivial tasks

How to update (evolve, not append)

Principle: The new REPLACES the outdated, it is not added alongside.

Situation	Action
The new contradicts the old	REPLACE the old information
The new complements the old	Add to the existing section
The information is outdated	Delete or archive

Example 1 — Project status change:

Old: "| Acme Corp NCP Meals | p1 | Активная разработка | $XXK |"
New info: "Acme Corp NCP Meals сдан клиенту"
→ ЗАМЕНИТЬ на: "| Acme Corp NCP Meals | ✅ | Завершён | $XXK |"

Example 2 — New decision:

Добавить в Key Decisions таблицу:
| 2026-02-01 | Отказ от X в пользу Y | причина | impact |

Example 3 — Change in the pipeline:

Old: "| LogisticsLead | Hot | $XXK |"
New info: "LogisticsLead подписал контракт"
→ Удалить из Pipeline
→ Добавить в Hot Projects или Financial Context

MEMORY.md sections to update

Section	When to update
Active Context	Change of ONE Big Thing, Hot Projects, Pipeline
Key Decisions	New solution with impact
Financial Context	Payments, debts, contracts
Key People	New important contact
Learnings	New pattern/insight
Current Crisis	Change in the current critical situation

Edit format

Use the Edit tool for targeted changes:

Edit MEMORY.md:
old_string: "| LogisticsLead | Hot | $XXK |"
new_string: "| LogisticsLead | ✅ Signed | $XXK |"

In the report

If you updated MEMORY.md, add the section:

<b>🧠 MEMORY.md обновлён:</b>
• Active Context → Hot Projects updated
• Key Decisions → +1 новое решение

Capture Observations (Step 10 Detail)

GOAL: Record friction signals, patterns, and ideas for improving the system.

When to record

After processing, check — were there any problems or observations?

Type	When
`[friction]`	mcp-cli errors, timeouts, empty daily, broken links, unexpected data
`[pattern]`	Recurring pattern (tasks are always overdue, daily is empty on weekends)
`[idea]`	Idea for improving the pipeline, schema, report

Format

Append в vault/.session/handoff.md section ## Observations:

## Observations
- [friction] YYYY-MM-DD: transcription timeout 3x — retry спас, но -60 сек
- [pattern] YYYY-MM-DD: daily без entries 2 дня подряд — выходные?
- [idea] YYYY-MM-DD: CRM карточки без deal_deadline = невидимые дедлайны

Rules

One line per observation (specifics, not abstractions)
Date is mandatory
Do not repeat already recorded observations
When observations ≥10 → signal for a system improvement session

In the report

If observations were recorded, add:

<b>👁 Observations:</b>
• [friction] mcp-cli timeout 3x

Entry Format

HH:MM [type]

Content

Types: [voice], [text], [forward from: Name], [photo]

Business Context Integration

ENTRY POINT: business/_index.md — read to understand the business context.

Structure:

business/
├── _index.md       ← Статистика, обзор
├── crm/            ← ВСЁ: компании + сделки + проекты в одном файле
├── network/        ← Структура холдинга
└── events/         ← Мероприятия

Recognizing mentions

When processing entries, look for mentions of clients and projects:

Pattern	Action
"called [Client]"	Find `business/crm/{client}.md`, add a link
"for the [Client] project"	Find `business/crm/{client}.md`
"meeting with [Client]"	Create a task + link it to `business/crm/{client}.md`
"sent a proposal for [Client]"	Link to `business/crm/{client}.md`

Finding a client by name

Name → kebab-case: "Acme Corp" → acme-corp, "Bi Group" → bi-group
Search: business/crm/{kebab-case}.md
If not found — fuzzy search by grep -l "{name}" business/crm/

Creating links

When a client/project is mentioned, add wiki-links:

To the task:

"Follow-up [[business/crm/acme-corp|Acme Corp]] по снекам"

В thought:

Связано с: [[business/crm/techco|TechCo]], [[business/crm/phonebrand-smm|PhoneBrand SMM]]

Priority of tasks with business

Condition	Priority
Client with priority: High + deadline	p1
Active project (In progress)	p2
Client with priority: High	p2
Client with priority: Mid	p3
Prospect without urgency	p4

Classification

task → checklist entry in daily/project notes idea/reflection/learning → thoughts/ (see references/classification.md) client/project mention → link to Business/Projects + create task if actionable

Projects Context Integration

Entry point: projects/_index.md

Structure:

projects/
├── _index.md       # Clients overview
├── clients/        # Clients
└── leads/          # Leads

Mention recognition

Pattern	File
"[Client A]"	projects/clients/{client-a}.md
"[Client B]"	projects/clients/{client-b}.md
"AI training", "workshop"	projects/ context

Difference from Business

Business = core business
Projects = personal projects (consulting, training)

If an entry mentions AI/ML training — look in projects/ first.

Contacts Context Integration

Entry point: contacts/_index.md

Name recognition in entries

Look for patterns:

"called with [Contact] from [Client]"
"meeting with @username"
"First Name Last Name wrote"

Classification

Indicator	Category	Vault Link
Known business clients	business	`business/crm/{client}`
AI/training expertise, known leads	projects	`projects/leads/{name}`
Others	personal	—

In the report

If people are mentioned in entries, add a section:

<b>👤 Упомянуто контактов:</b>
• [Contact Name] (business → [[business/crm/acme-corp]])
• [Contact Name] (personal)

Priority Rules

p1 — Client deadline, urgent p2 — Aligns with ONE Big Thing or monthly priority p3 — Aligns with yearly goal p4 — Operational, no goal alignment

Process Goals Preference

When creating tasks, prefer PROCESS over OUTCOME formulations.

Outcome (less effective):

"Close a deal with X"
"Launch a product"
"Prepare a program"

Process (more effective):

"Send a follow-up to client X" (actionable, controllable)
"2h deep work on the MVP" (time-bounded)
"Show a program draft to a colleague" (checkpoint)

When to transform:

Entry sounds vague/outcome-focused → make it specific/process-focused
User says "need to do X" → create an actionable next step, not X itself
Goal mentioned → create task that MOVES TOWARD goal, not goal itself

See: references/process-goals.md for patterns and examples.

Thought Categories

💡 idea → thoughts/ideas/ 🪞 reflection → thoughts/reflections/ 🎯 project → thoughts/projects/ 📚 learning → thoughts/learnings/

HTML Report Template

Output RAW HTML (no markdown, no code blocks):

📊 Processing for {DATE}

🎯 Current focus: {ONE_BIG_THING}

📓 Thoughts saved: {N} • {emoji} {title} → {category}/

✅ Tasks created: {M} • {task} ({priority}, {due})

🏢 Business Activity: • {client} — {action} • {project} — {status update} Clients mentioned: {N} | Projects: {M}

📋 Process Goals: • {process goal 1} → {status} • {process goal 2} → {status} {N} active | {M} need attention New created: {K}

📅 Weekly load: Mon: {n} | Tue: {n} | Wed: {n} | Thu: {n} | Fri: {n} | Sat: {n} | Sun: {n}

⚠️ Needs attention: • {overdue or stale goals}

🔗 New connections: • [[Note A]] ↔ [[Note B]]

⚡ Top 3 priorities:

{task}
{task}
{task}

📈 Progress: • {goal}: {%} {emoji}

🧠 MEMORY.md: • {section} → {change description} (if updated)

Processed in {duration}

If Already Processed

If all entries have  marker, return status report:

📊 Status for {DATE}

🎯 Current focus: {ONE_BIG_THING}

📋 Process Goals: • {process goal 1} → {status} • {process goal 2} → {status} {N} active | {M} need attention

📅 Weekly load: Mon: {n} | Tue: {n} | Wed: {n} | Thu: {n} | Fri: {n} | Sat: {n} | Sun: {n}

⚠️ Requires attention: • {overdue count} overdue • {today count} for today

⚡ Top 3 priorities:

{task}
{task}
{task}

Entries have already been processed earlier

Allowed HTML Tags

— bold (headers) — italic (metadata) — commands, paths — strikethrough — underline text — links

FORBIDDEN in Output

NO markdown: **, ##, -, *, backticks NO code blocks (triple backticks) NO tables NO unsupported tags: div, span, br, p, table

Max length: 4096 characters.

References

Read these files as needed:

references/about.md — User profile, decision filters
references/classification.md — Entry classification rules
references/goals.md — Goal alignment logic
references/process-goals.md — Process vs outcome goals, transformation patterns
references/links.md — Wiki-links building
references/rules.md — Mandatory processing rules
references/report-template.md — Full HTML report spec
references/business.md — Business client/project context, search patterns
references/contacts.md — Contacts search and classification

Business Quick Reference

Entry point: business/_index.md

Client search:

grep -l "Acme Corp" business/crm/
→ business/crm/acme-corp.md

Active deals:

grep -l "deal_status:" business/crm/

High priority clients:

grep -l "priority: High" business/crm/

Frontmatter fields:

type: crm
industry, priority, status, region, owner, responsible
deal_status, deal_deadline (for active deals)
updated

Relevant Skills

[[vault/.claude/skills/autograph/SKILL|autograph]] — Typed vault engine: graph, decay, MOC, dedup

About this skill

CRITICAL: Output Format

Processing Flow

MANDATORY: Logging to daily/

Evolve MEMORY.md (Step 9 Detail)

When to update MEMORY.md

Write Rules: What is worthy of MEMORY.md

How to update (evolve, not append)

MEMORY.md sections to update

Edit format

In the report

Capture Observations (Step 10 Detail)

When to record

Format

Rules

In the report

Entry Format

HH:MM [type]

Business Context Integration

Structure:

Recognizing mentions

Finding a client by name

Creating links

Priority of tasks with business

Classification

Projects Context Integration

Structure:

Mention recognition

Difference from Business

Contacts Context Integration

Name recognition in entries

Classification

In the report

Priority Rules

Process Goals Preference

Thought Categories

HTML Report Template

If Already Processed

Allowed HTML Tags

FORBIDDEN in Output

References

Business Quick Reference

Relevant Skills