Welcome to Agentic Package Assembly thatassembles the package from the current version of everything.
Submission day used to be archaeology: nine attachments, four contributors, three inboxes, and a folder where budget_FINAL_v3_REAL coexists with its siblings. Risely's agents assemble from the source of record, and the office submits a sealed package.
Package assembly · checked against the sponsor's rules
pulling 0 of 4
The seal stays open until every required part is present and valid.
The current version pulls itself.
Every research office has the wrong-biosketch story. The assembly pulls each component from its source of record at the version it currently is, so the story finally stops collecting sequels.
The assembly retires the folder
budget_FINAL_v3_REAL.xlsx
budget_FINAL_v3_REAL(1).xlsx
description_latest_USE_THIS.pdf
One source of record, per document
the assembly pulls the current version of each part from where it lives
Nine attachments from four contributors across three inboxes used to meet for the first time at midnight. They meet in the assembly now.
Validation runs before the sponsor's does.
The description holds at 15 pages, the fonts and margins pass, and the files carry the names the portal expects. The return-without-review that wastes an entire cycle has nothing left to catch.
The format gauntlet, run early
checking
A format miss after upload is a returned proposal. The same miss before upload is a Tuesday.
The package refuses to seal incomplete.
The mentoring plan came onto the checklist from the parsed solicitation, and the seal will not close without it. A required document cannot be forgotten, because the gate remembers for everyone.
The seal is a gate
checking
Mentoring plan · missing
required by the parsed solicitation · the checklist knew before anyone opened the folder
The package will not seal without it, which is the whole point of a gate.
Forgetting a required document stops being possible, because the seal remembers for everyone.
October's question becomes a lookup.
When the sponsor calls months later, the sealed manifest answers exactly which version of every component went out. Certainty replaces forensics, which is what version control was always for.
The sealed manifest
When the sponsor calls in October, the answer to what went out is a lookup instead of forensics.
One document changes. The package re-seals.
A late biosketch, a revised budget, a swapped letter. Any of them invalidates the old seal, and every one runs the same way.
A biosketch updates
two days before the deadline
The package re-assembles
it pulls the current version again
The format checks re-run
limits and fonts both check out
The seal re-stamps
every version recorded fresh
October gets its answer
what went out has one record
What changes, and how it runs.
The wrong-version story ends
Every part pulls from the source of record.
Format returns stop happening
Validation runs before submission instead of after.
What went out has one answer
The sealed manifest holds every component's version.
The technical read
Connects read-only to your document store, grants system, and submission portal records to start
An officer approves the package before the office submits
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.