automatic 26.08 → 26.09

data/automatic.gemspec

@@ -1,6 +1,6 @@
 # -*- coding: utf-8 -*-
 # Name::        automatic.gemspec
-# Author:       id774 (More info: http://id774.net)
+# Author:       id774 (More info: https://id774.net)
 # Source Code:: https://github.com/id774/automaticruby
 # License::     The GPL version 3, or LGPL version 3 (Dual License).
 # Contact::     idnanashi@gmail.com
@@ -87,8 +87,9 @@ Gem::Specification.new do |spec|
   spec.extra_rdoc_files   = ['README.md', 'doc/LICENSE.md']
 
   # Runtime dependencies: what the framework in lib/ requires, and nothing
-  # else. Requiring `automatic`, loading a Recipe, loading a plugin, running a
-  # pipeline and the CLI's own work are what these four are for.
+  # else. Requiring `automatic`, loading a Recipe, loading a plugin,
+  # running a pipeline and the CLI's own work are what these dependencies are
+  # for.
   #
   # A gem needed by a plugin is NOT declared here, however useful that plugin
   # is. It is required inside the plugin's own file and installed by the

data/bin/automatic

@@ -1,7 +1,7 @@
 #!/usr/bin/env ruby
 # -*- coding: utf-8 -*-
 # Name::        automatic
-# Author:       id774 (More info: http://id774.net)
+# Author:       id774 (More info: https://id774.net)
 # Source Code:: https://github.com/id774/automaticruby
 # License::     The GPL version 3, or LGPL version 3 (Dual License).
 # Contact::     idnanashi@gmail.com

data/doc/AI_TUTORIAL.md

@@ -41,17 +41,21 @@ FilterSakuraAI       ask one question about that text
 PublishMarkdown      write the answer to a document
 ```
 
-Seven plugins, each doing one thing, each handing its result to the next. The
+Each plugin does one thing and hands its result to the next. The
 Recipe that expresses it is in section 4, and nothing in it is a special case:
 every entry is a plugin the framework loads by name, and the order of the list
 is the order of the work.
 
 The store plugin's position is not an aesthetic choice. `FilterJoin` produces
 one item with **no link** — it is several articles at once, so there is no page
-it points at — and the store plugins are keyed on the link and drop an item
-without one. `StorePermalink`, `StoreFullText` and `StoreDigest` therefore
-belong **before** `FilterJoin`, where there is still one item per article to
-record. Put one after it and the Recipe stores nothing and publishes nothing.
+it points at. `StorePermalink` and `StoreFullText` use the shared link-based
+store path and drop an item without a link, so both belong **before**
+`FilterJoin`. `StoreDigest` is different: it identifies content from the
+configured fields and can store an item whose link is nil. In this tutorial it
+still belongs before `FilterJoin`, because the job is to record each source
+article before they are joined and before later work is repeated. Putting
+`StoreDigest` after `FilterJoin` changes its meaning to de-duplicating the whole
+joined digest rather than the individual articles.
 
 ## 2. Build it without AI first
 
@@ -133,7 +137,7 @@ gem install activerecord sqlite3
 gem install sanitize
 ```
 
-In a checkout the same three groups are selected together:
+In a checkout, select the groups required by those plugins together:
 
 ```sh
 bundle config set --local with "html store sanitize"
@@ -153,22 +157,28 @@ link, its date and whatever text the pipeline could get. No AI service has been
 contacted, no credential exists yet, and the Recipe is complete in itself: a
 person who only ever wanted this can stop here and put it in `cron`.
 
-**Expect `FilterFullFeed` to find nothing for these three sites, and read the
-log to see it.** The shipped `assets/siteinfo/items_all.json` is a snapshot of
-the LDRFullFeed database whose newest entries are from 2013, and none of its URL
-patterns matches these sites:
+**Read the `FilterFullFeed` log rather than assuming bundled siteinfo
+coverage.** The shipped siteinfo file is a snapshot. If a record matches an
+article URL, `FilterFullFeed` fetches the page and applies that record's
+XPath. If no record matches, the existing item is preserved and the log says:
 
 ```text
