diff --git a/directory/skills/raea/SKILL.md b/directory/skills/raea/SKILL.md index 6a357f1..948b36b 100644 --- a/directory/skills/raea/SKILL.md +++ b/directory/skills/raea/SKILL.md @@ -96,7 +96,7 @@ task needs. | the export, the share copy, platform specs, posting a deliverable | [delivery.md](delivery.md) | | working with the person in the raea app: the feed, controllers, the editor, boards | [collaborate.md](collaborate.md) | | planning the work and keeping its tasks: the project's plan.org, the person's to-do list | [plan.md](plan.md) | -| checking a cut against the person's taste, reading their notes on a sound, or teaching their fingerprint | [fingerprint.md](fingerprint.md) | +| checking a cut against the person's taste and rules, reading their notes on a sound, or teaching their fingerprint | [fingerprint.md](fingerprint.md) | Across all of them, `craft/`: [craft/ROUTER.md](craft/ROUTER.md) is how to decide what to make (the order of work and reading notes); [craft/floor.md](craft/floor.md) is read right before every edit; `craft/modes/` says what a pitch, @@ -123,7 +123,8 @@ holding projects and controllers. In the raea app a project shows as a channel. - `raea context .` in the project prints everything to read first, in order: the person's taste (`~/.raea/taste/taste.ts`; a line there beats any guide's default), the workspace's taste, the brief, the look, the - workspace's controllers, the craft floor and each of the brief's modes' guides. Read all of it. + workspace's controllers, the craft floor and each of the brief's modes' guides. Read all of it. In the raea app, + `rules_read` lists every rule the work follows, the project's own `taste.ts` first ([collaborate.md](collaborate.md)). - Run it once a session. If it refuses, say so in one line ("raea context failed: its message; reading the brief and controllers directly") and read `brief.ts`, any `*.script.ts`, `~/.raea/taste/taste.ts` and `raea controller ls` yourself. A `CONTEXT_STALE` line means `raea doctor` finds files from another version: run `raea doctor --fix`. @@ -140,7 +141,8 @@ holding projects and controllers. In the raea app a project shows as a channel. `controller_post` (its id, the fields as group.field, a line on what you need decided) rather than asking in prose; a controller you make with `controller_write` reaches their feed on its own. Fields are typed (toggle, choice, number, text, list, agents, channels, workflow, servers, skills, rule; reference/files.md), so put what they'll - adjust in fields, one controller per concern. + adjust in fields, one controller per concern. A style preference with no fields to set ("words never cover the + action") is a rule instead: `rule_add` in the app, or a line in the project's `taste.ts`. - A `rule` field is a line every piece is held to and the check that holds it: one of raea's by name with its values, or a `.ts` check written with `raea/check` (craft/ROUTER.md, step 7). `raea check PROJECT` runs every rule that applies, with raea's floor and the person's taste, and says what waits for a render. @@ -222,9 +224,11 @@ also says where in the frame and, on a render with a layer pass, the layers ther with that layer. Fix each gating moment, or say why you didn't, and score the fix against the cut before: `raea fingerprint score out/v2.mp4 --was out/v1.mp4` says whether each flag is fixed, still there, or looks disguised (nearer the axis's disguised defects than clean work, so the fix hid the defect -rather than removing its cause); only a fixed flag is fixed. `raea fingerprint which out/piece.mp4` names the fingerprint that judges this piece (the -project's, the workspace's, then the person's own) and why. Tell the person the axis and the moment, never a score. [fingerprint.md](fingerprint.md) has the rest: reading a -note's box on the sound, teaching the fingerprint, and keeping one with a project. +rather than removing its cause); only a fixed flag is fixed. `raea fingerprint which out/piece.mp4` names the +fingerprint that judges this piece (the project's, the workspace's, then the person's own) and why. Tell the person +the axis and the moment, never a score. In the app, `rule_check` scores it and holds it to every rule in one call. +[fingerprint.md](fingerprint.md) has the rest: the person's rules, reading a note's box on the sound, teaching the +fingerprint, and keeping one with a project. `raea fingerprint report` says what each axis has learned and what it can't judge yet. A fingerprint's axes are ~/.raea/fingerprints/NAME/fingerprint.ts, typed by `raea/fingerprint`: add, remove or reword an axis there, never its evidence. A script or brief scores on text axes only, and raea's own axes read pictures and sound, so a script scores diff --git a/directory/skills/raea/collaborate.md b/directory/skills/raea/collaborate.md index 5240c63..d3fde87 100644 --- a/directory/skills/raea/collaborate.md +++ b/directory/skills/raea/collaborate.md @@ -1,9 +1,9 @@ # Working in the raea app When the raea app launches you, its feed is where you and the person work together: you post what you make, they -look, play and leave notes, and the workspace's standing decisions live in controllers. Every tool here is PAGE (it -needs the person's feed open) and is listed in full in [reference/feed.md](reference/feed.md); this file says when -to reach for each. Headless, with no app, SKILL.md's steps 5 and 6 say what to do instead. +look, play and leave notes, and the workspace's standing decisions live in controllers. Most tools here are PAGE (they +need the person's feed open); the rules tools are HOST (the app answers them with no page open). All are listed in +full in [reference/feed.md](reference/feed.md); this file says when to reach for each. Headless, with no app, SKILL.md's steps 5 and 6 say what to do instead. ## When you need to... @@ -23,6 +23,9 @@ to reach for each. Headless, with no app, SKILL.md's steps 5 and 6 say what to d | read the workspace's standing decisions (delivery specs, who reviews what) | `controllers_read`, before you start | | have the person decide something that should hold for every piece from now on | `controller_post` with the fields and a line on why; a decision about one piece is a note on it, not a controller | | add a standing decision the person asked for, change one field, or retire one | `controller_write`, `controller_set`, `controller_remove`, only when the person asks | +| know the rules this project's work follows (the project's own, the workspace's house rules, the person's taste) and which fingerprint judges it | `rules_read`, before you start and again before you post: the person changes rules in Fingerprint › Rules while you work | +| keep a style preference the person states for all the work from now ("make this a rule", "always…", "never again…", "note that for later") | `rule_add` to the project's rules, with `why` and `when` it applies, and `axis` when a fingerprint axis guards against it. It holds at once and waits in Fingerprint › Rules for them to keep. A setting with fields (delivery sizes, who reviews) is a controller instead, and their own taste they change themselves | +| hold a render, a still, a sound or a game to every rule before you post it | `rule_check` with the file, and your `verdicts` on the rules nothing measures after you've looked; fix what it says broke and where, then `feed_post` | | work on what the person has open in the composition editor ("this", "here", "the selected one") | `editor_selection` first, then `editor_edit`: their undo takes it back, and it saves with their changes | | show a plan before making it | previz first: a rough raea render of blocking, timing and camera, `feed_post` watch. Else a storyboard: key frames as one `feed_post` look with `files` in order. Else the script: `feed_post` read with its `NAME.script.ts`, which the feed shows as a screenplay and as an A/V table (give each beat its `seconds` and the table is timed); a `.md` reads as prose | | map how ideas, options and references connect, a structure to rearrange together | `whiteboard_write` (say what's on it and how it's grouped; the feed lays it out), `whiteboard_read` for what the person drew back. Not for the plan itself: show that as previz, a storyboard or a script | diff --git a/directory/skills/raea/fingerprint.md b/directory/skills/raea/fingerprint.md index e532cdd..ecd3363 100644 --- a/directory/skills/raea/fingerprint.md +++ b/directory/skills/raea/fingerprint.md @@ -43,6 +43,25 @@ raea fingerprint score out/v2.mp4 --was out/v1.mp4 # after a fix: each of v1's f - References the person admires: `raea fingerprint profile REFS... --as NAME`, then `score --profile NAME` says which measures fall outside their ranges, where, and which way to move. +## The person's rules + +Their standing rules are taste files, nearest first: the project's own `taste.ts`, the workspace's house rules +(`taste.ts` at the workspace's root), then their own (`~/.raea/taste/taste.ts`, and `motion.ts`, `games.ts`, +`sound.ts`, `ui.ts` for each kind of work). A rule may say when it applies and what holds it: a check raea measures, a +script in the project, a fingerprint axis, or nothing but an eye. The file's `about` export keeps these (raea reads +only its default export). + +- In the app, `rules_read` lists every rule with the fingerprint that judges the project and its axes, and + `rule_check out/cut.mp4` holds a file to all of them before `feed_post`: measured rules through + `raea check --taste`, rules linked to an axis through `raea fingerprint score`, a script by running it, and the + rest by your own look, which you pass as `verdicts`. Say what broke and where. Headless, run + `raea check FILE --taste taste.ts` and the score yourself, and look at the rest. +- When the person states a preference for all the work from now, add it with `rule_add` (the project's rules, or the + workspace's): one plain sentence, why, when it applies, and the axis when one guards against it. It waits in + Fingerprint › Rules, where they keep, reword, move or drop it (PERSON). +- A rule linked to an axis is only as sure as the axis: one that is **learning** only advises. Linking a rule to an + axis, or teaching the axis from the notes a rule came from, is the person's (Fingerprint › Rules), not yours. + ## Reading their notes - A note on the picture can carry a mark (a pin, a box, a lasso): fix what's inside it. diff --git a/directory/skills/raea/reference/feed.md b/directory/skills/raea/reference/feed.md index 9c8fea4..f898d21 100644 --- a/directory/skills/raea/reference/feed.md +++ b/directory/skills/raea/reference/feed.md @@ -366,6 +366,42 @@ Bring footage, sounds or stills into this project's assets/footage/ by their pat | `files` | required | absolute paths of the clips or folders | | `go` | optional | true: add them (after a dry run you've read); left out: the dry run only | +## rules_read + +Access: HOST. + +Read every rule this project's work follows, nearest first: the project's own (its taste.ts), the workspace's house rules, then the person's taste (taste.ts for everything, then motion, games, sound and ui). Each rule has its words, its section, and when known: when it applies, what checks it (a check raea measures, a script in the project, a fingerprint axis), and who wrote it (an agent's rule the person hasn't kept yet says waiting). With the fingerprint that judges the project and its axes. Read it before you start, and again before you post: the person changes rules in Fingerprint › Rules while you work. + +No input. + +## rule_add + +Access: HOST. + +Add a standing rule to the project's rules (or the workspace's house rules, level workspace), when the person states a preference that should hold for all of this work from now ("make this a rule", "always…", "never again…", "note that for later"), not a fix for one item. One plain sentence that holds for future work, with when it applies. It holds at once, written to the project's taste.ts and committed; the person sees it under Waiting for you in Fingerprint › Rules, where they keep, change or drop it, or move it into their own taste. Never for the person's own taste: they move a rule up themselves. check only when raea can measure the rule; axis when one of the fingerprint's axes (rules_read lists them) names what it guards against; run for a script in the project that exits 0 while the rule holds. + +| input | | | +|---|---|---| +| `text` | required | the rule, one plain sentence in the person's terms ("Words never cover the action.") | +| `when` | optional | when it applies, the "if this" ("a line is on screen in a 9:16 ad"); left out, always | +| `why` | required | one line: what the person said or did that makes it a rule | +| `section` | optional | its section: a topic (Sound, Captions, Camera) or Always or Never; Always when left out | +| `check` | optional | a check raea measures, as FORM VALUE: text-hold S, text-above P%, text-below P%, text-margin N, loudness L, still-max S | +| `run` | optional | a script in the project's (or workspace's) folder, by its path there, that takes the file and exits 0 while the rule holds | +| `axis` | optional | the fingerprint axis that holds it (clip, dark…), from rules_read | +| `level` | optional | project (the default) or workspace | + +## rule_check + +Access: HOST. + +Hold a file (a render, a still, a sound, a game) to every rule that applies, before you post it: rules with a measured check run through raea check --taste, rules linked to a fingerprint axis through raea fingerprint score, rules with a script by running it, and the rest by your own eye, which you pass as verdicts after looking. Answers each rule held, broken (and where), flagged (the fingerprint points at moments it only advises on) or unchecked, with how it was checked, and a summary line the person sees in the chat. Never a score: say what broke and where. Fix what's broken and check again before feed_post. + +| input | | | +|---|---|---| +| `file` | required | the file to check, absolute or in the project's folder | +| `verdicts` | optional | your own look at rules nothing measures: each { text (the rule's words, as rules_read gives them), held (true or false), at (a moment, 0:06), how (one line on what you looked at) } | + ## project_collaborators Access: PAGE, when the person allows agents to share. diff --git a/skills/raea/SKILL.md b/skills/raea/SKILL.md index 6a357f1..948b36b 100644 --- a/skills/raea/SKILL.md +++ b/skills/raea/SKILL.md @@ -96,7 +96,7 @@ task needs. | the export, the share copy, platform specs, posting a deliverable | [delivery.md](delivery.md) | | working with the person in the raea app: the feed, controllers, the editor, boards | [collaborate.md](collaborate.md) | | planning the work and keeping its tasks: the project's plan.org, the person's to-do list | [plan.md](plan.md) | -| checking a cut against the person's taste, reading their notes on a sound, or teaching their fingerprint | [fingerprint.md](fingerprint.md) | +| checking a cut against the person's taste and rules, reading their notes on a sound, or teaching their fingerprint | [fingerprint.md](fingerprint.md) | Across all of them, `craft/`: [craft/ROUTER.md](craft/ROUTER.md) is how to decide what to make (the order of work and reading notes); [craft/floor.md](craft/floor.md) is read right before every edit; `craft/modes/` says what a pitch, @@ -123,7 +123,8 @@ holding projects and controllers. In the raea app a project shows as a channel. - `raea context .` in the project prints everything to read first, in order: the person's taste (`~/.raea/taste/taste.ts`; a line there beats any guide's default), the workspace's taste, the brief, the look, the - workspace's controllers, the craft floor and each of the brief's modes' guides. Read all of it. + workspace's controllers, the craft floor and each of the brief's modes' guides. Read all of it. In the raea app, + `rules_read` lists every rule the work follows, the project's own `taste.ts` first ([collaborate.md](collaborate.md)). - Run it once a session. If it refuses, say so in one line ("raea context failed: its message; reading the brief and controllers directly") and read `brief.ts`, any `*.script.ts`, `~/.raea/taste/taste.ts` and `raea controller ls` yourself. A `CONTEXT_STALE` line means `raea doctor` finds files from another version: run `raea doctor --fix`. @@ -140,7 +141,8 @@ holding projects and controllers. In the raea app a project shows as a channel. `controller_post` (its id, the fields as group.field, a line on what you need decided) rather than asking in prose; a controller you make with `controller_write` reaches their feed on its own. Fields are typed (toggle, choice, number, text, list, agents, channels, workflow, servers, skills, rule; reference/files.md), so put what they'll - adjust in fields, one controller per concern. + adjust in fields, one controller per concern. A style preference with no fields to set ("words never cover the + action") is a rule instead: `rule_add` in the app, or a line in the project's `taste.ts`. - A `rule` field is a line every piece is held to and the check that holds it: one of raea's by name with its values, or a `.ts` check written with `raea/check` (craft/ROUTER.md, step 7). `raea check PROJECT` runs every rule that applies, with raea's floor and the person's taste, and says what waits for a render. @@ -222,9 +224,11 @@ also says where in the frame and, on a render with a layer pass, the layers ther with that layer. Fix each gating moment, or say why you didn't, and score the fix against the cut before: `raea fingerprint score out/v2.mp4 --was out/v1.mp4` says whether each flag is fixed, still there, or looks disguised (nearer the axis's disguised defects than clean work, so the fix hid the defect -rather than removing its cause); only a fixed flag is fixed. `raea fingerprint which out/piece.mp4` names the fingerprint that judges this piece (the -project's, the workspace's, then the person's own) and why. Tell the person the axis and the moment, never a score. [fingerprint.md](fingerprint.md) has the rest: reading a -note's box on the sound, teaching the fingerprint, and keeping one with a project. +rather than removing its cause); only a fixed flag is fixed. `raea fingerprint which out/piece.mp4` names the +fingerprint that judges this piece (the project's, the workspace's, then the person's own) and why. Tell the person +the axis and the moment, never a score. In the app, `rule_check` scores it and holds it to every rule in one call. +[fingerprint.md](fingerprint.md) has the rest: the person's rules, reading a note's box on the sound, teaching the +fingerprint, and keeping one with a project. `raea fingerprint report` says what each axis has learned and what it can't judge yet. A fingerprint's axes are ~/.raea/fingerprints/NAME/fingerprint.ts, typed by `raea/fingerprint`: add, remove or reword an axis there, never its evidence. A script or brief scores on text axes only, and raea's own axes read pictures and sound, so a script scores diff --git a/skills/raea/collaborate.md b/skills/raea/collaborate.md index 5240c63..d3fde87 100644 --- a/skills/raea/collaborate.md +++ b/skills/raea/collaborate.md @@ -1,9 +1,9 @@ # Working in the raea app When the raea app launches you, its feed is where you and the person work together: you post what you make, they -look, play and leave notes, and the workspace's standing decisions live in controllers. Every tool here is PAGE (it -needs the person's feed open) and is listed in full in [reference/feed.md](reference/feed.md); this file says when -to reach for each. Headless, with no app, SKILL.md's steps 5 and 6 say what to do instead. +look, play and leave notes, and the workspace's standing decisions live in controllers. Most tools here are PAGE (they +need the person's feed open); the rules tools are HOST (the app answers them with no page open). All are listed in +full in [reference/feed.md](reference/feed.md); this file says when to reach for each. Headless, with no app, SKILL.md's steps 5 and 6 say what to do instead. ## When you need to... @@ -23,6 +23,9 @@ to reach for each. Headless, with no app, SKILL.md's steps 5 and 6 say what to d | read the workspace's standing decisions (delivery specs, who reviews what) | `controllers_read`, before you start | | have the person decide something that should hold for every piece from now on | `controller_post` with the fields and a line on why; a decision about one piece is a note on it, not a controller | | add a standing decision the person asked for, change one field, or retire one | `controller_write`, `controller_set`, `controller_remove`, only when the person asks | +| know the rules this project's work follows (the project's own, the workspace's house rules, the person's taste) and which fingerprint judges it | `rules_read`, before you start and again before you post: the person changes rules in Fingerprint › Rules while you work | +| keep a style preference the person states for all the work from now ("make this a rule", "always…", "never again…", "note that for later") | `rule_add` to the project's rules, with `why` and `when` it applies, and `axis` when a fingerprint axis guards against it. It holds at once and waits in Fingerprint › Rules for them to keep. A setting with fields (delivery sizes, who reviews) is a controller instead, and their own taste they change themselves | +| hold a render, a still, a sound or a game to every rule before you post it | `rule_check` with the file, and your `verdicts` on the rules nothing measures after you've looked; fix what it says broke and where, then `feed_post` | | work on what the person has open in the composition editor ("this", "here", "the selected one") | `editor_selection` first, then `editor_edit`: their undo takes it back, and it saves with their changes | | show a plan before making it | previz first: a rough raea render of blocking, timing and camera, `feed_post` watch. Else a storyboard: key frames as one `feed_post` look with `files` in order. Else the script: `feed_post` read with its `NAME.script.ts`, which the feed shows as a screenplay and as an A/V table (give each beat its `seconds` and the table is timed); a `.md` reads as prose | | map how ideas, options and references connect, a structure to rearrange together | `whiteboard_write` (say what's on it and how it's grouped; the feed lays it out), `whiteboard_read` for what the person drew back. Not for the plan itself: show that as previz, a storyboard or a script | diff --git a/skills/raea/fingerprint.md b/skills/raea/fingerprint.md index e532cdd..ecd3363 100644 --- a/skills/raea/fingerprint.md +++ b/skills/raea/fingerprint.md @@ -43,6 +43,25 @@ raea fingerprint score out/v2.mp4 --was out/v1.mp4 # after a fix: each of v1's f - References the person admires: `raea fingerprint profile REFS... --as NAME`, then `score --profile NAME` says which measures fall outside their ranges, where, and which way to move. +## The person's rules + +Their standing rules are taste files, nearest first: the project's own `taste.ts`, the workspace's house rules +(`taste.ts` at the workspace's root), then their own (`~/.raea/taste/taste.ts`, and `motion.ts`, `games.ts`, +`sound.ts`, `ui.ts` for each kind of work). A rule may say when it applies and what holds it: a check raea measures, a +script in the project, a fingerprint axis, or nothing but an eye. The file's `about` export keeps these (raea reads +only its default export). + +- In the app, `rules_read` lists every rule with the fingerprint that judges the project and its axes, and + `rule_check out/cut.mp4` holds a file to all of them before `feed_post`: measured rules through + `raea check --taste`, rules linked to an axis through `raea fingerprint score`, a script by running it, and the + rest by your own look, which you pass as `verdicts`. Say what broke and where. Headless, run + `raea check FILE --taste taste.ts` and the score yourself, and look at the rest. +- When the person states a preference for all the work from now, add it with `rule_add` (the project's rules, or the + workspace's): one plain sentence, why, when it applies, and the axis when one guards against it. It waits in + Fingerprint › Rules, where they keep, reword, move or drop it (PERSON). +- A rule linked to an axis is only as sure as the axis: one that is **learning** only advises. Linking a rule to an + axis, or teaching the axis from the notes a rule came from, is the person's (Fingerprint › Rules), not yours. + ## Reading their notes - A note on the picture can carry a mark (a pin, a box, a lasso): fix what's inside it. diff --git a/skills/raea/reference/feed.md b/skills/raea/reference/feed.md index 9c8fea4..f898d21 100644 --- a/skills/raea/reference/feed.md +++ b/skills/raea/reference/feed.md @@ -366,6 +366,42 @@ Bring footage, sounds or stills into this project's assets/footage/ by their pat | `files` | required | absolute paths of the clips or folders | | `go` | optional | true: add them (after a dry run you've read); left out: the dry run only | +## rules_read + +Access: HOST. + +Read every rule this project's work follows, nearest first: the project's own (its taste.ts), the workspace's house rules, then the person's taste (taste.ts for everything, then motion, games, sound and ui). Each rule has its words, its section, and when known: when it applies, what checks it (a check raea measures, a script in the project, a fingerprint axis), and who wrote it (an agent's rule the person hasn't kept yet says waiting). With the fingerprint that judges the project and its axes. Read it before you start, and again before you post: the person changes rules in Fingerprint › Rules while you work. + +No input. + +## rule_add + +Access: HOST. + +Add a standing rule to the project's rules (or the workspace's house rules, level workspace), when the person states a preference that should hold for all of this work from now ("make this a rule", "always…", "never again…", "note that for later"), not a fix for one item. One plain sentence that holds for future work, with when it applies. It holds at once, written to the project's taste.ts and committed; the person sees it under Waiting for you in Fingerprint › Rules, where they keep, change or drop it, or move it into their own taste. Never for the person's own taste: they move a rule up themselves. check only when raea can measure the rule; axis when one of the fingerprint's axes (rules_read lists them) names what it guards against; run for a script in the project that exits 0 while the rule holds. + +| input | | | +|---|---|---| +| `text` | required | the rule, one plain sentence in the person's terms ("Words never cover the action.") | +| `when` | optional | when it applies, the "if this" ("a line is on screen in a 9:16 ad"); left out, always | +| `why` | required | one line: what the person said or did that makes it a rule | +| `section` | optional | its section: a topic (Sound, Captions, Camera) or Always or Never; Always when left out | +| `check` | optional | a check raea measures, as FORM VALUE: text-hold S, text-above P%, text-below P%, text-margin N, loudness L, still-max S | +| `run` | optional | a script in the project's (or workspace's) folder, by its path there, that takes the file and exits 0 while the rule holds | +| `axis` | optional | the fingerprint axis that holds it (clip, dark…), from rules_read | +| `level` | optional | project (the default) or workspace | + +## rule_check + +Access: HOST. + +Hold a file (a render, a still, a sound, a game) to every rule that applies, before you post it: rules with a measured check run through raea check --taste, rules linked to a fingerprint axis through raea fingerprint score, rules with a script by running it, and the rest by your own eye, which you pass as verdicts after looking. Answers each rule held, broken (and where), flagged (the fingerprint points at moments it only advises on) or unchecked, with how it was checked, and a summary line the person sees in the chat. Never a score: say what broke and where. Fix what's broken and check again before feed_post. + +| input | | | +|---|---|---| +| `file` | required | the file to check, absolute or in the project's folder | +| `verdicts` | optional | your own look at rules nothing measures: each { text (the rule's words, as rules_read gives them), held (true or false), at (a moment, 0:06), how (one line on what you looked at) } | + ## project_collaborators Access: PAGE, when the person allows agents to share.