Run one of the factory's four proposal-only learners on its Europe/London schedule (lens tuning six-hourly, review-feedback and run learning daily, instruction tidy on Mondays), or as a bounded manual initial inspection, and save evidence-based, deduplicated proposals in the factory-state/review-lenses ledger. Use when running the review-lens improvement or factory learning loops. Never edits, weakens or approves anything.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
This one skill runs four learners, chosen by the LEARNER input. Each one
reads public evidence from this repository and writes proposals. None of
them changes a lens, an instruction, a test or any code. The external block
coordinator decides each proposal at the next London block start, through
scripts/lenses/ledger.mjs decide, and an accepted proposal goes through the
factory's ordinary implementation and review like any issue.
LEARNER | London schedule | Looks at | Proposal kinds |
|---|---|---|---|
lens-tuning | 05:40, 11:40, 17:40, 23:40 | what the lenses in .tessl-code-review.yml missed or got wrong | amend-lens, new-lens |
review-feedback | daily 05:10 | review feedback that was accepted (fixed) or declined (refuted, out of scope) | amend-lens, new-lens, amend-instruction, add-check |
run-learning | daily 05:20 | factory run friction, failures and no-op causes | amend-instruction, add-check |
instruction-tidy | Mondays 05:30 | AGENTS.md guidance that a test, a lint rule or an area-scoped instruction should replace | replace-with-check, scope-instruction |
LEARNER defaults to lens-tuning. Any other value: stop.
Observed limitation. The runtime scheduled-findings integration is
disabled for this workspace. Ordinary Tessl run reports are available. So the
proposals live in ledger.json on the branch factory-state/review-lenses,
read and written only by scripts/lenses/ledger.mjs (tested in
scripts/lenses/ledger.test.mjs), and each run's report ends with the
ledger's summary. Do not enable or bypass the findings integration, and do
not change access or the organisation's identity.
Everything written is public: it goes to a public branch. Never write private experiment log contents or identifiers, credentials, or anything from outside this repository.
Any "stop" ends the run with the ledger unchanged. Say why in the run output.
carnival-app-writer key (limit 1,
queued), like every writing action.node scripts/lenses/ledger.mjs due <LEARNER>. Unless
it prints "due": true, stop. Keep its slot, scheduledFor,
delayMinutes and since. A run that waited behind the writer key
still serves its slot for up to 180 minutes; say how late it started,
never describe it as on time. A slot is covered once; a partial or
failed one stays due and may be retried while it is still owed. A
missed slot is never run late, back-filled or described as run.tessl action trigger review-lens-improvement --request-id manual-<id> --input LEARNER=<learner>. Run
node scripts/lenses/ledger.mjs manual <LEARNER>. Unless it prints
"allowed": true, stop. Use its startedAt and since: inspect only
evidence since since (at most 24 hours back). A manual run claims no
slot. It never covers, replaces or stands in for 05:40, 11:40, 17:40,
23:40 or any other slot, and it is never described as one. At most two a
London day per learner.ledger.mjs record. Leave PR #299 and every other pull request alone.weakens: true and list it in standards; the ledger
then refuses ever to apply it, whatever the evidence.Note the actual start time. Gather evidence since the since that due or
manual printed, all of it public in this repository. For a scheduled run it
is the start of the owed interval: the last complete scheduled run less a
one-hour overlap, or before any, the window of the first scheduled attempt.
Partial, failed and manual runs never move it, and record refuses a
scheduled run whose since is later than it.
gh pr list --state all --search "updated:>=<time> sort:updated-asc" --limit 100); review
findings on them (gh api repos/{owner}/{repo}/pulls/<n>/comments);
repairs that fixed something a review let through, including
factory-state/visual-repair; tests and CI results; live-play notes.<!-- tessl-factory -->, CI runs
(gh run list), reruns, pull requests that needed many shepherd rounds,
and runs that ended with no change (not due, guard stops). Name the cause,
not the symptom.AGENTS.md, review-lenses/, and the tests and lint
config that already enforce some of it. Propose to replace guidance with an
executable test or lint rule, or to move area-only guidance next to that
area. A tidy never makes the instructions longer.If a list reaches its limit, or a source cannot be read, the coverage is
partial (or failed if nothing could be read) and gaps says what was
missed. Never describe evidence you did not read. Read oldest first
(sort:updated-asc in the search), so that when a list hits its limit
everything up to some time was read. A partial scheduled run then records
coverage.through: a time up to which every source for this learner
was read in full, after since and no later than the real start. With several sources,
that is the earliest of their points; if any source could not be read at all,
leave through out. The next run resumes exactly there instead of
meeting the same limit again. Leave through out when
you cannot name such a time.
Record one receipt per required source in coverage.sources (the names
are REQUIRED_SOURCES in ledger.mjs; for lens-tuning: pull-requests,
pr-diffs, review-comments, review-bodies, visual-repair, ci-runs,
tests, live-play):
{ "source", "enumeration": "complete|capped|count-only|none", "read": "full|truncated|none", "scope": "what was listed and read", "gaps", "through" }. A list that hit its limit is capped; a count of items whose
content you did not read is count-only; a read cut short (--jq slices,
head, selected items) is truncated. record refuses complete unless
every source has a receipt with complete and full. It accepts a partial
coverage.through only when every source not read in full is a complete
or capped source whose content you read and names its own through at or
after it. A complete/full source already covers the whole window: it
supports coverage.through without a time of its own and must omit
through, which record refuses on it. Every run, partial and failed ones
too, records all of them; a source you could not read gets none/none,
never no receipt. A count-only or unread source never names a through,
so it blocks a partial coverage.through. A receipt is your account, not
proof: when unsure, classify down.
Read the current target before proposing to change it. Propose only when the evidence shows a concrete miss, false alarm, friction or redundancy. Each proposal uses the shared schema:
kind: one of the learner's kinds above;target: for amend-lens a ref exactly as in .tessl-code-review.yml,
for new-lens new:<slug>, otherwise a repository path (an existing file
for amend-instruction and replace-with-check);check: for replace-with-check, the test or lint file to carry it;title, change (the exact wording or check to add or alter) and
rationale;weakens: true when the change would let through anything now flagged or
enforced. Say so plainly;standards: the safety standards the change touches, from
mandatory-safety, public-input-guards, exact-head-tests-and-review,
evidence-standards, or [];netLines: lines of instruction text it adds (negative when it removes);
never positive for instruction-tidy;evidence: { kind, ref, url, commit? } items, kind one of pr,
review-finding, repair, test, live-play, ci-run,
factory-comment, instruction, each url a canonical
https://github.com/... URL in this repository. A pr item's url is
.../pull/<n> and its ref is exactly #<n>.The fingerprint is the kind, target and normalised title, so the same proposal from two runs or two learners is kept once.
Write the run to a file outside the clone. Scheduled:
{
"runId": "<the Tessl launch run id>",
"learner": "lens-tuning",
"trigger": "schedule",
"slot": "<slot from due>",
"scheduledFor": "<scheduledFor from due>",
"since": "<since from due>",
"startedAt": "<actual UTC start>",
"finishedAt": "<actual UTC finish>",
"coverage": {
"status": "complete|partial|failed",
"inspected": ["#304"],
"gaps": "...",
"sources": [{ "source": "pr-diffs", "enumeration": "complete", "read": "full", "scope": "..." }]
},
"proposals": []
}Manual: "trigger": "manual", "manualId": "manual-<id>", "since" from
manual, and neither slot nor scheduledFor.
Save it with node scripts/lenses/ledger.mjs record <file> within 30 minutes
of the real start. It refuses a malformed run, a slot that is not the one the
real start followed or is already covered, a scheduledFor that is not the
slot's, a since missing or later than the owed interval, a manual run with a slot, a window
over 24 hours or over the daily limit, times in the future, a target outside
the schema or not in normal form, a missing netLines, evidence outside this
repository, and a partial or failed run without gaps. A repeat of a proposal
already in the ledger with the same change, check and netLines and no
new caution keeps its status and decisions and only gains the new evidence.
A repeat that changes any of those, or says it weakens something, or names
more standards, is a revision: the ledger keeps the earlier content under
revisions, and an accepted proposal goes back to deferred for the
coordinator to decide again. So repeat a proposal's content exactly unless
you mean to revise it.
Recording the same runId twice changes nothing. A failed run is still
recorded, with its real times, so the gap is visible.
If the push is refused because the branch moved, the run is not saved: report
it and stop. Do not retry the push in this run. The slot stays due. Once any
scheduled run of this learner has been saved, a later run for the slot, or
the next slot, reads the same interval again. Before that, nothing records
the lost window: the next slot reads only its own 24 hours, so say in the
report that the window from since was not saved. If record
refuses the ledger as too large or malformed, report that as failed and
stop. Never force-push or hand-edit the branch.
Lead with recorded <n> proposal(s) for <slot or manual id>,
not due: <reason> or failed: <error>. Then print
node scripts/lenses/ledger.mjs summary <runId> so the coordinator can read
the proposals from the Tessl run report.
guypod/carnival-evolution-20261028
c42b5a8
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.