-Fulltext SITEINFO not found: https://go.dev/blog/pkgsite-api
+Fulltext SITEINFO not found: https://example.com/article
 ```
 
-Where no record matches, the plugin leaves the item exactly as it arrived, and
-the run continues. That is the behaviour to rely on and also the reason the
-document above holds a title, a link and a date per article and no body: an
-index page read without a `description_selector` carries no description for
-`FilterFullFeed` to have improved on.
+A Recipe that relies on full article bodies should supply siteinfo for the
+sites it relies on under `~/.automatic/assets/siteinfo/`, rather than treating
+the bundled snapshot as a guarantee of coverage.
 
-Getting text into these items is a choice between two places, and both are
+Where no record matches, the plugin leaves the item exactly as it arrived and
+the run continues. If the index page also provides no description, that item
+therefore has metadata but no article body. If a bundled or user-supplied
+siteinfo record does match, `FilterFullFeed` may replace the description with
+the selected article body. The tutorial relies on that conditional behavior,
+not on either outcome being guaranteed for a particular site.
+
+Text can enter these items from the index page or from the article page,
+and both are
 configuration rather than code:
 
 - **From the index page.** Where the listing prints a summary, an
@@ -241,7 +251,7 @@ Now the AI filter goes between `FilterJoin` and `PublishMarkdown`:
   - module: FilterSakuraAI
     config:
       token: YOUR_SAKURA_AI_TOKEN
-      model: gpt-oss-120b
+      model: <Sakura AI Engine model>
       prompt: |
         以下の記事群について、個別記事の要約を羅列するのではなく、
         全体を一つのダイジェストとして日本語で要約してください。
@@ -291,7 +301,7 @@ plugins:
   - module: FilterSakuraAI
     config:
       token: YOUR_SAKURA_AI_TOKEN
-      model: gpt-oss-120b
+      model: <Sakura AI Engine model>
       prompt: |
         以下の記事群について、個別記事の要約を羅列するのではなく、
         全体を一つのダイジェストとして日本語で要約してください。
@@ -341,7 +351,7 @@ Move the AI filter to before `FilterJoin` and change nothing else:
   - module: FilterSakuraAI
     config:
       token: YOUR_SAKURA_AI_TOKEN
-      model: gpt-oss-120b
+      model: <Sakura AI Engine model>
       prompt: |
         以下の記事を日本語で三行に要約してください。
       retry: 2
@@ -374,16 +384,16 @@ and that no plugin had to be changed or configured to express it.
 
 ## 6. Change the service by changing one line
 
-The four AI filters — `FilterOpenAI`, `FilterClaude`, `FilterGemini` and
-`FilterSakuraAI` — are one per service rather than one plugin with a `provider`
-setting. Each replaces an item's description with what its service answers, so
+Automatic Ruby uses separate service-specific AI filters rather than one
+plugin with a `provider` setting. Their current catalogue and settings are
+maintained in [`PLUGINS.md`](PLUGINS.md) section 6.3. Each replaces an item's description with what its service answers, so
 in a Recipe they are interchangeable at the same position:
 
 ```yaml
   - module: FilterOpenAI
     config:
       token: YOUR_OPENAI_API_KEY
-      model: gpt-5.6
+      model: <OpenAI model>
       prompt: |
         以下の記事群を一つのダイジェストとして日本語で要約してください。
       retry: 2
@@ -394,7 +404,7 @@ in a Recipe they are interchangeable at the same position:
   - module: FilterClaude
     config:
       token: YOUR_ANTHROPIC_API_KEY
-      model: claude-opus-5
+      model: <Anthropic model>
       prompt: |
         以下の記事群を一つのダイジェストとして日本語で要約してください。
       max_tokens: 2048
@@ -406,27 +416,39 @@ in a Recipe they are interchangeable at the same position:
   - module: FilterGemini
     config:
       token: YOUR_GEMINI_API_KEY
