Bring the framework’s knowledge into the application
Application work needs more than API names. Wildo packages the framework’s authoring knowledge and assurance definitions so the application’s tools can use the same contracts the framework defines.
The package brings references, methods and control expectations together. A generated reference explains the framework; evidence from the application must still demonstrate its own configuration and operation.
Example — Keep a coding agent and a reviewer on the same basis
After a framework update, regenerated knowledge carries the relevant source references and assurance basis into application tooling. Both can identify the version they are using instead of relying on remembered behavior.
For engineers
Use the framework generation command
From a configured Wildo development environment, wildo fwk generate-docs resolves the framework repository and calls FrameworkKnowledgeGenerationService.generate. It reports its output directory, extracted topics and registry files. The generator discovers source anchors and authored knowledge, renders references and packages playbooks and assurance bases.
Preserve the basis identity
This source excerpt shows assurance bases being materialized and registered. A duplicate identity is rejected rather than silently replacing the earlier definition.
const assuranceAuthorityBasisRegistryEntries: Record<string, AssuranceAuthorityBasisRegistryEntryShape> = {};
for (const basisFile of FrameworkKnowledgeGenerationService.discoverAuthoredAssuranceAuthorityBases(frameworkRoot)) {
const entry = FrameworkKnowledgeGenerationService.materializeAssuranceAuthorityBasis(
basisFile,
assuranceAuthorityBasesDirectory,
frameworkRoot,
generatedAt,
);
const identity = `${entry.ref}@${entry.version}`;
if (assuranceAuthorityBasisRegistryEntries[identity]) throw new Error(`Duplicate authored assurance-authority basis identity "${identity}".`);
assuranceAuthorityBasisRegistryEntries[identity] = entry;
}
The resulting payload includes the portable basis and its source mapping. Topic and source-tag registries point back to the extracted reference material; authored skills explain how an application uses it. The output is generated knowledge, so changes belong in the source or authored definition before regeneration.
Keep generated knowledge distinct from operational evidence
A source excerpt can establish an API contract. A packaged assurance basis can establish what an objective demands. Neither demonstrates that a deployed application performed the action successfully. Link operating claims to the appropriate event, execution or review record and its version. The separate knowledge audit checks package/reference coherence; it is not an application assurance assessment.