Obsidian Template Library

Templates live in _templates/ of vanos-brain and are inserted via Obsidian’s core Templates (or Templater) plugin. Content may be Greek or English; frontmatter keys and controlled values are always English. All templates share the frontmatter standard from obsidian-vault-blueprint.md § 6 — skeletons below show only the fields that vary.

1. SOP template

Standard operating procedure — one procedure per file, 04-sops/sop-<dept>-<slug>.md.

---
name: <SOP title>
description: <one line — what this procedure achieves>
type: sop
status: draft
last-updated: "<date>"
owner: <role>
tags: [dept/<dept>, type/sop]
vault: vanos-brain
data_sensitivity: normal
---
Part of: [<dept> hub](../02-departments/<dept>/_index.md)

## Purpose & scope
## When to use / trigger
## Prerequisites (access, tools, inputs)
## Steps
1.
## Exceptions & escalation
## Related (process, systems, other SOPs)
## Review: next-review: <date+1y> | approved-by: <role>

2. AI prompt template

A proven prompt, 07-ai/prompts/<dept>/<slug>.md.

---
name: <prompt title>
description: <task in one line>
type: prompt
status: draft
owner: <role>
tags: [dept/<dept>, type/prompt]
data_sensitivity: normal
---
## Task
What this prompt does and when to reach for it.
## Context required
What to paste/attach (and what NOT to — sensitivity note).
## Model
<platform model / assistant profile>
## Prompt text
```text
<the prompt, with {variables} marked>

Variables

• {variable}: meaning, example

Quality checks

• How to verify the output before using it.

## 3. Meeting note template

`05-meetings/<cadence>/YYYY-MM-DD-<slug>.md`. Drafted by the Meeting Scribe Agent, curated by a human.

```markdown
---
name: <meeting> — <date>
description: <one-line outcome>
type: meeting
status: draft        # human promotes to approved after curation
owner: <role of curator>
tags: [dept/<dept>, type/meeting]
data_sensitivity: high
---
## Attendees (roles)
## Agenda
## AI summary
> Auto-drafted by Meeting Scribe Agent — verify before approving.
## Decisions
- D1: … (→ create 09-decisions/ entry if durable)
## Actions
| # | Action | Owner (role) | Due |
| --- | --- | --- | --- |
## Open questions

4. Decision log template

09-decisions/NNN-slug.md, ADR-style, append-only.

---
name: NNN — <decision title>
description: <one-line decision>
type: decision
status: approved     # or superseded-by NNN
owner: <deciding role>
tags: [type/decision, dept/<dept>]
data_sensitivity: high
---
## Context
## Decision
## Options considered
## Consequences
## Date & participants (roles)

5. Process documentation template

03-processes/<slug>.md — one process per file.

---
name: <process name>
description: <end-to-end, in one line>
type: process
status: draft
owner: <process-owner role>
tags: [dept/<dept>, type/process]
data_sensitivity: normal
---
Part of: [<dept> hub](../02-departments/<dept>/_index.md)

## SIPOC
| Suppliers | Inputs | Process (5-7 steps) | Outputs | Customers |
| --- | --- | --- | --- | --- |
## Swimlane
<!-- embed diagram: assets/<slug>-swimlane.png or Mermaid block -->
## Volumes & frequency
e.g. ~N orders/day, peak seasons.
## Systems touched
SoftOne modules, M365, other.
## Pain points & AI opportunities
Links to 14-improvement-backlog/ and 07-ai/use-cases/.

6. Requirement template

Company-side needs captured during and after the program.

---
name: REQ-<NNN> — <short title>
description: <the need in one line>
type: requirement
status: captured     # captured | validated | in-progress | delivered | dropped
owner: <requesting role>
tags: [dept/<dept>, type/requirement]
data_sensitivity: high
---
## Need (as stated)
## Who is affected & how often
## Current workaround
## Success looks like
## Source (interview/meeting link) & date
## Linked use case / project

7. Use-case template

07-ai/use-cases/<slug>.md — mirrors the program pipeline (../08-ai-portfolio/ai-use-case-pipeline.md).

---
name: UC — <use case>
description: <one line>
type: note
status: draft
owner: <sponsor role>
tags: [dept/<dept>, type/use-case]
data_sensitivity: high
---
## Problem & current cost (time/€/errors)
## Proposed AI solution (assistant / agent / automation)
## Users & volume
## Data & systems needed
## Value estimate & effort (T-shirt)
## Pipeline stage: idea | assessed | pilot | production | retired
## Linked requirement(s), agent spec, risks

8. Agent specification template

