Give each method the information it needs
Good instructions need the right information behind them. A method can request computed project facts and reference material alongside the product artifacts it reads.
Wildo makes those requests explicit. A method that names a supported context source in its instructions must also declare it, keeping the written guidance connected to the information supplied for the work.
Example — Write statements from the product's actual declarations
A document-facts method requests compliance facts and the facts that governed documents need. It can then connect the product’s declared behavior to the statements those documents must support.
For engineers
Select computed context deliberately
The document-facts method contains this selected configuration:
method: {
contextSources: [
MetaWorkflow_ContextSource.COMPLIANCE_PRIMARY_FACTS,
MetaWorkflow_ContextSource.DOCUMENT_FACT_OBLIGATIONS,
],
skillRefs: ['journey-status'],
},
Its method prose includes the following literal placeholder:
{{CONTEXT_SOURCE:compliance_primary_facts}}
During framework-knowledge compilation, expandContextSourcePlaceholders checks the named member and the method’s own declaration before replacing a supported placeholder. Unknown members and undeclared sources are refused. The catalog audit reports corresponding mismatches.
Keep inputs and context distinct
Artifact inputs select specification families. contextSources requests computed sections or catalogs, such as application declarations and document obligations. The source vocabulary carries the meaning of each supported section, and the companion composes the sections requested by the method.
| Authoring choice | What to review |
|---|---|
| Required artifact input | Does the method need the product’s authored information? |
| Computed context source | Does it need facts or reference material derived elsewhere? |
| Skill reference | Which instructions explain how to perform this work? |
| Source placeholder | Does prose refer to the same source the method declares? |
Adapt context without changing the method permanently
For supported generation runs, briefAdequacyGate optionally checks whether the composed brief is sufficient. An insufficient result can add permitted sources for that run and trigger one recomposition. briefAdequacyExcludedSources keeps deliberately excluded sections out of this widening.
The widening preserves declared sources. If the auxiliary check fails, generation retains the static brief. This check helps context selection; it does not establish that every source is complete or that the generated answer used it correctly. Review evidence in the resulting artifact as well as the source declaration.