Skip to content

Tagvico AI v3.0.0

Choose a tag to compare

View all tags
@arturict arturict released this 21 Jul 23:34
v3.0.0
b1728fc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Tagvico AI v3.0.0

Tagvico v3 turns Paperless-ngx documents into accountable household work while
keeping the established reviewable filing workflow intact.

Highlights

  • Create one Action Case per Paperless document with an owner, priority, due
    date, state, audit trail, and up to 100 checklist steps.
  • Ask the Companion about permitted documents and current actions. Read tools
    execute directly; every AI-proposed write becomes a durable proposal that an
    owner or adult must explicitly approve.
  • Give household members roles and encrypted, member-specific Paperless tokens
    instead of sharing one privileged credential.
  • Mirror top-level case state to reserved Paperless custom fields and the
    tagvico/action tag while keeping full checklists local to Tagvico.
  • Use the new Next.js console for actions, approvals, Companion sessions, and
    household settings alongside the existing filing and recovery operations.
  • Optionally list actions and approve or reject proposals through Telegram,
    still using each allowlisted person's own Paperless token.

Upgrade from v2

  1. Stop Tagvico and back up the complete tagvico_ai_data volume.
  2. Pin ghcr.io/arturict/tagvico-ai:3.0.0 in Compose.
  3. Start the container and allow the schema-v5 migration to finish. It adds
    households, members, cases, steps, Companion sessions, and approvals.
  4. Verify /health and /api/health, sign in, and test the Paperless and model
    provider connections.
  5. Process a non-sensitive document in Review first, create one Action Case,
    and approve one synthetic Companion proposal before using real household work.

The public application stays on port 3000. The scanner runs internally on port
3001 and must not be exposed. Do not run v2 and v3 against the same data volume.
Restore the backup before rolling back if v3 migrated the database.

Stable boundaries

  • Paperless-ngx remains the document system of record.
  • Companion tools never receive host shell or filesystem access.
  • AI-proposed writes cannot bypass the durable approval gate.
  • Provider model catalogs, prices, quotas, and subscription entitlements remain
    provider-controlled.
  • Telegram is optional, private-chat-only, and not end-to-end encrypted.

Full documentation: https://tagvico.arturf.ch/docs/

Assets 2
Loading