An auspex is not an oracle.

The read

Sample recommendation · full reasoning trace

Three sample reads spanning the verdict trinary. All values mocked for illustration. Live recommendations carry the same shape: verdict + confidence + per-lens contribution + counterfactual + sources + audit metadata. Tickers redacted on this page; the live pilot generates and audits one of these per ticker, per setup.

Four lenses. One reading.

Auspex aggregates signals across four independent lenses. Each lens runs its own extractor; the synthesis layer weighs them per the operator's preference profile. The reasoning trace surfaces every lens contribution on every recommendation.

The synthesis layer reads across all four panes. The reasoning trace shows per-lens contribution on every recommendation. When lenses disagree, the trace names the dispute by lens, not by ticker.

The execution

Operator setup DSL · fire-vs-block decisions

The AI recommends; code decides whether to fire. Setups are operator- authored rules in a code-like DSL. Same recommendation passes or fails a setup deterministically; every fill traces back to the rule that fired and the signals that triggered it.

 1// setups/catalyst-aware-swing.setup
 2// Catalyst-aware Swing — operator-authored
 3// Last modified: 2026-06-04 · operator: REDACTED
 4
 5WHEN
 6  recommendation.verdict       IN ["BUY", "PEND"]
 7  AND recommendation.confidence    >= 0.80
 8  AND recommendation.lens_weight("PoI") >= 0.30
 9  AND portfolio.position(ticker)    <  0.05
10  AND macro.vol_regime              IN ["low", "moderate"]
11
12THEN
13  execute(
14    MARKET,
15    size = recommendation.size_hint * (
16      verdict == "BUY" ? 0.75 : 0.40
17    ),
18    time_in_force = "DAY"
19  )
20
21ON FAIL
22  audit.block({
23    setup: "catalyst-aware-swing",
24    failing_condition: $auto,
25    operator_override: ALLOWED
26  })

Three sample reads passing through one operator setup. The fire carries the order ticket; the blocks carry the failing condition and the operator-override posture. Every decision (fire or block) is captured in the audit ledger with the rule that fired, the condition that failed, and the signal state at evaluation time.

The audit

Pipeline + execution trace · simulated

Every recommendation traces to its code path and its execution log. Below: the pipeline as TypeScript, with a sample run of the same pipeline as a live trace. the trade should be auditable before it executes.

 1// auspex/pipeline.ts
 2import { ingest, llm, rules, broker } from "@/auspex";
 3 
 4export async function recommend(
 5  ticker: string,
 6  operator: OperatorContext,
 7): Promise<Recommendation> {
 8  // [01] INGEST · code
 9  const filings = await ingest.filings(ticker);
10  const prices  = await ingest.prices(ticker, "1y");
11  const macro   = await ingest.macro();
12 
13  // [02] EXTRACT · llm — texture
14  const facts = await llm.extract({
15    filings, prices, macro,
16    schema: FactSchema,
17  });
18 
19  // [03] SYNTHESIZE · llm — texture
20  const synth = await llm.synthesize({
21    facts,
22    profile: operator.lensProfile,
23  });
24 
25  // [04] GATE · code — load-bearing
26  const decision = rules.evaluate({
27    synth,
28    setup: operator.setup,
29  });
30 
31  // [05] EXECUTE · code — load-bearing
32  if (decision.verdict === "FIRE") {
33    return broker.execute({
34      ticker,
35      ...decision.order,
36    });
37  }
38  return decision;
39}

The method

Architectural note · principles · vocabulary · scope

Most AI trading products are black boxes. They recommend, or worse execute, without showing the work. Auspex inverts that. The model contributes signal extraction, pattern recognition, and natural-language reasoning. The execution decision lives in code the operator wrote. Same architectural rule the studio applies in Verum's clinical gate, transposed to capital decisions: load-bearing actions in code, AI for the texture around them.

The in-scope items define the pilot deployment surface. The not-in-scope items establish what we will not pretend to do. Quarterly target dates for the in-flight items sit in Pilot Terms, section 07.

Pilot terms

Eligibility · onboarding · mechanics · status · brief us