-      model: gemini-3.5-flash
+      model: <Gemini model>
+      prompt: |
+        以下の記事群を一つのダイジェストとして日本語で要約してください。
+      retry: 2
+      interval: 2
+```
+
+```yaml
+  - module: FilterKimi
+    config:
+      token: YOUR_KIMI_API_KEY
+      model: kimi-k3
       prompt: |
         以下の記事群を一つのダイジェストとして日本語で要約してください。
       retry: 2
       interval: 2
 ```
 
-Nothing before or after the swapped entry changes. `token`, `model` and `prompt`
-are required by all four; `max_tokens` exists only for Claude, because that API
-requires it. Model names move with the services, so take them from the provider
+Nothing before or after the swapped entry changes. `token`, `model` and
+`prompt` are shared required settings of the AI filters; `max_tokens` exists
+only for Claude because that API requires it. Model names move with the services, so take them from the provider
 you are using rather than from this document, and see
 [`PLUGINS.md`](PLUGINS.md) section 6.3 for each plugin's endpoint,
 authentication and answer handling.
 
-That a Recipe names the service on its face is the reason for four plugins. A
+A Recipe naming the service on its face is the reason for keeping
+service-specific plugins. A
 line reading `FilterClaude` says where the text is going, which is a question
 worth being able to answer by reading the Recipe.
 
 ## 7. Change the prompt, and the Recipe does another job
 
-None of the four filters is a summarizer. The prompt is the instruction and the
+None of the AI filters is a summarizer. The prompt is the instruction and the
 item's description is the text it applies to, so summarizing, translating,
 extracting and classifying are the same plugin with different words in one
 setting. Keeping the Recipe of section 4 and replacing only the `prompt`:
@@ -457,15 +479,17 @@ still worth remembering what the input is: pages fetched from the open web. A
 prompt that states what to do when the text does not contain what was asked for
 is more robust than one that assumes it does.
 
-**Long input has a limit that belongs to the model, not to the framework.** A
-joined text of forty full articles can exceed what a model accepts, and the
-service answers with an error that ends the run. Fewer sites, a smaller
-`fetch_items`, a stricter `include`, or the per-article arrangement of section 5
-are the ways to stay under it with the plugins that ship today. Splitting one
-long text into pieces, transforming each and asking a final question about the
-results is the natural next arrangement conceptually, and it is **not**
-something this repository provides: there is no chunking plugin, and a Recipe
-cannot express it today.
+**Long input has a limit that belongs to the model, not to the framework.**
+A joined text can exceed what a model accepts, and the service then returns an
+error that ends the run. `FilterLimit` can cap how many source items proceed,
+and `FilterBatch` can group source items into fixed-size item batches before
+an AI filter so that one request need not contain the whole pipeline. Their
+exact behavior is specified in [`PLUGINS.md`](PLUGINS.md) section 6.3.
+
+`FilterBatch` does not split one already-joined text by character or token
+length, and Automatic Ruby does not perform recursive summarization or a
+final synthesis automatically. A Recipe that needs those operations still
+needs a different pipeline design or a purpose-built component.
 
 ## 8. Why it is built this way
 

data/doc/BASIC_DESIGN.md

@@ -17,6 +17,12 @@ repository.
 
 ## 2. Design policy
 
+Automatic Ruby is a general-purpose composition framework, not host
+infrastructure and not a purpose-built application. The design therefore
+protects the small set of contracts that make composition possible without
+treating every framework implementation detail or every shipped plugin as
+equally permanent.
+
 - **The framework is the small part.** It loads a Recipe, finds classes by name,
   and calls them in order. It has no domain knowledge, and gaining some would be
   a design error rather than a feature.
@@ -32,6 +38,25 @@ repository.
 - **The library never exits and never prints.** Exit status is decided by the
   entry point; user-facing text is written by the entry point or logged.
 
+Maintenance strength follows the architectural layer:
+
+- **Core contracts are strongly protected.** The Recipe format, plugin
+  contract, single pipeline shape, lookup and override semantics, execution
+  order and established CLI behaviour are depended on outside this repository.
+- **Framework internals may improve inside those contracts.** The loader, CLI,
+  helpers and internal structure are not frozen merely because they are old,
+  provided the invariants and public contracts remain intact.
+- **Plugins are intentionally replaceable.** They may be added, repaired,
+  replaced or removed as their external systems change. A plugin whose service
+  or interface no longer exists is not preserved by simulation merely to retain
+  catalogue size.
+
+Composability is an architectural invariant, not an optimization preference.
+It is the architectural property that defines the framework: a small core,
+independent plugins, one pipeline representation and Recipe-level composition.
+A change that replaces those properties changes the identity of the system and
+is judged as an architecture change.
+
 ## 3. Composition
 
 A typical run is a short, linear flow. Markdown is one publisher at the edge,
@@ -280,6 +305,12 @@ The categories are a convention with one mechanical consequence — the director
 name is part of the lookup key (section 4.6) — and no other. Nothing enforces
 that a `Filter` does not reach the network.
 
+Replaceability is part of this boundary. A plugin is not given the same
+permanence as the Recipe format or the plugin contract itself. The framework
+preserves the rules that let plugins compose; it does not preserve a plugin
+whose external purpose has disappeared, and it does not move a plugin's domain
+behaviour into the core merely to make that behaviour permanent.
+
 **`Publish` is the boundary at which the pipeline meets a representation that is
 not the pipeline's.** A publishing plugin reads the value described in section
 4.8, writes it out in whatever form its destination wants — a line on a

data/doc/DEPLOYMENT.md

@@ -28,15 +28,16 @@ nothing to stop.
 
 - A Unix-like system. GNU/Linux and macOS are what this is used on; Windows is
   not supported.
-- **Ruby 3.3 through 4.0.** Check with `ruby -v`. CI validates 3.3, 3.4 and 4.0;
-  a version between them is supported and is simply not checked on every commit,
-  and a Ruby newer than 4.0 is permitted rather than refused. See
-  [`REQUIREMENTS.md`](REQUIREMENTS.md) section 20.
+- **Ruby 3.3 through 4.0.** Check with `ruby -v`. The continuously validated
+  versions are the matrix in [`.github/workflows/ci.yml`](../.github/workflows/ci.yml);
+  a supported version absent from that matrix is simply not checked on every
+  commit, and a Ruby newer than the matrix is permitted rather than refused.
+  See [`REQUIREMENTS.md`](REQUIREMENTS.md) section 20.
 - Optional gems for particular plugins, listed in the table under
   "Optional plugin dependencies" below. None is needed to install Automatic
   Ruby, or to run a Recipe that does not use the plugin; a Recipe that does
-  name one installs it as a step of its own, which is what the Quick Start's
-  step 4 is.
+  name one installs it as a step of its own, which is what the "Install what
+  the Recipe needs" section of [`QUICKSTART.md`](QUICKSTART.md) demonstrates.
 - A build environment may be needed for one of those optional gems — `nokogiri`
   and `sqlite3` build a native extension where no binary package matches your
   platform. The framework's own dependencies are pure Ruby, so the normal
@@ -52,9 +53,9 @@ gem install automatic
 automatic --version
 ```
 
