feat(contract): v4 social contract draft — indexOnly likes, single hashtag, author agreements

[PastaPastaPasta]

What

Phase 2b of PLAN_LIKE_OVERHAUL.md: the contract v4 shape, produced by a deterministic, reviewable transform (scripts/build-v4-contract.py) of the v3-topology contract:

• like → indexOnly (entries are the rows; no stored body): byPost / byHashtagPost / byAuthorPost with full ranked chains + preallocated, byAuthorTimePost [postAuthor, $createdAt, postId] (notifications + unlike-tuple recovery; not preallocatable — the like's own timestamp isn't derivable from the post), byLiker (membership / my-likes). One-like-per-(post, owner) now falls out of structural uniqueness.
• likeReply → indexOnly, lean (countable + notification + membership; no ranked).
• Single-hashtag model: post.hashtag (+ tagAndTime listing index), postHashtag doctype deleted — tagged posts become one write instead of two. '' = untagged is a stand-in until the upstream null-skip release, at which point hashtag flips optional and this contract re-registers before any cutover.
• author on post/reply (poster-attested = $ownerId), consensus-bound onto likes via refersTo propertyAgreement — the denormalized copies can no longer be poisoned (40127).
• Everything else (flat threads, quotes, permanence/tombstones, embed triple, ipfs mediaUrl, sensitive, token costs) carried unchanged from v3/4UW9im1y.

Live validation so far

• Registered on moutai as a draft: Aux325ifCRkYUteevirCv7ptHm3YB2g7PbMo8UjQwoz — consensus accepted the full PV14 indexOnly grammar first try; bots funded 1000 YAPP on its token.
• Shape-critical behaviors independently verified 12/12 (branch feat/like-overhaul-phase2a, folds in via feat(experiments): indexOnly Phase 1 battery + results on moutai devnet #322's lineage): 3-property notification-index recovery end-to-end (multi-device unlike rebuilds its delete tuple from one query), byAuthorPost does NOT trip the one-like-per-author trap, author-pinned ranked queries work (zero-count groups filtered client-side).
• byAuthorPost is included per DESIGN_CREATOR_LEADERBOARD.md — index sets freeze at registration, and this keeps the leaderboard path open for the upstream prefix-level-ranked-aggregation ask while serving the profile Top tab server-side today.

Landing on this branch before merge

• scripts/verify-v4.mjs + docs/V4_BATTERY_RESULTS.md — the full battery (v3's 31 topology cases rebased onto v4 + the new indexOnly/agreement/ranked/recovery/tombstone-interplay suite) is being authored and run against Aux325if… right now; results push here when green.

Not in this PR: no client changes, no .env.devnet flip (a v3 client pointed at v4 queries doctypes that don't exist — cutover is Phase 3), and final registration waits for null-skip.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ad15280e-1f98-4560-a4d8-2066ec067e04

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[thepastaclaw]

🕓 Ready for review — 4 ahead in queue (commit 7bd3875)
Queue position: 5/6
ETA: start ~14:47 UTC · complete ~15:04 UTC (median 17m across 30 recent reviews; 3 slots)
Queued 47m ago · Last checked: 2026-08-29 14:30 UTC

[PastaPastaPasta]

Internal review note for the record: an independent code-review pass verified the transform is faithful (byte-identical carry-over of all untouched doctypes/config/tokens, collision-free positions, clean postHashtag deletion, no aliasing, idempotent script) and flagged the "countable": "countable" string form on the four ranked-chain indexes as unprecedented in this repo.

Disposition: intentional, not a defect — it is the enum form used by the upstream consensus-pinned reference fixture for indexOnly likes (packages/rs-drive/tests/supporting_files/contract/yappr-likes/yappr-likes-contract.json on dashpay/platform v4.2-dev), and upstream documents the boolean as the equally-valid legacy form. The reviewer's underlying ask — an actual count/ranked query against a contract registered from this exact file — is satisfied by the verify-v4 battery running against Aux325if… (registered from this JSON verbatim); results land on this branch per the PR checklist.

Two doc-drift findings (plan text contradicting the shipped byAuthorPost inclusion, and a stray preallocated tag on byAuthorTimePost) are fixed in PLAN_LIKE_OVERHAUL.md.

---

🤖 Posted autonomously by Claude on behalf of pasta.

[cloudflare-workers-and-pages]

Deploying yappr-v2 with    Cloudflare Pages

Latest commit:	7bd3875
Status:	✅  Deploy successful!
Preview URL:	https://cd94e6f8.yappr-v2.pages.dev
Branch Preview URL:	https://feat-contract-v4.yappr-v2.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying yappr with    Cloudflare Pages

Latest commit:	7bd3875
Status:	✅  Deploy successful!
Preview URL:	https://f21a99b0.yappr.pages.dev
Branch Preview URL:	https://feat-contract-v4.yappr.pages.dev

View logs

[PastaPastaPasta]

Battery landed: verify-v4.mjs + docs/V4_BATTERY_RESULTS.md (commit 7bd3875). 68/68 strict checks green live against Aux325if…, full run repeated twice — zero contract defects. Every purchased surface validated: rebased topology cases, all four propertyAgreement directions incl. both ''-sentinel mismatches, structural uniqueness, the byAuthorPost trap-guard, batched terminal-IN membership with proved absence, all four ranked shapes with exact counts (this also empirically settles the countable enum-form question from the earlier review — count/ranked queries return correct values against this exact contract), tuple-recovery unlikes, self-authorizing deletes, likeReply mirror, and the documented likes-outlive-tombstones behavior.

Two evo-sdk 4.2.0-dev.5 issues surfaced for upstream filing (details in the results doc): the devnet protocol-version ratchet requires one proved non-v4 warm-up query after connect() before any PV14-grammar contract read, and quorum rotation (~20min) permanently poisons a long-lived trusted context. Both have working mitigations in the battery and are flagged into the Phase 3 client work.

The battery commit was independently code-reviewed within its authoring run (findings fixed and re-validated live). PR checklist is now complete.

---

🤖 Posted autonomously by Claude on behalf of pasta.