mirror of
https://github.com/morluto/rea.git
synced 2026-10-31 11:56:12 +00:00
38719a6fa9
* feat(environment): explain values an application derives from other fields
Prompt-built environments withheld creates whose responses carry values the
application derives deterministically, which the write model kept as
constants or could not match across calls:
- A composed string is literal text plus parts read from the fields other
rules write: a field's value, its slug, or a clock's calendar digits. A
create composes a string only when another entity of the type spells it
the same way and none spells it otherwise, and never from two sources
serving could tell apart; an update composes an unsent change from members
stored as sent and unchanged fields that also spell its value before the
call. A composed field no longer pins the members it reads.
- A trimmed clock format drops trailing fraction zeros, as Go spells
nanoseconds. It is learned from the type's values, a later create or a
later update, and spreads to the plan's other clocks unless a value shows
a fixed width.
- A large integer no entity of the type holds, among distinct ones of the
same length and kind, is a generated unique value, served as a seeded
integer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(environment): record the derived-values verification
Gates, tests, write plans over 69 recorded captures and served write tasks on the baseline and on this branch.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(environment): keep clock spellings, linked ids and word boundaries honest
- A later update's clocks take the plan's spelling, sibling-trimmed
clocks included, wherever the call's values fit it, so an update whose
later call trims only one of two clocks is served.
- A held value that ends its fraction in a zero keeps a create's clock
at a fixed width, whatever order the held spellings come in.
- A large integer that another field of the created entity also holds
is linked, as a repeated token is: it is never unique, and the create
is withheld as unexplained-change.
- Composed parts are delimited by whole characters through the shared
joinsBefore/joinsAfter, so an astral letter joins a match to its word.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(environment): keep a same-width fixed clock out of trimming
A held .123456780 beside a held .12345678 keeps the create's clock at
nine digits in either order; the cases fail on 8ce1127b5.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(environment): check composed parts and clock fits before they shape a plan
- A composed string whose part has nothing to spell refuses the create
or update through the apply Result instead of keeping a stale value.
- A composition learned on a later call is rebuilt from each earlier
call's fields, so an earlier call that left the value otherwise
contradicts it.
- An update adopts its fitted clock spellings only after the
unknown-entity and contradiction checks, so a call on an entity an
unmodelled write left unknown no longer trims a served plan's clock.
- Sibling trimming on a later create also checks that call's fields,
so a sibling clock it shows with a trailing zero stays fixed-width.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(environment): split the derived-values view tests by rule
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(environment): keep fixed-width, zone and generated-integer evidence through a plan
- A plan keeps the first value that showed each clock at a fixed width,
from held entities and every accepted create or update. No later fit
or sibling trim widens that field, and a later call that shows it
shorter is withheld.
- Two stamped clocks are one composed source only when they share a
zone offset. A held entity that holds the target field as anything
the parts do not spell, a non-string included, vetoes the
composition. The token index is built once, and only when a string is
left to compose.
- A generated integer that another field repeats as a number at any
depth is linked. Compare treats two integers of one JSON kind and
length under a unique rule as generated values.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(setup): share registration prewarm host preparation
* fix(environment): retain write evidence and match trimmed response clocks
* fix(environment): withhold creates whose generated integer another string repeats
A unique integer whose digits show in another top-level string that no
template or composed rule rebuilds from it (an echoed serialText, or a
token like folder-<id>) withholds the create as unexplained-change,
since serving would seed the integer and keep the string. A templated
copy is still served.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(environment): hold later creates and compare to the composed and integer forms
- A later create whose response spells a composed field otherwise than
the plan rebuilds it is withheld as unexplained-change.
- A unique field learned from a generated integer accepts only an
integer of the same length and kind from a later create, as serving
seeds one.
- Compare counts a composed field as equal when each side's response
spells it from its own fields, which compare under their own rules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(environment): preserve composed parts and unique generator families
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
92 lines
6.8 KiB
Markdown
92 lines
6.8 KiB
Markdown
# Verification
|
|
|
|
Executed on macOS with Node v24.22.1 at `a1edeafd` (main `79845063` plus this branch). The prompt-built recordings and
|
|
evaluations used a local, unpushed build of this branch merged with the scenario-timing branch (#6967), whose request
|
|
times the clock rules need from browser scenarios, on Ubuntu 24.04 VMs with snap Chromium 155. The baseline is the same
|
|
merge without this branch.
|
|
|
|
## Gates
|
|
|
|
Follow-up on 2026-10-25, after merging main `a5bfd0440`, with Node 24.22.1 and npm 11.16.0 on macOS:
|
|
|
|
- Environment write/compare source tests: 26 files, 839 passed.
|
|
- Analysis-view CLI/MCP, environment served-write MCP, environment-compare CLI, managed bundle read guards, and setup
|
|
registration prewarm boundaries: 6 distinct files, 77 passed. The managed low-headroom failure is fixed by main's
|
|
Evidence ownership change (#7036); the setup tests share host preparation to satisfy lint without removing cases.
|
|
- `check:fast`, `format:check`, and `docs:check`: passed.
|
|
- New capture-to-plan regressions reproduce missing composition parts on earlier updates (null and structured sources)
|
|
and fixed-width clock evidence from either the selected entity or another held entity. Rule tests exercise several
|
|
separator/zone groups in both orders, choosing each group's widest trimmed peer while preserving fixed-width fields.
|
|
- Compare uses the domain clock matcher on parsed readings. Tests cover shorter fractions, absent fractions, maximum
|
|
width, trailing zeros, separators, zones, and response-entity scope; the compiled CLI accepts a Go-style create whose
|
|
live clocks have eight digits and served clocks have none, preserving all input Evidence files.
|
|
- The original application's recordings and model evaluations below were not rerun in this follow-up.
|
|
|
|
Original author validation:
|
|
|
|
- `npm run -s typecheck`, `lint`, `format:check`, `docs:check`, `mcp-catalog:check`, `verify:test-discovery`,
|
|
`scan:todos` and `npx knip`: passed.
|
|
- `npx vitest run --project domain --project services --project adapters`: 17,246 passed, 25 skipped, 1 failed ("stops
|
|
Inspector target authorization after the current stat settles"), which fails the same way on main in this environment.
|
|
- `npm run test:prepare`, then `npm run test:focused --` the environment build, export and serve CLI boundaries, the
|
|
analysis-view CLI and MCP boundaries, the environment serve, served-writes and bundle MCP boundaries, MCP schema
|
|
validation and output schema constraints: 10 files, 82 passed.
|
|
|
|
## Tests
|
|
|
|
- View: Go-spelled tag creates and renames are served with a trimmed clock; bookmark creates are served with a composed
|
|
snapshot address and accept any URL; folder creates and renames are served with a composed address and a generated
|
|
integer id.
|
|
- Serving: a served tag create spells its clocks without trailing zeros; a served bookmark create composes its snapshot
|
|
address from the served clock and the sent URL; a served folder create gets a fresh sixteen-digit id and an address
|
|
that follows its uid and title, and a rename moves the address.
|
|
- Unit: fitting clock formats (trimmed, fixed width, separator and zone), calendar digits, seeded integers, generated
|
|
integer detection, composition and its refusals (one call alone, a held entity spelling otherwise, two sources with
|
|
one text, a member stored otherwise than sent, a value the parts do not spell before the call), and a wide body
|
|
composed within the existing time limit.
|
|
|
|
## Write plans over recorded captures
|
|
|
|
Every write plan of 69 captures, built by the baseline and by this branch: the 50 published captures, 18 captures
|
|
Claude Code recorded from a prompt for the prompt branch's checks, and one new timed Grafana recording.
|
|
|
|
| Captures | Write plans | Served on the baseline | Served on this branch |
|
|
| ------------------------- | ----------- | ---------------------- | --------------------- |
|
|
| 50 published | 187 | 68 | 68 |
|
|
| 19 recorded from a prompt | 120 | 56 | 61 |
|
|
|
|
- No write goes from served to withheld. The five gains are Linkding's bookmark create, Homebox's tag create, and
|
|
Grafana's folder create in two recordings and folder rename in the timed one.
|
|
- Published plans change only where a value is now composed: Linkding's bookmark create and BookStack's book create and
|
|
update (`description_html` as `<p>` around the description) now accept the member they read.
|
|
- Unchanged by design: Grafana's published folder, whose uid and title slug are the same text, so its address names two
|
|
sources; Ghost's post update, whose `lexical` keeps the `derived` rule that explained it before; BookStack's page HTML
|
|
and Jellyfin's playlist path, which other pages and playlists of the capture spell otherwise.
|
|
- What still withholds a create the composed value now explains: a later Linkding create that sends a member the first
|
|
did not (`shared`), Homebox item creates that differ from the first location create, and a Linkding create whose
|
|
read-back lists `tag_names` sorted.
|
|
|
|
## Served write tasks
|
|
|
|
The same timed captures, rebuilt by the baseline and by this branch, with the models `fireworks_ai/gpt-oss-120b` and
|
|
`fireworks_ai/glm-5p3-flash`. Create tasks are new; recorded write tasks are the applications' existing ones with entity
|
|
counts taken relative to each bundle's state.
|
|
|
|
| Application | Tasks | Baseline (gpt-oss, GLM) | This branch (gpt-oss, GLM) |
|
|
| ----------- | ---------------------------------- | ----------------------- | -------------------------- |
|
|
| Linkding | 2 bookmark creates | 0/2, 0/2 | 2/2, 2/2 |
|
|
| Linkding | 3 recorded (update, notes, delete) | 3/3, 3/3 | 3/3, 3/3 |
|
|
| Homebox | 2 tag creates | 0/2, 0/2 | 2/2, 2/2 |
|
|
| Homebox | 2 recorded deletes | 0/2, 0/2 | 0/2, 0/2 |
|
|
| Grafana | folder create and rename | not served | 1/2, 2/2 |
|
|
| Grafana | 2 recorded deletes | | 2/2, 2/2 |
|
|
|
|
- Smoke and retrieval match on both builds (Linkding 9/9 and 8/9, Homebox 3/3 and 3/3); Grafana's new recording passes
|
|
its smoke task and 9/9 retrieval with both models.
|
|
- gpt-oss missed the Grafana rename by sending the update without the title it was asked to change, ten times; the
|
|
served environment refused each call with the members it accepts.
|
|
- Homebox's recorded deletes fail on both builds: this recording's served entity list holds its locations only, so the
|
|
models never find the item to delete.
|
|
- The created bookmarks' snapshot addresses and the created and renamed folders' addresses are checked from the
|
|
environment's state.
|