Quartz 4

Templates Library Hub

6 min read

Templates Library Hub

This hub indexes all 8 Obsidian Templater templates in wiki/_templates/. Templates are scaffold files used by Obsidian’s Templater plugin to create structured new files (agents, daily notes, feedback rules, friction entries, project memories, project plans, reference memories, and session bridges). Use these templates as the canonical starting structure for any new file of their type — do not create these file types from scratch. Curator: claude. Review cadence: on-demand when new file types crystallize.

Quick reference

FieldValue
Source docwiki/_templates/ (vault-native)
Source doc last updatedvaries per template
Canonical path/home/opsadmin/openclaw-vault/wiki/_templates/
Curatorclaude
Review cadenceon-demand
Staleness risklow — templates are structural scaffolds that rarely change
Applies to agentsall 42 active agents (templates govern new file creation for all agent types)
Governance gates enforcedn/a

Template catalog

All 8 templates live at /home/opsadmin/openclaw-vault/wiki/_templates/. They use Obsidian Templater syntax (<% tp.* %> expressions evaluated at file creation time).

agent-status.md

Purpose: Scaffold for new agent status files at wiki/agents/<name>/ paths. Type tag: agent-status Key fields: title, agent name, tier, status, capabilities, active workflows, memory DB path and chunk count, open issues Templater expressions: tp.file.title, tp.date.now("YYYY-MM-DD"), tp.date.now("YYYY-MM-DDTHH:mm:ssZ") Auto-links to: wiki/agents/<agent-name>/SOUL, wiki/system-map/agents-tier-map Use when: Adding a new agent to the 42-agent fleet Related hub: agent-registry

daily-note.md

Purpose: Scaffold for daily operations notes — done today, open/blocked, decisions, tomorrow. Type tag: daily-note Key fields: date, done today, open/blocked, decisions, tomorrow, links to yesterday and tomorrow Templater expressions: tp.date.now("YYYY-MM-DD"), tp.date.yesterday(), tp.date.tomorrow() Use when: Creating a new daily operations note in Obsidian Related hub: henry-preferences (§3 session continuity)

feedback-rule.md

Purpose: Scaffold for memory/feedback_*.md files — durable Claude behavior rules. Type tag: feedback Key fields: name, description, incident_derived flag, incident_date, Rule / Why / How to apply body Default: incident_derived: false — set true for rules derived from specific incidents; these MUST live above line 150 in MEMORY.md per G-MEMORY-FOLD-PROTECTION Templater expressions: tp.file.title.replace(/^feedback_/, "").replace(/_/g, " ") Use when: Creating a new feedback rule after observing a pattern or incident Related hub: memory-rule-clusters

friction-entry.md

Purpose: Scaffold for friction log entries in SYSTEM-FRICTION-LOG.md — recurring friction tracking. Type tag: friction Key fields: date, status, severity, recurrence_count, friction observed, where it happened, cost Default: recurrence_count: 1 — increment on each recurrence Templater expressions: tp.date.now("YYYY-MM-DD"), tp.file.title Use when: Documenting a recurring friction point for the nightly friction report Related hub: plan-governance

project-memory.md

Purpose: Scaffold for memory/project_*.md files — per-project memory index entries. Type tag: project Key fields: name, description, status, priority, created date, plan_file path, status snapshot Required by: G-PLAN-INDEX-REQUIRED — every new plan file in ~/.claude/plans/ MUST have a matching project_*.md memory file created in the same session Templater expressions: tp.file.title.replace(/^project_/, "").replace(/_/g, " ") Use when: Creating a new project plan (G-PLAN-INDEX-REQUIRED mandates this) Related hub: plan-governance

project-plan.md

Purpose: Scaffold for new project plan documents — the GSD-style plan format. Type tag: project-plan Key fields: title, status, priority, created date, owner, Outcome + Scope section Required sections per HENRY-PREFERENCES.md: System-first audit findings, Source of Truth Matrix, Data Flow Audit, Keep/Rework/Replace/Remove table, Anti-scope section, Plan Q&A, Acceptance criteria Naming convention: [category]-[topic].md — NEVER auto-generated random names (per henry-preferences §2) Templater expressions: tp.file.title, tp.date.now("YYYY-MM-DD") Use when: Creating any new project plan Related hub: plan-governance

reference-memory.md

