Repository navigation
Description
Reconciled 25 October 2026 with the independent assessment on #254 (edit 4). P1's assumptions exposed by #256: language comes from the scope's lexemes, not
page.language_tag; scopes are exact sorted lexeme sets, overlapping lexical-page scopes cannot coexist; Published owns eligibility, the reader maps its result; assessment rows are absent until P5; definition highlights have their own tile; actor labels come from the record (the wireframes' "Holden" is "Account #2" until the owner sets a label). The approved typography change and the actual live five-lexeme love scope stand, not the two-lexeme fixture. P1's temporary work/exemplar withholding (:unsupported_item) was repaired by P2 (#258) and is resolved. This issue stays closed; its delivery is evidenced.Rewritten 23 October 2026 as one end-to-end implementation specification for P1 of #254, under #253 (the product rules, which govern on any conflict) and #193. The earlier body and its addendum are merged here; nothing was dropped. Checked against
mainatdc888b7and the live corpus.
1. Outcome
On one pilot word page, /on/love, a manually reviewed and published composition appears as the curated opening: a sourced lead, up to three sourced highlights in stored order, each with its intended meaning and a signed reason, with correct attribution read from persisted records. Withdrawing the publication removes the opening on the next page load. Anything invalid is withheld with a named reason, never substituted. Everything below the opening (Definitions, Examples, discovery shelves, Subjects, Sources) is unchanged.
This is the first visible slice of the curation MVP. It makes the record real on the site so the owner's screen (P2), the pin (P3), the packet (P4), freshness (P5) and proposals (P6) each have a page to prove themselves on.
2. What the reader sees
Every wireframe is the Opening component (#156 Phase 1) drawing the existing %Curation.Opening{} struct from a published origin. Measure with every <details> closed, the way #111 measures.
2.1 /on/love, desktop 1280 × 900, after Delivery B
┌──────────────────────────────────────────────────────────────────────────────┐
│ On love │
│ love /lʌv/ noun · verb 4 dictionaries · 36 senses · 1 subject │
│ forms · origin │
├──────────────────────────────────────────────────────────────────────────────┤
│ ┌── THE DEVIL'S DICTIONARY · Ambrose Bierce · 1911 ─────────────── satire ┐ │
│ │ LOVE, n. A temporary insanity curable by marriage or by removal of the │ │
│ │ patient from the influences under which he incurred the disorder… │ │
│ │ Read the whole entry ↓ │ │
│ │ Editorial preference: where The Devil's Dictionary defines a word, its │ │
│ │ entry leads. Leading is a choice of voice, not a claim that it is true. │ │
│ └──────────────────────────────────────────────────────────────────────────┘ │
│ ┌ DEFINITION ──────────────────────────┐ ┌ QUOTATION ───────────────────────┐ │
│ │ Samuel Johnson · 1755 · n. s. │ │ "…" — Wiktionary example │ │
│ │ (first lines of the entry) │ │ under sense ● noun 1 │ │
│ │ for: love, noun │ │ Read on the card ↓ │ │
│ │ Why this is here: Johnson's four │ │ Why this is here: the plainest │ │
│ │ senses map the word before Bierce │ │ modern use, so the two leads │ │
│ │ turned it. — Holden │ │ can be compared. — Holden │ │
│ └──────────────────────────────────────┘ └──────────────────────────────────┘ │
│ ▸ How this was curated · published 24 Oct 2026 · global-default v1 │
├──────────────────────────────────────────────────────────────────────────────┤
│ Definitions 4 dictionaries · one open at a time (unchanged) │
Height budget: the "Definitions" heading stays inside the first 900 px at 1280 wide. If the lead's full entry breaks it, the lead card shows its first sentence (Curation.Excerpt.sentences/3) and "Read the whole entry" links to the card below, which is what LeadPolicy promises ("a lead is always an entry this page already shows").
2.2 The disclosure, open
Rows P1 fills. The assessment rows (last assessed, checked against the record, inputs last changed, next assessment after) are absent, not blank: they are P5's.
│ ▾ How this was curated │
│ Configuration global-default, version 1 · lead rule bierce_first_v1 │
│ Selected by Holden (operator) · 24 Oct 2026 │
│ Published by Holden (operator) · 24 Oct 2026 · version 1 · receipt #… │
│ Panel none: published by the operator │
│ Withheld nothing │
│ Composition #… version 1 │
2.3 One item withheld
The superseded-revision case. The slot is not refilled; the disclosure names it; the withheld content is not shown.
│ ┌ DEFINITION ──────────────────────────┐ ┌ QUOTATION ───────────────────────┐ │
│ │ Samuel Johnson · 1755 … │ │ Withheld: its source revision │ │
│ │ │ │ was superseded since selection. │ │
│ │ │ │ Nothing was put in its place. │ │
│ └──────────────────────────────────────┘ └──────────────────────────────────┘ │
│ ▾ How this was curated … Withheld Highlight 2: its source revision was │
│ superseded. Nothing was put in its place. │
A withheld lead renders the same way in the lead's place (a short card saying it is withheld and why), with the highlights still shown. Only a version withheld as a whole, or no lead and no highlights, draws nothing.
2.4 Nothing to show
No active configuration, no composition for the scope, withdrawn, rejected, or the whole version withheld: no heading, no skeleton, no empty slots. The page begins at "Definitions" exactly as today. A withdrawn composition and a never-curated page are indistinguishable to the public.
├──────────────────────────────────────────────────────────────────────────────┤
│ love /lʌv/ noun · verb … │
├──────────────────────────────────────────────────────────────────────────────┤
│ Definitions 4 dictionaries · one open at a time │
2.5 Phone, 375 wide
One column, lead first, highlights stacked, disclosure collapsed; "Why this is here" and "Read the whole entry" are 44 px tap targets.
┌──────────────────────────────┐
│ On love │
│ love /lʌv/ noun · verb │
├──────────────────────────────┤
│ THE DEVIL'S DICTIONARY 1911 │
│ LOVE, n. A temporary insanity│
│ curable by marriage… │
│ Read the whole entry ↓ │
│ Editorial preference: … │
├──────────────────────────────┤
│ DEFINITION · Johnson 1755 │
│ (first lines) │
│ Why this is here: … — Holden │
├──────────────────────────────┤
│ QUOTATION · Wiktionary │
│ "…" · under sense ● noun 1 │
│ Why this is here: … — Holden │
├──────────────────────────────┤
│ ▸ How this was curated │
├──────────────────────────────┤
│ Definitions │
2.6 Fixture versus published, so no screenshot confuses them
| Row | ?opening=fixture (dev and test only) |
Published (this issue) |
|---|---|---|
| Banner | "Development fixture · … · not published" | none |
| Configuration | "None. A development fixture resolves no curation configuration…" | "global-default, version 1 · lead rule bierce_first_v1" |
| Published by | absent | operator label, date, version, receipt id |
| Panel | "no persona panel ran" | "none: published by the operator" |
| Composition | "fixture key, version n: a development fixture, not a published composition" | "#id version n" |
2.7 The exact-word page, /words/14794/love
Shows nothing. It is a different scope (§3.1), and because overlapping lexical-page scopes cannot coexist it cannot have a composition of its own beside the On page's. Whether exact-word pages should display the On page's composition is a product and routing decision, not implied by the scope rule.
3. The seams: existing functions this builds on
3.1 How a page finds its composition
A composition's identity is (curation_configuration_id, scope_kind ∈ {:lexical_page, :lexeme}, language_tag, scope_signature); the signature is the SHA-256 of the sorted member lexeme ids (Compositions.signature/1, K2), never a spelling or a slug. The page already carries its lexeme set in page.headword.lexemes (WordLive, used at lines 282, 574 and 639 for the shelves). So:
{:ok, %{configuration: config}} = Curation.Configurations.resolve_default() # or unavailable → nil opening
ids = Enum.map(page.headword.lexemes, & &1.id)
comp = Curation.Compositions.active(config.id, :lexical_page, page.language_tag, Curation.Compositions.signature(ids))
comp && Curation.Published.current(comp.id) # {:ok, %{composition, version, receipt, lead, highlights, withheld}} | {:withheld, reasons} | :unpublishedAs built (#256): the language comes from the scope's lexemes, not page.language_tag, and the scope is the exact sorted lexeme set. /on/:slug reads every lexeme the slug reaches (the live love reaches five: 9051, 14794, 401975, 402387, 1492222); /words/:id/:slug exactly one. Different signatures, different compositions. No binding table and no new column: routing's page–composition binding (Stage 4, deferred to #156 Phase 2's reader) is not needed for this.
3.2 What Published.current/1 already does
Revalidates the published arrangement now through Curation.Eligibility and Curation.Standing: a retired composition, a moved or disabled configuration, a changed scope or a review that is no longer an acceptance withholds the whole version ({:withheld, reasons}); a problem with one item withholds that item with its reason; a Bierce entry that appeared after a fallback lead withholds the lead :priority_source_available. An exemplar carries its subject. Nothing fetched, nothing written. Reuse it; do not re-implement eligibility in the reader.
3.3 The reader contract
Curation.OpeningReader (one callback, opening(page, opts)), %Curation.Opening{} with Lead, Highlight, Reference, Meaning, Reason, Credit, Review, Configuration under lib/devils_dictionary/curation/opening/. Curation.ManualFixture is the only implementation today and shows how each item kind maps to a Reference and Credit (content revision; sense quotation by words_sha256 and locator; catalog work; exemplar claim).
3.4 Authority and the operator path
Curation.Authority.actor(scope, :author | :reviewer) from the account's flags; Compositions.provision/3, create_version/3, Reviews.decide/4, Publications.publish/3, withdraw/3; Configurations.seed!/0 (via mix dd.curation.seed) and activate/4. Attribute shapes are in each function's @doc; the item spec for create_version/3 is %{kind:, object_id:, <reference>, meaning: {:lexeme, id} | {:sense_revision, id}, note: %{text: …}}. A note naming its own author is refused (:note_attribution_not_an_input): attribution is the authenticated actor, by design.
4. Scope
- A published reader implementing
OpeningReader: resolve by §3.1, readPublished.current/1, map onto%Opening{origin: :published}:composition: %{id, version},configuration(%Opening.Configuration{}with slug, version, resolution reason and policy version fromresolve_default/1),leadwith itspolicyandregisterfromLeadPolicy,highlightsin position order with each item's note as itsReasonand the note'snote_author_label/note_author_kindas its signature,review(%Opening.Review{}: selected by the version'screated_by_actor_idlabel and kind, published by the receipt's actor and date, state:published),withheldas%{role, position, reason}. Curation.Opening.reader/1returns the published reader by default. The fixture reader only when:curated_opening_fixturesis set and?opening=fixtureis asked, exactly as now; production config never sets it.WordLivecallsOpening.for_page/2on every request (not only with the fixture parameter). An unavailable default, no composition,:unpublished, or an empty opening renders no section.DevilsDictionaryWeb.Openinggains the published branch (§5.2).- Reads perform no provider fetch, no inference, no composition write, no refresh admission.
Out of scope, by the owner's word: the operator screen (P2); pinning (P3); packet changes (P4); freshness tables, jobs or dates (P5); model calls, proposals, personas, automatic publication (P6, later); new public work or history pages; corpus-wide activation; schema changes of any kind. If a concrete blocker needs one, write it on the PR and stop.
5. Build
5.1 Files
| Add | |
|---|---|
lib/devils_dictionary/curation/published_reader.ex |
the OpeningReader for the published origin (§3.1–3.3) |
test/devils_dictionary/curation/published_reader_test.exs |
§6 reader tests |
test/devils_dictionary_web/live/word_live_opening_test.exs |
§6 page tests through the real routes |
| Change | What |
|---|---|
lib/devils_dictionary/curation/opening.ex |
reader/1 default; keep fixtures_enabled?/0 and the gate |
lib/devils_dictionary_web/live/word_live.ex |
call the reader unconditionally (near lines 171 and 248); pass page.language_tag |
lib/devils_dictionary_web/components/opening.ex |
§5.2 |
docs/curation/persistence-slice-1.md |
one paragraph under Deferred: "#156 Phase 2 / #255: the page reads Published.current/1 through Curation.PublishedReader" |
5.2 Component changes
The component was written for fixtures and hard-codes that in copy. Add the published branch, keep the fixture branch byte-for-byte:
- the configuration row (≈ line 595): slug and version and lead rule for
:published; the fixture sentence stays for:fixture; - a Published by row from
review(actor label, date, version, receipt id); absent for fixtures; - a Panel row: "none: published by the operator" for
:published; - the "Development fixture · … · not published" banner (≈ line 64) stays
:fixture-only; withheld_reason/1(≈ lines 749–755) covers every reason the record emits, with a plain fallback so an unmapped atom never raises on a public page::revision_superseded,:revision_deleted,:object_deleted,:meaning_deleted,:claim_deleted,:claim_not_current,:claim_not_accepted,:claim_not_visible,:meaning_mismatch,:claim_context_changed,:catalog_changed,:catalog_row_missing,:work_identity_mismatch,:words_changed,:priority_source_available,:priority_source_missing,:source_inactive, plus the five it has;- a withheld lead renders a short card in the lead's place (§2.3), never the withheld content.
5.3 The demonstration composition for love, verified on v2
| Role | Item | Registry |
|---|---|---|
| Lead | Bierce, LOVE, n. "A temporary insanity curable by marriage…" | source bierce, record LOVE/n → its current content_revision_id; passes LeadPolicy as :priority_source |
Highlight 1, content |
Johnson, LOVE, n. s. | source johnson, record LOVE/n. s./0 → current content_revision_id; meaning {:lexeme, 14794} |
Highlight 2, sense_quotation (optional) |
a Wiktionary example on a current sense revision of 14794 or 9051 (sense_revisions.examples) |
sense_revision_id, locator "quotation:N", words_sha256 of the words; meaning {:sense_revision, id} |
| Not available for this scope | verified quotes (wikiquote-pd-v1): none under a love concept; artworks: none pinned |
pin nothing in P1 |
Scope: scope_kind: :lexical_page, language_tag: "en", and the lexeme ids the live page actually resolves, read from WordLive's page build for /on/love on v2 at the time of Delivery B, not assumed. On 23 October the live page shows noun · verb · name, so the scope is at least three lexemes (9051, 14794 and a capitalised Love, 401975 or 402387), not the demonstration's two. The reader resolves by whatever the page reaches; the provisioning must match it exactly or the composition is never found.
6. Tests
Reader (published_reader_test.exs), on the test partition with a seeded and activated default:
- no active configuration →
nil; no composition for the scope →nil;:unpublished→nil. - a published composition →
origin: :published, lead withpolicy: :priority_source, highlights in stored order, each reason text and signature equal to the stored note and its author label,review.published_bythe receipt's actor,configuration.version1. - withdrawn →
nil. - a superseded source revision on highlight 2 → that item in
withheldwith:revision_superseded, the rest intact. - a version whose lead is Johnson while the Bierce entry is on the page → the lead in
withheldwith:priority_source_available, never replaced. - a draft version (no acceptance) and a rejected version →
nil. - the On scope and the exact-word scope of the same word resolve different compositions (provision both; publish one; the other page shows nothing).
- table-driven: every reason atom
EligibilityandPublishedcan emit renders a label through the component'swithheld_reason/1, and an unknown atom renders the fallback.
Page (word_live_opening_test.exs), through the real routes /on/love and /words/14794/love on the test partition:
- no composition → no
#openingelement; the Definitions section is present. - published →
#openingwith the lead card, the highlight cards in order, each "Why this is here" and signature, and the disclosure rows of §2.2; no fixture banner. - withdrawn → no
#openingon a fresh request. ?opening=fixturewith fixtures enabled (test config) → the fixture, with its banner; with:curated_opening_fixturesfalse → the published opening or nothing, never the fixture.?opening=published,?configuration=…,?composition=…or any other parameter changes nothing (no URL-selected configuration or composition).- the exact-word page of the same word shows nothing while the On page shows the composition.
Required checks: MIX_ENV=test MIX_TEST_PARTITION=_curation_p1 DD_NO_OBAN=1 mix precommit green; report the test count.
7. Delivery A, implementation ready for review
- Branch from
mainin a worktree under.claude/worktrees/on the external drive; symlinkdeps,dataand eachpriv/replay/*.jsonl.gzfrom the main checkout (orSources.ManifestTestfails). - Build §4–§5, tests §6, precommit green.
- Demonstrate on the test partition through the real route: seed, activate, provision the §5.3 composition, review, publish, load
/on/love, withdraw, load again. Keep the ids. - Screenshots: §2.1, §2.2 open, §2.3, §2.4 and §2.5 at 1280 × 900 and 375 wide, every
<details>closed; one fixture and one published shot for §2.6. Record the Definitions heading's offset at 1280 × 900. - Open the PR titled "Curation P1 (Curation P1: show one manually published opening on a pilot word page #255): one published opening on /on/love", with the test count, the ids, the screenshots and any limitation. Address CodeRabbit; get one independent review; address it.
- Tick the P1 line on Curation MVP implementation plan: seven parts with agent-ready briefs (P1 read compositions, P2 screen, P3 pin, P4 packet, P5 freshness, P6 proposals, P7 runtime) — under #253 #254 with the PR link; comment here that the PR is up.
- Stop. The owner merges.
8. Delivery B, owner-approved live proof
Issue creation and implementation authorization do not authorize live activation. After the PR is merged, present these steps in chat with the actual ids and wait for the owner's explicit yes; run nothing against v2 before it.
Mechanics: no migration, no restart, no launch-script edit. After the merge, git pull in the main checkout, then one local request curl -s -o /dev/null http://127.0.0.1:4007/on/love: the published host's loopback code reloader (#250's LocalDevelopment plug) recompiles _build/published on that request; watch ~/Library/Logs/dictionary-phx-4007.launchd.log for the compile. A tunnel request never compiles. Run the data steps from a separate shell with DD_NO_OBAN=1 DD_DATABASE_PORT=5434 mix run -e '…' or iex -S mix against v2, never by restarting the agent.
Never on v2: superseding a sense or content revision to show the withheld case. That test is Delivery A's, on the test partition only; live content is not altered to prove a display.
Final state: the composition stays published unless the owner says otherwise. The point of Delivery B is a public example on On love that stays up, not only a demonstration.
Steps, each with its before and after:
- Inspect:
select count(*) from curation_configurations / curation_configuration_versions / curator_profiles / editorial_compositions, andselect count(*) from oban_jobs. mix dd.curation.seed(idempotent; writes the draftglobal-default, version 1, five proposed profiles; activates nothing). Counts after.- Activate: as the reviewer account the owner names in chat (never assume one),
Configurations.activate(scope, configuration_id, version_id, reason: "P1 #255"). - Provision:
Compositions.provision(scope, configuration_id, %{scope_kind: :lexical_page, lexeme_ids: <the ids from step 0>, language_tag: "en", reason: "P1 #255 demonstration"}).
Step 0, read-only, before anything: build the/on/lovepage as the server does (or read the ids the published reader computes for it) and record the headword lexeme ids; those are the scope. Confirm the BierceLOVE/nand JohnsonLOVE/n. s./0content revisions and the chosen sense example are current on v2. - Version:
Compositions.create_version(scope, composition_id, %{lead: <Bierce spec>, highlights: [<Johnson spec>, <quotation spec>], reason: "P1 #255", expected_parent: nil})with the owner's own words in eachnote: %{text: …}. - Review:
Reviews.decide(scope, version_id, :accepted, reason: "P1 #255"). - Publish:
Publications.publish(scope, version_id, reason: "P1 #255", idempotency_key: "p1-255-love-1"). - Verify through the tunnel:
https://wordhoard.eu.ngrok.io/on/loveshows §2.1;/words/14794/loveshows nothing; the disclosure shows §2.2. Screenshot both widths. - Withdraw:
Publications.withdraw(scope, composition_id, reason: "P1 #255 proof"); reload through the tunnel: nothing. Screenshot. - Re-publish (default), so the example stays public; withdraw only if the owner says so. State the final state explicitly.
oban_jobscount after: unchanged. Rollback at any point is step 9; the active configuration can stay (with zero compositions it changes nothing).
Keep every row, version, receipt id and screenshot as evidence on this issue. An open page is not promptly updated on withdrawal in P1 (that is #253 §6a's reader-stability requirement, P5): say so rather than claim a reload proves it.
9. Environment and review constraints
Work from the external-drive checkout /Volumes/LLM Models/dictionary/src/dictionary; worktrees under its .claude/worktrees/; never a checkout or database on the internal disk. The dictionary's Postgres is port 5434, not the shared 5432. Tests only with MIX_ENV=test and a private partition. The server on port 4007 is the public site through ngrok: never restart it, never edit ~/Library/Application Support/dictionary/phx-4007.sh. gh pr merge is refused by the owner's permission classifier: stop at a reviewed PR. Build only this issue; report a concrete blocker instead of widening scope.
10. Acceptance
- Delivery A: reader, component branch and
WordLivewiring complete; tests 1–14 pass; precommit green with the count reported. - The scope seam is §3.1 and test 7 proves On and exact-word scopes are distinct.
- Every withheld reason renders a label (test 8).
- Screenshots §2.1–§2.6 attached; Definitions heading within 900 px at 1280 wide.
- Reviewed PR (CodeRabbit and one independent review addressed); P1 ticked on Curation MVP implementation plan: seven parts with agent-ready briefs (P1 read compositions, P2 screen, P3 pin, P4 packet, P5 freshness, P6 proposals, P7 runtime) — under #253 #254 with the link.
- Delivery B: explicit live approval recorded; seed → activate → publish → visible through the tunnel → withdraw → absent, with ids and screenshots;
oban_jobsunchanged; final live state stated. - Curation MVP implementation plan: seven parts with agent-ready briefs (P1 read compositions, P2 screen, P3 pin, P4 packet, P5 freshness, P6 proposals, P7 runtime) — under #253 #254 P1 stays incomplete until Delivery B is met.
11. Implementation prompt
Implement #255 exactly as written. Read it in full, then #254's ground rules and P1 section, #253 §§2–4, 8, 9.1–2 and 12, docs/curation/persistence-slice-1.md, and the files in §5.1 and §3. Reuse the seams in §3; do not re-implement eligibility, do not add a binding table, do not change the schema. Build §4–§5 with the tests in §6, demonstrate on the test partition through the real routes, take the screenshots in §2, run the required precommit, open the PR, address CodeRabbit and one independent review, tick P1 on #254, comment here, and stop. Then present Delivery B's steps with real ids for the owner's approval and run nothing against v2 until it is given. Do not build the operator screen, pinning, packet changes, freshness, model calls or anything in a later part. Report a concrete blocker instead of broadening scope.
Activity
holden commentedon Oct 23, 2026
Delivery A is up for review: #256, "Curation P1 (#255): one published opening on /on/love".
Curation.PublishedReaderis the default reader: §3.1's seam, thenPublished.current/1, mapped per §4._curation_p1: 2,836 tests, 1 failure, inRecoverySourceIdentityTest. This partition name makes its scratch database names 64 bytes, over Postgres's limit; it is untouched by the PR. On_cp1: 2,836 tests, 0 failures./on/loveand/words/14794/love. The ids, before and after counts, and screenshots for §2.1–§2.7 are in the PR.Nothing has been run against v2. Delivery B waits for the owner's yes.
holden commentedon Oct 23, 2026
Owner's decisions on #256's limitations, 23 October 2026
The owner accepted the audit and decided:
sm:text-4xl/12→text-3xl/10, shared with the fixture), measured at 882 px. Commit it on Curation P1 (#255): one published opening on /on/love #256, re-take the §2.1 and §2.5 screenshots, re-run precommit on a short private partition.Merging #256 is the owner's; Delivery B runs after it, on the owner's yes in chat with the reviewer account named.
Prompt for the P1 agent
The lead is one step smaller on desktop, so the Definitions heading s…
Merge pull request #256 from razrfly/claude/255-published-opening
holden commentedon Oct 23, 2026
Delivery B done, 23 October 2026: On love is live through the tunnel
Owner's yes in chat (height lever accepted, placeholders accepted, reviewer
issue84-browser@local.test, final state published). PR #256 merged as8b6e2c9;git pull; one local request to/on/loverecompiled the published build (Elixir.DevilsDictionary.Curation.PublishedReader.beamin_build/publishedat 22:30). No restart, no launch-script change, no migration.Step 0, the live scope (
Lexicon.lookup("love"), whichWordPage.build/2keeps whole): lexemes 9051 (love, noun), 14794 (love, verb), 401975 (Love, noun), 402387 (Love, name), 1492222 (LoVe). Five, not the demonstration's two. Scope signatureaf85949f…cd96e.Counts before → after:
curation_configurations0 → 1,curation_configuration_versions0 → 1,curator_profiles0 → 5,curation_configuration_activations0 → 1,editorial_compositions0 → 1, versions 0 → 1, reviews 0 → 1, publications 0 → 3,oban_jobs833 → 833 (curation enqueued nothing; the only row inserted in the window was discovery's scheduledCleanupWorker).Configurations.seed!/0global-default(draft), version 1bierce_first_v1, 5 proposed profilesConfigurations.activate/4, keyp1-255-activate-1, actor 5 (Account #2)Compositions.provision/3,:lexical_page, the five ids,enCompositions.create_version/3LOVE/n(content 1779138, revision 41…), highlight 1 JohnsonLOVE/n. s./0, highlight 2 Milton under sense 1991670 (revision 248575,quotation:3), meanings{:lexeme, 9051}and the sense revisionReviews.decide/4 :accepted, keyp1-255-review-1Publications.publish/3, keyp1-255-love-1GET https://wordhoard.eu.ngrok.io/on/love/words/9051/loveand/words/14794/loveshow none; no fixture banner; disclosure: Configuration, Selected by Account #2, Published by Account #2 · version 1 · receipt #1, Panel none, Withheld nothing, Composition #1 version 1, exact revisionsPublications.withdraw/3, keyp1-255-love-withdraw-1,expected_pointer: 1/on/lovethrough the tunnel: no openingPublications.publish/3, keyp1-255-love-2/on/lovethrough the tunnel: the openingFinal state: published (composition 1 → version 1, receipt 3). No revision on v2 was superseded. The three notes are the placeholders the owner accepted for now, signed "Account #2"; a new version from the P2 screen can replace them. Two API notes for P2's implementer:
activate/4requiresexpected:andwithdraw/3requiresexpected_pointer:explicitly (bothnil-able), which §8's sketch omitted.Closing: #255's acceptance is met. P1 ticked on #254.
holden commentedon Oct 23, 2026
Done: Delivery A merged (#256), Delivery B live on v2 and verified through the tunnel; evidence in the comment above. Next: P2, #257.