Evidence and control

A useful financial agent should leave a result you can inspect. Boomkin records reviewed source pins, copied resource hashes, project briefs and run artifacts. These checks give observations and decisions a traceable context.

Four different milestones

Installing a skill, discovering a provider, reading live data and authorizing a financial action are different milestones. Boomkin reports them separately.

doctor --live probes public connection discovery. A discovered tool still needs a successful read to prove data access. An authenticated account still needs scoped authority before a consequential action.

Research projects

Projects save a separate brief and prompt for each run, with recorded hashes and the installed pack version and revision. Native Hermes writes the report, raw sources, evidence observations and unsigned plan.

The result stays in review until its evidence checks pass. The checker verifies captured source hashes, report citations, declared freshness deadlines and the no-action or unsigned-plan contract. A successful model process alone does not satisfy those checks.

These are consistency and integrity checks. They cannot establish that a provider is correct or an agent's reasoning is sound. Read the project documentation for the schema and the exact validation boundary.

Market snapshots

Data helpers retain the provider identity, query, source timestamps, raw-response hash and limitations. Missing or stale data becomes an explicit gap. It must not become a zero balance, zero price or verified current observation.

Strategy results

Every simulation records asset identity, price provenance, strategy rules, fees, slippage, assumptions and the benchmark. Synthetic observations are explicitly labeled. Research marks cannot prove a venue could fill a trade at that price.

Financial control

Onboarding installs procedures and connections. It does not create or fund a wallet, submit a transaction or start an autonomous trading service.

Financial actions use the selected provider's official tools and require the user's authorization for the actual action, target and amount. Provider-enforced scopes, spending limits and separate read-only accounts provide controls beyond agent instructions.

Reconciliation

An uncertain remote action needs reconciliation before a retry. Source-chain confirmation does not establish bridge arrival. A submitted transaction does not establish settlement. A report cannot replace terminal position or balance evidence.

Local ownership

Hermes remains the runtime. Profiles preserve your model and tool configuration, instructions and sessions. The independent MIT skill packs are inspectable and portable. Keep credentials in native secret facilities and outside project inputs and saved source URLs.