Glossary A-Z
Every term Fito’s knowledge model uses, in alphabetical order. Each entry is the short form. Where a page covers a term in full, the entry links to it.
This glossary is the one place each of these words is defined. The rest of the guide uses them and links back here, term by term — every entry below has its own anchor, so a link can land on the word rather than on the page.
Alternative definition
Section titled “Alternative definition”The same idea captured in different words, by a different author or for a different audience. It is a component in its own right, with its own reference id, linked to the one it sits beside. It is not a version of anything and it does not replace what it sits beside. See Versions and alternative definitions.
Applies to
Section titled “Applies to”The panel on a component’s page listing the major lines that component describes. Every one of them belongs to the same technology.
Bloom level
Section titled “Bloom level”A target level, declared in a case’s files: KNOWLEDGE, COMPREHENSION or
APPLICATION. A case declares one on a rubric criterion, a quiz question, a
prerequisite and a learning objective. It is the intention — what a case aims
at, never what you hold. On a criterion or a question, it is the depth a score
of 2 or 3 certifies.
The unit of practice. A case declares what it teaches, what it expects, and how it is scored, and you work it in the terminal.
Competence
Section titled “Competence”A named, standing capability in Fito’s competence registry, formed by elements and demanded by one or more technologies. It exists whether or not any case mentions it. See Competences and learning objectives.
Competence element
Section titled “Competence element”One leaf of a competence, defined by exactly one knowledge component. It carries no Bloom level, and the elements of one competence all define different components.
Concept
Section titled “Concept”One of the three component types: domain vocabulary and the conceptual model. Example: “Idempotence in HTTP”.
Execution fact
Section titled “Execution fact”One of the three component types: a behavioral fact about how the technology
works at runtime. Example: “PUT must be idempotent”.
A technology’s classification, either tool or practice. Two values only, and
practice means everything that is not a tool. See
Technologies, tools and practices.
Knowledge component
Section titled “Knowledge component”The unit of the vocabulary: one small, separately addressed piece of knowledge about a technology, in one of three types. See Knowledge components.
Learning objective
Section titled “Learning objective”One edge a single case declares about itself — a knowledge component plus the
Bloom level that case targets for it, with a description and a weight of
PRIMARY or SECONDARY.
Major line
Section titled “Major line”A technology’s release line, labelled 7 rather than 7.1.4. For a practice
the label is Fito’s own numbering and matches nothing outside Fito.
Practice
Section titled “Practice”practice. A technology kind meaning everything that is not a tool — techniques
and methodologies included.
Prerequisite
Section titled “Prerequisite”A knowledge component and Bloom level a case expects you to arrive with. The same kind of edge as a learning objective, tagged differently.
Proficiency
Section titled “Proficiency”A recorded state on your profile for one knowledge component:
NOT_ACHIEVED, KNOWLEDGE, COMPREHENSION or APPLICATION. It is the record
— what the profile keeps. The absence of a value means never assessed;
NOT_ACHIEVED means assessed, and the criterion not met. See
Bloom levels and proficiency.
Reference id
Section titled “Reference id”A component’s canonical identifier, shaped
<type>:<technology-slug>.<component-slug> — for example
concept:javalin.handler. It is what a case pins and what URLs route on, and it
never changes once published.
Revision
Section titled “Revision”A component’s own content history, shown as Revision 1.0.0. A revised
component is a new component linked to the one it replaces, never an overwrite.
Rubric criterion
Section titled “Rubric criterion”One scored line of a case’s rubric. It names a knowledge component and a Bloom
level. A score of 2 or 3 records that Bloom level as your proficiency for the
component; a score of 0 or 1 records NOT_ACHIEVED.
The measurement: how well your work met one rubric criterion or quiz question, from 0 to 3 — not met, partly met, met, met well. A score says how well, never how deep; the depth is the Bloom level the criterion or question declares. See How a case is scored.
The lower-case, dash-separated form of a name, used in ids and URLs. A technology has one; so does a component, and so does a major line.
Technology
Section titled “Technology”The subject knowledge hangs off — a tool such as Javalin, or a practice such as Hexagonal Architecture. Every component belongs to exactly one, and every technology has at least one major line.
Template
Section titled “Template”The field schema a component of a given type is written against: the keys, labels, order, and whether each field is one value or a list. Loaded by the backend’s seed script, with no editing interface.
tool. A technology kind meaning concrete software — a library, a framework, a
command-line program. The other kind is practice.
Usage scenario
Section titled “Usage scenario”One of the three component types: a goal-oriented pattern for applying the technology. Example: “Implementing an idempotent payment endpoint”.
What’s next
Section titled “What’s next”- Knowledge components — the unit the rest of the model is built from.
- Browse the knowledge area — see these words on screen.