Welcome to Agentic Document Generation thatrenders nine documents from one set of facts.

A proposal is one set of facts expressed in nine documents, and maintaining them by hand is how they drift apart. Risely's agents render every document from one source, and the officer reviews a diff whenever anything changes.

The proposal · one source, nine documents

a change lands

THE CHANGE

Postdoc start moves to March

Y1 salary drops $9,700

Fringe and indirect re-derive

New Y1 total: $96,300

RE-RENDERED IN THE SAME MINUTE

·Budget justification
·Project summary
·Current & pending
·Cover form

Every document is a rendering of one source.

The budget justification, the summary, the facilities page, and the forms all draw from the same fact base. None of them can quietly disagree, because none of them holds its own copy.

One source, many renderings

The proposal facts

people · dates · amounts · rates · aims

Budget justification

Project summary

Facilities page

Sponsor forms

A document maintained by hand is a copy waiting to go stale. A rendering cannot drift from its source.

The change ripples to the last page.

The budget moves $14K between years, and the justification, the summary, and two forms follow in the same minute. The mix of stale and current that used to survive the final midnight has nothing left to survive in.

One move, followed everywhere

rippling

·The budget model$14K moves from year one to year two
·Budget justificationboth year narratives re-render
·Project summarythe funding sentence updates
·Two sponsor formstotals agree to the dollar

The old way left the mix of stale and current that survived the final midnight. Reviewers noticed.

The current-and-pending is already true.

The document that torpedoes late submissions updates with every proposal and every award. When a sponsor asks just in time, the answer is a render rather than a scramble.

Current & pending support

syncing

The award that closed last monthremoved
The proposal submitted this weekadded
The PI's committed effortrecalculated

The document that torpedoes late submissions updates with every proposal, so the answer to a just-in-time request already exists.

The last 48 hours go to the science.

Arithmetic consistency is guaranteed by construction, so nobody spends deadline week proofreading numbers across nine files. The PI reads the science, and the officer reads the story.

What deadline week checks now

·Numbers across nine documentsagree by construction
·The scienceread by the PI
·The story the package tellsread by the officer

Nobody proofreads arithmetic across nine files at midnight. The last 48 hours go to the science.

One number moves. Every page follows.

A shifted budget line, a swapped co-investigator, a revised aim. Any of them touches half the package, and every one runs the same way.

  1. A budget line moves

    $14K shifts between years

  2. The source updates

    one fact changes in one place

  3. Nine documents re-render

    each one from the same source

  4. The diff shows what changed

    the officer sees it page by page

  5. The package stays consistent

    it holds to the dollar by construction

What changes, and how it runs.

Documents stop being copies

Each one renders from the source instead of chasing it.

Reviewers stop finding contradictions

The summary and the justification cannot disagree.

Deadline week reads for substance

The last 48 hours belong to the science.

The technical read

Connects read-only to your grants system, budget model, and document store to start

An officer reviews the diff on every change

Every action lands on an append-only log

SOC 2 Type IIFERPAGDPR

Runs alongside what you have. Nothing rips out.