Documentation
Documentation for setup, validation, and API review
Move from quick start to technical review without bouncing between marketing pages, docs, and repository notes.
Start paths
Pick the first documentation surface that matches the question
Start with the most relevant guide instead of forcing every reader through the full docs tree.
Start here
Quick Start a Valdrics Workspace
The fastest path from an empty workspace to a first working Valdrics setup.
Open guideValidate
Technical Validation
Capability and architecture material for teams doing technical review.
Open guideIntegrate
API Reference
Endpoint groups and request examples for product and platform integrations.
Open API DocsCore guides
Use the core guides for the operating loop
These are the guides most teams need after quick start: first connection, owner routing, and decision record handling.
Documentation
Connect the First Provider
Use the first provider connection to prove signal quality, review access posture, and establish the operating context for downstream decisions.
Confirm the access model before enabling broad coverage
Validate that spend signals map to a real owner queue
Check that approval and export records are retained correctly
Documentation
Owner Routing and Approval Path
Make every material spend issue land with a named owner, clear approval context, and a reviewable next action.
The issue lands with a named decision owner
Checks stay attached before the conversation starts
Approvals are explicit instead of implied in chat threads
Documentation
Decision History and Export Records
Keep a durable record of what changed, who approved it, and what outcome was captured after action.
Decision context survives handoff
Outcome proof is linked to the original issue
Export-ready records reduce diligence friction
Repository docs
Repository docs and adjacent surfaces
Use GitHub for full runbooks and implementation notes. Use `proof` and `resources` for evaluation and rollout conversations.