Draft 0.1 · open specification
Example files and schemas
Real packages, not illustrations. Each one is a valid ZIP container with a mimetype entry, a manifest carrying SHA-256 integrity for every file, and a design document. Open them with any unzip tool and read the JSON.
Example packages
Start with the designed and as-built pair. Read one, then the other, and the round-trip model explains itself.
| Package | What it demonstrates | Size | Download |
|---|---|---|---|
| Muscle strip, as designed muscle-strip-designed.wwd | The minimum viable package: mimetype, manifest, design. A specification before anything has been built. | 2.3 KB | Download |
| Muscle strip, as built muscle-strip-asbuilt.wwd | The same component after manufacture, carrying results and a measured twitch trace. This is the round trip the format exists for. | 3.6 KB | Download |
| Muscle strip, stiffer anchors muscle-strip-highstiff.wwd | A variant differing only in anchor stiffness. Useful for seeing what a design revision looks like as a diff. | 3.4 KB | Download |
| Graded strip, field-valued stiffness graded-strip.wwd | Stiffness supplied as a spatial field rather than a constant, with the field payload delegated to a VTU file. The scalar-or-field upgrade path in practice. | 2.9 KB | Download |
| Bioprinted strip with process data bioprinted-strip.wwd | Carries a 3MF print job alongside the design, showing how a manufacturing process attaches to a component. | 3.4 KB | Download |
| Neural tile, as built neurontile-asbuilt.wwd | A neural culture component with electrophysiology results. A different component class through the same model. | 3.7 KB | Download |
A .wwd file is an ordinary ZIP archive. On any machine:
unzip -l muscle-strip-designed.wwd lists it,
and unzip -p muscle-strip-designed.wwd wwd/design.json prints the design.
To check a package you have made, use the
browser validator — it runs locally and uploads nothing.
JSON Schemas
Normative for the 0.1 draft. A package that does not validate against these is not a WWD package.
| Schema | Covers | Size | Download |
|---|---|---|---|
| Container manifest manifest.schema.json | Package contents, media types, byte counts and SHA-256 integrity for every file in the archive. | 4.4 KB | Download |
| Design design.schema.json | Components, regions, properties, fields, interfaces and requirements. The substance of the format. | 31.7 KB | Download |
| Results results.schema.json | As-built measurements bound back to the requirements they answer. | 8.2 KB | Download |
The draft is open for correction
Version 0.1 has one implementer, which is us. That is the honest number, and it is the reason the specification is published in draft rather than announced as finished. If a package cannot express something your work requires, that is the most useful thing you can tell us.