Skip to content

PL8: one way to keep work, and any tracker beside it - #210

Merged
shinyobjectz merged 3 commits into
mainfrom
one-plan
Nov 21, 2026
Merged

shinyobjectz merged 3 commits into
mainfrom
one-plan

Conversation

@shinyobjectz

@shinyobjectz shinyobjectz commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

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/task and the spec)

  • Trackers: trackersOf, trackerStates, keywordFor and statusFor read 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.
  • checkPlan names each problem with its fix: a bad entry, a URL, a system twice on one task, one tracker item on two tasks, or a mapped keyword the plan doesn't have. It requires nothing else.
  • Keywords: newPlan(title, keywords) keeps whatever sequence it's given.
  • Cloud fixture: raea cloud's own plan.org passes checkPlan with nothing flagged.

PL8a (core/brief and the CLI)

  • A brief has no stages or tasks; plan.org is the one list. An old brief's stages still read, and raea doctor says they belong in plan.org.
  • The object plan is now parts() in NAME.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

  1. raea-feed 3D: a Cone's picking bounds are twice its height #98
  2. raea-skills ci: run the check, CLI, spec, workspace, tools, kernel and bundle tests #105
  3. This stack, with the skills pin bumped and after L1: PJ9: controllers are gone; a standing rule is a taste line #209 (no-controllers), then this PR.

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
shinyobjectz changed the base branch from no-controllers to main November 21, 2026 00:38
…rg the one list

It also carries raea-skills #104, whose raea side (#205) is already in main.
@shinyobjectz
shinyobjectz marked this pull request as ready for review November 21, 2026 00:50
@shinyobjectz
shinyobjectz merged commit 6298d12 into main Nov 21, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant