Collect evidence from connected systems
Internal product research scaffold for “Collect evidence from connected systems”. Questions and product/code evidence needed before public copy can be written.
Working research scaffold. This page lists questions for Product and Engineering; it does not confirm that the feature is available. The current foundation marks detailed first-party collection, proof-pack generation, buyer inspection, and AI-assisted response preparation as planned. Verify each answer against the released Mockup product and its code before turning it into a public capability claim.
Questions to answer
- Which information is collected today, from which systems, and under what product status?
- Is collection user-triggered, scheduled, event-driven, or a mix?
- What is the first-sync process, and how are pagination, rate limits, and partial results handled?
- Can a customer pause or disconnect collection, and what happens to previously collected data?
- How are collection boundaries and tenant isolation enforced?
Product and code information needed
- Released collectors, connector jobs, queues, schedules, event subscriptions, and feature flags.
- A source-by-source inventory of collected objects, fields, permissions, cadence, and known limits.
- Sync state, retry, rate-limit, and partial-result behavior in code and tests.
- Disconnect, deletion, and tenant-isolation flows, supported by implementation and tests.