Level 3: + Board sync

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 five 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 and 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:

Field	Required?	Notes
`pm-task`	Yes	must be the literal boolean `true`
`id`	Yes	stable unique id
`projectId`	Yes	the parent project’s id
`project`	Yes	human-readable project name
`title`	Yes	task title
`type`	Yes	e.g. `task`
`status`	Yes	one of `todo · in-progress · blocked · review · done · closed`
`kind`	No	set to `day` to appear in the daily checklist
`priority`	No	`critical · high · medium · low`, sets XP weighting
`start` / `due`	No	`YYYY-MM-DD`
`tags`	No	carries the skill tag (below)

The bridge silently skips a note missing any required field. 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 five skill lanes:

Lane	Tag
Leadership	`skill/leadership`
Business Acumen	`skill/business-acumen`
Technical	`skill/technical-skills`
Content	`skill/content`
Physical Training	`skill/physical-training`

Tag a task with skill/<category> in its tags list:

tags:
  - skill/technical-skills

Board tasks earn the same XP in every lane. The lane decides which skill tree grows, and priority decides how much. (Physical Training also receives XP from Apple Health workout imports, which is a separate path from board sync.) A task with no skill lane lands in a synthetic unassigned bucket and earns 0 XP. This is the one thing to get right. A lane is resolved in this order, first match wins:

The skill/<category> tag on the task.
A per-project default. Set one and every task in that project inherits the lane without needing its own tag. Set it in the iOS app, or with the /domain-expansion tooling.
Otherwise the task is unassigned and earns 0 XP.

An unrecognised value at any step falls through to the next rather than resolving to a lane that doesn’t exist, so a typo like skill/technical behaves as untagged rather than silently landing somewhere wrong. 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 and tags are allowed to sync. This is fail-closed: nothing syncs until you add something here.

{
  "filter": {
    "allowedProjects": ["6-Month Execution"],
    "allowedTags": ["domain-expansion"]
  },
  "pollIntervalSec": 60
}

VISION_API_TOKEN is a cqk_ key that needs the obsidian:sync scope. Mint it in the app under Connected Apps. A key without that scope is rejected before anything is stored.

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. Board sync is off by default, even once everything above is running. Conquoreum’s server has its own master switch (syncEnabled, off by default) that discards even allowlisted data until you opt in. Turn it on in the app under Privacy / Connected Apps.

Preference	Default	Effect
`syncEnabled`	off	master switch; off means the server stores nothing
`shareWithCompanion`	off	lets your Companion see your open day tasks
`hideTaskTitles`	on	when shared, sends status only; titles stay private
`perSkillShare`	none	which skill lanes your Companion may see

perSkillShare filters skill-tagged tasks only. A task with no lane (unassigned) belongs to you rather than to any lane, and is always shared while shareWithCompanion is on; otherwise an empty lane list would hide your entire board. If you want an untagged task kept back from your Companion, turn off shareWithCompanion, or leave hideTaskTitles on so only its status is sent.

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, so expect up to one poll interval of delay. Reopening a completed task never claws back XP.

Board sync is part of the Reality Harness subscription. It is not included in the free tier or in the other subscription tiers. Without it the board routes answer payment_required and nothing syncs. Subscribe or manage it in the iOS app under Settings.

6. Reaching your board from anywhere

Once Level 3 is syncing, the board is also reachable remotely: the remote MCP endpoint lets any MCP client read your week view and tick tasks off over HTTPS with a board:read / board:write key. A remote check-off awards XP through the same server logic and lands back in your vault on the bridge’s next poll.

Get Started

Reality Harness

API Keys & Scopes

Troubleshooting

Level 3: + Board sync

1. Your Obsidian board

2. Tagging for skill lanes

3. The board-sync bridge

5. Ticking tasks off

6. Reaching your board from anywhere

​1. Your Obsidian board

​2. Tagging for skill lanes

​3. The board-sync bridge

​4. Turning it on and sharing with your Companion

​5. Ticking tasks off

​6. Reaching your board from anywhere

1. Your Obsidian board

2. Tagging for skill lanes

3. The board-sync bridge

4. Turning it on and sharing with your Companion

5. Ticking tasks off

6. Reaching your board from anywhere