Research And Store

<!-- daita-sensitivity: internal -->
# research-and-store

Research organizations using admitted tools and save a bounded, cited batch to an explicitly permitted relational target.

## Instructions

1. Discover admitted research tools and resolve the exact target using current catalog facts. If the target is ambiguous, ask one concrete question. Report a missing integration or permission honestly.
2. Inspect the target schema, supported unique conflict key, permitted insert/update columns, identity generation and row ceiling. Ensure the full request classification fits both research outbound ceilings and the target classification.
3. Gather citations, distinguish conflicting assertions, state inclusion criteria and coverage limits, and normalize one uniform scalar batch. Do not claim an exhaustive list of all companies.
4. For immediate work, preview the grounded batch and invoke the corresponding write with its current-run fingerprint when execution was requested and the remaining allowance permits proceeding. Report preview-only or unfinished work honestly. Zero existing matches can permit insertion; a nonempty unchanged batch still consumes an invocation. For now-and-weekly work, propose one recurring assignment with an explicit immediate occurrence. Use discovery's automation contract; loading future execution tools is unnecessary unless the contract was omitted. Do not also perform a separate initial foreground write.
5. During assignment approval, specify whether no findings may succeed without an action or whether a write is required. Freeze the exact scope, call ceiling, supported evidence basis, budgets, expiry and inbox outcome.
6. Report researched claims separately from adapter-verified inserted, updated and unchanged counts. Server-reported MCP evidence establishes invocation only. Research or an artifact cannot satisfy a missing required write.
7. If an action is uncertain, preserve its receipt and direct the user to human receipt inspection/recovery. Never retry, replay, chunk or compensate automatically. Recovery grants no connector permission and performs no action.

This procedure is advisory. It cannot admit connectors, provide credentials, expand scope, grant permissions, replace current schema facts or authorize recovery. Saved assignments execute only while an eligible Daita host is open and use the exact retained skill version.