Written for the people who would have to run this. The short version: it belongs in your AWS account, reached through Bedrock, behind Okta — nothing in the design requires Ansco data to leave Ansco.
The questions that decide it
- Where does it run?
- In Ansco's AWS account, in Ansco's region. The models are reached through Bedrock, which is a console toggle on infrastructure you already own — no new vendor, no new contract, no procurement cycle. Bedrock also carries non-Anthropic models, so the choice of model is a configuration value rather than a dependency.
- What leaves your network?
- In the Bedrock configuration, nothing. Photographs, manifests and documents go from the phone to an endpoint in your account and are read by a model in your account. The proof of concept you are looking at runs on our infrastructure because you have not sent us anything yet; that is a property of the demo, not of the design.
- Who holds the photographs?
- You do. Captures land in your object storage under your retention policy. There is no second copy, no training use, and no path by which a photograph reaches a model vendor as anything other than a single inference request your account made.
- How do people sign in?
- Okta, which you already run. The app has no user store of its own and no passwords to leak. Subcontractor provisioning and offboarding stay where they are today rather than becoming a second thing to remember.
- What does the phone need?
- Nothing but the app. Every judgement a technician sees — focus, exposure, legibility, the segment check — is computed on the device, so it works in a vault with no signal. The package uploads itself when the phone next has coverage.
Who owns what
| Component | Built by | Runs where |
|---|---|---|
| The iOS app | PTP builds | Ships through your MDM or TestFlight |
| The review desk | PTP builds | Runs in your account on your infrastructure |
| The engines | PTP builds | Python and TypeScript; no managed service to licence |
| Models | Ansco owns | Bedrock in your account, your region, your spend |
| Identity | Ansco owns | Okta, unchanged |
| Storage and retention | Ansco owns | Your S3, your policy |
| The rule set | Ansco owns | Your shot list, calibrated by your rejection history |
From here to production
- NowProof of concept on PTP infrastructure, public documents only. Nothing of yours has been sent anywhere.
- On an NDAYour close-out packages and a real AT&T CD. Everything here is re-run against your paperwork, and the rule set stops being our reading of the spec.
- PilotOne crew, one business line, in your AWS. Reviewers work the real queue beside their existing process and we compare the two.
- ProductionBoth lines. The desk becomes the process rather than a second opinion on it.
What is not true yet
- Nothing here has run against an Ansco document. Every finding is from public filings or data we generated.
- The shot list is our reading of AT&T's requirements, not their published spec. Your rejection history is what sets where the line actually falls.
- The capture app has not run on a physical phone — camera and microphone paths are unexercised.
- Bedrock is wired and selectable but has not been run against your account, because we do not have credentials to one.