SWMS Builder

Public showcase for a controlled Safe Work Method Statement (SWMS) builder workflow.

This repository explains the shape of a private production system that helps prepare Australian construction SWMS documents through deterministic generation, validation, and agent-assisted review gates. It is intentionally a showcase, not a release of the production codebase.

Live links:

• GitHub repository: https://github.com/mcxl/swms-builder
• GitHub Pages: https://mcxl.github.io/swms-builder/

What It Does

SWMS Builder turns verified project inputs into structured SWMS packages. The private implementation is designed around a controlled document pipeline:

1. Capture job-specific intake and source evidence.
2. Classify confirmed, conditional, and not-triggered high-risk construction work (HRCW).
3. Generate a structured SWMS document from a controlled template.
4. Post-process the document for file integrity.
5. Validate required fields, risk codes, legal basis metadata, placeholders, and workflow gates.
6. Prepare an agent review packet.
7. Run read-only verification and WHS review gates.
8. Release only after deterministic checks and human acceptance.

Who It Is For

This project is for WHS consultants, construction compliance teams, subcontractor administrators, and agent-workflow designers who need a reliable way to keep SWMS documents specific, auditable, and resistant to uncontrolled AI drafting.

Why It Exists

SWMS drafting often fails in predictable ways: copied client details, generic task rows, missing hold points, over-called HRCW triggers, inconsistent risk codes, or untracked assumptions. The builder workflow exists to reduce those failures by separating:

• confirmed project facts from uncertainty;
• deterministic document generation from human judgement;
• source evidence from draft wording;
• read-only review from content mutation;
• private client records from public examples.

Public Scope

Included here:

• public-facing overview;
• architecture notes;
• synthetic demo scenario;
• static GitHub Pages site;
• security and privacy boundaries;
• synthetic SVG workflow diagrams, including the anti-hallucination and anti-slop control loop.

Deliberately excluded:

• production source code;
• client/job folders;
• generated DOCX, PDF, XLSX, CSV, and report outputs;
• photos, source PDFs, logs, data stores, deployment files, and secrets;
• real names, site addresses, phone numbers, emails, Supabase details, service keys, or API keys;
• private git history from the original workspace.

Agent And Tool Framing

The workflow treats agents as controlled assistants, not as uncontrolled authors. Agents may help inspect source material, prepare review packets, and run read-only review gates. The authoritative path remains the controlled generator, post-processor, validator, and human release decision.

The anti-slop principle is simple: the model can suggest, but the workflow must verify. Unsupported claims are quarantined as unknowns or sent back to intake; they do not move directly into issue-ready content.

Current Status

Status: public showcase.

This repository is suitable for explaining the project and linking from a portfolio or project page. It is not a legal template, production SWMS generator, or complete application release.

Demo

Open index.html locally or visit the GitHub Pages site once published.

Visuals:

• Workflow diagram
• Anti-hallucination / anti-slop loop

Read more:

• Architecture
• Demo Scenario
• Reusable Public Showcase Repo Prompt
• Security Policy