Skip to content

feat: revising-manuscript with revision ledger; specific synthesis conclusions - #136

Merged
leiverkus merged 3 commits into
mainfrom
feat/revision-ledger-specific-synthesis
Nov 15, 2026
Merged

leiverkus merged 3 commits into
mainfrom
feat/revision-ledger-specific-synthesis

Conversation

@leiverkus

Copy link
Copy Markdown
Owner

Why

Feedback from a user in theology and biblical studies:

  • The research part works well.
  • Two problems show up once people work on the real text:
    1. Revising paragraph by paragraph: arguments discussed and agreed earlier seem to be forgotten later in the session.
    2. Syntheses and conclusions are sloppy and very general.

Diagnosis

  1. No skill covered revising an existing text. drafting-manuscript keeps the planned argument on disk (outline, sketches). The decisions made while discussing a text paragraph by paragraph lived only in the chat, where attention dilution, compaction and local re-optimisation erode them.
  2. The synthesis page only required Evidence base and What stays open, and no review checked whether a conclusion was specific. When a model integrates many sources at once, it defaults to hedged consensus prose ("a complex picture emerges").

What

  • New skill revising-manuscript:
    • a revision ledger on disk (outline/<name>-revision.md) with decisions in the user's words, including rejected proposals and why
    • the ledger is re-read from file before every paragraph
    • minimal edits, shown as before/after with a ledger check
    • approved paragraphs are frozen and change only when explicitly reopened
    • a look-back every ~5 paragraphs and after compaction
  • Synthesis contract in executing-research-plan → Writing a synthesis:
    • the author states the conclusion first
    • source pages are re-read before concluding
    • each conclusion is a claim block: concrete anchor, carrying sources with pages, kind, counter-position, what would make it wrong
    • a specificity test cuts sentences that would be just as true of a neighbouring topic
  • The rules are enforced in three places:
    • the hermeneutic synthesis review
    • semantic-wiki-review, which flags generic conclusions as weak-support with a generic: detail (no schema change)
    • a new precision rule in drafting-manuscript
  • Registered everywhere the skills are listed: session index, OpenCode fallback index, using-research-powers, README/docs, and the phase-flow graph (SVG regenerated).
  • New pressure scenario: tests/pressure/revising-manuscript/forgotten-decision.md.

Verification

  • python3 -m unittest discover -s tests: 533 tests OK (2 skipped)
  • scripts/lint-plugin.py: 18 skills, 7 agents, no drift
  • scripts/pressure-test.py validate: 6 scenarios, 0 problems
  • bun test opencode/tests: 7 pass
  • claude plugin validate .: passed
  • Example project lints clean

Not done yet: the new pressure scenario has not been run RED/GREEN against a model.

🤖 Generated with Claude Code

leiverkus and others added 3 commits November 15, 2026 16:05
…nclusions

Feedback from the writing phase: arguments agreed earlier were lost when a
text was revised paragraph by paragraph, and syntheses/conclusions read as
generic.

- New skill revising-manuscript: decisions kept in an on-disk ledger and
  re-read before every edit, minimal edits with a ledger check, approved
  paragraphs frozen, periodic look-back.
- Synthesis contract in executing-research-plan: author's conclusion first,
  claim blocks with concrete anchor and falsifier, specificity test; checked
  in synthesis review and semantic-wiki-review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…decision

Option B no longer spells out the compliant answer, and the author's explicit
P06 request now counts as a legitimate reopening rather than a violation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leiverkus
leiverkus merged commit da0effd into main Nov 15, 2026
7 checks passed
@leiverkus
leiverkus deleted the feat/revision-ledger-specific-synthesis branch November 15, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant