Source-first social annotation · easy flat-file deploy
Don't repost the internet.
Annotate it.
Select the exact claim, add your own commentary, keep the original source one click away, then let people like, love, laugh, comment, save, share, or challenge the annotation.
100 words
max text
90 seconds
media concept
Original source
attached
File a claim
visible
Design-story artifact supplied for the MVP: people + AI + provenance + a road forward.
Trust receipt:
what was selected · where it came from · who commented · why it matters · view original · file a claim.
This reading desk is the core loop.
Highlight evidence, then explain why it matters.
The source title, URL, marker color, commentary, and claim status travel together as a lightweight Source Passport. Nothing here pretends to be a production backend.
Podcast
Open models, cost, and the argument underneath the argument
Open-weight models create price and deployment alternatives. If policy removes those alternatives, some firms would face higher AI costs and less freedom to choose how they deploy models.
The economic transmission path is the interesting part: input cost → margin pressure → investor repricing.
The leap from “repricing” to “the whole market crashes” deserves a separate annotation.
That is exactly why source-linked commentary is useful: disagreement can point to the same evidence instead of becoming a detached quote-card.
The bigger issue is identity, provenance, and accountability. If autonomous systems can act through accounts and tools, the system needs a way to answer who or what made the request and under whose authority.
Everyone can argue about the moat; Annotated keeps the fence — the source — visible.
Human commentary needs source provenance. Agent actions need authority provenance.
The interfaces are different, but the accountability instinct is the same.
The GTR prototype uses the passport metaphor to make identity, authority, provenance, and revocation visible to humans.
The bridge to Annotated is not “everything needs blockchain.” The bridge is that consequential claims and consequential actions both need inspectable provenance.
For this bounty MVP, the Source Passport is intentionally lightweight: source URL, selection, commentary, color, time, and claim status. No claim of cryptographic verification is made.
Every saved highlight becomes a source-linked annotation card. This is local MVP behavior: no accounts, no server, no public posting.
Showing all published annotations
Timestamps humans can read
Point to a moment in the creator's original player. Use
01:06
, not subtitle milliseconds. Describe the moment in your own words.
Timestamp pointers
0
Artifacts
Use images as transformed supporting artifacts: caption them, color-tag them, and keep source/context visible. The four supplied visuals are now separate, cacheable files in the artifacts folder.
Mission / collaboration visual
Use as an editorial artifact for the design story, not as proof of an external claim.
“Who's the BOT?” channel artwork
Creator-side demo artifact. Keep a no-endorsement note wherever third-party likenesses or brands appear.
Optional provenance bridge
Create Robot Passport
Owner-provided iA.xyz/GTR screenshot. It demonstrates identity, guardian, hash, and revocation language without making GTR the main bounty story.
Full product context
GTR training world + passport action
Supporting artifact: consequential agent actions need inspectable identity and authority, just as public commentary needs inspectable source provenance.
Drop images here, or click to choose
PNG, JPG, WEBP · local browser only · 700 KB per image for persistence
Claim log
A rights-holder or source participant needs a visible door. In this MVP, claims stay in the local browser and are exported with the annotation state.
Chrome side-panel extension
The security-hardened Manifest V3 package is a separate static ZIP in this deployment. It captures the active tab only after a user action, requires commentary, stores locally, and keeps the source URL attached.
No broad host permissions. No remote code. The content script runs only after the user invokes capture on the active tab.
House rules
The product rules are part of the interface.
Keep the source attached.
Every annotation stores the source title and canonical/current URL alongside the selection and commentary.
Commentary is mandatory.
Highlighting alone is not publishing. The MVP requires an original note before the annotation is saved to the feed.
Keep text selections short.
This build enforces a 100-word maximum for captured article/page text.
Point at media; don't re-host it.
Timestamp pointers open the original YouTube source. The product's 90-second concept is not represented as a copyright safe harbor.
Give people a challenge path.
Every feed annotation has “File a claim,” and every claim becomes visible in the local claim log.
Prototype honestly.
Local storage, share-by-URL, demo reactions, claims, and Source Passports are not a production identity, moderation, or legal adjudication service.
Flat-file tools
Everything here works on an ordinary static host. No framework, database, analytics, remote code, or secret keys.
Deployment shape:
index.html + styles.css + app.js + enhancements.js + service worker + manifest + four image artifacts + the Chrome extension ZIP. The standalone one-file fallback is packaged separately.
Quick source capture
static form
0 / 100 words
Source material
0 / 25 words
Transformative take
This creates a local annotation record. The Chrome Side Panel remains the primary current-tab capture path.
Backup, export, and print
portable
CSV is spreadsheet-friendly. JSON preserves the complete local prototype state. Share links place the state in the URL hash; nothing is uploaded.
Deployment health
not run
Run after upload. In this one-file build it verifies index.html itself from the deployed origin — nothing else is required.
