SCHEMA

Conventions for the Lakuyo Obsidian vault (same pattern as HaloRT docs).

Folders

Folder	Purpose
Product/	Vision, personas, business model, roadmap, founding decisions
Architecture/	System design summaries (detail specs stay in control-plane)
Surfaces/	One note per product surface (docs, Android, iOS, backend, …)
Team/	Collaboration and ownership
Guides/	How-to and release process
Ops/	Hostnames, DNS, deploy notes (no secret values)
Projects/	Project hub
Meta/	Vault meta, repo map
assets/	Images
private/	Ignored by Quartz — do not publish

Frontmatter

title: "Note title"
created: YYYY-MM-DD
updated: YYYY-MM-DD
type: meta           # idea | issue | task | process | meta | project
tags: [project/lakuyo, type/meta, status/current]
status: current      # current | archived
project: lakuyo

Linking

Prefer Obsidian wikilinks ([[Product/Vision]]) so Quartz graph and backlinks work.

Hub entries: index · Lakuyo · Overview.

Specs vs docs

Concern	Repo
Product narrative, decisions, guides	This vault (lakuyo-docs)
Behavioural specs, contracts, implementation status	lakuyo-control-plane

If a decision changes required behaviour, update the matching control-plane spec in the same change set.