Documentation / public contracts
NEES developer documentation hub
Start with a bounded proof in the Dashboard, then integrate a registered supported action from your trusted backend. Public docs describe integration contracts, not private Core implementation.
Quickstart and setup
The website quickstart provides a six-step guided path: workspace → register action → resolve assessment → select integration → execute/report → test the boundary. The GitHub Developer Preview repo is the detailed source for version-matched public guidance.
SDK, assessment and integration
- Use nees-sdk 3.x RC from a trusted Python 3.11+ backend, not the legacy nees-core-sdk chat package.
- The Dashboard resolves existing version-bound assessment commitments; exports never confer authority.
- REST, Gateway, MCP and framework coverage depend on the specific connector and deployed contract.
Operations, errors and security
Before enabling real effects, test denied, timeout, stale-assessment, target-mismatch and uncertain-outcome paths, including any retry/idempotency behavior supported by your API revision.
Evidence and case studies
The Lab can demonstrate bounded synthetic governance, but it does not perform real account changes. Internal reference cases are illustrative of integration behavior, not independent security certification.