activeadmin_annotations 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 27efb5276816339c66980cb3e77752ab208f0a3f25ac290b051957f48542b489
+  data.tar.gz: 8367a3f0d88f6ad69e2c18721f1576a0ed8e2027ede89a20d64edfa252b238a6
+SHA512:
+  metadata.gz: aaf877c12d55510f4713004c8716fa87e0ab16c32cdd459e2ea3a5e070faeb7ecb4fc7a7969c1b40a499499ebba5c091c3944ca1d1f0ccbfe21ebc9d969531d9
+  data.tar.gz: 13991c461e4965f4e86800ea9585ae548ab36a69b64ea9878d86288aeb63a3710c5b0371b72b3bfc3451c59defc24719e941b49a8f84f90650af336820b58c1e

data/CHANGELOG.md

@@ -0,0 +1,14 @@
+# CHANGELOG
+
+## 0.1.0 (2026-07-10)
+
+- Add span-level annotations inside a bounded ActiveAdmin block.
+- Add review and span models with JSONL export from the reviews index.
+- Add Stimulus annotator and clipboard controllers with panel helper `activeadmin_annotations_panel`.
+- Add `ActiveAdmin::Annotations::ReviewPanel` for revision pinning, stale banners, and advance-to-latest review flows.
+- Add optional content revision pinning (`:auto`, `:active_version`, custom resolvers).
+- Add `ActiveAdmin::Annotations::Annotatable` concern for host models.
+- Add configurable review admin menu visibility via `review_menu_visible`.
+- Add optional annotation categories and copy instructions via initializer settings.
+- Add composite index on `annotation_spans` for panel load by review, field, and revision.
+- Add PostgreSQL GIN index on review `metadata_json` for follow-up filtering.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,31 @@
+# Code of Conduct
+
+## Our pledge
+
+We pledge to make participation in our community a harassment-free experience for everyone. We operate on principles of mutual respect, privacy, and authentic engagement. We value substantive contributions and clarity on intentions.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Authenticity: engaging with genuine curiosity and admitting uncertainty rather than feigning knowledge.
+- Responsible innovation: taking full responsibility for any content or code contributed, whether manually written or generated by automation tools.
+- Gentle correction: responding politely to errors. We view mistakes as opportunities for learning, provided they are addressed with humility.
+- Inclusive language: using language that welcomes diverse perspectives and respects the privacy and identity of all participants.
+
+Examples of unacceptable behavior include:
+
+- Harassment: public or private harassment, trolling, or insulting comments.
+- Weaponized complexity: using jargon or overwhelming volume (including automated spam) to silence others.
+- Publishing private information: sharing others' data or personal context without explicit permission.
+
+## Artificial intelligence and automation
+
+In accordance with our commitment to collective awareness:
+
+- Contributors are responsible for the accuracy and security of any AI-generated artifacts they submit.
+- "The AI wrote it" is not a valid excuse for introducing bugs, security vulnerabilities, or bias.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@kiskolabs.com. All complaints will be reviewed and investigated promptly and fairly.

data/CONTRIBUTING.md

@@ -0,0 +1,29 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to activeadmin_annotations. We value learning over perfection but require rigor and responsibility.
+
+## The golden rule of automation
+
+We welcome the use of AI and automation tools to reduce toil, but you must strictly adhere to the following:
+
+1. You are the author. You act as the responsible agent for any code you submit. You must review, debug, and understand every line.
+2. Manage cognitive load. Do not submit massive, unreviewed automated dumps. Respect the reviewers' time by annotating complex logic.
+3. Security. Never feed project secrets or private context into public AI models.
+
+## How to contribute
+
+### Reporting issues
+
+- Verify accuracy before posting. Avoid generalizations.
+- Use issue templates to provide clear goals, constraints, and reproduction steps.
+
+### Pull request process
+
+- Scope: keep PRs focused on a single goal.
+- Context: explain why the change is necessary.
+- Testing: run `make test` locally before opening a PR.
+
+### Review process
+
+- We encourage productive friction. Expect questions about your approach.
+- If a reviewer suggests a change, view it as mutual aid, not criticism.

data/GOVERNANCE.md

