mneme-cli 0.4.0__py3-none-any.whl

mneme/templates/workspace/README.md

@@ -0,0 +1,33 @@
+# {{PROJECT_NAME}}
+
+A Mnemosyne knowledge workspace.
+
+## Quick start
+
+```bash
+# from inside this directory
+mneme stats
+mneme ingest path/to/document.md {{DEFAULT_CLIENT}}
+mneme search "your query"
+```
+
+Or from anywhere:
+
+```bash
+mneme --workspace /path/to/{{PROJECT_SLUG}} stats
+```
+
+## Layout
+
+```
+{{PROJECT_SLUG}}/
+  wiki/{{DEFAULT_CLIENT}}/   structured markdown pages
+  sources/{{DEFAULT_CLIENT}}/  immutable source archive
+  schema/                    entities, graph, tags, traceability
+  memvid/                    semantic search archive (created on first sync)
+  inbox/                     drop files here, run `mneme tornado`
+  index.md                   master catalog
+  log.md                     activity timeline
+```
+
+Created with `mneme new` on {{CREATED_DATE}}.

mneme/templates/workspace/index.md

@@ -0,0 +1,18 @@
+# {{PROJECT_NAME}} - Index
+
+Last updated: {{CREATED_DATE}}
+
+## Clients
+
+### {{DEFAULT_CLIENT}}
+(no pages yet)
+
+## Shared Knowledge
+(no pages yet)
+
+---
+
+| Metric | Count |
+|---|---|
+| Total pages | 0 |
+| Total sources | 0 |

mneme/templates/workspace/log.md

@@ -0,0 +1,6 @@
+# {{PROJECT_NAME}} - Log
+
+## [{{CREATED_DATE}}] INIT | Workspace scaffolded via `mneme new`
+- Project: {{PROJECT_NAME}}
+- Default client: {{DEFAULT_CLIENT}}
+- Profile: {{PROFILE}}

mneme/templates/workspace/profiles/README.md

@@ -0,0 +1,109 @@
+# Workspace-local profiles
+
+Drop a `<name>.md` file here to define a profile local to this workspace.
+Workspace profiles **shadow** any bundled profile with the same name, so you
+can either add a brand-new framework or override a bundled one with
+project-specific tweaks.
+
+## Format
+
+A profile is a markdown file with YAML frontmatter for the structured fields
+and recognized H1 headings for the writing-style prose. The simplest possible
+profile:
+
+```markdown
+---
+name: My Profile
+description: A short description
+version: 1.0
+tone: formal
+voice: passive-for-procedures
+trace_types: [derived-from, implemented-by, verified-by]
+requirement_levels:
+  shall: mandatory
+  should: recommended
+vocabulary:
+  - use: medical device
+    reject: [product, unit, item]
+  - use: nonconformity
+    reject: [bug, defect]
+---
+
+# Principles
+
+- Be specific.
+- Cite everything.
+
+# General Rules
+
+- Avoid editorial language.
+- Define every term at first use.
+
+# Terminology
+
+| Use | Instead of | Why |
+|---|---|---|
+| medical device | product, unit | The term is reserved by EU MDR. |
+
+# Framing: Reporting a result
+
+**Wrong:**
+
+> The algorithm is highly accurate.
+
+**Correct:**
+
+> The algorithm achieved 0.91 MCC against the reference standard.
+
+**Why:** state the number, not the editorial judgement.
+
+# Document Type: design-validation-report
+
+A description of this document type goes here as plain prose.
+
+## Section: context
+
+Per-section guidance for the `context` section of a design-validation-report
+goes here. The agent will pull this in when reviewing a page whose
+frontmatter says `type: design-validation-report`.
+
+# Submission Checklist
+
+- All references include ID and version
+- No clinical claims
+```
+
+## Recognized H1 headings
+
+| Heading | What it becomes |
+|---|---|
+| `# Principles` | `writing_style.principles` (each `-` bullet is one entry) |
+| `# General Rules` | `writing_style.general_rules` (bullets) |
+| `# Terminology` | `writing_style.terminology_guidance` (parsed from a 3-column table: Use / Instead of / Why) |
+| `# Framing: <context>` | one entry in `writing_style.framing_examples` (parses **Wrong:**, **Correct:**, **Why:** blocks) |
+| `# Document Type: <slug>` | `sections[<slug>]`. Body before any `## Section:` becomes the description |
+| `## Section: <slug>` (under a `# Document Type:`) | `sections[<doc-type>].section_notes[<section-slug>]` |
+| `# Submission Checklist` | `submission_checklist` (bullets) |
+
+Unrecognized H1 headings are silently ignored - you can use them for
+authoring notes that should not affect mneme's behavior.
+
+## Activate it
+
+```bash
+mneme profile set my-profile        # name without the .md extension
+mneme profile show
+```
+
+## Use it
+
+```bash
+mneme harmonize my-client                          # vocabulary check
+mneme harmonize my-client --fix                    # auto-fix vocabulary
+mneme validate writing-style my-client/some-page   # build LLM review packet
+```
+
+## CSV mappings
+
+Workspace-local CSV column mappings (used by `mneme ingest-csv`) live in
+`profiles/mappings/<name>.json`. The same shadowing rules apply.

mneme/templates/workspace/schema/entities.json

@@ -0,0 +1,5 @@
+{
+  "version": 1,
+  "updated": "{{CREATED_DATE}}",
+  "entities": []
+}

mneme/templates/workspace/schema/graph.json

@@ -0,0 +1,6 @@
+{
+  "version": 1,
+  "updated": "{{CREATED_DATE}}",
+  "nodes": [],
+  "edges": []
+}

mneme/templates/workspace/schema/tags.json

@@ -0,0 +1,5 @@
+{
+  "version": 1,
+  "updated": "{{CREATED_DATE}}",
+  "tags": {}
+}

mneme/templates/workspace/wiki/_templates/page.md

@@ -0,0 +1,31 @@
+---
+title: [Page Title]
+type: [overview|entity|concept|source-summary|comparison|deliverable]
+client: {{DEFAULT_CLIENT}}
+sources: []
+tags: []
+related: []
+created: YYYY-MM-DD
+updated: YYYY-MM-DD
+confidence: medium
+---
+
+## Summary
+
+[2-3 sentences. Specific. No abstractions.]
+
+## Key Facts
+
+- [Fact 1] (source: filename)
+
+## Detail
+
+[Main content]
+
+## Open Questions
+
+- [What we don't know yet]
+
+## Cross-References
+
+- [[related/page-1]]