Teach the framework through its contracts and methods
An agent working in an application needs a usable account of the framework: what it provides, how to extend it and which connections a change affects. That guidance should work without requiring a framework checkout.
The problem it answers
A copied API example can outlive the contract it describes. A correct API reference can also leave the reader unsure how to use it across an application. The contract and the method answer different questions; useful guidance needs both.
Delivery matters too. An updated guide helps only after the application receives it and its agent host loads it. Source linkage, publication, installation and use are separate steps in keeping that guidance useful.
What it rules in, and what it rules out
- Extract selected public contracts through named source topics, with their package origin.
- Author the decisions, workflows and explanations around those contracts.
- Keep detailed references available on demand and reserve standing guidance for broadly relevant conventions.
- Obtain application-specific facts from the project and its context tools.
- Check reference integrity, example validity and installed loading with the evidence appropriate to each.
A named source excerpt reduces duplicated declarations. It does not eliminate the need to review explanations or verify a resulting application change.
What it means for someone building with Wildo
Start from the guide for the change, then inspect the application’s own declarations and available context. Use the delivered contract for the installed version, implement the product-specific behavior and verify the affected interaction.
When a reference looks old, follow its delivery chain before changing correct application code. A source edit needs generation and installation to reach an existing guide; context queries may also reflect compiled application output rather than an uncompiled edit.
For engineers
Where it lives in the framework
Framework maintainers author skills, references, partials, rules and methods. The knowledge generator resolves the source topics and compiles the delivery payload. Application builders receive that payload through their installed framework-knowledge package and wildo assets sync.
The integrity audit checks supported relationships between topics, references, skills and methods. Example checks keep samples in compiler coverage and connect executable examples to tests. Running those tests remains a separate verification step.
Standing rules are connected through the application’s managed guidance imports. The agent host must support and load that entry point. Project-specific instructions belong outside framework-managed files.