State what a Task name carries #78

Merged

PerishFire merged 1 commit from land/concord-task-naming into main 2026-08-15 11:33:25 +00:00

Conversation 0 Commits 1 Files changed 4 +25 -10

PerishFire commented 2026-08-15 11:28:15 +00:00

Owner

Copy link

State what a Task name carries

A name is the first thing a reader of this estate sees and the last thing
anyone changes, yet nothing said what it should carry. Names drawn from the
finding that opened a line bind nothing, so the work outgrows them, and the
prose references left behind in other Tasks and in frozen Phases are exactly
the drift this estate audits for.

A name states what will be true once the Task is done. A standing line with no
terminal state names its function instead, correct for that shape alone. When
the deliverable is not yet clear enough to name, the caller owns that
vocabulary; report the unclear shape rather than settling for the name that
was easiest to write.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

Advance Keel to 0.10.4

Refresh the Concord lockfile to Keel and keel-macro 0.10.4, and reaffirm the
document seals against the exact dependency delta.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

State what a Task name carries A name is the first thing a reader of this estate sees and the last thing anyone changes, yet nothing said what it should carry. Names drawn from the finding that opened a line bind nothing, so the work outgrows them, and the prose references left behind in other Tasks and in frozen Phases are exactly the drift this estate audits for. A name states what will be true once the Task is done. A standing line with no terminal state names its function instead, correct for that shape alone. When the deliverable is not yet clear enough to name, the caller owns that vocabulary; report the unclear shape rather than settling for the name that was easiest to write. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Advance Keel to 0.10.4 Refresh the Concord lockfile to Keel and keel-macro 0.10.4, and reaffirm the document seals against the exact dependency delta. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

PerishFire added 1 commit 2026-08-15 11:28:15 +00:00

State what a Task name carries ... 64de696b44

State what a Task name carries

A name is the first thing a reader of this estate sees and the last thing
anyone changes, yet nothing said what it should carry. Names drawn from the
finding that opened a line bind nothing, so the work outgrows them, and the
prose references left behind in other Tasks and in frozen Phases are exactly
the drift this estate audits for.

A name states what will be true once the Task is done. A standing line with no
terminal state names its function instead, correct for that shape alone. When
the deliverable is not yet clear enough to name, the caller owns that
vocabulary; report the unclear shape rather than settling for the name that
was easiest to write.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Advance Keel to 0.10.4

Refresh the Concord lockfile to Keel and keel-macro 0.10.4, and reaffirm the
document seals against the exact dependency delta.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Land-Source: concord-task-naming@2792894d8093cd5cb65832047bcedc34848b9270

PerishFire merged commit 64de696b44 into main 2026-08-15 11:33:25 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

PerishFire/concord!78

No description provided.