Resolve everything it can
One trigger. It reads the federal record and the drawing, grounds every fact in a quote, and derives the conflict between them. No clicks.
The Collaborative Partner
A plan no owner should have to write alone.
Give Downstream a dam and it works on its own: it resolves the public record, reads the legacy drawing, notices when two sources disagree, drafts every section it has evidence for, refuses the map it cannot justify, and schedules its own follow-ups. Then it stops and asks the owner the handful of things only they know, and keeps working between sessions, for weeks, without being opened.
The public workspace needs no key at all. A developer key takes about thirty seconds: self-service, no invitation, with a browser console and full reference.
Boundary: this demo never generates an inundation boundary, evacuation zone, certification, or submission. It produces a synthetic draft and a documented safe stop.
The friction
The form is not the hard part.
Facts are scattered across public records, old drawings, local memory, and jurisdiction-specific guidance.
Ask only what it must not invent
Owner knowledge is the one input it is not allowed to guess. It asks one question at a time, and says why it is asking.
Between sessions, unattended
Durable wakes reopen questions held for later and follow up on a stalled draft. Cloud Scheduler runs them whether or not anyone is watching.
A receipt, not a claim
Every step is on an ordered timeline with the actor that performed it, so the autonomy is counted from stored state rather than asserted.
Measured multimodal evidence
The drawing was read, recorded, and graded.
One real Vertex AI Gemini 3.5 Flash response ships beside the image, truth, and accuracy report.
Gemini 3.5 Flash, recorded output
5 of 5 measured checks passed
- 3/3
- target values matched adjacent truth
- All
- quotes occur in Gemini's own transcription
- 0
- facts dropped by the guard
The drawing says 31 feet while the synthetic registry fixture says 28. Downstream keeps both and marks the conflict for owner review.
Interactive judge preset
Build the draft with Cedar Hollow.
A synthetic dam keeps the workflow testable without making claims about a real owner.
Nothing has run yet
One request does fifteen things.
It resolves the dam record, reads the 1958 drawing with Gemini, checks every fact against a quote it can point to, derives the conflict between two sources, drafts the sections it has evidence for, refuses the map it cannot justify, and schedules its own follow-ups. Then it stops and asks you the six things it is not allowed to guess.
Start a clean preset.
I will resolve three drawing facts first, turn the source conflict into a targeted question, and ask only what the fixture cannot answer.
Your corrections stay attributable.
After the first answer, revise it here. Downstream keeps both versions and updates the draft.
Autonomy receipt
What ran without being asked.
Counted from the stored run timeline, not from a description. The agent stops at owner knowledge because inventing it would be the failure.
Steps it took on its own0
Facts only the owner could give0
Clicks needed to keep it going0
Follow-ups it scheduled for itself0
Start the preset to open a run.
Prove it runs without you
Everything above uses a clock you control. This one does not: it registers a wake on the real calendar, and Cloud Scheduler executes it. Close the tab and it still fires.
Not armed.
What ran
View the ordered run timeline
What it learned about you
No style preferences yet. Accept the style or ask for concise summaries and they appear here.
Use it beyond the demo
A tenant-private planning API, explained before credentials.
The public Cedar Hollow preset is the fastest evaluation path. The API opens private workspaces from exact public USACE NID records.
Evaluate publicly
Run the guided synthetic workflow, hold and reopen a gap, revise an answer, and inspect the evidence ledger.
Run the guided demoGet your own API key
Self-service, no invitation and no account. Enter a label, get a seven-day key, and run every endpoint from the browser with the built-in console.
Create a key nowRead the API reference
Every endpoint documented with parameters, an example request, and a live runner. The interactive OpenAPI schema is one click away.
Open the referenceThree calls to a private workspace
The key identifies a tenant the server minted. Nobody else’s key can read your workspaces, even with the id.
- 50 keys per network per day
- 1,000 API calls per key per day
- 7 days key lifetime, revocable instantly
- 0 accounts, invitations, or payment details
# 1. get a key (or use the console at /developer)
curl -X POST -H "Content-Type: application/json" -d '{"label":"My integration","acknowledge_terms":true}' $BASE/developer/keys
# 2. open a workspace from a real public dam record
curl -X POST -H "X-API-Key: $KEY" -H "Content-Type: application/json" -d '{"nid_id":"IA03081"}' $BASE/v1/workspaces
# 3. see what the agent did on its own
curl -H "X-API-Key: $KEY" $BASE/v1/workspaces/$ID/autonomyAPI boundary: screening and drafting support only. No engineering-grade inundation extent, certification, approval, or submission.
Mapping safety gate
Useful enough to guide, disciplined enough to stop.
The line is a documented flow-path input. It is deliberately not drawn as an area.
Synthetic damCounty road input
!
Boundary withheld
No approved map was supplied. Method applicability, jurisdictional acceptance, and reference comparison are unproven. Downstream refuses to invent an extent.
Next safe action
Request an approved map or route this section to the state dam-safety office or a qualified engineer.
Public evidence
Every number and requirement has a route back.
Live query not run yet. It requests high-hazard records whose public EAP status field is null, and labels that field as unreported rather than absent.
| Source | What it supports | Boundary |
|---|---|---|
| USACE National Inventory of Dams | Public inventory and live record fields | Inventory status is not structural condition or proof of compliance |
| FEMA P-64 | EAP purpose, roles, and typical contents | Federal guidance does not replace state requirements |
| ASDSO Emergency Action Planning | Owner collaboration and notification planning | State review and emergency-manager coordination remain necessary |
| SIMS methodology | When simplified mapping may be applicable | Not a substitute for engineering judgment or regulatory compliance |