Appearance
Fields
Fields describe data attached to things in Anchorline.
They let you record structured information without turning logs or items into free-form notes or rigid schemas.
What fields are
A field is a named piece of data.
Fields can describe logs, items, links, or events depending on context. They capture details like status, category, notes, dates, or any other information that helps explain what something is or how it is used.
Fields answer the question: what do we know about this.
Fields do not replace events
Fields do not change history by themselves.
When a field value changes, that change is recorded as an event. The field's current value is derived from its history, just like everything else in Anchorline.
Fields describe state. Events describe change.
Item fields
Item fields describe properties of individual items.
Examples include:
- Status
- Location
- Condition
- Tags
- Custom attributes specific to a collection
When an item field changes, the update is recorded as an event on the collection log.
Log and link fields
Fields can also exist on logs and links.
Log fields describe properties of the log itself, such as purpose or classification. Link fields describe how two items relate, such as role, quantity, or notes about the relationship.
These fields add context without collapsing structure.
Custom fields
Fields can be customized to match your system.
You are not limited to a fixed set of attributes. Custom fields let you model real-world details without forcing everything into generic labels.
As with all fields, changes are recorded, not overwritten.
Why fields matter
Fields add meaning without adding fragility.
They let you enrich logs and items while preserving clarity, history, and structure. Because field changes are recorded as events, you can always understand how and when details evolved.
Fields work best when they explain state, not when they try to encode process.
A simple guideline
If something describes what it is, use a field. If something describes what happened, use an event.
Keeping this separation clear makes systems easier to understand and maintain.