BUILD WITH US / DESIGN PARTNER PREVIEW
Start with one real workflow.
Three useful starting points for a design partner engagement.
A research tool that keeps its work
An agent collects structured notes and builds a digest tool. Later sessions improve ranking or formatting while keeping the research history. This is closest to the current fixture.
First boundary: one tenant, text records, no external network access from generated code.
An internal utility that evolves
A small team needs a recurring report or a specialized data transformation. Instead of regenerating a script each time, preserve the tool, version its behavior, and explicitly grant the input it can use.
First boundary: one approved input source and one output, with integrations mediated by the trusted host.
A real environment for agent feedback
A developer wants an agent to test a bounded change against actual infrastructure, observe the result, and clean up afterward. The embedded infrastructure-engine experiment is a starting point.
First boundary: one resource class, a fixed account and budget, and a recorded cleanup policy. Recoverable orchestration must be built before relying on unattended runs.
What makes a good first project
- You can describe the task and recognize a correct output.
- You know which data it should and should not access.
- It can begin with a small, reversible resource set.
- You can test with synthetic or non-sensitive data first.
- The tool will be useful again after its first execution.