Docs / Cards
What a card is
A card is one processing step, and everything that changes its output is on its face.
The rule the built-in cards follow
Anything that changes the result appears as a parameter. A
value hard-coded in the implementation is treated as a bug, because it is invisible
to whoever reads the pipeline later.
What a card is made of
| Manifest | card.json: identity, ports, parameters. Also draws the card, so there is no separate interface to write |
|---|---|
| Implementation | Usually run.py, a single function receiving a context |
| Panel | Optional panel.html for a custom editor |
Where they come from
Built-in cards ship with the application and are validated. Community cards come from the marketplace, reviewed before publication but not run through the validation harness. Your own cards live in your user directory and appear in the palette without a build step.
Every card, listed
The card reference is generated from the manifests, so it cannot drift from the software. Each card has a page with its ports, its parameters, its defaults and its validation figures.