Wiki:HTML Packs
An HTML pack is a deployable analytical tool published through this wiki. It carries one single-file HTML tool that opens from a local disk with no server and no network, the data contract the tool reads, an assistant kit (an instruction block and context files for a Claude project) that collects the problem statement and generates the tool's shape file, and this page's description of the problem archetype the tool solves.
HTML packs are the published form of the shape file bridge: a tool is built outside a data boundary against a de-identified shape file, then carried back inside by email and run on the real data, which never leaves. They differ from packs, which carry instructions and reference material for a Claude project.
How to use an HTML pack
- Open the pack page and read When to use it to confirm the problem archetype fits
- Download the tool from the address on the pack page and save it locally; if it arrived by email with a neutral extension, rename it to
.html - Open it in a browser. It runs entirely on your machine; nothing you load into it is sent anywhere
- On the Data tab, paste or upload your file against the contract, map the columns once, and read the validator findings
- Optional: create a Claude project, paste Block 1 into its instructions and upload the remaining blocks as knowledge, so the next problem statement and shape file are generated rather than typed
A tool shows its version in the footer. A newer version is a new file; the pack page's change history says what changed.
Inventory
| ID | HTML pack | Domain | Contract | Tool | Status |
|---|---|---|---|---|---|
HP-WFM-001 |
Problem Statement Intake | WFM | wfm.shape.problem |
— | in design |
HP-WFM-002 |
Staffing Outlook | WFM | wfm.shape.staffing-outlook |
— | tool built, pack pending |
Domains follow the pack domains: WFM · ANL · OPS · RES · CNT · DEV · META.
Structure of an HTML pack page
- Infobox: ID, domain, version, tool address, contract and version, source articles
- When to use it, and when not to
- What it shows: the tabs or panels, which numbers are headline, and the grade each carries
- The contract: columns, meanings, declared conventions (handle-time basis, gross or net supply, go-live counting) and validator rules
- How to deploy: the five steps above, specific to the tool
- Block 1: the project instruction block for the assistant kit
- Blocks 2–n: context files, each headed with the filename to save it as
- Usage notes: confidentiality (what the tool never does), transport, versioning
- Change history and See also
What an HTML pack never contains
No client, employer, vendor or person names, including in sample data, screenshots and file names. No real figures from any one operation: sample data is synthetic and says so. No network calls, external scripts, fonts or analytics. No credentials. Every pack is checked against a code-name list before it is published, and the tool's provenance block asserts the same of every shape file it writes.
Adding an HTML pack
An HTML pack is justified when a view is built by hand more than once and its data can be described by a contract. Write the contract first, then the tool against synthetic data in that contract, then the page. Tools are built from a shared template so that every pack reads and writes the same shape-file envelope; a pack that needs a new contract adds it rather than inventing a second envelope. The tool is hosted at an address under wfmlabs.com named on the pack page, and that address serves the exact file the page describes.
See also
- The Shape File Bridge, the pattern these packs implement
- Wiki:Packs, project packs; Wiki:Skills, installable skills
- Wiki:Library, the hub for all deployable material
