Kinic Wiki

Console

Skip to main content
Skills

Evidence capture

Ingest

Use ingest workflows when source material needs to become durable wiki evidence before review, synthesis, or later query.

SKILL.md

Read the skill as documentation or switch to the exact source.

Frontmatter

name
kinic-wiki-ingest
description
Kinic Wiki workflow skill for ingesting evidence source material into the current canister-backed wiki workflow.

Kinic Wiki Ingest

Use this skill when the user wants to:

  • ingest local markdown, notes, docs, or folders into the wiki
  • normalize evidence source material before wiki synthesis
  • persist selected source material under /Sources/...
  • update existing wiki pages from new evidence
  • repair existing wiki pages only when the edit is part of source intake; otherwise use kinic-wiki-edit
  • initialize or repair an explicit LLM Wiki scope when the user asks for scoped structure
  • refresh database discovery metadata for public retrieval
  • generate conversation wiki pages from evidence sources, preferring one review-ready page unless the source clearly needs a split
  • create review-ready wiki pages without pushing immediately

Do not use this skill for:

  • ad hoc question answering without source intake
  • health-only review of an existing wiki
  • hidden publish or push workflows
  • OKF Context Pack export after wiki structure exists; use kinic-context-pack
  • skill store package lifecycle work; use kinic-skill-registry
  • leakage cleanup or broad existing-node repair without new source ingestion; use kinic-wiki-edit

Core rules:

  • Treat the canister wiki as the source of truth.
  • Organized wiki nodes live under /Knowledge/...; evidence sources live under /Sources/<provider>/<id>.md.
  • Treat local Markdown as review or drafting aid unless the workflow explicitly writes it back through VFS commands.
  • Stop at review-ready unless the user explicitly asks for push. review-ready means edits and any existing or requested log.md updates are complete, but no push or publish step has run.
  • Keep source persistence separate from wiki synthesis.
  • Hand off to kinic-context-pack when the user asks to export a completed /Knowledge/... scope for AI handoff.
  • For conversation sources, default to one generated wiki page rather than a fixed page scaffold.
  • Read current canonical notes before editing them.
  • Preserve settled exact fact spans in facts.md instead of paraphrasing or normalizing them away.
  • Do not rewrite exact values such as dates, money, fractions, spellings, product names, or role labels when a settled source span already exists.
  • facts.md is not a transcript dump. Exclude gratitude, acknowledgements, question phrasing, tentative future plans, scheduled meetings, deadlines, and dated event lines unless they are being routed to their canonical note.
  • When a relevant log.md already exists or the user asks for logging, update it append-only.
  • Do not create log.md by default.
  • PDF handling stays inside kinic-wiki-ingest as source normalization.
  • Use the embedded note-role rules in ingest.md as the trust model. When this skill runs inside the repo and docs/STORE_API.md is available, use that file only as the current repo-local refinement.

Read ingest.md before doing substantive Kinic Wiki ingest work.

Kinic Wiki Ingest Workflow

Goal

Turn source material into review-ready Kinic Wiki updates. Keep raw evidence under /Sources/... and organized notes under /Knowledge/....

CLI Reference

  • Use kinic-vfs-cli for all remote VFS reads and writes.
  • Run kinic-vfs-cli --help for the command list.
  • Run kinic-vfs-cli <command> --help before using an unfamiliar read or mutation command.
  • Use docs/CLI.md as the full CLI usage reference when working inside this repo.

Workflow

  1. Confirm target database and access with status --json.
  2. Inspect existing scope before drafting changes.
  3. Prefer query-context --json for current wiki context.
  4. Use list-nodes for path inventory, overwrite checks, and destructive-operation review.
  5. Use search-remote or search-path-remote to find existing related notes before creating new pages.
  6. Use query-sql for 2 or more known-path reads or bulk overwrite checks.
  7. Persist source material under /Sources/<provider>/<id>.md before linking or synthesizing /Knowledge/....
  8. Write review-ready /Knowledge/... pages through CLI mutation commands only after the write set is clear.
  9. Use read-node --json immediately before overwriting existing nodes and pass the returned etag through mutation guards.
  10. Verify with a representative read and search over the affected prefix.

Content Rules

  • Preserve exact values such as dates, money, fractions, spellings, product names, and role labels.
  • Keep transcript-like acknowledgements, tentative plans, and question phrasing out of facts.md unless they are canonical facts.
  • Route unresolved items to the appropriate question/open item page instead of promoting them into settled notes.
  • Keep source persistence separate from wiki synthesis.
  • Do not move or rewrite existing evidence sources unless the user explicitly asks.
  • Stop at review-ready unless the user explicitly asks to push or publish.

Mutation Safety

  • For existing nodes, always read current content and etag before mutation.
  • Use --expected-etag when the command supports it.
  • For delete-tree, inspect first with list-nodes --prefix <path> --recursive --json and report unexpected paths before deletion.
  • Update an existing relevant log.md append-only when the workflow or user requires logging. Do not create log.md by default.

Handoffs

  • Use kinic-wiki-query for answer-only questions.
  • Use kinic-wiki-edit for existing-node repair without new source intake.
  • Use kinic-context-pack for portable AI handoff after the wiki structure exists.