Before you begin
- The workflow begins by inventorying each draft.
- Placeholders and unsupported claims are removed before drafting.
- Drafting uses constrained MiniMax input only.
- An independent risk review checks for operational and jurisdiction risk.
- The shared renderer enforces the site's structural rules.
- Automated structural and link checks run on every output.
1. Inventory the draft
Each existing page is inspected before drafting. The inventory records routes, headings, substantive copy, links, imagery, placeholders and duplicated material so the rebuild begins from what is actually present.
The planned content schema is then compared with that inventory. Missing required fields cause validation to fail rather than being described as content that already existed.
- Record routes, headings, copy, links and imagery
- Separate substantive material from placeholders and duplicates
- Treat a missing required field as a validation failure
2. Flag placeholders and unsupported claims
The second pass separates real content from leftover scaffolding. Placeholder phrases and unsupported claims are removed before drafting starts.
Claims that name a specific law, authority, statistic, date, emergency action or equipment specification are set aside. Where a detail is jurisdiction-specific, the page is rewritten so it tells the reader which authority or qualified professional to ask, rather than guessing the answer.
- Placeholder phrases are deleted, not patched.
- Jurisdiction-specific details are redirected to named authorities.
- Universal requirements are not invented.
- Source-panel links are assigned from the page specification during candidate preparation
3. Draft with constrained input
Drafting is done from a short brief that lists only what site truth authorises. MiniMax is used purely as a constrained drafting input: it is given the page plan, the permitted scope and the implemented site truth, and it is asked to write within those bounds.
The model is not asked to invent links, projects, results, contacts, dates or qualifications, or to fill gaps with adjacent activities. Candidates are checked for consistency with the page plan and implemented site truth, and identified discrepancies must be corrected before acceptance.
- Inputs are limited to the page plan and site truth.
- External links are not invented.
- Personal or professional details are not inferred.
- Output is checked against the page plan before it is accepted.
4. Independent risk review
Once a draft is written, an independent risk review reads it for jurisdiction-specific and operational risk. The reviewer checks whether the page could still be read as a step-by-step for aiming, firing, loading, stalking, dispatch, butchery or injury response, and whether it suggests a universal rule where one does not exist.
This review is not legal sign-off. It is a focused check for the kinds of risk the build is designed to catch, and it cannot replace qualified expert review where one is genuinely required.
- Operational instruction is checked for.
- Jurisdiction-specific claims are re-checked.
- Universal rules are flagged.
- The limits of the review are recorded on the page itself.
5. Render and run automated checks
Approved candidates pass through the shared renderer. It supplies category, estimated reading time, updated date, contents, takeaways, related guides and an official-resource panel when a source is supplied. The updated date records a substantive revision, not legal or expert review.
Automated checks validate required structure, generated inventory, internal link targets, asset paths, source-link format and configured phrase lists. They do not fetch external pages or prove factual, legal or field accuracy. A failed check blocks the build until the candidate is corrected and the checks are rerun.
- The renderer enforces the shared page structure
- Internal links are checked against generated targets
- Supplied external sources are checked for valid HTTPS form, not live availability
- A failed check blocks the build until correction and recheck
The field standard
This workflow is one rebuild method applied to existing drafts. It does not prove legal, field or factual perfection, and it is not described as Edward's personal editorial process. Where a detail is jurisdiction-specific, readers are directed to ask the relevant authority or qualified professional. Recommendations are not legal mandates.