--- type: types/type-spec.md name: entity description: Base type for entity pages - projects, systems, tools, technologies or people schema: types/entity.schema.yaml subtype_field: entity_type base_dir: entities page_ref_fields: [related, sources] layout: project: {dir: projects, title: Projekte} system: {dir: systems, title: Systeme} tool: {dir: tools, title: Werkzeuge} technology: {dir: technologies, title: Technologien} person: {dir: people, title: Personen} --- # Entity `entity` is the type for concrete things: projects, systems, tools, technologies or people. Entities are the primary building blocks of the knowledge graph. ## Contents - [When to use](#when-to-use) - [When NOT to use](#when-not-to-use) - [Frontmatter](#frontmatter) - [Authoring guidance](#authoring-guidance) - [Template](#template) ## When to use - Representing a software project, an initiative or a piece of work - Documenting a running system, service or infrastructure component - Describing a CLI tool, utility or software library - Recording information about a language, a framework or a protocol - Documenting a person, a team or an organization ## When NOT to use - For abstract concepts, patterns or methodologies (use `concept`) - For source documents or ingested material (use `source`) - For comparative analyses (use `comparison`) ## Frontmatter | Field | Required | Use | |---|---:|---| | `type` | Yes | `types/entity.md` | | `entity_type` | Yes | One of: project, system, tool, technology, person | | `tags` | No | Navigation tags for categorization | | `created` | Yes | Creation date (YYYY-MM-DD) | | `modified` | Yes | Date last changed (YYYY-MM-DD) | | `related` | No | Titles of related pages (entities, concepts, sources) | | `sources` | No | Titles of the source pages backing this page's claims | | `provenance` | Yes | sourced, general or mixed | | `summary` | Yes | One-liner for `kb/index.md` | ## Authoring guidance - The title is the entity's canonical name and follows the subject's established designation, not the KB language (`kb/CONTRACT.md` § "Titles are identifiers", `kb/CONVENTIONS.md` §§ "Naming" and "Language") - The main description goes near the top - Link to related entities and concepts wherever relationships exist - Under `provenance: sourced` or `mixed`, back hard facts inline with a `[^cite-id]` footnote - `tools/wikitool cite add --page "" --source "Source - X"` mints the id and its definition - Wikipedia register: factual, neutral, no marketing language ## Template The block below is page material, so it is written in this instance's KB language (`kb/CONVENTIONS.md` `language:`) rather than in the control plane's English - its headings become the headings of every page `wikitool new entity` scaffolds. ```markdown # {name} **Typ:** {entity_type|capitalize} ## Beschreibung TODO: 1-2 Absätze dazu, was diese Entity ist und wozu sie dient. ## Kerndaten - **Zweck:** TODO - **Status:** aktiv, abgelöst, in Planung usw. - **Version:** TODO (falls zutreffend) - **Sprache/Technik:** TODO (falls zutreffend) - **Verantwortlich:** TODO (falls zutreffend) - **Repository:** TODO (falls zutreffend) ## Details TODO: Ausführliche Informationen, nach sinnvollen Abschnitten gegliedert ## Historie - [{today}] - Page created via wikitool ``` The relationships section is deliberately **not** in the template: it is a generated region that `wikitool xref` creates between markers on the first edge entry and re-renders from `related:`. An author never writes into it. The value behind `**Typ:**` stays the English enum value - that is what `search --field` filters on. --- Additional notes: - Entity pages form the concrete inventory of the knowledge base - Every entity type (project, system, tool and so on) is a variant of this base type - The relationships between entities carry the knowledge graph's interconnection