-That installs the framework, the `automatic` command and four pure-Ruby
-runtime dependencies: `activesupport`, `hashie`, `rexml` and `rss`. That is the
-whole of it. No HTML parser, no database, no service client — a gem needed by
+That installs the framework, the `automatic` command and the runtime
+dependencies declared in `automatic.gemspec`. That gemspec is the source of
+truth for the framework's runtime dependency set. No HTML parser, no database, no service client — a gem needed by
 one plugin is installed by the operator who uses that plugin, so installing
 Automatic Ruby does not install what your Recipes do not use.
 
@@ -71,7 +72,7 @@ which, and is the list to check before adding anything.
 ### From a checkout
 
 For working on the framework, or for running a version that is not released.
-There are three ways to set one up, and the first is the one to start with.
+The supported checkout setups are shown below; start with the minimal setup.
 
 **Minimal — the framework and its test suite.** What you want for running the
 checkout, and for developing the framework itself:
@@ -99,8 +100,10 @@ bundle install
 bundle exec rake
 ```
 
-That adds `activerecord`, `sqlite3`, `nokogiri`, `sanitize` and `feedbag`,
-and their specs then run as part of the ordinary suite. The setting
+That installs the gems declared in the `plugins` group of `Gemfile`, and
+their specs then run as part of the ordinary suite. The
+[Optional plugin dependencies](#optional-plugin-dependencies) table maps
+those dependencies to the plugins and tools that use them. The setting
 is written to the checkout's own `.bundle/config`, which is not committed;
 `bundle config unset --local with` returns the checkout to the minimum, and
 `bundle install` afterwards.
@@ -115,7 +118,7 @@ bundle install
 ```
 
 Several at once are space-separated: `bundle config set --local with "store
-html"`, and a Recipe using plugins from two groups needs exactly that. The group
+html"`, and a Recipe using plugins from multiple groups needs exactly that. The group
 names are in the table below, and "Working out what a Recipe needs, in a
 checkout" takes one Recipe through choosing them.
 
