Give your agent a research routine.
Run a fixed research question, retain the evidence and pick up where you left off. Financial Evidence 0.1.7 connects LiquiLens bank disclosures, Seiche funding context and Undertow market-liquidity observations to a private, durable workflow.
No data API key is required for the public research inputs. Your state stays on your machine. Package installation starts no service and sends no installation telemetry.
Install the published package
Use Python 3.10 or newer and a local filesystem. Downloaded release artifacts carry checksums and GitHub build attestations; inspect the verification record.
python3 -m venv .venv .venv/bin/python -m pip install 'https://github.com/beepboop2025/financial-evidence-skills/releases/download/v0.1.7/financial_evidence-0.1.7-py3-none-any.whl' .venv/bin/financial-evidence-runtime catalog
The core CLI has no package dependencies. The full guide covers optional private MCP, offline acceptance, scheduling and recovery.
Make one recurring question concrete
Download the US-dollar funding workflow. It checks source dates, values, units, rights and whether the returned page is complete. Review its limits, then register it using a private state path:
.venv/bin/financial-evidence-runtime --root /absolute/private/research-state init .venv/bin/financial-evidence-runtime --root /absolute/private/research-state register runtime-funding-watch.json .venv/bin/financial-evidence-runtime --root /absolute/private/research-state run funding-watch --key first-review .venv/bin/financial-evidence-runtime --root /absolute/private/research-state metrics
Retain the returned run ID. Reusing the same key returns the same attempt. A blocked result includes its reasons; missing or old evidence remains explicit. A completed research check grants no trading permission.
Choose the product for the question
| Question | Product | Runtime preset |
|---|---|---|
| What do the published funding observations show? | Seiche | funding-watch |
| What do covered banks disclose? | LiquiLens | bank-evidence |
| What market-liquidity evidence is available? | Undertow | liquidity-watch |
These products have different observation clocks and coverage. Narrow broad presets to your question; a broad query may correctly remain blocked by missing rows, rights or incomplete pagination.
Schedule, replay and recover
# Invoke from your scheduler once a minute; at most one due job runs. .venv/bin/financial-evidence-runtime --root /absolute/private/research-state tick --limit 1 # Replace RUN_ID with the retained identifier. .venv/bin/financial-evidence-runtime --root /absolute/private/research-state replay RUN_ID .venv/bin/financial-evidence-runtime --root /absolute/private/research-state backup --output /absolute/new/runtime-backup.sqlite .venv/bin/financial-evidence-runtime --root /absolute/private/research-state stop
Replay uses the captured bytes without network access. It preserves the original source dates. Backups retain policies, idempotency keys and event cursors. Restore to a new private directory and resume only one copy of the installation.
Connect a private MCP client
Install the package’s workspace extra to use financial-evidence-runtime-mcp --root /absolute/private/research-state as a stdio server. It exposes six tools for catalog, registered jobs, bounded runs, replay, events and metrics. The owner controls job registration and policy; an agent can call only registered jobs.
Evaluate a useful repeat task
Start with one question. Record time to the first useful result, then run it again when a new observation is expected. Use the 14-day scorecard to track useful outcomes and returns. Local runs and package downloads do not establish independent users or revenue.
The runtime stores research evidence. A separate execution host must acquire eligible evidence and enforce its own account and order permissions. Explore that integration.
Keep it running unattended
Runtime Operations 1.0.3 adds a private live console, schedule and capacity checks, encrypted offsite backup on UTC quarter-hours with missed-run catch-up and an exact restore check after every backup. Recovery works even when the original host journal and local backup receipts are lost. It verifies an explicitly selected encrypted snapshot, preserves retry keys and keeps the restored copy stopped. Use your existing Linux host and encrypted backup repository.
Follow the installation and recovery guide and inspect the release verification record. Operations health and source readiness are shown separately. The console explains blocked source rows with original observation dates, affected fields and next steps. Upgrades verify installed service files against the prior applied plan before replacing them. The console stays on loopback and can be reached through your existing SSH access.