Where would PCIFIC fit in your business?

GOAL
Find out where PCIFIC for Business could fit into this codebase, and tell me in plain words. PCIFIC (https://business.pcific.ai) is a set of trust tools for every team, from marketplaces and shops to anyone writing to customers. This is a look, not an integration: read, report, change nothing. When you finish, I should know which tools fit, where, how much work each would be, and where to start. If I want, save the findings as a notes file.

APPROACH
1. Inspect the repository before drawing any conclusion. Work out what it sells, who sells it, who buys it, and how a product gets from being added to being paid for. Use the words the code uses (advert, product, item, listing, whatever it says).
2. For each tool below, look for the places where it would earn its place: where products are created or imported, where product pages are shown, where customers ask questions, where photos are uploaded, where devices are checked in or traded in, and where anything is reviewed before it goes live. Look across the whole journey, not just the first match.
3. Plan your report from what you actually found. Do not guess file names or behaviour you have not read.

The tools:
- PixelTrace: Know which photos were taken live. For anyone who ships, takes returns or relies on a photo as proof, from a one-person shop to a claims team. Photos taken live on PixelTrace's camera page get a certificate anyone can check. Photos used before are flagged for a person to review.
- Orbit: Your listing form. Filled faster, with important details checked. From photos and a few details, Orbit researches the product, checks important details and fills your existing listing form. Sellers do less typing, and anything it cannot verify is flagged for clarification. Every draft follows your own listing format, ready for the seller to review.
- Safeguard: Reviews each listing before it goes live. For anyone who publishes product pages, their own or other people's. Safeguard reads a page the way a careful customer would and says what is missing, what does not add up and what to ask. Before a page goes live, it scores it and gives the exact fixes that lift it.
- Ask PCIFIC: Answers to customers' questions, with the source shown. For any team fielding the same questions, in a chat window or a busy inbox. Ask PCIFIC answers from your documents and shows the source.

Facts to use when judging fit:
- There are two ways in today, from least to most work. Hosted pages, where PCIFIC serves the check on its own web address in the business's colours and logo and the site only links to it, are coming soon: mention them only as coming soon, never as a way in now. Drop in templates: a ready made front end per tool that is embedded or copied into the site. The API: the site's own server calls PCIFIC and shows the result in its own design. A business can also run the AI tools on its own model provider and key (Bring Your Own). Say which way suits each fit.
- Safeguard checks a listing a buyer is looking at. It reads the title, description, price, condition, item details and up to 12 photos, and works with only a title or a description.
- Orbit writes a listing from the seller's photos, notes or known details. Photos help but are not required, so a text only listing form still fits.
- PixelTrace certificates have their own public page that anyone can open without an account, and the business shows the certificate code on the listing.

REQUIREMENTS
Read only
- Do not change, add, move or delete any file, except the notes file below if I say yes to it.
- Do not install anything, run migrations, start services or change configuration.

Privacy
- Do not send any code, file contents, customer data, keys or secrets anywhere. Do not make outbound calls.

How to talk to me
- Explain everything in plain words. If a technical term is unavoidable, say what it means in brackets straight after it.
- Use this environment's question tool if it has one. Otherwise end your message with the questions as a short numbered list and wait for my answers. Put every question you have into one batch.

The report
- One line on what this business is.
- For each tool that fits: where (the real file and function names), what it would do there in one sentence, and roughly how much work it would be (small, medium or large).
- The tools that do not fit, in one line each. A tool that fits nowhere is a fine answer; say why.
- The one place you would start, and why.

The notes file
- After the report, ask whether I want the findings saved as a markdown file named pcific-fit.md. Suggest a sensible place (for example the repository's docs folder) and let me pick. Only write it if I say yes, and only where I chose.

TEST-WRITING
Do not write or run tests in this repository; this is a read only look. Instead, for each tool that fits, describe the tests a real integration would need, so I can judge the work honestly:
- The starting state, what the person does, and what they should see or what the system should record.
- The meaningful failure paths: the check fails, PCIFIC cannot be reached, the person cancels or retries.
- Where the test would live in this repository's existing test setup, if it has one. Name the real test folder and tool you found, or say there is none.
Keep it to a few lines per tool. Include this in the report and in the notes file.

WHAT FINISHED LOOKS LIKE
- I have the report above, with real file and function names for every fit and the tests each integration would need.
- No file in the repository has changed, apart from pcific-fit.md if I asked for it, in the place I chose.
- Nothing was sent outside this machine.
- You have told me anything you could not work out, rather than guessing.