bareloop 0.55.0 → 0.56.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +47 -0
- package/bareloop.context.md +4 -2
- package/package.json +2 -2
- package/src/authorflow.js +141 -264
- package/src/authoring.js +2 -3
- package/src/authorjob.js +117 -88
- package/src/authorreadout.js +9 -15
- package/src/authorrun.js +13 -4
- package/src/behaviour.js +14 -0
- package/src/blockasks.js +43 -0
- package/src/checkblock.js +772 -0
- package/src/checklist.js +128 -0
- package/src/checkpick.js +30 -312
- package/src/checkwords.js +3 -1
- package/src/declaredclose.js +30 -1
- package/src/destpoint.js +3 -1
- package/src/draftspend.js +46 -0
- package/src/facts.js +8 -1
- package/src/fitcheck.js +5 -3
- package/src/pagemap.js +15 -3
- package/src/panel/authorroutes.js +15 -3
- package/src/panel/authorsession.js +133 -46
- package/src/panel/index.html +194 -22
- package/src/panel/jobplan.js +85 -33
- package/src/panel/server.js +52 -7
- package/src/pickrecord.js +19 -1
- package/src/placerule.js +355 -0
- package/src/promptregisters.js +11 -0
- package/src/questionbox.js +112 -0
- package/src/rowedit.js +115 -0
- package/src/rubricstep.js +212 -125
- package/src/run.js +10 -2
- package/src/userrun.js +46 -1
- package/types/authorflow.d.ts +32 -139
- package/types/authorjob.d.ts +24 -6
- package/types/authorreadout.d.ts +4 -10
- package/types/behaviour.d.ts +12 -0
- package/types/blockasks.d.ts +37 -0
- package/types/checkblock.d.ts +361 -0
- package/types/checklist.d.ts +134 -0
- package/types/checkpick.d.ts +3 -140
- package/types/declaredclose.d.ts +4 -0
- package/types/destpoint.d.ts +2 -0
- package/types/draftspend.d.ts +21 -0
- package/types/fitcheck.d.ts +7 -1
- package/types/pagemap.d.ts +4 -0
- package/types/panel/authorsession.d.ts +13 -2
- package/types/panel/jobgrid.d.ts +8 -8
- package/types/panel/jobplan.d.ts +48 -10
- package/types/panel/server.d.ts +14 -13
- package/types/pickrecord.d.ts +12 -0
- package/types/placerule.d.ts +194 -0
- package/types/questionbox.d.ts +87 -0
- package/types/rowedit.d.ts +32 -0
- package/types/rubricstep.d.ts +91 -48
- package/types/run.d.ts +10 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,10 +5,57 @@ All notable changes to bareloop are documented here. Format:
|
|
|
5
5
|
[SemVer](https://semver.org/spec/v2.0.0.html). Pre-1.0: **minor** = a ladder rung or
|
|
6
6
|
feature lands, **patch** = docs, fixes, scaffolding.
|
|
7
7
|
|
|
8
|
+
## [0.56.0] - 2026-11-13
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
|
|
12
|
+
- **Place rules: a phrase check that names a version or a date follows the input instead of being refused as week-only (place rules P1-P6, hamr go 2026-11-11; `src/placerule.js`).** Test-proven; one live paid test passed (0.54.1 to 0.55.0 swapped; a mixed heading stopped at $0). At drafting, code (never the AI) fits a place rule (the newest release heading's version or date) to a phrase fact and strips a heading piece such as `## [0.54.1]` or `2026-11-04` to its bare value(s); a version plus a date become two facts, named plainly ("version", "date"). The signed fact carries the rule, never the run's value. At each run, code alone re-reads the value before any spend: the same value passes, a new value is swapped in, and a rule that finds no value stops at $0 listing every rule in plain words. The week-only decision has one owner, the list row; the door's Accept/Rerun bind the run's own read value; one place-rules record per run goes to the spine; the Job tab shows the row. Old runs are not repaired.
|
|
13
|
+
- **The Audit lists every check the card lists, each with its result (hamr ruling A, 2026-11-13, live run mwenvde5).** The Audit tab had only the built checks; it left out the Always checked guards and the Not checked rows. It now has one fold, "Checks", with the card's own sections in bold: Checks, Not checked, Always checked. Each row carries its tag (`[you]`, `[agent]`, `[default]`) and, after the run, its result: passed or failed read from the run's own recorded close verdicts, "not checked" with its reason, or "no result recorded" when the run recorded nothing for it. The checks were also listed in the drafting table of the Audit; that second list is gone. Test-proven on the real run (tests/audit-checks-section.test.js); not seen live in the panel.
|
|
14
|
+
- **The Audit's write fence row shows the gate's own record (hamr ruling A, 2026-11-13, live run mwenvde5).** The row read "no result recorded" because the fence is enforced per write by the gate, not by a close stage. It now reads "held · N writes blocked" from the gate audit of this run (N = write/edit attempts the gate denied as outside the write scope; allowed writes and denied reads are not counted), "held · 0 writes blocked" on mwenvde5; with no gate audit for the run it says "the gate's record for this run is missing", never "held". The fold header counts "held" as passed and wears one state sign before "Checks" ([✗] if any row failed, else [·] if any row has no recorded result or the gate's record is missing, else [✓]; "not checked" rows do not move it). Test-proven on the real audit (tests/audit-checks-section.test.js); not seen live in the panel.
|
|
15
|
+
- **Live draft 3 fixes (hamr 2026-11-13, session smwen1p12tyhc; F336).** The job's own word wins over the long page name: a `!` fact whose page words are "Boston Logan International Airport" for the job's "Boston" is job-derived and checks `must say "Boston"` (only a row with no word from the job goes to Suggested). A Drop on an `[agent]` row moves it to Suggested with Add instead of removing it; Add puts it back; a Revise carries it. The "Always checked" rows carry `[default]`; the section headings (Suggested, Not checked, How the page was read, Always checked) are bold. Test-proven (the real page and page-map reply of that session, tests/card-live3.test.js); not seen live. Seen, not fixed: after a drop a new suggestion "must say 12 results returned" (a page status line) appeared under Suggested; legal, off unless added.
|
|
16
|
+
- **The confirm card has Drop and Add (hamr 2026-11-13, live drafts smwelq2l6srdb and smwelw0jrax5c).** A job-derived `[agent]` check has a Drop button; the checks the agent suggests that are not in the job sit under "Suggested · not in your job, not checked unless you add it" with an Add button, and only ones code has already proved it can build are offered. Both are instant and cost nothing: no model call, no new draft; the row goes back through the check block and the card is drawn again from the rows. The choices are kept when you Revise, and signing reads the rows. A `[you]` row has no Drop (edit the job). New route `POST /api/author/<id>/row-edit`.
|
|
17
|
+
- **A suggested check code could not build is no longer a Not checked row on the card (hamr 2026-11-13, F-b).** It used to show raw gate text ("code could not build a legal check from it: ... Nothing was signed."). It is now one plain sentence in the Audit's draft lines. A `~` rule you wrote always shows, built or Not checked.
|
|
18
|
+
- **Card tags are by row kind, written by code (hamr 2026-11-13, live drafts smwelq2l6srdb and smwelw0jrax5c).** A `~` row, and a fact built from the person's own rule, is `[you]`; a `!` row is `[agent]`; a `$` row is `[default]`. Rule-built facts used to read `[agent]`, and picks read `[you picked]`. Not checked rows carry their tag too, and the heading "Not checked (the AI's own reading)" is now "Not checked". The confirm card, the signed card, the Job tab and the Result tab share the tags.
|
|
19
|
+
- **The check list splits the agent's `!` checks into job-derived and suggested, with Drop and Add (hamr 2026-11-13, live drafts smwelq2l6srdb and smwelw0jrax5c; block level).** A `!` check whose words (or result count) are in the job line or its `~` rules is built and can be dropped; one that is not is only Suggested: not checked unless the person adds it, and offered only when code has already proved it builds. A suggestion code cannot build is hidden from the card (it is one plain sentence in the Audit's draft lines). Drop and Add are instant row edits through the block (no AI call, every one reconciled), and a Revise keeps them. The signed list gains an optional per-row `facts` (the names of the facts a row built) so every reader can tag each fact by its row. Off by default for older callers; the panel's drafting turns it on.
|
|
20
|
+
- **A `~` rule that says what is NOT needed builds no check (hamr 2026-11-13, live drafts smwelq2l6srdb and smwelw0jrax5c).** "nonstop is not mandatory" used to get the check `must say "Nonstop"`, the opposite of the rule. A rule with a negation (not, no, never, without, except...) can no longer give a phrase check: it is Not checked, "it says what is not needed, so there is nothing to check". A suggested check whose words are in such a rule is refused alone, naming the rule ("your rule 3 says it is not needed").
|
|
21
|
+
- **The panel answer door refuses an answer with no typed choice (hamr 2026-11-12, fwd M10 am32 A).** While a question is open (a look, drafter, fit-check or Destination question), a send with no `choice` is refused 400 `bad-choice` with "This page is out of date. Reload it and answer again. Nothing was saved."; nothing is logged and the question stays open. The page already posts a choice on every answer (buttons, and the box's Send as `rule` or `path`). Other chat sends and the CLI are unchanged. Test-proven (real route, real session); not seen live. fwd's sheet-look part does not apply (bareloop has no sheet look).
|
|
22
|
+
- **The job-plan legend "Done when every › check passes" shows only when the plan has a › check row (hamr 2026-11-12, bareloop's own).** The goal-only confirm card, which has no check rows yet, no longer draws it; the plan card, final card and Job tab keep it whenever they have rows. Test-proven, not seen live.
|
|
23
|
+
- **The fit-check question names the asks it found too (hamr 2026-11-12, bareloop's own).** It read "I found 3 of 4 ... Not found: X"; it now lists the found asks with their lines before the not-found list (found 0 keeps the old shape). Wording only; the prompt sent to the model is unchanged. Test-proven, not seen live.
|
|
24
|
+
- **The fit-check question and the Destination question get buttons in the panel (hamr 2026-11-12, bareloop's own; items D and E).** Test-proven (real panel sessions); not seen live. The fit check shows [Go on] [Stop] and no answer box (Go on = today's "go on", Stop = anything else stops). The Destination question shows [Yes, set it to <folder>] [No, keep <current>] and a box "Or type a different Destination:"; a typed Destination goes through the same $0 check the card's Destination uses (inside the repo, not absolute, must exist) and a refusal keeps the question open with that check's own words; the log row says `yes`, `no` or `typed`. The panel hides each question's typed-words tail (exact suffix); the stored question and the CLI keep it.
|
|
25
|
+
- **A look question's answer is a typed choice in the panel (hamr 2026-11-12, fwd M10 am29 + am30 + am31; item B).** Test-proven (real panel sessions over a real rubric job and the real page of run mve5y8fa); not seen live. The send route takes an optional `choice` (`agree`, `drop`, `rule`); no choice is today's words reading (the CLI, old pages). Agree shows only when the question carries a proposal, Drop it only on a question about one of the person's `~` rules; the box's own words are kept whole as a `~` rule even when they read "agree" or "drop it". The panel shows the question without its `Answer "agree"...` tail (exact suffix; the stored question and the CLI keep it). A bad or not-offered choice is refused in fwd's words and leaves the question open, nothing logged. The `human` drafting-log row also records the `choice`.
|
|
26
|
+
- **A question asked while drafting gets its own question box in the panel (hamr 2026-11-12, as fwdloop M10 am29; item A).** Test-proven (real panel sessions, the page's own functions on stubs); not seen live, phone width not checked. The box shows the head ("A question the plan raised (i of n)"), "About job line N", the question, a labelled one-line answer box with an alert error line, and a wide Send; while it is open it takes the chat input's place and the chat input returns when it closes. The poll rewrites the texts only when the question changes, never what is typed. The question's message waits out of the thread until it is answered. The CLI's terminal asks are unchanged.
|
|
27
|
+
- **"Under N" / "below N" bullets, items or points now build `maxListItems N-1`** (F315 follow-up; "under 1" is no bullets, "under 0" is refused). Before it built the exact `listItems`. "Under N words" and lines are unchanged. Test-proven on real bareguard; not seen live.
|
|
28
|
+
- **Adopted bareguard `^0.35.0`** (was `^0.31.0`); no existing `rubricSha` changes. Test-proven; not seen live.
|
|
29
|
+
- **"At most / up to / no more than / fewer than N bullets" and "at least / minimum / no fewer than / more than N bullets" are now directional list-item checks (F315, BG-5).** They build bareguard's `maxListItems` / `minListItems` instead of the exact `listItems` (which graded "at most 3" red at 2 bullets); "exactly N" and a bare "N bullets" stay `listItems`, and a signed spec with `listItems` is untouched. Both are pickable (`OFFERED`), with plain words, card sentence, red line and worker brief. Test-proven on real bareguard; not seen live.
|
|
30
|
+
- **A rubric job now has ONE list of checks, made once before the first try (check list, Phase A, hamr 2026-11-11).** Test-proven; not seen live. Before, the confirm AI, the page look, the person's picks and the drafter each kept their own list of what a line checks, and they drifted (paid rounds 8-10). Now, after the look and the pick path and before the confirm turn, code builds one list (`src/checklist.js`): a `~` row for each rule the person wrote, a `!` row for each fact the look kept and for up to three count or phrase checks one new call (`ledger-suggest`, its spend joins the drafting cap) suggests from the inputs, and a `$` row for each default code adds itself (every claim quotes the input on a text line of a one-input job; the numbers tie after a fact line). Code proves each `!` row against the input and drops it with a reason otherwise; a `~` rule always wins over a `!` on the same thing. The drafter is shown the list in one code-written block; after each try a part with no row goes to Not checked ("Not on the list of checks made before the draft, so you judge it at Accept."), a fact's result count rides with its fact, and the default cited part is decided after the draft settles (also after the last-try drop). A check that needs exact words holding a version or a date ("## [0.54.1] - 2026-11-04") is refused as true only for the input as it is today ("It names a version or a date from the input, true only for the input as it is today, so you judge it at Accept."). An empty list is logged as "empty list: nothing to check" and ends in the existing no-check stop. Both doors build it (the panel and the author CLI; the CLI asks nothing); there is no switch. The drafting log gets a `ledger` line per row at the build and at the end, and a `ledger-try` line per try. Rubric jobs only; a code job's prompts are unchanged.
|
|
31
|
+
- **The signed close carries the list, and the readers read it (check list, Phase B, hamr 2026-11-11).** Test-proven on 38 real saved drafts of paid rounds 9 and 10; not seen live. `closeDecl.list` holds each row's line, key, from, by, kind, state, rule, part (the part that carries a built row) and reason, and never the row's words (the words stay in the drafting log); the close validator shape-checks it, and no hashing code changed. When a close carries the list: the card's and the Job tab's Not checked read its not-checked rows (one reader, `refusedOf`), the end check is "no built row" (the mechanical floor never counts), retention is counted from its final rows, and signing refuses a close whose list and checks disagree (`listMatchesClose`). A close with no list reads as before. The card after drafting is read from the signed close alone (`cardOfClose`, the same source as the Job tab) and now shows the close's notes too; `reconcileRubricPlan`'s three-source merge, `moved` and the `rulesOfLine` twin are gone. The rubric drafter is no longer offered `covers` or numbered confirmed checks (a legacy `covers` on a saved part still validates).
|
|
32
|
+
- **The run-time worker is told the checks the person picked (R10, fwd am28 "Check 0b", ported by rewrite).** Test-proven; not seen live. A facts line that also carries picked checks (keep-both) now has one plain line per pick in its worker brief, written by code from the signed record of the picks (`closeDecl.picks`), for example `Your "text" must have exactly 3 list items; a list item is its own line starting with "1." or "- " followed by a space and its text.` or `Your "text" must have at most 80 words.`; a check that is not the person's pick is not told, and a close with no picks reads as before. A text-only line with picks is not told yet (fwd tells only its page-quoting steps; same scope here).
|
|
33
|
+
- **A rubric job's confirm turn now plans the goal only.** The turn sends one sentence; any check, gap or question the model sends is discarded by code, so the confirm card shows no check and the drafter is no longer told "the person confirmed" checks (the list is the one plan). The plan card and the Job tab mark a check code added itself `[default]`, beside `[you picked]` and `[agent]`. Phone width not checked.
|
|
34
|
+
|
|
35
|
+
- **A rubric job's checks are now built by code from ONE list; the AI only sends edits to it (check block, hamr 2026-11-12: "one flow one place, ai suggests !, code adds $ and code decides what worked/doable").** Test-proven through the real drafting loop and the real panel session; not seen live. The drafter's reply is a list of edits (add a fact, phrase or result count; read a limit for a `~` rule; pick a check for a counting rule; say a rule cannot be checked), each judged alone: a refused edit says why and costs the others nothing. Code proves every word on the saved page, builds every check, and says in plain words why a row is Not checked. The AI never writes a check or a declaration, and the prompt no longer restates the list. A Tickets job's reply keeps its optional `ticketFilter`.
|
|
36
|
+
- **A draft revises only when an edit was refused or the starting-point read failed, at most twice (check block, ruling 3).** Before, every failed gate sent the drafter back. A plan code built that fails its own gate now stops as a build fault in plain words ("the plan code built from your checks did not pass its own gate ... a fault in the build, not in your job"), and the AI is never asked to fix it. Test-proven; not seen live.
|
|
37
|
+
- **Code reads a limit from the person's own words (hamr ruling A, 2026-11-12).** When the look picked the shape for a `~` rule but gave no limit, "under $450", "at least $200", "between $100 and $300", "between 05:00 and 21:59" are read by code; a rule with two limits, a negated one, a one-sided time or a 12-hour time stays Not checked with a plain reason. Test-proven on a frozen table of 42 rules; not seen live.
|
|
38
|
+
- **The progress lines of a rubric draft say edits: "N edit(s) kept, M refused" and "the list at the end: N built, M not checked".** Test-proven.
|
|
39
|
+
|
|
40
|
+
### Fixed
|
|
41
|
+
|
|
42
|
+
- A rule like "under $450" is now checked as under, from your own words, even when the page reader wrote at most. A page-reader or AI reading that disagrees with a limit code can read in your words is refused with a plain reason; words code cannot read behave as before.
|
|
43
|
+
- **The confirm card of a rubric job now shows the checks the draft built (hamr 2026-11-12, live draft session smwe2qz5g3xrq).** It showed only the summary, the job line, "How the page was read" and "Always checked": none of the rules, facts or the result count the list had built, and no Not checked row. It read the confirm turn's own plan (the goal only) instead of the list's rows. It now draws each row under its job line, and each Not checked row with its reason, through the same readers as the signed card, so the two cards cannot differ. The model's own plan is still the goal only and what is accepted is unchanged. Test-proven (real page map, real session, fixture of the live rows); not seen live. The short "Your answers are in" bubble after a question still shows the lines and your picks only (the full card follows it).
|
|
44
|
+
- **A fact the look tied to a `~` rule carries that rule by code when it has a bound (hamr 2026-11-12: "checks that are checkable and agreed should be part of the plan and should be verified").** On a job with "~ under $450" the look ties the price fact to rule 1 and drops its list row ("a ~ rule wins"); the drafter then put `rules` on the fact or nowhere, the fact was refused "not on the list" and the rule went unchecked (a draft stopped after 3 refused tries; another run went green with the rule not checked). Now the part carries the rule number by code, and the fact's bound is the drafter's own `rule`, else the look's reading, else (a phrase fact) its own fixed words; with no bound the rule stays not-checked. Test-proven on the saved session shape (smwdiy4k3bk0v); not yet seen in a fresh live draft.
|
|
45
|
+
- **The Job tab now names every Not checked row of the check list, and shows the one the list dropped for naming a version or a date (F318, first live run mwc2u3yh).** Test-proven on a copy of that run's own signed spec and draft log; the real screen is re-checked by hamr. A phrase row the plan did not build read ` — the plan did not build it` with no name; it now reads `phrase "### Fixed" — the plan did not build it` (the words come from the drafting log; with no log, a CLI or imported run, from the row's key: `phrase "### fixed"`). A row dropped because it names a version or a date used to be missing from the tab; it now shows under its line with its reason, as the card preview of the build spec says. Other dropped rows (a `~` rule wins, words not in the input) stay out.
|
|
46
|
+
- **The drafting plan card's Not checked now names a phrase row the same way the Job tab does (F318).** Test-proven; not seen live. It read `line 1: rule phrase — the plan did not build it`; it now reads `line 1: phrase "### Fixed" — the plan did not build it` (one owner, `listRowName`; the drafting log's words, else the row's key).
|
|
47
|
+
- **Answering "agree" to a reading that is the rule's own words no longer adds a second identical `~` line (F318).** Test-proven (real panel session); the pick now cites the rule that is already there. Case, spacing and a trailing full stop do not make words different. Agreeing to DIFFERENT words still adds a `~` line, as before.
|
|
48
|
+
- **A fact the look tied to a counting `~` rule ("exactly 3 bullets") now stays in the plan beside the pick, and a pick follows the line's fact on the card (check block).** The tied fact used to be swallowed; the card drew picks first. Test-proven; not seen live.
|
|
49
|
+
- **A word the draft gate would refuse now makes that one check Not checked, in the gate's own words, and the draft goes on (check block).** A label the look dropped or never kept, a unit or currency sign not on the page, words found fewer times than the line's result count, an input the job does not have, or no input named when the job has two used to stop the whole draft. Test-proven; the real run mwdhma1l's "12 results returned." counted once for 3 results is one of the cases; not seen live.
|
|
50
|
+
- **A file job's "I can't check this" question is fwd's again, and a proposal comes before it in rule order (check block).** The look's questions come first, then the pick questions in rule order; the Drop it button on a can't-check question drops the rule. All questions go to the person whole, so Agree shows on a proposal. The picks record is now written on every draft (a Revise that asks nothing still carries the picks), and a rule a broken pick pair rides is not asked on its own. Test-proven in real panel sessions; not seen live.
|
|
51
|
+
- **A rule the person left reads "You chose to leave it Not checked, so you judge it at Accept." and a rule they answered in their own words reads "Your own words are on the line; the machine has no check for them, so you judge it at Accept." (check block).** The words the old chain used, kept. A job line no check could be built for is listed under Not checked as a line, never as a draft stop. Test-proven.
|
|
52
|
+
- **A version or a date a tied `~` rule does not name is no longer signed as fixed words (check block, hamr 2026-11-11 one owner).** It is placed by a place rule or stays Not checked; a version and a date in one phrase are two facts named "<name> version" and "<name> date". Test-proven; not seen live.
|
|
53
|
+
|
|
8
54
|
## [0.55.0] - 2026-11-10
|
|
9
55
|
|
|
10
56
|
### Added
|
|
11
57
|
|
|
58
|
+
- **A rubric job whose declaration ends with no real check is refused before signing, whatever the seed gate says (R10 end check, hamr ruling 2026-11-10).** Test-proven; not seen live. Paid round 6 draft 17 (session smwag7ncubmip) ended signed-ready with a rubric-step holding no part plus files-changed: the earlier stop fires only when the seed gate reads green, and an empty rubric-step reads red at seed. Now, after the declaration is settled and before the signing gates, both doors (the panel `finish`, the author CLI) refuse such a close with exactly the same words (`noCheckStopText`, one owner in `src/authorreadout.js`); a part of class none or guard no longer counts as a check. No prompt text changed.
|
|
12
59
|
- **A rubric / page job whose close has no check that can fail now stops with words that say so (R10, hamr ruling 2026-11-10).** Seen live as draft 18 of paid round 5 (session smwabidzpqvgt: the only stage was files-changed, so signing refused with the repository sentence); the new words not seen live. Test-proven. When signing is refused because nothing fails on the seed and the close is a text-lang close holding no check part (only files-changed, or rubric-step stages with no parts), the stop reads "This job has no check that can fail..." with a to-do to add a `~` rule or answer the question. Repo jobs and rubric closes with a real check keep the old words. This stop fires only when nothing in the close fails on the seed. A plan can still end with zero checks (after a drop, or when every part goes to Not checked), seen live in paid round 6 drafts 2 and 17; an end check that closes this is the next release's first fix (F309). `isNoCheckRubricClose` and the `closeDecl` argument of `signingStopText` are in `src/authorreadout.js`; the CLI (`src/authorrun.js`) and the panel (`src/panel/authorsession.js`) both pass the close.
|
|
13
60
|
- **A rubric draft whose last try still has a broken AI check now drops that check to Not checked instead of dying (R10, PRD v1.131 tick 4).** Seen live in paid round 6 (3 drafts); round 5 had 0 firings. After the LAST try failed the plan check, and only when every red points at one part the AI wrote (not a pick, not a guard, not a check code built from the person's picks), code drops those parts: a pure extra becomes a `line N: "<words>"` note, a part that carried a `~` rule no other part carries becomes that rule's Not checked row, both with `The AI couldn't build a working check for this, so you judge it at Accept.`; the plan is then checked once more. Any red on a pick or on no part leaves the plan refused as before. A $0 replay of the 7 saved dead drafts of paid rounds 1-4b rescued the 3 that were still red (round 4 d8, round 4b d1 and d4) with both agreed picks and the picks record identical, and 21 passing real declarations came out unchanged. Rubric jobs only. The retention record counts each drop as `dropped`. `dropExtras` is in `src/checkpick.js`, `dropAfterLastTry` in `src/authorflow.js`. Caveat (F309): when the drop removes every AI part of a line the rubric-step is left with `parts: []` and the plan is still accepted, so it can sign with zero checks (seen live, paid round 6 draft 2); the next release's first fix is an end check for this.
|
|
14
61
|
|
package/bareloop.context.md
CHANGED
|
@@ -66,6 +66,8 @@ A rubric or plain-folder job whose signed spec carries `mcp` (and flow type `tic
|
|
|
66
66
|
- **R7b: no Ticket box, a Destination that must exist, a visible refused look.** The New job card no longer has a Ticket box (the page never sends `ticket`; the server still reads `card.ticket` from a scheduled fire and "Run it anyway", which become `run-u --ticket N`). A by-hand Tickets run takes the newest unrun ticket, looked up by `execute` (`ctx.pickNewest`) before the run's row is built; a refused look (token, unreadable list, nothing new) lists the run and settles it at $0 as `refused before start` with the words `The newest ticket could not be looked up. The reason: <cause> Fix that, then start the job again. The run did not start. Nothing spent.` A repo job's Destination (`startDestinationProblem`, the one check) must name a folder, file or a glob under a real folder of the repo's committed tree (`destinationMissingInRepo`, `src/source.js`), else `Destination `<piece>` is not a folder or file in this repo. Type the folder that holds the files the job should change, like src/.`
|
|
67
67
|
- **R7b: the drafter points at a file outside Destination (`src/destpoint.js`, `runDestPoint`/`decideDestPoint`, wired in `src/panel/authorsession.js` before the composer; `deps.destFn` is the test seam).** A repo job only. The model sees the numbered job lines and the Destination, never the file list; code keeps a point only when the path is written in that line, is in `repoTrackedFiles`, the folder is its parent and `destinationCovers` says the file is outside. One `answer` ask with `source: 'dest-point'`; `yes` sets `writeScope`, `draft.writeScope` and `state.card.destination` (the caller's card object is not mutated), `no` changes nothing. Draft-log rows: `dest-point`, `dest-answer`.
|
|
68
68
|
- **R7b rulings: the Start-time ticket check, the skip, the Job tab.** `startSession` (non-headless, Tickets flow incl. Reuse) calls `newestUnrunTicket` (`opts.newestUnrunTicket` is the test seam) before `createSession`: a failure is a 400 whose `error` is the reader's `say` + ` Nothing spent.`; the reader's nothing-new result is `{ok:false, nothingNew:true, say:'No new ticket since #N. Nothing to run.'}`. In `run-u` the same result at run start settles the listed row as `reason:'skipped'` (`words` = say + ` Nothing spent.`, exit 0); any other look failure stays `reason:'refused before start'`. `getRunJob` reads `resolved-spec.json` from the session folder the row's spine path names even when the spine file does not exist.
|
|
69
|
+
- **One check block per rubric job (`src/checkblock.js`, `CheckBlock`; made by `authorCloseForJob` and driven by `authorClose({block, editGenerate})`; it replaced the Phase A/B list's own readers).** Pure (no I/O, no clock, no model): ONE store, `rows`, of three kinds: `~` (the person's rule, `by: you`), `!` (the agent's: a look fact, or an AI edit, `by: agent`) and `$` (code's defaults: the cited rule on a text line of a one-input job, the numbers tie after a fact line, the mechanical floor which never counts; `by: default`). Code matches every row against the saved page and builds every check through the bareguard shapes; a row it cannot build keeps its place with a plain reason. Every row ends `built`, `not-checked` (with a reason), `suggested` or `dropped`. The AI's whole part is a list of row EDITS (`add`, `reading`, `pick`, `not-checkable`; `src/rowedit.js`, tool `submit_edits`), each judged alone by code (a refused edit costs the rest nothing; at most `MAX_BANG` = 3 adds per reply); `editGenerate` is its model boundary and `ledgerGenerate` the `ledger-suggest` call that seeds the `!` rows (absent = the block is built from the look and the defaults). A `~` wins over a `!`; a check needing exact words that hold a version or a date is refused as week-only unless a place rule fits it (below); a `~` rule that carries a negation (`NEGATING_RE`) builds no phrase check. With `split` (the product path) code splits the `!` rows: words (or the count number) found in the job line or its `~` rules = JOB-DERIVED (built, the person may Drop it); anything else is SUGGESTED (held out of the close, offered only when code has proved it builds, switched on by Add). A rubric job's confirm turn plans the goal only (`confirmSystemFor`, `RUBRIC_CONFIRM_NOTE`; `accepted.goalOnly` is `true`). Progress: `onPhase('draft-ledger-try', {label, kept, refused})` per try, `onPhase('ledger-built', {rows})` once when the block is made and `onPhase('draft-ledger', {rows})` / `onPhase('draft-retention', {lines})` at the end; the panel writes `draft-log.jsonl` lines `kind: 'ledger'` (per row, `phase: 'built'` or `'final'`, with `key`, `line`, `rowKind`, `from`, `by`, `words`, `state`, `reason`), `kind: 'ledger-try'`, `kind: 'draft-notbuilt'` (suggested checks code could not build, one plain sentence each) and `kind: 'row-edit'`; the CLI emits the same phases to the author spine as `author-phase`. `authorClose` returns the signed form of the final rows as `ledger` (`signedRows`) and `authorCloseForJob` returns the unbuilt suggestions as `notBuilt` and carries the rows as `closeDecl.list` (fields `SIGNED_ROW_FIELDS`: line, key, from, by, kind, state, rule, part `{line, part}`, reason; never words), admitted by `CLOSE_DECL_FIELDS` and shape-checked by `validateCloseDecl`. Readers: `refusedOf`/`ruleNotChecked` (Not checked), `retentionOfList`, `listMatchesClose` (called by the panel's `signRun`), `cardOfClose` (the card after drafting, from the close alone). The confirm card's Drop / Add are `POST /api/author/<session>/row-edit` `{op: 'drop'|'add', key}`: $0, instant, no model call, answered 400 `bad-row` / `bad-choice` / `no-plan` in plain words. While a question is open, `POST /api/author/<session>/send` with no typed `choice` is refused 400 `bad-choice` (an out-of-date page): nothing is logged and the question stays open. The Audit's `Checks` fold lists the card's sections (Checks, Not checked, Always checked) with each row's recorded result. Rubric jobs only; a code job is unchanged.
|
|
70
|
+
- **Place rules (`src/placerule.js`; hamr go 2026-11-11).** A phrase fact whose words hold a version or a date is true only while the input stays as it is. At drafting, CODE fits a place rule (`{kind: 'headingBetween'|'headingDateAfter', prefix, end, shape, skip}`; `fitPlacePhrase`) to the input's own newest release heading and the signed fact carries it as `fact.place`; the value itself is never signed. At run start, before any provider call, code re-reads the run's own frozen copy of the input with each rule (`readPlaceRules`): the values found are bound as those facts' phrases on the run's in-memory copy AFTER the approval check and the `job-start` record (`bindPlaceValues`, so the signed spec and its hash never change), and the run records one `place-rules` spine event (rows `{key, kind, found, value, was, reason}`) right after `job-start`. A rule that finds no value stops the run at $0 with every rule listed in plain words (`stopWords`). A resume or a door Accept/Rerun rebinds the values from that run's own `place-rules` record (`placeValuesOfEvents`), and a door with no record refuses (`NO_PLACE_RECORD_WORDS`); `runJob` takes them as `opts.placeValues` / `opts.placeRead`.
|
|
69
71
|
|
|
70
72
|
## Public API` → "THE JUDGED FLOOR" and "THE REVIEW DOOR" below. `green` and
|
|
71
73
|
`soft-green` are the only classes on offer for new jobs.
|
|
@@ -4535,7 +4537,7 @@ A **Rubric** job whose first Input is the full path of a FILE (not a repo folder
|
|
|
4535
4537
|
|
|
4536
4538
|
For a rubric job (a text file input; `RUBRIC_LANG`) the **drafter writes no word, section, line, list-item or phrase check**; the person's picks put them there. All of it is fwdloop v0.29.0's, ported and ruled 2026-11-09 (`docs/product/ITEM33-BUILD.md`, R10).
|
|
4537
4539
|
|
|
4538
|
-
- **The
|
|
4540
|
+
- **The twelve pickable rules** (`OFFERED` in `src/checkwords.js`, bareguard `^0.35.0`'s own `rubricVocabulary`): `nonEmpty`, `maxWords`, `minWords`, `maxLines`, `listItems`, `maxListItems`, `minListItems` (bareguard 0.35, F315: "at most / up to / no more than N bullets" and "at least N bullets" map to these; "exactly N" and a bare "N bullets" stay `listItems`), `sections`, `sectionOrder`, `sectionWords`, `mustCarry`, `blockLines`. Each is a `countable` part of the line's `rubric-step` stage (`COUNT_CHECKS` in `src/rubricstep.js`, same mapping to bareguard `createRubric`/`checkStep`), with one fixed plain sentence from `partSentence` (the plan card) and `plainWords` (the ask). `cited`, `minClaims`, `maxClaims` and `numbersFromFacts` are NOT picks and are drafted as before.
|
|
4539
4541
|
- **The call.** After the look and its asks, before the confirm turn, ONE call (`runCheckSuggest`, over `askStructured`: the ceiling is read first, one retry, the scrubbed answer and its price land in `draft-log.jsonl` as `call` label `check-suggest`) suggests, per in-scope `~` rule, one check or `none`. The tool is `suggest_checks` with a per-rule `anyOf` answer form. An unusable answer reads "I can't check this" for every rule (never a guess). Needs `pickGenerate` (the panel wires it from the draft's provider; absent = no pick path, nothing asked).
|
|
4540
4542
|
- **Scope (`scopedRules`).** A rubric job's `~` rules, minus a rule a kept look fact carries (`forRule`) or the look put under Not checked, and minus (fwd's `codeScope`) a rule of a job with a web-page input that names no whole-output word number. `guardLines` cover whole lines and never settle one word-count rule, so they do not remove a rule from scope. D5 mandatory guards are never offered or replaced.
|
|
4541
4543
|
- **Keep-or-drop (`keepOrDrop`).** A suggestion is kept only if its rule is on bareguard's list AND offered, it carries only that rule's own fields, every number is one the rule names (`maxWords 79` for "under 80 words" is dropped) and every word is a word of the rule; a section count must match the rule's.
|
|
@@ -4551,7 +4553,7 @@ For a rubric job (a text file input; `RUBRIC_LANG`) the **drafter writes no word
|
|
|
4551
4553
|
|
|
4552
4554
|
### Required facts — a line that finds, lists or looks something up (Part 1b, `src/facts.js`, `docs/product/ITEM33-BUILD.md` "Addendum 2026-10-13" and "Part 1c", PRD item 33 RF1–RF22)
|
|
4553
4555
|
|
|
4554
|
-
Check what the person asked for, not what the worker chose to write. bareloop needs bareguard `^0.
|
|
4556
|
+
Check what the person asked for, not what the worker chose to write. bareloop needs bareguard `^0.35.0` (0.31 adds `listItems` and `carriesAny`; 0.35 adds `maxListItems` and `minListItems`) (`cited` + `decides`, bind-only and `text` decides, word-edge anchors; 0.24 lets money currency/unit be lists, ruling #65; bareloop facts now carry them, see "Currency and unit lists" below; 0.25 returns `full.evidence`, the spans the Result tab marks, see `rubric-evidence`).
|
|
4555
4557
|
|
|
4556
4558
|
- **The part.** A `rubric-step` stage's `params.parts` may hold ONE part of `class: "fact"` (a line that finds, lists or looks up): `{ text, class: "fact", source: <input label>, facts: [{ name, shape, unit? | currency?, phrase?, anchor?, until?, rule?, aiProposal? }], count?: { min?, max? }, rules?: [n], covers?: [n] }`. `shape` is `money | number | date | time | phrase | text`; `rule` is `{ op: lt | lte | gt | gte, value }` or `{ op: "between", lo, hi }` (not on `text` or `phrase`); `money` names at least one of `unit` (the input's own words, e.g. `"US dollars"`) or `currency` (`$ € £`), and may name both, each one value or a list (below); `phrase` carries the fixed `phrase` the quote must contain; `anchor` / `until` are labels copied VERBATIM from the input. A fact name is letters, spaces, `_` or `-` only (it is written into the claim text bareguard scans for numbers). A line with a fact part has no word, section or claim-count parts (a drafting red). Code fills `tested` (the early-test evidence) and `sample` (what the drafter saw of a big input) into the signed part; a model-written one is replaced.
|
|
4557
4559
|
- **The step file.** `output/steps/<n>.json` of a facts line is `{ "results": [ { "quote": "...", "values": { "<fact name>": "<value as the quote writes it>" } } ] }` — no free text, no `cites`. ONE quote per result holds all its facts, so a worker cannot mix a price from one result with a time from another. `buildStepSpec` makes one bareguard `cited` check with `decides` (the fact's index is its `d<j>` key; a phrase fact is a presence decide and takes no value). The claim text is written by CODE from the values (`name: value; ...`); a `count` becomes `min` / `max` on the number of results. Every value is compared by shape and exactly (`8:15 AM` equals `08:15`, `389` equals `389.00`); a red names the result and the fact in plain words (`plainFactItem`). A JSON number in `values` is read as the string it prints as.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "bareloop",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.56.0",
|
|
4
4
|
"description": "Workflows that earn their own design, with receipts — agent-authored workflows for repeated, long, verifiable jobs that improve across runs under an un-gameable gate.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./src/index.js",
|
|
@@ -29,7 +29,7 @@
|
|
|
29
29
|
"dependencies": {
|
|
30
30
|
"bare-agent": "^0.59.0",
|
|
31
31
|
"barebrowse": "^0.25.0",
|
|
32
|
-
"bareguard": "^0.
|
|
32
|
+
"bareguard": "^0.35.0",
|
|
33
33
|
"litectx": "^0.41.0"
|
|
34
34
|
},
|
|
35
35
|
"devDependencies": {
|