Web5 — Tri-Anchor Protocol (TAP)

What TAP specifies

• Fragment semantics: #p;s;h → paragraph anchor, sentence ordinal, short-hash.
• Resolution: open the correct UI state (tabs/accordions), scroll, highlight.
• Verification: confirm the sentence’s short-hash; show a drift badge on mismatch.
• Fallbacks: nearest stable anchor; never mislead silently.
• Privacy & robots: no fingerprinting; honor robots and charter.json.

Anchors & multimodal (consolidated)

Exact-line semantics extend to PDFs, tables, code blocks, audio/video transcripts via stable segment IDs and hashes.

This page supersedes prior “multimodal anchors” drafts.

Interoperability notes

• Aligns with existing text-fragment thinking while adding verification.
• Stack-agnostic: can be generated by humans, build tools, or MM2.
• Locale-true mapping supported via line-ID correspondence tables.

Continue

Start at: Introduction · Web 3 · Web 4 · Web 5 Overview · TAP · Proof · MM2 · Web 6 (MM3) · Conclusion

TL;DNS — A new disturbance in the Force.