@@ -0,0 +1,29 @@
+# Project Governance
+
+## Overview
+
+This project balances individual autonomy with collective coordination. We aim for a workflow that supports rapid iteration while maintaining strict guardrails for safety and architectural integrity.
+
+## Roles
+
+### Contributors
+
+Anyone who submits code, documentation, or participates in discussions. Contributors are expected to exercise direct action—taking ownership of problems they identify—while adhering to our quality standards.
+
+### Maintainers (Human Oversight)
+
+Maintainers are responsible for:
+
+1. Strategic judgment: defining scope and architectural direction.
+2. Review: verifying that contributions (human or automated) meet security and logic standards.
+3. Consensus building: facilitating decisions when the community is divided.
+
+## Decision making process
+
+### Lazy consensus
+
+For most routine changes, we operate on lazy consensus. If a proposal is made and no objections are raised within two weeks, it is considered approved.
+
+### Strategic alignment
+
+Major architectural changes, high-risk automation integrations, or changes that affect business logic require explicit approval from the maintainers. We prioritize substance over performance—a change must solve a real problem, not just appear polished.

data/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 amkisko
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,321 @@
+# activeadmin_annotations
+
+[![Gem Version](https://badge.fury.io/rb/activeadmin_annotations.svg)](https://badge.fury.io/rb/activeadmin_annotations) [![Test Status](https://github.com/amkisko/activeadmin_annotations.rb/actions/workflows/test.yml/badge.svg)](https://github.com/amkisko/activeadmin_annotations.rb/actions/workflows/test.yml)
+
+Collect span-level text highlights and comments inside a bounded ActiveAdmin block.
+
+The gem stays domain-agnostic: the host app chooses what review context means, which optional categories to offer, where to render the panel, and whether annotations are pinned to content revisions.
+
+## Requirements
+
+- Ruby 3.2+
+- Rails 7.1+
+- ActiveAdmin 3.0+
+- PostgreSQL recommended for production (SQLite works for development; some metadata filters use Postgres JSON operators)
+
+## Host app setup
+
+Subject models and the reviewer model should use UUID primary keys. Migrations store `subject_id` and `reviewer_id` as UUIDs.
+
+Set the reviewer model in the initializer:
+
+```ruby
+ActiveAdmin::Annotations.reviewer_class_name = "User"
+```
+
+The reviewer must be available as `current_user` (or your ActiveAdmin authentication helper) when the panel renders.
+
+The Review admin menu item is visible when `review_menu_visible` returns true for the signed-in user. Default checks `user.administrator?`. Override in the initializer:
+
+```ruby
+ActiveAdmin::Annotations.review_menu_visible = ->(user) { user&.can_review_annotations? }
+```
+
+## Installation
+
+Add to your Gemfile:
+
+```ruby
+gem "activeadmin_annotations"
+```
+
+Then:
+
+```bash
+bundle install
+rails activeadmin_annotations:install:migrations
+rails db:migrate
+```
+
+Configure the reviewer model and optional categories:
+
+```ruby
+# config/initializers/activeadmin_annotations.rb
+ActiveAdmin::Annotations.reviewer_class_name = "User"
+ActiveAdmin::Annotations.review_menu_visible = ->(user) { user&.administrator? }
+ActiveAdmin::Annotations.category_label = "Category"
+ActiveAdmin::Annotations.categories = {
+  "needs_follow_up" => "Needs follow-up"
+}
+ActiveAdmin::Annotations.copy_instructions = <<~TEXT
+  These annotations capture span-level review notes for evaluation datasets.
+TEXT
+```
+
+`copy_instructions` can be a string or a callable `(annotation, review) -> string`.
+It is prepended to the text copied from the annotation show page.
+
+## Host model
+
+```ruby
+class Article < ApplicationRecord
+  include ActiveAdmin::Annotations::Annotatable
+end
+```
+
+## ActiveAdmin panel (basic, no content revisions)
+
+When the subject does not use content revisions, render the panel directly:
+
+```ruby
+text_node helpers.activeadmin_annotations_panel(
+  subject: resource,
+  field: :body,
+  context: {title: resource.title, author: resource.author_name},
+  context_panels: [
+    {title: "Metadata", content: JSON.pretty_generate(resource.metadata)}
+  ],
+  content: markdown(resource.body)
+)
+```
+
+The gem stores annotations against the live subject text. If the reviewed text changes, stale detection uses `context_digest` only. No version UI is shown.
+
+## Content revisions (optional)
+
+Annotations use character offsets. If reviewed text can change in place, pin annotations to a content revision.
+
+The gem does not depend on `active_version`. Revisions are optional and disabled unless:
+
+- `content_revision_strategy` is `:active_version` or `:auto` (default), and the subject model uses `has_revisions` from [active_version](https://github.com/amkisko/active_version.rb), or
+- you provide custom revision resolvers (below).
+
+### Using active_version (recommended when content changes)
+
+`active_version` is not a gem dependency. When present on a subject, the gem follows this convention:
+
+- `subject.class.has_revisions?` is true
+- `subject.current_version` returns the head revision number
+- `subject.at_version(number)` returns a read-only copy at that revision
+
+Pinned version `N` on the head `H` resolves content as:
+
+- `N == H` → live `subject`
+- `N < H` → `subject.at_version(N + 1)` (active_version stores the previous text in the next revision row)
+
+Setup in the host app:
+
+```bash
+rails g active_version:revisions Article
+rails db:migrate
+```
+
+```ruby
+class Article < ApplicationRecord
+  include ActiveAdmin::Annotations::Annotatable
+  has_revisions(only: %i[title body])
+end
+```
+
+Then either render the panel through `ActiveAdmin::Annotations::ReviewPanel` (handles pinning, stale state, and version filtering):
+
+```ruby
+text_node ActiveAdmin::Annotations::ReviewPanel.render(
+  subject: resource,
+  reviewer: current_user,
+  field: :body,
+  view_context: self,
+  context_builder: ->(content_subject) { {title: content_subject.title} },
+  content_builder: ->(content_subject) { markdown(content_subject.body) },
+  advance_review_url: advance_annotation_review_admin_article_path(resource)
+)
+```
+
+Wire the stale-banner action on the host subject resource:
+
+```ruby
+# app/admin/articles.rb
+ActiveAdmin.register Article do
+  member_action :advance_annotation_review, method: :post do
+    context = {title: resource.title, body: resource.body}
+    ActiveAdmin::Annotations::ReviewService.advance_to_latest!(
+      subject: resource,
+      reviewer: current_user,
+      context: context,
+      latest_content_revision_version: resource.current_version
+    )
+    redirect_to resource_path, notice: "Review moved to the latest content version."
+  end
+end
+```
+
+Pass the same path helper to `ReviewPanel.render` as `advance_review_url`. The panel shows the button only when the review is stale and a URL is present.
+
+Or pass revision options manually to `activeadmin_annotations_panel`.
+
+Enable active_version detection explicitly:
+
+```ruby
+ActiveAdmin::Annotations.content_revision_strategy = :active_version
+```
+
+### Custom revision backend (no active_version)
+
+Disable auto-detection and provide callables (use `:auto`, not `:none`):
+
+```ruby
+ActiveAdmin::Annotations.content_revision_strategy = :auto
+
+ActiveAdmin::Annotations.current_content_revision_version = lambda do |subject|
+  subject.published_version
+end
+
+ActiveAdmin::Annotations.content_subject_for_revision = lambda do |subject, version|
+  subject.versions.find_by!(number: version)
+end
+```
+
+With custom resolvers, revision mode is enabled even without `active_version`.
+
+### Revision configuration reference
+
+- `content_revision_strategy` — `:auto` (default), `:active_version`, or `:none` / `false`
+- `current_content_revision_version` — `(subject) -> Integer` override for head version
+- `content_subject_for_revision` — `(subject, version) -> Object` override for rendered content
+- `content_revision_label` — `false`, format string (`"Draft %{version}"`), or `(version) -> String`
+- `stale_content_review_message` — string (`%{pinned_version}`, `%{latest_version}`) or `(review, pinned_version:, latest_version:)`
+- `stale_context_message` — string or `(review)` when revisions are off but `context_digest` changed
+
+Disable all revision UI and logic:
+
+```ruby
+ActiveAdmin::Annotations.content_revision_strategy = :none
+```
+
+## Storage
+
+- `ActiveAdmin::Annotations::Review` — one row per subject + reviewer, with frozen `context_json`
+- `ActiveAdmin::Annotations::Annotation` — span highlights tied to a review and field name
+- `content_revision_version` — optional pin when revision mode is enabled (defaults to `0`)
+
+## Export
+
+ActiveAdmin registers review and span resources. Use the Export JSONL action on the reviews index for downstream tooling.
+
+## Theme customization
+
+The panel loads `activeadmin_annotations.css` and uses stable `aa-annotations-*` class names. Action buttons use ActiveAdmin's `action-item-button` so they inherit your admin chrome; colors, spacing, borders, and text highlights are overridden in the host app.
+
+### Override styles
+
+Add a host stylesheet that loads after the gem asset (for example in your ActiveAdmin layout or `app/assets/stylesheets/active_admin/`):
+
+```css
+/* app/assets/stylesheets/active_admin/custom_annotations.css */
+.aa-annotations-sidebar {
+  border-color: var(--border-color, #e5e7eb);
+}
+
+.aa-annotations-save-button {
+  background-color: var(--primary, #2563eb);
+  border-color: var(--primary, #2563eb);
+}
+
+::highlight(aa-annotations-saved) {
+  background-color: color-mix(in srgb, var(--primary, #2563eb) 30%, #fef08a);
+}
+
+::highlight(aa-annotations-pending) {
+  background-color: color-mix(in srgb, var(--primary, #2563eb) 40%, #fef08a);
+  text-decoration-color: var(--primary, #2563eb);
+}
+```
+
+Gem defaults include `.dark .aa-annotations-*` rules for ActiveAdmin 4 dark mode. Mirror host overrides under `.dark` when you change light-mode colors.
+
+Main layout hooks: `.aa-annotations-panel`, `.aa-annotations-layout`, `.aa-annotations-sidebar`, `.aa-annotations-annotatable`, `.aa-annotations-composer`, `.aa-annotations-stale-banner`.
+
+### Override partials
+
+Copy views from the gem into `app/views/active_admin/annotations/`:
+
+- `_panel.html.erb` — review UI and composer
+- `_read_only_content.html.erb` — content-only fallback when no reviewer is signed in
+- `_copy_details_action.html.erb` — copy action on the span show page
+
+Override `_panel.html.erb` when you need different markup or to pin a custom Stimulus controller on the annotator root.
+
+## Authorization
+
+The gem registers ActiveAdmin resources for reviews and spans. Member actions use your host authorization adapter.
+
+Span create, update, destroy, and copy actions verify that the signed-in reviewer owns the target review. Host policies should still gate who may access annotation resources at all (`create?`, `update?`, `destroy?`, `show?`).
+
+With [ActionPolicy](https://github.com/palkan/action_policy) (or ActiveAdmin's ActionPolicy adapter), allow the span Copy details action explicitly:
+
+```ruby
+# app/policies/active_admin/annotations/annotation_policy.rb
+class ActiveAdmin::Annotations::AnnotationPolicy < ApplicationPolicy
+  def copy_text?
+    show?
+  end
+end
+```
+
+Review resources use the usual CRUD predicates (`index?`, `show?`, `create?`, `update?`) from your app policy base class.
+
+Place policies under `app/policies/active_admin/annotations/` so Zeitwerk maps them to `ActiveAdmin::Annotations::*Policy`.
+
+## Dependencies
+
+Required:
+
+- Rails >= 7.1
+- ActiveAdmin >= 3.0
+
+Optional (host app):
+
+- `active_version` for revision snapshots — not bundled; follow active_version setup when content can regenerate
+
+## Development
+
+From the gem root:
+
+```bash
+bundle install
+bundle exec appraisal install
+bundle exec rubocop
+bundle exec polyrun parallel-rspec --workers 5 --merge-failures
+```
+
+Matrixed Rails versions use [Appraisal](https://github.com/thoughtbot/appraisal): `gemfiles/rails72.gemfile`, `rails8ruby34.gemfile`, and `rails8truffleruby.gemfile`. Run `bundle exec appraisal rspec` to execute RSpec in each gemfile context.
+
+Shared agent guidance is managed with [pray](https://github.com/kiskolabs/pray) via `Prayfile`.
+
+[Trunk](https://docs.trunk.io) config lives in `.trunk/`; CI can run `trunk` via `.github/workflows/_trunk_check.yml`. Releases: `make release` or `usr/bin/release.rb`.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md). Bug reports and pull requests are welcome at https://github.com/amkisko/activeadmin_annotations.rb/issues
+
+## License
+
+MIT — see [LICENSE.md](LICENSE.md).
+
+## Sponsors
+
+Sponsored by [Kisko Labs](https://www.kiskolabs.com).
+
+<a href="https://www.kiskolabs.com">
+  <img src="kisko.svg" width="200" alt="Sponsored by Kisko Labs" />
+</a>

data/SECURITY.md

@@ -0,0 +1,27 @@
+# SECURITY
+
+## Reporting a vulnerability
+
+Do NOT open a public GitHub issue for security vulnerabilities.
+
+Email security details to: security@kiskolabs.com
+
+Include: description, steps to reproduce, potential impact, and suggested fix (if available).
+
+### Response timeline
+
+- We will acknowledge receipt of your report
+- We will provide an initial assessment
+- We will keep you informed of our progress and resolution timeline
+
+### Disclosure policy
+
+- We will work with you to understand and resolve the issue
+- We will credit you for the discovery (unless you prefer to remain anonymous)
+- We will publish a security advisory after the vulnerability is patched
+- We will coordinate public disclosure with you
+
+## Automation security
+
+- Context isolation: it is strictly forbidden to include production credentials, API keys, or personally identifiable information in prompts sent to third-party LLMs or automation services.
+- Supply chain: all automated dependencies must be verified.

data/activeadmin_annotations.gemspec

@@ -0,0 +1,68 @@
+# frozen_string_literal: true
+
+require_relative "lib/activeadmin/annotations/version"
+
+Gem::Specification.new do |spec|
+  spec.name = "activeadmin_annotations"
+  spec.version = ActiveAdmin::Annotations::VERSION
+  spec.authors = ["Andrei Makarov"]
+  spec.email = ["contact@kiskolabs.com"]
+
+  spec.summary = "Span-level annotations for ActiveAdmin"
+  spec.description = "Collect text highlights and comments inside a bounded ActiveAdmin block, with optional review context, content revision pinning, and JSONL export."
+  spec.license = "MIT"
+  spec.platform = Gem::Platform::RUBY
+  spec.required_ruby_version = ">= 3.2.0"
+
+  repository_url = "https://github.com/amkisko/activeadmin_annotations.rb"
+
+  spec.homepage = repository_url
+  spec.metadata = {
+    "homepage_uri" => repository_url,
+    "source_code_uri" => "#{repository_url}/tree/main",
+    "changelog_uri" => "#{repository_url}/blob/main/CHANGELOG.md",
+    "bug_tracker_uri" => "#{repository_url}/issues",
+    "documentation_uri" => "#{repository_url}#readme",
+    "rubygems_mfa_required" => "true"
+  }
+
+  spec.files = Dir.chdir(__dir__) do
+    %w[
+      CHANGELOG.md
+      CODE_OF_CONDUCT.md
+      CONTRIBUTING.md
+      GOVERNANCE.md
+      LICENSE.md
+      README.md
+      SECURITY.md
+      activeadmin_annotations.gemspec
+    ].select { |path| File.file?(path) } +
+      Dir["{app,admin,config,db,lib,sig}/**/*"]
+  end
+
+  spec.require_paths = ["lib"]
+
+  spec.add_dependency "rails", ">= 7.1"
+  spec.add_dependency "activeadmin", ">= 3.0"
+
+  spec.add_development_dependency "appraisal", "~> 2"
+  spec.add_development_dependency "bundler-audit", "~> 0.9"
+  spec.add_development_dependency "bundler", ">= 2"
+  spec.add_development_dependency "polyrun", ">= 2.2.0"
+  spec.add_development_dependency "prosopite", "~> 2.0"
+  spec.add_development_dependency "rake", "~> 13"
+  spec.add_development_dependency "propshaft", ">= 1.0"
+  spec.add_development_dependency "factory_bot", "~> 6"
+  spec.add_development_dependency "rspec", "~> 3"
+  spec.add_development_dependency "rspec-rails", ">= 6"
+  spec.add_development_dependency "sqlite3", ">= 1"
+  spec.add_development_dependency "rubocop-rails", "~> 2.34"
+  spec.add_development_dependency "rubocop-rspec", "~> 3.8"
+  spec.add_development_dependency "rubocop-thread_safety", "~> 0.7"
+  spec.add_development_dependency "standard", "~> 1.52"
+  spec.add_development_dependency "standard-custom", "~> 1.0"
+  spec.add_development_dependency "standard-performance", "~> 1.8"
+  spec.add_development_dependency "standard-rails", "~> 1.5"
+  spec.add_development_dependency "standard-rspec", "~> 0.3"
+  spec.add_development_dependency "rbs", "~> 3"
+end

data/admin/annotation_reviews.rb

@@ -0,0 +1,102 @@
+# frozen_string_literal: true
+
+ActiveAdmin.register ActiveAdmin::Annotations::Review, as: "annotation_reviews" do
+  menu priority: 3,
+    label: "Review",
+    if: proc { ActiveAdmin::Annotations.review_menu_visible.call(current_user) },
+    menu_name: :auxiliary
+
+  controller do
+    def scoped_collection
+      super.includes(:annotations)
+    end
+  end
+
+  actions :index, :show, :create, :update
+
+  permit_params :review_status, :notes, :metadata_json
+
+  filter :subject_type, as: :select
+  filter :subject_id
+  filter :reviewer_id, label: "Reviewer"
+  filter :review_status, as: :select, collection: ActiveAdmin::Annotations::Review::REVIEW_STATUSES
+  filter :context_digest
+  filter :created_at
+
+  scope :all, default: true
+  scope :pending
+  scope :reviewed
+  scope :escalated
+  scope :needs_follow_up
+
+  index do
+    selectable_column
+    id_column
+    column :subject_type
+    column :subject_id
+    column :reviewer
+    column :review_status
+    column("Annotations") { |review| review.annotations.size }
+    column :context_digest
+    column :created_at
+    actions
+  end
+
+  show do
+    attributes_table_for(resource) do
+      row :id
+      row :subject do |review|
+        label = "#{review.subject_type} ##{review.subject_id}"
+        subject = review.subject
+        if subject.present?
+          auto_link(subject, label)
+        else
+          label
+        end
+      end
+      row :reviewer
+      row :review_status
+      row :notes
+      row :context_digest
+      if ActiveAdmin::Annotations::ContentRevision.enabled_for?(resource.subject)
+        row :content_revision_version
+      end
+      row("Context stale?") { |review| review.context_stale? ? "yes" : "no" }
+      row :created_at
+      row :updated_at
+    end
+
+    panel "Context" do
+      pre JSON.pretty_generate(resource.context_json)
+    end
+
+    panel "Annotations" do
+      if resource.annotations.any?
+        table_for(resource.annotations.order(:created_at)) do
+          column :field_name
+          column :selected_text
+          column :comment
+          column :category
+          if ActiveAdmin::Annotations::ContentRevision.enabled_for?(resource.subject)
+            column :content_revision_version
+          end
+          column :start_offset
+          column :end_offset
+        end
+      else
+        para "No annotations yet."
+      end
+    end
+  end
+
+  collection_action :export_jsonl, method: :get do
+    exporter = ActiveAdmin::Annotations::Exporter.new(reviews: collection)
+    send_data exporter.to_jsonl,
+      filename: "annotation-reviews-#{Time.current.strftime("%Y%m%d%H%M%S")}.jsonl",
+      type: "application/jsonl"
+  end
+
+  action_item :export_jsonl, only: :index do
+    link_to "Export JSONL", export_jsonl_admin_annotation_reviews_path(request.query_parameters), class: "action-item-button"
+  end
+end