07-ai/agents/<slug>.md — mirrors the fields of ../08-ai-portfolio/ai-agent-registry.md.

---
name: Agent — <agent name>
description: <what it does, one line>
type: agent
status: draft
owner: <business-owner role>
tags: [dept/<dept>, type/agent]
data_sensitivity: high
---
## Purpose & scope (what it does / must NOT do)
## Trigger & schedule
## Inputs (data sources, permissions)
## Outputs & destinations
## Model & tools used
## Human-in-the-loop points
## Guardrails & failure behaviour
## Metrics (usage, quality, incidents)
## Runbook link & technical owner (role)

9. Risk template

10-risks/<slug>.md.

---
name: RISK — <title>
description: <one line>
type: risk
status: approved
owner: <risk-owner role>
tags: [type/risk, dept/<dept>]
data_sensitivity: high
---
## Description
## Category (operational | compliance | ai | security | adoption)
## Likelihood (1-5) × Impact (1-5) = Score
## Mitigation & contingency
## Status & review date

10. Training note template

11-training/<slug>.md.

---
name: Training — <topic>
description: <one line>
type: training
status: draft
owner: <trainer role>
tags: [type/training, dept/<dept>]
data_sensitivity: normal
---
## Audience & prerequisites
## Learning objectives
## Content / walkthrough
## Exercises
## Assessment / how we know it stuck
## Related SOPs & prompts

11. Vendor evaluation template

12-vendors/<vendor>-evaluation.md.

---
name: Vendor evaluation — <vendor/product>
description: <what was evaluated, one line>
type: vendor
status: draft
owner: <evaluating role>
tags: [type/vendor]
data_sensitivity: high
---
## Need & evaluation scope
## Criteria matrix
| Criterion | Weight | <Option A> | <Option B> |
| --- | --- | --- | --- |
| Fit to need | | | |
| Cost (TCO, placeholder €[X]) | | | |
| On-prem / data residency | | | |
| Support & lock-in | | | |
## Recommendation & decision link (09-decisions/NNN)

12. Project status template

06-projects/<project>/status.md — refreshed, not duplicated.

---
name: <project> — status
description: <current one-line status>
type: project
status: approved
owner: <project-lead role>
tags: [type/project]
data_sensitivity: high
---
## Status: 🟢 | 🟡 | 🔴 — as of <date>
## Done since last update
## Next milestones
## Risks & blockers
## Decisions needed

13. Department hub template

02-departments/<dept>/_index.md — required sections per blueprint § 8.

---
name: <Department> — knowledge hub
description: Entry point for all <department> knowledge.
type: note
status: approved
owner: <department-head role>
tags: [dept/<dept>]
data_sensitivity: normal
---
## What we do
## Processes
## SOPs
## Systems
## Contacts (roles)
## FAQs
## Prompt shortcuts
## Knowledge map: [knowledge-map.md](knowledge-map.md)

14. Lessons-learned template

13-lessons-learned/YYYY-MM-DD-<slug>.md.

---
name: Lessons — <event/project>
description: <one line>
type: note
status: approved
owner: <facilitator role>
tags: [type/lessons, dept/<dept>]
data_sensitivity: high
---
## What happened (facts, dates)
## What went well
## What went wrong
## Root causes
## Changes we commit to (→ backlog items / SOP updates)

15. Improvement-backlog item template

14-improvement-backlog/<slug>.md.

---
name: IMP — <title>
description: <the improvement in one line>
type: note
status: draft        # draft | triaged | planned | done | dropped
owner: <proposer role>
tags: [dept/<dept>, type/improvement]
data_sensitivity: normal
---
## Problem / friction
## Proposed improvement
## Expected benefit (time/€/quality)
## Effort guess (S/M/L) & dependencies
## Triage decision & link (use case? project? SOP fix?)

16. Data-source inventory entry template

08-data/sources/<slug>.md.

---
name: Data source — <name>
description: <what data it holds, one line>
type: data-source
status: approved
owner: <data-owner role>
tags: [type/data-source, dept/<dept>]
data_sensitivity: high
---
## System & location (e.g. SoftOne module, SharePoint site)
## Contents & key entities
## Update frequency & volume
## Access method (export, API, report)
## Quality notes & known gaps
## Used by (reports, agents, use cases)

17. Glossary entry template

01-company/glossary/<term>.md — one term per file; keep the Greek original.

---
name: <term (English)>
description: <definition in one line>
type: glossary
status: approved
owner: knowledge-manager
tags: [type/glossary]
data_sensitivity: public
---
## Term
<English> (Greek: <original Greek term>)
## Definition
## Context & example usage
## Related terms