Specification

Changelog

Initial standalone draft of tasknotes-spec including:

0.3.0-rc.6 - Unreleased#

Move app behaviour out of the tasknotes.task binding into the collection's TaskNotes settings record (_settings/dev.tasknotes.md, contract tasknotes.settings 1.0.0): nlp, templating, time_tracking, archive.move_on_archive, archive.folder, recurrence.reset_body_checkboxes, links.write_format, and each status definition's next_status, exclude_from_cycle, auto_archive and auto_archive_delay_minutes.
Readers take each moved setting from the record, then from an rc.5 binding, then its default, so a collection still on rc.5 keeps its behaviour.

Make assignees links to mdbase.person records, declared in collection.links and resolved by mdbase link resolution, replacing the person-ID assignments of rc.4. This matches how projects are linked and lets person notes show their assigned tasks as backlinks.

Add optional portable person-ID assignees to the task record contract.
Define exact identity matching, unresolved-reference preservation, explicit clearing, and recurrence inheritance without granting collection access.
Published rc.3 contract artifacts remain unchanged; implementations must explicitly opt into rc.4 field mappings.

define manual ordering as an opaque string rank so clients can insert and reorder tasks without renumbering an entire view

add first-class attachments as an ordered frontmatter list of portable file links, with explicit membership, canonical-path, reference-safety, and materialized-occurrence semantics
expose attachment references in the tasknotes.task mdbase contract while leaving binary metadata authoritative in the file store

adopt the discriminated first-class mdbase contract shape for tasknotes.task, including explicit contract_type: record
add the tasknotes.task.completed 1.0.0 event contract and minimal privacy-preserving event-data schema for the mdbase interoperability profile
separate type-file record implementation bindings from application-level event-source declarations

add optional materialized-occurrences profile for recurrence occurrence notes, on-completion materialization, and occurrence-state reconciliation
add optional NLP trigger configuration so TaskNotes clients can share capture suggestion vocabulary
replace the private x-tasknotes discovery envelope with the first-class tasknotes.task 0.2.0 mdbase data contract, portable task-view schema, and implementation binding schema
document the precedence and consistency rules between JSON Schema, collection, lifecycle, contract field mappings, and TaskNotes behavior

Initial standalone draft of tasknotes-spec including:

motivation, scope, and normative conventions
terminology
task model and field mapping
temporal semantics
recurrence semantics
operation semantics
validation model
conformance profiles
compatibility and migration policy
collection configuration schema and provider model (tasknotes.yaml, TaskNotes data.json)
full dependency (blocked_by) semantics
full reminder (reminders) semantics
explicit time-tracking management semantics (time_entries lifecycle, start/stop/edit/remove, and completion-triggered auto-stop configuration)
explicit links chapter and link-resolution rules for projects/dependencies
optional templating conformance profile with create-time template expansion/merge semantics