Purpose: Scaffold for memory/reference_*.md files — contextual reference entries for recurring patterns, API findings, architecture decisions. Type tag: reference Key fields: name, description, last_updated, When to use / What’s needed / How to apply body Templater expressions: tp.file.title.replace(/^reference_/, "").replace(/_/g, " ") Use when: Documenting a reusable reference pattern (e.g., reference_il_marketplace_pipeline.md, reference_hubspot_api_key_findings.md) Related hub: memory-rule-clusters

session-bridge.md

Purpose: Scaffold for session bridge files — structured handoff between sessions. Type tag: session-bridge Key fields: session_goal, session_date, session_owner, Key decisions, Files changed, Blockers found, Next actions Required by: CLAUDE.md §Before Ending Any Session — bridge file is mandatory for every session Stop hook at ~/.openclaw/tools/hooks/on-stop.sh reads these for richer session summaries Templater expressions: tp.date.now("YYYY-MM-DDTHH:mm:ssZ"), tp.date.now("YYYY-MM-DD HH:mm") Use when: Ending any session — must write bridge file before session close Related hub: action-gate

Template usage matrix

File typeTemplateGovernance gateRequired by
New agent statusagent-status.mdnoneagent additions
New daily notedaily-note.mdnoneops cadence
New feedback rulefeedback-rule.mdG-MEMORY-FOLD-PROTECTION (if incident-derived)incident response
New friction entryfriction-entry.mdG-GOVERNANCE-LOG-FRESHNESSfriction tracking
New project memoryproject-memory.mdG-PLAN-INDEX-REQUIREDevery new plan file
New project planproject-plan.mdG-PLAN-INDEX-REQUIREDevery new plan
New reference memoryreference-memory.mdnonepattern documentation
New session bridgesession-bridge.mdnone (but missing = fallback inference)every session end

How it’s used

  • In Obsidian — use Templater (Alt+E or command palette) to apply a template to a new file
  • In Claude Code — when creating a new file of a known type, check this hub for the canonical structure before writing from scratch
  • Before creating a new plan — use project-plan.md scaffold AND project-memory.md scaffold (G-PLAN-INDEX-REQUIRED requires both)
  • After documenting an incident — use feedback-rule.md to capture the rule; set incident_derived: true and ensure placement above line 150 in MEMORY.md (G-MEMORY-FOLD-PROTECTION)
  • At session end — use session-bridge.md structure for the bridge file written to /tmp/claude-session-summary-$$.json
  • Failure mode: creating project_*.md files without the project-plan.md structure, or forgetting project-memory.md when creating a plan (G-PLAN-INDEX-REQUIRED violation)

Plans that govern this

Governance hubs

  • plan-governance — project-plan and project-memory templates enforce plan governance
  • memory-rule-clusters — feedback-rule and reference-memory templates feed this hub
  • action-gate — session-bridge template enforces session close protocol

Process hubs

  • deal-ingestion — deal ingestion flows may generate new project-memory entries
  • compliance-gates — compliance gate violations may generate new feedback-rule entries

Feedback rules

System maps

Resource hubs (knowledge curation cluster)

  • kb-directory — anchor — check KB before creating any template-based content
  • henry-preferences — §2 plan naming convention applies to project-plan template usage
  • workflow-patterns — WF-5 bridge file uses session-bridge template
  • runbooks-master — runbooks document how templates are used in context

Knowledge curation cluster

This hub is a member of the Knowledge curation cluster anchored at kb-directory.

HubRole in cluster
kb-directoryAnchor — 165 KB platform docs Claude must check first
henry-preferencesFounder operating standards — rules for HOW Claude works
workflow-patternsRecurring patterns — canonical procedures
runbooks-masterTactical runbooks — step-by-step procedures
templates-libraryTemplates — structured scaffolds for new files

Open issues / TODOs

  • wiki/_templates/ has no index file — consider adding _index.md in a future wave
  • friction-entry.md template type is friction (no type: prefix) — check if Obsidian Templater requires consistent type values
  • No template exists for Wave-style resource hubs (this hub type) — may be useful for Wave 4+
  • session-bridge.md template outputs to /tmp/ (not vault) — ensure vault-sync does NOT pick up /tmp/ session bridges

Recent activity

  • 2026-05-04: hub created (W3-S1, Wave 3 resource hubs batch); live count probed at 8 templates

Graph View

Backlinks