design overview
SAPCT + NKPZ classes, entity styles, CSS, and the OLI-it meaning
Class overview
This page demonstrates the current real OLI-it classes and entity card styles used in the application.
| Class group | Class | Example purpose in design overview |
|---|---|---|
| SAPCT | S | Stamm (author/source in the cycle) |
| A | Angler (filter profile / receiver logic) | |
| P | PostIt (message payload) | |
| C | Code/classification cues in the message context | |
| T | TopLab (answer/response) | |
| NKPZ | N | Netz (network structures in Wortraum) |
| K | Knoten (nodes) | |
| P | Pfad / process path in communication flow | |
| Z | Zweig (branches in tree-like structures) |
Entity design samples (real classes)
These samples render the same shared partials used by Stamm/PostIt/Angler/TopLab pages.
Looking for a project partner
This PostIt represents the message payload with motivation and topic details.
Angler: Data Engineering Filter
Date Created:
2026-05-22
Scanned:
Yes
Description: Angler receives and filters matching PostIts.
Candidate response
TopLab is the response sent back into the Kreislauf.
Flow documentation
Mermaid flow diagrams and editable architecture assets are documented in
docs/design-overview-page/README.md.