What becomes the locked base?

Your own proven document becomes the locked base, while current facts stay separate as named fill-in fields.

What does Document Factory produce?

A print-ready document in your own format, its source references, the check results, the verification receipt, and a running release log.

When does Document Factory stop?

It stops and asks rather than inventing a value.

Kit 03 · Document production

Document Factory

A controlled drafting lane built from the documents you already trust, with every draft held until you verify it.

Authority rule
The document owner supplies the proven document, verifies the draft against its sources, and clicks to release it. The click is logged.

Field sheet

Separate source, instruction, draft, and approval.

Document Factory prevents last month’s file from quietly becoming this month’s truth. Your own proven document becomes the locked base, current facts stay separate as named fill-in fields, and every section of the draft points back to the wording it came from, by paragraph and source document.

Worked exampleIllustrative workflow

Current dragA recurring engagement letter starts from whichever old file is easiest to find.

Control addedLock the firm's own proven letter as the base, name the variable facts as fields, and record what that class of document must carry.

System preparesPrepare a draft, run the mechanical checks, and hold the file: nothing saves or downloads until it is verified.

Human releaseThe responsible person reads it, ticks the attestation, and releases it. The date, version, sources, and any accepted flags are recorded.

Processing boundary

Local by default. External by decision.

The operating record remains useful without a connected service. External assistance is limited to approved context and explicit tasks.

Runs locally

Template library
Matter or job fact sheet
Draft and revision history
Source-to-output checklist
Release record

May run externally

Organizing approved text
Comparing a draft to a base document
Suggesting wording for human review

Never automatic: writing your base wording for you, choosing legal or commercial terms, inventing a missing fact or writing "TBD" into a customer-facing document, or releasing the file.

Ownership and hand-off

The workflow remains useful when the tool changes.

Client keeps the sourceThe wording is theirs; the kit never sells them its own prose back.
Decisions remain visibleFacts and drafting instructions remain separate.
Review stays attributableEach released version records who accepted it, when, and against which sources.
Tools remain replaceableA replacement tool can consume the same source packet.

Human review checklist

Before the work moves.

Is the base document explicitly approved?
Are current facts separated from drafting instructions?
Can each material statement be traced back to the source paragraph it came from?
Are prohibited changes and mandatory clauses visible?
Did the responsible person approve the released version?

See the demonstrated source-aware document workflow record for the implementation boundary and operating artifacts.

Discuss this workflow Back to all kits