explaingit

refactoringhq/portent-vault-template

Analysis updated 2026-06-24

26Audience · writerComplexity · 1/5Setup · easy

TLDR

Starter folder of Markdown files that seeds a personal knowledge vault following the Portent model with eight object types, two relationship fields, and a capture-organize-archive lifecycle.

Mindmap

mindmap
  root((portent-vault-template))
    Inputs
      Markdown files
      YAML front matter
      Wikilinks
    Outputs
      Seeded notes vault
      Type definitions
      Relationship schema
    Use Cases
      Bootstrap an Obsidian vault
      Adopt Portent model
      Use with Tolaria
    Object Types
      project
      task
      event
      note
      topic
      person
    Lifecycle
      Capture
      Organize
      Archive
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Copy the template into a new Obsidian or Tolaria vault to start using Portent

USE CASE 2

Adapt the eight type files to fit a personal knowledge workflow

USE CASE 3

Wire notes together using belongs_to and related_to YAML fields

USE CASE 4

Teach the capture, organize, archive lifecycle to a team

What is it built with?

MarkdownYAMLObsidianTolaria

How does it compare?

refactoringhq/portent-vault-templatealicankiraz1/gemma-4-31b-mtp-vllm-serverantonp29/sylvasigner
Stars262626
LanguagePythonTypeScript
Setup difficultyeasyhardmoderate
Complexity1/54/53/5
Audiencewriterops devopsdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Needs a notes app that understands wikilinks and YAML front matter, such as Obsidian or Tolaria.

In plain English

This repository is a starter pack for a personal knowledge system called Portent. It is not a piece of software with code to run. It is a folder of Markdown files that a person copies into their own note-taking app and uses as the seed of their notes vault. The word vault here is the term used by tools like Obsidian and the README's mentioned tool, Tolaria, to mean a folder of Markdown notes that link to each other. Portent itself is described as an opinionated knowledge model. The opinion is that everything a person tracks should fit into one of eight object types: project, operation, responsibility, task, event, note, topic, and person. The template provides one Markdown file for each of those types, written in a way that local-first apps can read directly and use as type definitions. There is also a small lifecycle that every item passes through: first it is captured, which makes it available, then it is organized, which means giving it a type and relationships so it becomes actionable, then it is archived when it should no longer appear in active views. So a Portent vault is not just a pile of notes, it is notes that move through these three states. To link notes together, Portent suggests two relationship fields in the YAML front matter at the top of each file. The first is belongs_to, used for strong ownership where one thing is part of another, for example an event that belongs to a particular project. The second is related_to, used for weaker, many-to-many connections such as topics or other notes that are merely about the same subject. The README shows a short example where an Event note belongs to a launch project and is related to two topic notes. The README is short and points the reader to a longer write-up called introducing-portent for the full description. There is no installation step beyond placing these files in a notes app that understands wikilinks and YAML front matter, since the template's value is the structure itself rather than any executable behavior.

Copy-paste prompts

Prompt 1
Walk me through the eight Portent object types in portent-vault-template and when to use each one
Prompt 2
Show me how to add a new custom type to portent-vault-template that fits between task and project
Prompt 3
Write a sample event note that uses portent-vault-template conventions for belongs_to and related_to
Prompt 4
Convert my existing Obsidian folder into a portent-vault-template structure without losing links
Prompt 5
Draft a one-page cheat sheet for the capture, organize, archive lifecycle used in portent-vault-template

Frequently asked questions

What is portent-vault-template?

Starter folder of Markdown files that seeds a personal knowledge vault following the Portent model with eight object types, two relationship fields, and a capture-organize-archive lifecycle.

How hard is portent-vault-template to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is portent-vault-template for?

Mainly writer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.