Boards

Boards help teams move records through visible process stages without creating a separate tracker beside the governed data. A board item can carry status, responsibility, due dates, comments, attachments, links, and history while still pointing back to the record or resource the work is about.

Use this section to understand board screens, cards, statuses, transitions, movement, responsibility, cycles, filters, and board-specific collaboration.

Board Security controls which items each person can see and which exact actions they can perform. Lists and counts include only items allowed by BoardItem.View; card target details are shown only when both the Board and the target record allow that projection. Status columns remain visible process structure and do not reveal denied items. A newly configured Board starts fail-closed until an administrator assigns executable View Statements.

Board Constraints and reusable Board Statements can be authored, validated, and enabled. Moltaro enforces event constraints during Board operations and status invariants while governed Board Items, Board Data, or Entity targets are mutated. Board Automation Rules are a separate future after-commit mechanism whose implementation has not started.

Developers and AI agents automating boards over the API should start with the Boards configuration walkthrough and the Boards runtime walkthrough.