Authentication and Credentials and Telemetry have separate security and privacy contracts.
Start with this project layout
Use the generated agent folder as the root for every path in the Harnest docs. This is the same default guided scaffold shown during initialization. Select a path to see what it owns and an example of its format. You only need the active root files and the capabilities your agent uses. Optional directories contain ignored_README.md guides by default and may be deleted. harnest init --example adds ignored code samples without replacing the default agent or storage code.
When a page titles a code block tools/lookup_order.py, create that path inside your project root. For discovered resources, the filename is also part of the contract:
Put reusable code in
lib/ and Pydantic contracts in models/. Those folders are import namespaces, not discovered capabilities: lib/storage.py imports as harnest.lib.storage, and models/orders.py imports as harnest.models.orders.
Discovery rules
harnest init creates the required root files. Use --example for opt-in templates in guide-only managed folders. Python templates stay named _example.py; skill, plugin, and eval templates use ignored native-format paths. Follow each sample’s activation instructions before renaming it to a public path.
Coding-agent guide
Install Harnest’s bundled project-editing guidance for a coding agent:--target or --project when auto-detection is wrong. This coding guide is separate from runtime Agent Skills.