Dknowc Official Document Writer

Problem It Addresses

Formal official documents require stable structure, verifiable policy basis, accurate data, and strict formatting. Plain drafting can produce unsupported policy references, mixed-up sources, generic language, or inconsistent Word output.

How It Works

Dknowc Official Document Writer selects the minimum workflow for each task:
- Task routing: simple notices, rewrites, and polishing can proceed directly; reports, plans, speeches, and policy-based documents first confirm key details, outline, or search plan.
- Trusted search: when policy, data, or cases are needed, it presents a search plan for confirmation, then runs scripts/dkag_search.py; recalled materials are split into policy basis, data support, reference cases, and wording references.
- Generation and review: it drafts according to document standards, checks factual boundaries, tone, and official-document risks; formal tasks default to .docx, and red-header files are generated only on explicit request.
- Traceability delivery: when search is used, it also generates an HTML traceability report; the document body avoids inline citations or long links, while source jumps are centralized in the report.
- Local state: it can maintain a local knowledge base and writing preferences, both stored locally and not distributed in the public package.

Boundaries

It depends on python3, python-docx, and requests; an API key is required only when trusted search is actually needed. It does not replace trusted search with public web search, does not automatically generate PDFs, and does not infer the user's organization from examples. Formal Word files retain the AI-generation notice, while red-header files remove that notice to preserve standard layout.