A shared state model for consistent behavior
Sectile derives the next state and ordered work from the current state and input. Navigation, selection, editing, validation, dates, tables, and virtualization compose through contracts that define results, failures, and cost bounds together.
Behavior contracts for results, failures, and cost
A public contract covers successful results, failure behavior, and computational cost. The same input trace remains verifiable as implementations change.
- State
- Represent position, selection, expansion, text, and validation facts as values.
- Operations
- Accept semantic input and calculate a new state with ordered work.
- Failures
- Return typed errors for rejected input while preserving the previous state.
- Cost
- Include time, space, allocation, and retained-resource bounds in the public contract and evidence.
State models by problem domain
Each package owns one problem domain and connects through public values and operations.
CoreSequence, range, grid, and tree structures with transitions, commands, and failuresFormField paths, values, validation, errors, submission, and resetTemporalCivil dates, wall-clock time, ranges, and calendar operationsTabular · Virtual · ChartTabular data, viewport layout, measurement, chart models, and queries