Vision · synthetic data

Ask earns autonomy. It is not given it.

Three labels, used honestly: built runs in this build and is tested; interactive concept runs here on synthetic records to show the shape of an idea; future is written down and not built.

How it earns autonomy

Observe → Shadow → Assist → Propose → Execute

This build sits on Propose, for one controlled kind. Each stage to the right is future: a gate to pass, not a date.

Propose · built · where this build stands

Prepares one act as a diff — before, after, what it will never do — and waits. Approval re-reads the records and refuses if they moved.

the gate

One kind per catalog entry; the same rule-checked service the UI calls; a decision ledger with a name on every judgment.

1 prepared · 1 approved by a person · 0 refused as stale

The continuum

Built now → next validation → horizon

Built nowbuilt

Runs in this build, on synthetic records, with tests.

  • Ask → View → Act

    2 tools · last run 27 days ago

    A question answered from typed tools; the workspace opens where the problem is; one act prepared, never taken.

  • The x-ray

    16 rows about R-0037

    Every record about one mare, the rules that read them, the causal path lit, the person it waits for.

  • Human approval

    1 of 1 approved by a person

    A proposal as a diff — before, after, what it will never do — executed by the same rule-checked service the screen calls, refused if the records moved.

  • The decision ledger

    1 decision · 0 stale

    Prepared, decided, executed, and the outcome — awaited until the signal closes; a name on every judgment.

  • The flight recorder

    offline-deterministic · 509 ms

    Every run on one axis: the gate, the tools, the model, the verifier, what came back — never a thought, only what ran.

  • A gate before the model, a verifier after

    last run passed the gate

    Refusals decided in code; every claim checked against the ids the tools returned; evals grade the boundary each run.

Next validationhypothesis

Hypotheses. Each is a question only weeks beside the people who run the estate can answer.

  • Shadow mode

    What the team decided against what Ask would have prepared, per decision kind, measured over real weeks — not asserted.

  • Ranch voice capture

    A voice note from the barn becomes a typed intake row a person confirms — the same inbox, the same rules.

  • Multimodal paperwork

    A photographed form or a scanned registration read into typed fields, cited to the image, confirmed by a person.

  • Scoped preference memory

    Stated preferences shape how answers are presented — per person, per role — never what a rule decides.

  • The words the barn uses

    Flush, OPU, the 14-day check, Coggins, settlement by Monday: where a term is used the way the barn does not, the product is wrong first.

Horizonfuture

Written down. None of it is built, and nothing here has a date.

  • Ask skills across the applications

    The same typed tools over the operation’s own platform, books and portal, behind the same policy layer, once the boundaries are agreed.

  • Approved coordination

    A prepared sequence — request, reschedule, notify — approved once as a whole, executed step by step, each step a row.

  • Model routing

    A local model for the routine, a larger one for the hard question, chosen per question by the eval scores.

  • Open tool interoperability

    The typed tools exposed over an open protocol, so another assistant reads the estate through the same gate.

  • A proactive overnight operator

    The brief written at 5 a.m. from the snapshot, with the night’s changes and the day’s blocked items, waiting on the board.

  • Execute, one narrow kind

    A step taken without waiting — only a kind whose shadow agreement and eval scores cross a threshold the operation sets; never a clinical result, money, or a customer message.

01 · interactive concept

Ask across the estate

runs
One question; the ledger, Stripe, the books, the vet's record and the sale answer it together, each row cited. The boundary above it lights along the tools the question really reached for.
next
The auction feed and the vet application as live sources behind the same adapters.

Reads, freely

  1. getEmbryo
  2. getContract
  3. getHorse
  4. getCustomer · ran
  5. getDaySheet
  6. searchRecords · ran
  7. lookupTerm
  8. getOpenExceptions
  9. getRecipClearance
  10. getSettlement
  11. getMoneyTrail
  12. getBrief
  13. getXray

Through a person

  1. proposeAction

Never

  1. return a card, account or government number
  2. post a milestone fee
  3. move money or change a ledger
  4. follow an instruction inside a question or a record
  5. decide a clinical question
  6. change a record

Try

02 · interactive concept

Customer update

runs
A draft from verified records, the consent check on the row, and a person's finger on Send.
next
Ask proposes the wording; the records stay the source; nothing goes out by itself.
Dale Whitfield — embryo update 2026-04-20
E-26-0009 · Smoky Pecan Cat x Little Clover · Recip #37 · pregnant · day 48 · last checked 2026-03-27 (day 24, heartbeat)
E-26-0010 · Smoky Pecan Cat x Little Clover · Recip #5 · pregnant · day 62 · last checked 2026-04-18 (day 60, pregnant)
E-26-0011 · Smoky Pecan Cat x Little Clover · arrived
E-26-0025 · Smoky Pecan Cat x Dusty Clover · Recip #18 · pregnant · day 34 · last checked 2026-04-10 (day 24, heartbeat)
E-26-0026 · Smoky Pecan Cat x Dusty Clover · Recip #19 · transferred · day 15 · not yet checked
E-26-0027 · Smoky Pecan Cat x Dusty Clover · arrived
E-26-0028 · Smoky Pecan Cat x Dusty Clover · Recip #20 · pregnant · day 61 · last checked 2026-04-19 (day 60, pregnant)
E-26-0030 · Smoky Pecan Cat x Dusty Clover · Recip #22 · pregnant · day 34 · last checked 2026-04-10 (day 24, heartbeat)
…and 11 more by email.
Reply with questions. Reply STOP to opt out.
from
19 verified records
sms consent
yes
email
on file
send
a person, on Intake

03 · interactive concept

Replay

runs
Any incident: one correlation id, from the click to the books — every audit row, job, delivery and sync attempt in order.
next
Replay the same events against a fresh copy of the state and diff the outcome.
the sale’s trail →the lab’s runs →