configure-whiteboard

To automate whiteboard setup in Obsidian, you can trigger a command that creates a fresh Original Whiteboard. This enforces a consistent flat-architecture by generating the 原白板/ file and 节点/ seed notes automatically.

Yes, you can generate seed notes from an existing Markdown file by passing the file path as a parameter. This derives a new Original Whiteboard directly from your specified MD path, promoting quick project initialization.

The v3 flat-architecture is a vault structure where the whiteboard is stored as 原白板/<board>.md and node seeds live in 节点/. It reads the subject from .canvas-config.yaml to ensure vault-wide consistency and prevents writes to deprecated wiki paths.

The whiteboard creation workflow enforces a seven-step process that reads subjects, parses parameters, detects conflicts, and classifies seeds. It issues explicit user prompts at key decision points to ensure accurate directory creation and structured receipt generation.

Yes, the Original Whiteboard setup reads the vault subject directly from the .canvas-config.yaml file. This ensures vault-wide consistency and avoids using deprecated paths during the automated whiteboard and seed note creation process.

A key limitation is that the configuration process avoids deprecated wiki and canvases paths entirely. It strictly enforces a v3 flat-architecture, meaning all whiteboard files and node seeds must conform to the 原白板/ and 节点/ directory structure.