docs(plans): examine Hypothes.is integration with chrest capture pipeline#29
Open
friedenberg wants to merge 1 commit into
Open
docs(plans): examine Hypothes.is integration with chrest capture pipeline#29friedenberg wants to merge 1 commit into
friedenberg wants to merge 1 commit into
Conversation
…line Feasibility analysis only — no code changes. Walks through four architectural options for integrating the Hypothes.is annotation protocol (sidecar fetch, new chrest format, sibling RFC-0001 capturer, browser-extension overlay), the cross-cutting concerns (payload determinism, secrets, rate limits, target-URL canonicalization), and the existing extension points the integration would land on.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a feasibility examination of integrating the Hypothes.is web-annotation protocol with the existing nebulous → chrest → madder capture pipeline. Documentation only — no code changes.
The examination covers four architectural options:
api.hypothes.is, writes annotations throughmadderas an extra artifact alongside chrest captures. Smallest blast radius; bifurcates the pipeline.hypothesis-annotations: cleanest fit with RFC 0001 (spec/payload/envelope tri-fold), but couples HTTP-API-client work into a browser capturer and forces cross-repo + RFC churn.Recommendation: A for one-off, C if a family of sources is planned. B is architecturally tempting and likely to age badly.
Cross-cutting concerns (apply to any option): payload determinism vs. unstable Hypothes.is server-side timestamps (or markl-ID dedupe breaks), bearer-token secrets plumbing (must mirror
NEWSBLUR_TOKENnot policy TOML), rate limiting, target-URL canonicalization mismatches with Hypothes.is's URI normalization, and "empty annotation set is success" handling so the orchestrator's circuit breaker doesn't trip on the common case.Open questions enumerated for follow-up before any design phase begins.
Test plan
docs/plans/2026-04-30-hypothesis-chrest-integration-examination.mdand confirms the architectural options are accurate against the current pipeline (internal/alfa/orchestrator/,internal/alfa/capturer/,docs/rfcs/0001-web-capture-archive-protocol.md).https://claude.ai/code/session_0127otAtm656uw7dyuKnVqzD
Generated by Claude Code