CONTEXT.md

Rama main · réplica de lectura del repositorio original.

# Context Glossary

Domain terms for the homelab repo. Implementation details belong in specs/plans, not here.

## Homelab Landing Page

The public one-page site at the apex domain, distinct from both the documentation site and from the daughter's art portfolio. "Service" was previously used for three different things; each now has its own term and exactly one source of truth.

### Language

**Landing Page**:
The public one-page site at `homelabor.net`, whose purpose is to make a hiring audience take the infrastructure seriously.
_Avoid_: Portfolio (that name is taken by the art site), homepage (that is the internal dashboard)

**Documentation Site**:
The MkDocs site at `docs.homelabor.net` holding setup guides and host references.
_Avoid_: Docs site, wiki

**Compose Stack**:
One directory under `compose/<host>/<name>/` containing a compose file, in any of its three accepted spellings: `docker-compose.yml`, `compose.yml` or `compose.yaml`. Both `compose.yaml` spellings are in use here, so a definition naming only `docker-compose.yml` undercounts by two. A directory holding no compose file is not a Compose Stack, however it is named. This is the unit the repo version-controls, and therefore the only service count that can be derived rather than asserted.
_Avoid_: Container, app, service

**Proxmox Guest**:
One LXC container or VM on the hypervisor. Includes things that are not Compose Stacks at all, such as AdGuard, Vaultwarden and n8n.
_Avoid_: VM, node, machine

**Monitored Service**:
One Uptime Kuma monitor. Not one-to-one with either count above: some services carry two monitors (an internal check plus a public tunnel check), and some Compose Stacks have none.
_Avoid_: Check, probe

**Publicly Monitored Service**:
The curated subset of Monitored Services shown on the public status page. Deliberately smaller than the full set, because every name on that page is a public statement about what the infrastructure is for.
_Avoid_: Public service, exposed service

**Self-Hosted End to End**:
The claim that every part of the public path is operated by the owner, including the tunnel onto it - no third-party provider, no forwarded ports, and no third-party origin fetched by the browser. It is a claim a visitor can check, so anything the pages load from someone else's domain contradicts it directly rather than merely falling short of it.
_Avoid_: Self-hosted (unqualified - the whole point is the "end to end")

**Uptime**:
The thirty-day availability figure. The twenty-four hour figure exists in Uptime Kuma but is never shown publicly, because a single outage distorts it past usefulness.
_Avoid_: Availability, SLA

## Brand

The visual identity shared by the owner's public properties. There is one brand and it is the person, not the infrastructure: the Landing Page title, its hero kicker and the Documentation Site name all read "Norbert Csicsay", and the Landing Page exists to answer a question about a specific person rather than to sell a product.

### Language

**Mark**:
The single symbol identifying Norbert Csicsay wherever his properties appear - favicon on both sites, Documentation Site header, share card, CV header. It is diagrammatic rather than a monogram: one hypervisor over two guests, taken from the topology map and reduced until it still reads at 16px. There is exactly one, and the infrastructure has no separate mark of its own.
_Avoid_: Logo (implies a company or product mark, which is the confusion this term exists to prevent), monogram (it is deliberately not one), brandmark, icon

**Portrait**:
The owner's face, from a real photograph, used where a person rather than a property is being identified - GitHub avatar, Documentation Site authorship, CV. Distinct from the Mark and never a substitute for it.
_Avoid_: Avatar, headshot, profile picture

**Brand Tokens**:
The values the properties hold in common: accent colour and typefaces. Background and surface colours are deliberately not among them - the Landing Page is dark-only by design, and the Documentation Site keeps its own light and dark reading surfaces. There is no shared spacing scale; spacing is written inline per surface.
_Avoid_: Theme, palette (both imply a full surface treatment, which this deliberately is not)

**Framed Artifact**:
A surface presented inside another one as a bordered inset rather than bled into it, and therefore allowed its own palette and typeface. The topology map is the only one: its colours key node type in a legend, so they carry information rather than decoration, and the Landing Page already sets it in a bordered plate. Its palette differing from the Brand Tokens is a property of what it is, not a defect.
_Avoid_: Embed, widget, diagram (the last is what it depicts, not what it is here)

