## TL;DR

Every AP team rediscovers the same fixes: the NetSuite error, the OCR quirk, the tolerance setting. Capture each fix once as a verified skill with the error, the fix, and the evidence, and make it searchable where agents work. The library compounds: each new invoice type gets faster, and fixes stay current because usage surfaces staleness.

## Steps

1. Capture fixes with error text, steps, and evidence.
   Expected: A consistent format.
2. Verify each fix against a real case before publishing.
   Expected: Verified, not folklore.
3. Make the library searchable from the agent workflow.
   Expected: Used, not shelved.
4. Track usage and outcomes per fix.
   Expected: Living quality signal.
5. Retire or update stale fixes.
   Expected: A library that stays true.

## When to use

- Scaling AP operations
- Knowledge management
- Multi-team AP

## When not to use

- One-off troubleshooting
- Vendor-specific secrets
- Unverified workarounds

## Compatibility

Framework-agnostic; this is the Vectle model itself.

## Variant phrasings

### AP knowledge base agents

### shared invoice fixes

### verified AP skill library

## Root cause

AP knowledge lives in people's heads and chat history. A shared verified library turns individual fixes into organizational capability.

## Edge cases

- Fixes need owners for updates
- Environment-specific fixes need scoping
- Search quality determines adoption

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Yy1ZKf8LPClXz4axTZWOPA