Repository navigation
PL8: one way to keep work, and any tracker beside it - #210
Merged
Merged
Conversation
docs/plan.feature PL8: plan.org is the one list, a message isn't a task, closing follows the work, the keywords are the file's, and a task is kept in step with another tracker by :LINK: and #+LINK_STATES:, agreed with raea cloud. @raea/task: trackersOf, trackerStates, keywordFor and statusFor read a task's :LINK: entries (SYSTEM:ID, one per system) and the head's status maps; checkPlan names a bad entry, a URL, a system twice on one task, one tracker item on two tasks and an unknown mapped keyword, each with its fix, and requires nothing else. newPlan takes the keyword sequence its caller keeps. A raea cloud plan.org passes with nothing flagged.
core/brief's Brief drops stages and its Stage, Mark and Task types: a project's tasks are its plan.org. An older brief with stages still reads; raea doctor says its tasks belong in plan.org and moves nothing. core/brief's object plan, the solids contract, is parts() in NAME.parts.ts (raea spec --as parts), so plan means only a project's plan.org. No project used plan(); the bevy guides that teach it, the manual and the reference pages follow.
shinyobjectz
marked this pull request as ready for review
November 21, 2026 00:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/plan.feature PL8. Tasks were written in four places and closed in one: an agent remembering to. Plans made in the app closed almost nothing, while plans kept by an agent in a terminal closed most of theirs. Agreed with raea cloud, which keeps its projects in plan.org on
@raea/task.PL8 (
@raea/taskand the spec)trackersOf,trackerStates,keywordForandstatusForread a task's:LINK: linear:ENG-12 asana:…entries and the head's#+LINK_STATES:maps. Syncing with a client's tracker then needs a mapping, not code per client.newPlan(title, keywords)keeps whatever sequence it's given.checkPlanwith nothing flagged.PL8a (core/brief and the CLI)
raea doctorsays they belong in plan.org.parts()inNAME.parts.ts(raea spec --as parts), so "plan" means only plan.org. The guides, the manual and the reference pages follow.PL8b–d are in the app (raea-feed #98): a message is no longer a task, the keeper is gone, a task on an item closes when the person approves the item, and the app writes
TODO | DONE DROPPED.Merge order
no-controllers), then this PR.