**Display Face**:
A typeface used for one surface's headline treatment rather than shared across the properties. Only a Framed Artifact gets one. It sits outside the Brand Tokens on purpose, because a face chosen for one page's headline is not a claim about the others.
_Avoid_: Heading font, brand font

## Daughter's Art Portfolio Site

- **Category** — a grouping of drawings shown as a filterable tab in the gallery (e.g. "Csendelet", "Anime karakterek"). Backed by a folder under `content/`. Has two distinct names:
  - **name** — the folder name on disk (e.g. `csendelet`, `anime-karakter`). Technical identifier: used for file paths and as the internal filter key. Not shown to the user.
  - **label** — the human-readable, properly accented/capitalized text shown on the tab (e.g. "Csendelet", "Anime karakterek"). Never derived automatically from `name` — always explicit, so Hungarian accents and casing are correct.

## Pedikur

The pedicure practice management tool at `compose/proxmox-lxc-100/pedikur/`.
The practitioner works from fixed premises in Slovakia; statutory receipt
issuing stays outside this system, so every term below describes practice work,
never bookkeeping.

### Language

**Treatment**:
One named, priced, timed thing the practitioner performs, as it appears in her
price list. The catalogue entry, not an instance of it being carried out.
_Avoid_: Service (the repo already gives that word three infrastructure
meanings), procedure, job

**Visit**:
One client session, whether booked ahead or walked in, from its planned state
through to what was actually done. Booking and treatment record are the same
thing at different points in its life, not two things.
_Avoid_: Appointment (excludes the walk-in), booking, session

**Visit Item**:
One line of what a Visit is charged for: a Treatment, or a Product sold. Holds
the price actually charged, which is why a later price rise cannot rewrite an
earlier Visit.
_Avoid_: Line, charge, entry

**Treatment Recipe**:
What a Treatment is expected to consume, stated as how many Treatments one
unit of a Product lasts for. Asked that way because a practitioner knows a
bottle gives about thirty fills and does not know it gives 0.4 ml a time. It
drives automatic consumption when a Visit is completed, and is an estimate by
nature, reconciled against the shelf by counting.
_Avoid_: BOM, bill of materials, consumables list

**Product**:
Anything held in stock: professional supplies consumed during a Visit, and
goods sold to a client. One catalogue, two ways of leaving the shelf; a
Product with no sale price is one she only uses. Counted in the unit it is bought in - a bottle, a roll, a box - never
in a unit that would have to be converted, so a part-used bottle simply leaves
the stock figure fractional.
_Avoid_: Item, stock item, material

**Stock Movement**:
One recorded change to what is on the shelf, signed: a purchase, an opening
balance, consumption, a sale, a correction or waste. A Product's quantity is
the sum of its Movements, never a stored number, and a Movement is never
edited or deleted - a mistake is corrected by another Movement, which is what
makes the sum something that can be audited.
_Avoid_: Transaction, adjustment, stock entry

**Expense**:
Money out, dated, with a category from a fixed list. Optionally carries line
items, which also bring the goods onto the shelf as inbound Stock Movements,
so a purchase is typed once rather than twice. An Expense with no line items
is just money out.
_Avoid_: Cost, purchase, bill, invoice (nothing here is issued or owed)

**Visit Interval**:
How often a client tends to come back, taken as the median gap between their
completed Visits rather than asked for. A manual value overrides it when the
client states their own rhythm.
_Avoid_: Frequency, cadence, cycle

**Recall List**:
Clients whose Visit Interval has run out and who have no Visit booked ahead,
most overdue first. It stops showing a client once they are past three times
their interval, because by then they have stopped coming rather than being
late.
_Avoid_: Follow-up list, reminders (nothing is sent; this is a list she reads)

**Archive**:
Removing a client from the working lists while keeping every record intact.
Reversible, and the practitioner's own call.
_Avoid_: Delete, deactivate, hide

**Erase**:
Satisfying an erasure request by emptying a client's identifying and health
fields and deleting their photos from disk, while the Visits, their treatments
and their amounts stay. Irreversible, admin only, and distinct from Archive.
_Avoid_: Delete, purge, GDPR delete

**Stock Movement**:
One append-only entry of stock arriving or leaving, carrying its own unit
cost. A mistake is settled by an opposing correction entry, never by editing
or removing the original, so the shelf always follows from the entries.
_Avoid_: Adjustment, transaction, stock change