@@ -162,8 +165,8 @@ full path runs without it.
 automatic -c ~/.automatic/config/example/feed2console.yml
 ```
 
-That fetches one feed and prints its items. Two things can go wrong and both are
-worth telling apart:
+That fetches one feed and prints its items. Distinguish an unreachable feed
+from an optional-dependency failure:
 
 - A message about the feed being unreachable means the network or that
   particular feed, not the installation.
@@ -230,12 +233,12 @@ plugins:
       interval: 3
 ```
 
-That Recipe needs three optional gems, because of the plugins it names rather
-than because of the framework: `nokogiri` for `FilterImageSource`, and
-`activerecord` and `sqlite3` for `StorePermalink`. See "Optional plugin
-dependencies" below.
+That Recipe needs `nokogiri` for `FilterImageSource`, and `activerecord` plus
+`sqlite3` for `StorePermalink`, because of the plugins it names rather than
+because of the framework. The canonical mapping is the
+[Optional plugin dependencies](#optional-plugin-dependencies) table.
 
-Three things in that Recipe are the operational advice of this document:
+The operational advice illustrated by that Recipe is:
 
 - **`StorePermalink` before the plugin with the effect.** It records what has
   been seen and passes on only what has not, which is what makes the Recipe safe
@@ -318,8 +321,7 @@ mkdir -p ~/notes && chmod 700 ~/notes
 
 **Keeping the document clean.** With no `file`, the document goes to standard
 output — and so does the log ([`REQUIREMENTS.md`](REQUIREMENTS.md) section 14),
-so a redirect that collects one collects the other. Two ways out, and the Recipe
-chooses:
+so a redirect that collects one collects the other. Either disable log output in the Recipe or give `PublishMarkdown` a `file`:
 
 ```yaml
 global:
@@ -446,8 +448,10 @@ Recipe is stated there in terms you can act on.
 
 ## Optional plugin dependencies
 
-This table is the list. Which plugin needs which gem, how to install it, and
-whether the plugin still works are all here, and nothing else repeats it.
+This table is the operator-facing source of truth for which plugin or tool
+needs which optional dependency and how to install it. Current plugin support
+status is maintained separately in
+[`PLUGINS.md`](PLUGINS.md#6-the-plugins).
 
 None of these gems is installed by `gem install automatic` or by a default
 `bundle install`. Install one only if you use the plugin.
@@ -456,26 +460,27 @@ None of these gems is installed by `gem install automatic` or by a default
 --local with <group>` and `bundle install`, because `bundle exec` sees only the
 bundle. `plugins` is every group in the first block at once.
 
-| Plugin | Needs | Installed gem | Checkout group | Status |
-| --- | --- | --- | --- | --- |
-| `StorePermalink`, `StoreFullText`, `StoreDigest` | `activerecord`, `sqlite3` | `gem install activerecord sqlite3` | `store` | Supported |
-| `FilterImageSource`, `FilterDescriptionLink`, `SubscriptionLink`, `SubscriptionTumblr`, `CustomFeedWeb` | `nokogiri` | `gem install nokogiri` | `html` | Supported (`SubscriptionTumblr` external) |
-| `PublishMarkdown` | `nokogiri`, for HTML bodies only | `gem install nokogiri` | `html` | Supported; runs without it |
-| `FilterSanitize` | `sanitize` | `gem install sanitize` | `sanitize` | Supported |
-| `autodiscovery` and `inspect` subcommands | `feedbag` | `gem install feedbag` | `autodiscovery` | Supported |
-| `FilterFullFeed` | `nokogiri`, and a siteinfo file | `gem install nokogiri` | `html` | Supported (external) |
-| `CustomFeedSVNLog` | the `svn` command; no gem | — | — | Supported (external) |
-| `ProvideFluentd`, `PublishFluentd` | `fluent-logger`, and a Fluentd instance | `gem install fluent-logger` | `fluentd` | Supported (external) |
-| `PublishMemcached` | `dalli`, and a memcached server | `gem install dalli` | `memcached` | Supported (external) |
-| `PublishAmazonS3`, `StoreFile` S3 path | `aws-sdk-s3`, and a bucket | `gem install aws-sdk-s3` | `s3` | Supported (external) |
-| `PublishInstapaper` | an Instapaper account; no gem | — | — | Supported (external) |
-| `PublishEject` | the `eject` or `drutil` command | — | — | Supported (external) |
-| `NotifyIkachan` | an `ikachan` gateway you run | — | — | Supported (external) |
-| `FilterOpenAI`, `FilterClaude`, `FilterGemini`, `FilterSakuraAI` | an account and an API token with that one service; no gem | — | — | Supported (external) |
-| `PublishHatenaBookmark` | the current Hatena API, which it does not speak | — | — | Needs rework |
-
-The `plugins` group is the first five rows: the optional gems of the plugins
-whose specs need nothing but the gem. The gems below it are in their own groups
+| Plugin | Needs | Installed gem | Checkout group |
+| --- | --- | --- | --- |
+| `StorePermalink`, `StoreFullText`, `StoreDigest` | `activerecord`, `sqlite3` | `gem install activerecord sqlite3` | `store` |
+| `FilterImageSource`, `FilterDescriptionLink`, `SubscriptionLink`, `SubscriptionTumblr`, `CustomFeedWeb` | `nokogiri` | `gem install nokogiri` | `html` |
+| `PublishMarkdown` | `nokogiri`, for HTML bodies only | `gem install nokogiri` | `html` |
+| `FilterSanitize` | `sanitize` | `gem install sanitize` | `sanitize` |
+| `autodiscovery` and `inspect` subcommands | `feedbag` | `gem install feedbag` | `autodiscovery` |
+| `FilterFullFeed` | `nokogiri`, and a siteinfo file | `gem install nokogiri` | `html` |
+| `CustomFeedSVNLog` | the `svn` command; no gem | — | — |
+| `ProvideFluentd`, `PublishFluentd` | `fluent-logger`, and a Fluentd instance | `gem install fluent-logger` | `fluentd` |
+| `PublishMemcached` | `dalli`, and a memcached server | `gem install dalli` | `memcached` |
+| `PublishAmazonS3`, `StoreFile` S3 path | `aws-sdk-s3`, and a bucket | `gem install aws-sdk-s3` | `s3` |
+| `PublishInstapaper` | an Instapaper account; no gem | — | — |
+| `PublishEject` | the `eject` or `drutil` command | — | — |
+| `NotifyIkachan` | an `ikachan` gateway you run | — | — |
+| `FilterOpenAI`, `FilterClaude`, `FilterGemini`, `FilterSakuraAI`, `FilterKimi` | an account and an API token with that one service; no gem | — | — |
+| `PublishHatenaBookmark` | the current Hatena API, which it does not speak | — | — |
+
+Membership of the aggregate `plugins` group is defined in `Gemfile`. It
+contains the optional gems whose corresponding specs need no external
+service; the table above maps those dependencies to their consumers. The gems below it are in their own groups
 only, because each of those plugins also needs a service, a bucket or a
 command, and installing a gem alone would not make the plugin — or its spec —
 work.
@@ -546,7 +551,7 @@ plugins:
 
 [`QUICKSTART.md`](QUICKSTART.md) runs that Recipe end to end, with the sites it
 watches and what each plugin does. What follows is the part a checkout does
-differently: turning those three plugins into a bundle that can run them.
+differently: turning the Recipe's plugins into a bundle that can run them.
 
 **1. List the plugins the Recipe names.** They are the `module` lines, in order:
 `CustomFeedWeb`, `StoreDigest`, `PublishMarkdown`.
@@ -693,7 +698,7 @@ bundle exec ruby -ractive_record -e 'puts ActiveRecord::VERSION::STRING'
 bundle exec ruby -rsqlite3       -e 'puts SQLite3::VERSION'
 ```
 
-Those three `require` the libraries the way the plugins do — note
+Those commands `require` the libraries the way the plugins do — note
 `active_record` for the `activerecord` gem — under the same bundle the Recipe
 will run under. `gem list` answers a different question and is the one to
 distrust here: it lists what RubyGems has, which in a checkout is neither what
@@ -701,7 +706,8 @@ the plugins will load nor what a missing-gem message is about.
 
 ### All of the optional gems, or only the ones a Recipe names
 
-Two ways to select groups, for two purposes:
+Choose the aggregate `plugins` group for plugin development, or
+purpose-specific groups for the Recipe being run:
 
 ```sh
 bundle config set --local with plugins        # all of them, at once