Skip to main content
Level 3 is the full experience: your actual to-do list, tagged by skill, becomes the Throne Room’s daily checklist and weekly strip, feeds all four skill trees, and — if you allow it — is visible to your Companion, who can tick items off with you. This level adds a second local process, the board-sync bridge, separate from the Reality Harness MCP you installed for Levels 1-2. It runs alongside the MCP, not instead of it.

​
1. Your Obsidian board

The bridge looks for markdown notes under <your vault>/10-PM/**/*_tasks/*.md. Each note needs YAML frontmatter:
FieldRequired?Notes
pm-taskYesmust be the literal boolean true
idYesstable unique id
projectIdYesthe parent project’s id
projectYeshuman-readable project name
titleYestask title
typeYese.g. task
statusYesone of todo · in-progress · blocked · review · done · closed
kindNoset to day to appear in the daily checklist
priorityNocritical · high · medium · low — sets XP weighting
start / dueNoYYYY-MM-DD
tagsNocarries the skill tag (below)
A note missing any required field is silently skipped by the bridge — if fewer notes sync than you expect, check for a missing field first.
For a task to show up in the daily checklist specifically, it needs both kind: day and a due date. Every other task still syncs, still earns XP, and still feeds the skill trees — it just won’t appear in the day view.

​
2. Tagging for skill lanes

There are four skill lanes: leadership · business-acumen · technical-skills · content. Tag a task with skill/<category> in its tags list: 
tags:
  - skill/technical-skills
A task with no skill tag lands in a synthetic unassigned bucket and earns 0 XP. Tag your tasks — this is the one thing to get right. If you generate tasks with Conquoreum’s task-writer tooling, tasks are auto-tagged for you based on their title and project, and any tag you already set is left alone. To retroactively tag an existing board, a one-off backfiller script scans your vault and adds the right tags (dry-run first, then --apply).

​
3. The board-sync bridge

A small Node/TypeScript daemon that runs on your own machine, reads your vault directly, and talks to Conquoreum’s API. 
cd vision-harness
npm install
npm run build
Allowlist which projects/tags are allowed to sync (fail-closed — nothing syncs until you add something here): 
{
  "filter": {
    "allowedProjects": ["6-Month Execution"],
    "allowedTags": ["domain-expansion"]
  },
  "pollIntervalSec": 60
}

export VISION_CONVEX_URL="https://api.conquoreum.com"
export VISION_API_TOKEN="cqk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
export VISION_VAULT_PATH="/absolute/path/to/your/obsidian-vault"

node dist/cli.js sync     # one-shot
node dist/cli.js watch    # poll forever, also applies check-off write-backs
Full variable list: Environment variables.

​
4. Turning it on and sharing with your Companion

Board sync is off by default, even once everything above is running — Conquoreum’s server has its own master switch (syncEnabled, defaults off) that discards even allowlisted data until you opt in. Turn it on in the app under Privacy / Connected Apps.
PreferenceDefaultEffect
syncEnabledoffmaster switch — off means the server stores nothing
shareWithCompanionofflets your Companion see your open day tasks
hideTaskTitlesonwhen shared, sends status only — titles stay private
perSkillSharenonewhich skill lanes your Companion may see

​
5. Ticking tasks off

Ticking a task off in the app doesn’t edit your vault instantly — the app queues the change, and the bridge (the only thing that ever writes to your vault) applies it on its next poll. Expect up to one poll interval of delay. Reopening a completed task never claws back XP.
Free tier: connect 1 folder. Premium tier: unlimited folders + bonus features. Manage your subscription in the iOS app under Settings.