| Age | Commit message (Collapse) | Author |
|
Follow-ups from review of the consolidation pass:
- The agent is a restricted type with the same read-only wording as its
siblings, and every field on its numbered list is a single bounded line, so
a rule name containing a newline cannot fake another entry.
- A group with any number out of range or not an integer is rejected whole
instead of being coerced into a different merge.
- A merge keeps the most conservative review state: the highest priority, the
lowest confidence, and every suspected defect and SME question of the folded
rules.
- Every folded rule is returned with the rule it went into, and the rules
document lists them under "Rules folded into another", so nothing disappears
untraceably. Extra citations show as "Also cited" without the joining word.
|
|
Replace mean
Follow-ups from review of the tolerance check: an absolute tolerance above
1e-6 is refused like a relative one above 1%, numbers are compared as exact
decimals rather than doubles, dotted runs such as 1.2.3 or 10.0.0.1 are text
that must match exactly, and the self-check now changes the leading digit of
every sampled number to prove the tolerance cannot hide a real change.
The business-rules header says how many rules there were at extraction, since
later steps add rules. The assessment says what to do when it recommends
Rehost or Replace, which change no code and so have no build command.
|
|
The extractor is told to cite a single file range per rule, but on a large
Perl codebase it kept returning two or three files and a sentence of
explanation in the source field, which the report and the pane cannot
resolve to a line. The renderer now takes the first path:line-range as the
rule's citation and puts anything after it on an "Also cited" line.
|
|
finish
Two problems from running the commands on real repositories:
- The P0 definition was money- and regulation-shaped, so a music-library
tool got no P0 rules and its behavior contract came out empty. P0 now
means the system's core purpose depends on the rule, or a wrong result is
costly or irreversible (money, legal, data integrity, security or safety,
or the central calculation or decision the system exists to perform).
- Citations came back as lists of ranges, and the rule renderer numbered
RULE-NNN in a different order from the document. Each rule now cites one
range and the numbers read in sequence.
Commands that start subagents now say to run them in the foreground and
wait, because a headless session ends when the model stops talking even if
it said it was waiting for a background agent.
|
|
that ship with the plugin
The command used to carry a 35-line shard-building script inline and asked
the model to write a rules renderer on every run, so the shard list and the
BUSINESS_RULES.md layout varied from run to run and could not be tested.
scripts/make_shards.py builds the shard list from topology.json when the map
has run, and from the directory tree when it has not (skipping vendored,
generated and test-fixture directories, one shard per directory, split at 25
files or about 5,000 lines). scripts/render_rules.py turns the workflow's
result into BUSINESS_RULES.md and DATA_OBJECTS.md with RULE-NNN headings, the
SME section and the coverage gaps, and writes every value from the analysis as
plain text.
The workflow takes an optional sourceDir, so the code can live outside the
workspace, and shard files are kept relative to it. The command drops from 305
to about 150 lines.
|