Wiki home · related: Trust · Glossary · full rules: knowledge rules

A card is one Markdown file in AuroraKnowledgeDB/ that holds the knowledge about one entity — a concept, a process, a system, a role, a status, a requirement. It is not a summary of a document: five documents about one subject feed one card, and a side explanation inside a card is moved out into its own card and left as a link.

---
title: "Refund"
aliases: ["Return of payment"]
type: concept
status: draft
kind: knowledge
sources:
  - "Sources/Confluence/Payments/Refund.md"
built: machine
created: 2026-09-01
updated: 2026-09-01
related: ["Payment", "Chargeback"]
---

A refund returns money to the payer within ten days of a request. …   ← the thesis, written by the model

## Source (carried over verbatim)

…the original text, moved by a script, never retold…

## Change history

- 2026-09-01: card created

One parser reads the head (aurora_common.frontmatter): a list may be written inline (aliases: ["A", "B"]) or as a block (aliases: with - "A" items below) — the graph, search, embeddings and maps of content see both forms the same way. A blank line or a # … comment inside a block does not close it. The body starts after the closing --- line; a triple dash inside a value (title: "Retro --- results") does not end the head.

The kind is stronger than the status: a trusted dictionary still must not be retold.

The type (type) is what the card is about and by which template it is made; the kind (kind) answers a different question — "who edits the body". Every type has a template — a file TemplatesCommon/akdb_<type>_v1.0.md: the type's passport (name, base section, allowed kinds and statuses, body sections), a head and body skeleton, an example and a self-check list. It is read by a human, an assistant and the engine itself. There are thirteen types:

Unsure which type to choose — take concept; the borders of neighbouring types are worked out in the templates themselves. The template: field in the head names the file the card was made by (template: akdb_concept_v1.0.md); older cards do not have it — that is a "pre-template" card, not an error. The list of types and sections is kb:cards --list, the check is kb:cards --check (and the "card templates" section of kb:lint). For now the check only advises: it rewrites nothing and forbids nothing. A released template is not edited — a fix comes as a new version (v1.1).

Project rules. The type is chosen by the instruction "How to determine the card type" — the file Prompts/KB_classify.md: steps 0–7, the answer in one line type: …; template: …; section: …; why: …. The file belongs to the project: your edit stays, the kit's new version lands next to it as .new; kb:cards --guide prints the text. A type's title, description and switch are the cards: block of aurora.config.yaml. For now the switch only advises: the check names the cards of a switched-off type, the classifier rejects such a type, and creating cards does not look at it. The type catalogue AuroraKnowledgeDB/meta/card_types.md is generated (install, update --apply, kb:cards --write --apply), manual edits in it are lost. All of this is edited in "Project settings → Card types". Details — card templates.

stateDiagram-v2
  [*] --> draft: parsed
  [*] --> placeholder: a link exists, no card yet
  placeholder --> draft: a definition appeared
  draft --> knowledge: kb#58;trust — sources trusted
  knowledge --> draft: an issue went back to work
  knowledge --> deprecated: kb#58;supersede
  draft --> deprecated: kb#58;supersede

• A card is an entity. If you find two cards about one thing, kb:twins / agent:twins bring them together — the model decides, not a human.
• Links are mandatory. A card nobody can reach is on disk but not in the base (kb:links --cards, kb:moc).
• The engine does not rewrite what it did not write. Dictionary and document bodies, the history footer and the previous thesis are kept.
• File names must pass on Windows, macOS and Linux — no < > : " / \ | ? *, not CON/NUL, up to 255 bytes. The check is kit:doctor; the fix is kb:names. → Windows and macOS

Deeper: knowledge rules · one-page summary · card templates · the path of one card.

This wiki is generated from the wiki/ folder of the repository — edit the pages there, changes made here are overwritten. · RU-Home