document explicit set levels
This commit is contained in:
parent
8e38b8f7e8
commit
98a4e2e007
1 changed files with 7 additions and 4 deletions
11
ai/shared.md
11
ai/shared.md
|
|
@ -9,14 +9,17 @@ these rules.
|
|||
- Attainly is in early development.
|
||||
- Attainly helps users break hierarchical goals into scheduled assignments,
|
||||
complete daily work, and track progress toward a target date.
|
||||
- Schedules target whole sets. Users choose an element kind as the assignment
|
||||
- Sets define explicit ordered element levels. Every depth has one kind, and
|
||||
a kind can appear at only one depth within a set. Root elements use the
|
||||
first level, and children use the level immediately after their parent.
|
||||
- Schedules target whole sets. Users choose a set level as the assignment
|
||||
granularity. To schedule a subset, create a separate named set containing
|
||||
that subset.
|
||||
- Schedules are immutable historical snapshots. Copy the set name and each
|
||||
assignment's name, kind, and full path when creating a schedule.
|
||||
- Persisted schedules must not reference their source set, and persisted
|
||||
assignments must not reference their source elements. Later source edits or
|
||||
deletions must not change an existing schedule.
|
||||
- Persisted schedules must not reference their source set or selected level.
|
||||
Persisted assignments must not reference their source elements. Later
|
||||
source edits or deletions must not change an existing schedule.
|
||||
- Schedule recalculation must preserve completed work while redistributing
|
||||
unfinished assignments across the remaining dates.
|
||||
- Planned features in `README.md` are future ideas, not authorized scope.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue