Data provenance
Record the provider, field, source date, permitted purpose, and fallback order. A waterfall can improve fill while making conflicts and deletion requests harder to explain.
Security & Data
Inspect provenance, permissions, and review gates before scale
Company intelligence is operationally trustworthy only when a reviewer can trace where a field came from, when it was observed, how it changed, and what the workflow may do next.
npx -y @okki-global/okki-go-taroballFact ledger
Four questions every deployment must answer
Credential handling
Use environment secrets with minimum scope. Keep API keys out of prompts, repositories, shared screenshots, prospect exports, and error reports.
Runtime behavior
Review package permissions, outbound connections, retries, rate limits, logs, temporary files, and destinations. Installation success does not prove safe configuration.
Retention and deletion
Specify who can access intermediate and final records, how corrections propagate, when stale data expires, and how suppression or deletion is enforced.
Connection matrix
Follow the data through each runtime stage
The labels below describe evaluation states, not official partnerships. Confirm supported runtimes and providers in current package documentation.
Input sources
- Company provider
- API credential · least privilege · status: configure and verify
- Email verifier
- Point-in-time deliverability signal · status: optional
- CRM cohort
- Known test records · status: reviewer supplied
Research agent
- Task brief
- Firmographic, technographic, recency, and exclusion criteria
- Resolution
- Domain and entity comparison with explicit unknown state
- Review gate
- Named human accepts, corrects, rejects, or withholds action
Output destinations
- Preview
- Local review surface · no automatic sending
- CRM update
- Disabled until mapping and rollback are approved
- Outreach draft
- Separated from send permission and suppression checks
Compare operating models, not badge counts
Evaluation method checked 21 July 2026. Changing vendor facts, pricing, certifications, and integrations must be confirmed from official sources.
| Dimension | Agent-native research | Seat-based platform | Reviewer test |
|---|---|---|---|
| Setup path | Package, runtime, configured sources | Managed application and account | Document every required permission |
| Task model | Natural-language brief with structured output | Saved filters and platform workflows | Run the same known cohort |
| Source disclosure | Depends on configured connector and output | Depends on vendor documentation | Demand field-level source and date |
| Human review | Must be designed as an explicit gate | Depends on team process | Trace who approved the next action |
| Security evidence | Inspect package and runtime locally | Review current vendor materials | Mark unconfirmed claims Unknown |
| Deletion control | Depends on every connected store | Depends on vendor and integrations | Test a correction and deletion end to end |
Unknown is a valid result. It is safer than turning absent public evidence into a favorable or unfavorable claim.
Run a controlled security review
- Copy the exact command and record the package version.
- Run in a test environment and inspect the installation prompt.
- Configure minimum-scope credentials through a secret store.
- Review a known cohort, including an exclusion and an ambiguous identity.
npx -y @okki-global/okki-go-taroballDo not connect live outreach until provenance, secret handling, access, retention, deletion, suppression, opt-out, and human approval controls have been tested.