Set up a document type
Answer these and ArcCompose can run your document. There is no code in this page and none comes out of it — what it produces is the same kind of description the built-in documents use, which the engine reads directly.
Shared document types
In the database, so everyone sees the same list. New document opens ArcCompose on that type; Edit brings it back into the form below, and saving it again publishes a new revision. Old revisions are kept, so a document can always be reopened against the shape it was drafted under.
Only in this browser
Drafts that have not been published. They are on this machine and nobody else can see them.
The document
What it is called and what it is written under. The authority shows in the header, so whoever fills one in always knows which rule book they are in.
Opening questions
The short intake, before anything is drafted. Ask only what the requiring activity always knows and what changes the document. Everything else is better left to the decisions step, where the guidance is — a question nobody can answer yet stalls them at the door.
The document, section by section
This is the outline. Sections print in the order you put them, and so does everything inside one. Three things can go in a section, and the difference between them matters:
- Decision — a judgment the tool will not make on their behalf. Guidance, a cite, approved wordings, and nothing exports until it is settled. This is where the expertise goes.
- Fact — looked up, not decided. A contract number, an agency. Prints as typed and carries no guidance.
- Paragraph — prose the model writes for that section.
The thing there can be many of
Most documents have one: factors, findings, objectives, line items. Leave the name blank if yours does not.
Decisions on each one. Same as above, but asked once per finding.
Checks
Contradictions worth catching — two answers that cannot both be true. These are warnings, not blocks: they appear on the review step next to everything else the checker found.
Use it
Publish to the team writes it to the database as a new revision, where everyone sees it. Keep in this browser saves it on this machine only. Save and make a document keeps it and then opens ArcCompose on it so you can fill one in.
Publishing does not mean approved. A document type is a sandbox type until someone who knows the subject has read every word of it, and ArcCompose prints a warning over every document made from one either way.
Show what this produces
This is the whole document definition. The built-in ones look exactly like this — the only difference is that they live in the repository instead of your browser.