Demo (intent restated): tighten the sync SLA from 5s to 3s by rdryfoos · Pull Request #3 · rdryfoos/specassay

rdryfoos · 2026-08-10T17:28:54Z

A deliberate demonstration of an intent change — the third Thread Report specimen, alongside green #1 (debt paid) and red #2 (thread broken).

What it does

One line changes — the wording of an existing criterion:

AC-SYNC-01 — a change made offline appears on a second device within 5s 3s of reconnect.

No code changes. No test changes. The Gate stays green — a reword breaks no exact-set or silent-gap rule, and the existing proof test_AC_SYNC_01 still passes… because it asserts the old 5s.

What you should see

The Thread Report posts a new ⚠️ Intent Changed section:

AC-SYNC-01 — restated, with the was: 5s / now: 3s wording.
A re-confirm list — sync.py:51 · test_sync.py:18 — the carriers written against the old wording, linked to their current code.

That proof is the point: green, but wrong. The number moved under it and nothing forced a human to look — until now. This is pure illuminate (it never blocks); an enforcing re-confirm gate is a later slice.

Not intended to merge; it's the intent-restatement specimen.

Generated by Claude Code

Summary by CodeRabbit

Documentation
- Updated the offline synchronization requirement: changes made offline must appear on a second device within 3 seconds after reconnection, reduced from 5 seconds.

Reword only — no code or test change. The existing proof (test_AC_SYNC_01) still passes because it asserts the OLD 5s; the criterion now says 3s. The Gate stays green (a reword breaks no exact-set/gap rule), but the Thread Report's Intent Changed section flags AC-SYNC-01 restated and lists its carriers to re-confirm. This is the intent-restatement walkthrough specimen (the yellow one alongside green #1 and red #2). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TM5e4tKiqCUNANBCkTtH2r

github-actions · 2026-08-10T17:29:06Z

🧵 Thread Report

🟢 Golden Thread intact

What moved

No status changes in this PR.

Intent Changed

⚠️ 1 intent was restated — its wording moved under the code and tests written against the old text. Re-confirm each still satisfies the new statement.

AC-SYNC-01 — restated
- was: A change made offline appears on a second device within 5s of reconnect.
- now: A change made offline appears on a second device within 3s of reconnect.
- re-confirm:
  - sync.py:51
  - test_sync.py:37 — ⚠ still contains the old 5s

Thread Status

SYNC

ID	Status
`AC-SYNC-01`	🟢 proven	◀ changed
`AC-SYNC-02`	🟠 tracked-debt

_{+2 untouched backlog rows not shown.}

Off Thread

Every changed file carries a mark tying it to an intent. Nothing sits off the thread.

_{Thread Report illuminates; it does not refuse. "Off thread" is a visibility call, not a gate. Set offthread_ack: record|required in the SpecAssay config to add a human tick.}

coderabbitai · 2026-08-10T17:29:11Z

📝 Walkthrough

Walkthrough

Changes

Offline synchronization requirement

Layer / File(s)	Summary
Reconnect synchronization deadline `examples/example-app/PRD.md`	`AC-SYNC-01` changes the reconnect synchronization deadline from 5 seconds to 3 seconds.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: claude

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely states the main change: tightening the synchronization SLA from 5 seconds to 3 seconds.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch demo/restate-intent

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

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

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@examples/example-app/PRD.md`:
- Line 14: Update the AC-SYNC-01 proof in test_sync.py to assert reconnection
synchronization completes in under 3.0 seconds and revise its accompanying
comment to match. Then verify the implementation at sync.py’s synchronization
path satisfies the tightened 3-second SLA.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2add2591-af97-46cf-b390-65785501c42b

📥 Commits

Reviewing files that changed from the base of the PR and between 888a196 and 203c91b.

📒 Files selected for processing (1)

examples/example-app/PRD.md

coderabbitai · 2026-08-10T17:30:12Z

 - US-SYNC-01 — As a user, I keep my lists in sync across devices.
 - FR-SYNC-01 — Two-way sync reconciles list changes across devices.
- AC-SYNC-01 — A change made offline appears on a second device within 5s of reconnect.
+- AC-SYNC-01 — A change made offline appears on a second device within 3s of reconnect.


🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Update the AC-SYNC-01 proof to enforce 3 seconds.

examples/example-app/tests/test_sync.py:18-37 still asserts elapsed < 5.0. The gate can therefore pass an implementation that takes 4 seconds. Change the assertion and comment to 3 seconds, then re-confirm examples/example-app/src/sync.py:51 against the tightened SLA.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@examples/example-app/PRD.md` at line 14, Update the AC-SYNC-01 proof in test_sync.py to assert reconnection synchronization completes in under 3.0 seconds and revise its accompanying comment to match. Then verify the implementation at sync.py’s synchronization path satisfies the tightened 3-second SLA.

Followed the procedure Rik pointed at directly (~/Downloads/ SCREENSHOTINSTRUCTIONS.md) for the visual clause of the taught-by standard: PNG not JPEG, <slug>-YYYYMMDD.png naming, a caption stating the self-dating identity line explicitly (not just alt text), and a one-time maintenance note per doc that carries captures. Urgent item first: instruction #3 warned the Loupe PROVEN-over-No-proof capture (FR-GATE-40's drawer) needs to happen before FR-GATE-60 ships, since that symptom is scheduled to disappear once provenVia exists. Checked first -- FR-GATE-60 is still backlog, not too late -- then confirmed the capture I'd already taken this session (real browser, this repo's own live manifest) qualifies, and refiled it: provenvia-incoherence-20260819.png + provenvia-incoherence-no-proof-20260819.png, both with proper captions stating the manifest's real generatedAt timestamp. Also refiled the two existing README screenshots (homesflow proven state, example-app GAP state) to the same convention -- both were already real captures, just needed PNG + dated names + explicit timestamp captions instead of alt-text-only. Verified: this repo's own Gate (17/17 rows, gate.ok=true) and example-app's Gate (unchanged, still gate.ok=true).

claude added 2 commits August 10, 2026 17:28

Merge branch 'main' into demo/restate-intent

203c91b

coderabbitai Bot reviewed Aug 10, 2026

View reviewed changes

claude added 2 commits August 10, 2026 17:36

Merge branch 'main' into demo/restate-intent

ce1da19

Merge branch 'main' into demo/restate-intent

c5cef95

This was referenced Aug 10, 2026

example-app: tighten the offline-sync reconnect budget to 2s #4

Open

example-app: field-measured reconnect beats the budget — tighten AC-SYNC-01 to 2s, proof included #5

Open

Navigation Menu

Demo (intent restated): tighten the sync SLA from 5s to 3s - #3

Demo (intent restated): tighten the sync SLA from 5s to 3s#3
rdryfoos wants to merge 4 commits into
mainfrom
demo/restate-intent

rdryfoos commented Aug 10, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

github-actions Bot commented Aug 10, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Aug 10, 2026 •

edited

Loading

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Aug 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

rdryfoos commented Aug 10, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What it does

What you should see

Summary by CodeRabbit

Uh oh!

github-actions Bot commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧵 Thread Report

What moved

Intent Changed

Thread Status

Off Thread

Uh oh!

coderabbitai Bot commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Aug 10, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

rdryfoos commented Aug 10, 2026 •

edited by coderabbitai Bot

Loading

github-actions Bot commented Aug 10, 2026 •

edited

Loading

coderabbitai Bot commented Aug 10, 2026 •

edited

Loading