SCHEMA

Memova Wiki Schema

Domain

Memova project knowledge: product narrative, handwriting recognition research, whitepaper evolution, technical architecture, user workflows, and project decisions.

Conventions

• Use Markdown readable in Obsidian.
• Use wikilinks for related notes.
• Prefer YAML frontmatter for durable pages. At minimum use type; for OKF-compatible notes also include title, description, resource, tags, created, updated, confidence, and status when known.
• Treat index.md files as progressive-disclosure navigation, not as the entire retrieval system.
• Treat log.md as the audit trail for meaningful knowledge-base changes.
• Preserve source evidence and cite it when promoting durable memory.
• Keep source notes in 10_sources/.
• Keep project synthesis in 40_projects/memova/.
• Keep open product/research questions in 50_questions/.
• Secrets, API keys, and credentials may be stored only when the vault owner explicitly requests it. Put them in a dedicated 10_sources/private_credentials/ note marked sensitivity: restricted, and keep them out of ordinary project notes and logs.
• A restricted credential may be projected into a company knowledge base only after the exact destination folder's effective permissions have been inspected and confirmed appropriate for the credential's intended users. Record the verified destination and access scope without repeating the credential in general logs.
• Never copy credentials into summaries, general reports, public artifacts, unrestricted folders, or chat responses. Refer to them by purpose and masked suffix only outside the restricted credential note.
• Private message dumps remain prohibited unless the owner explicitly requests a narrowly scoped archival record.
• Mark speculative, stale, or unverified claims clearly.

Folder Contract

• 00_inbox/ - unprocessed Memova raw material.
• 10_sources/ - Memova source notes.
• 20_concepts/ - reusable concepts from Memova work.
• 30_playbooks/ - repeatable Memova workflows.
• 40_projects/ - Memova project pages.
• 50_questions/ - unresolved Memova questions.
• 90_index/ - Memova navigation and maps.
• _templates/ - note templates.

Operating Rule

Before adding new Memova material, read index.md and search existing Memova pages to avoid duplicates.

Retrieval Priority

• Treat 40_projects/ as the high-value project-outcome layer for Memova. For current product state, strategy, pitch, specifications, research conclusions, and shipped artifacts, inspect it before raw material in 00_inbox/ or 10_sources/.
• Treat 40_projects/memova/ as the canonical synthesis area. Use source layers to verify evidence or recover missing detail, not as the default answer surface when a current project artifact exists.
• Treat 40_projects/memova_pitch_deck_newst1.key as the current canonical pitch deck. Older pitch deck versions are superseded context and must not be restored to the company General/pitch/ folder. Explicitly approved formal supporting materials, such as the public company manifesto, may coexist with the single current deck master.
• High retrieval priority does not imply permission to share. Do not bulk-publish 40_projects/; apply the existing authorship, meeting-record, sensitivity, and explicit-approval boundaries to each artifact.

LLM Wiki Gardener Rule

Daily maintenance should scan the whole vault, not only 00_inbox/Memova. 00_inbox/Memova is the raw/staging layer; durable knowledge belongs in 10_sources, 20_concepts, 30_playbooks, 40_projects/memova, and 50_questions, with navigation updated in index.md and 90_index.