Publish the framework knowledge package
Framework contracts and their explanations need a delivery path. Wildo generates a knowledge package from its authored guidance and selected source contracts.
That publication supplies the skills and references installed into applications. It is separate from the documentation an application publishes for its own customers.
Example — Ship a revised configuration guide
A maintainer updates a configuration contract and its guide, generates the package and reviews its checks. Applications using that package can refresh their delivered guidance through the asset installer.
For engineers
Use the command in the correct workspace
The generation commands are for a configured framework checkout. The final command below runs separately in the consuming application:
# Framework workspace: publish generated knowledge output.
wildo fwk generate-docs
# Framework workspace: require a clean integrity report.
wildo fwk audit --strict
# Application workspace: deliver assets from its installed package.
wildo assets sync
The generator writes staged output, including compiled guidance and its manifest and registries. It validates that staged payload before replacing the published output. Application delivery then reads the installed package; generation alone does not update every application.
Know which document you are producing
| Surface | Audience and ownership |
|---|---|
| Framework-authored guide | Maintainers explain how to use Wildo |
| Extracted API reference | Selected framework contracts with package provenance |
| Generated knowledge package | Distributable output of the framework compiler |
| Installed application skill | Guidance loaded by the application’s agent host |
| Application documentation portal | Information for that application’s users and integrations |
Authored files remain the inputs. Edit the owning guide or source contract and regenerate rather than patching the published output as a second source of truth.
Read failures at the appropriate stage
A generation error concerns compilation or payload validation. An integrity finding concerns a supported source-to-guidance relationship. A delivery problem concerns the package and installed files. An instruction can also require a semantic correction even when those mechanical checks pass.
Review the generated reference and its installed consumer when changing a public contract. Run the example’s compiler or runtime checks where appropriate; successful knowledge publication is not a substitute for exercising the API it describes.