How it works
Robin learns the context before it builds the plan.
Robin starts from a natural-language outcome, investigates authorized organization knowledge and connected systems, builds a grounded project Wiki and roadmap, then continues through chat and polling-based updates.
- 01Connect
Authorized sources
Bounded preflight - 02Understand
Context and relationships
Relationships mapped - 03Detect
Risk and missing evidence
Caveats visible - 04Act
A governed next move
Human review retained
Context first, then execution
Robin starts from a natural-language outcome, investigates authorized organization knowledge and connected systems, builds a grounded project Wiki and roadmap, then continues through the same project conversation and polling-based updates.
Describe the outcome
Before project creation, Robin runs a read-only preflight. It either proceeds with the supplied outcome or asks one bounded set of exactly three focused questions. This is not a multi-step setup wizard or an interview that interrupts durable setup midway.
Connect and investigate
The model chooses relevant searches and exact reads across authorized provider adapters, the organization Wiki and People. Access remains constrained by tenant, active connection, provider scopes and setup policy, and Robin shows caveats when a source is unavailable or incomplete.
Build durable execution artifacts
Robin creates a project Wiki and a readable roadmap with owners, dates, dependencies, success evidence and grounding. A verified owner is assigned only when evidence supports the choice; credible candidates trigger user confirmation; no suitable candidate leaves ownership explicitly unresolved.
An empty directory or honest no-match outcome does not erase the work. All three ownership outcomes preserve a readable roadmap and Robin never silently skips discovery.
Continue in the same project conversation
Setup transitions into ordinary project chat. Robin can refresh project context, read sources and people, answer questions and propose roadmap revisions. Accepted roadmap history is versioned, and proposed changes are not silent overwrites.
When durable source history exists, the original request survives refresh and re-authentication. Ownership questions, choices and accepted answers remain part of project history rather than disappearing after application.
Monitor material change
Robin periodically reviews active projects using read-only tools, validates material changes and publishes evidence-backed updates to the Updates and project surfaces. A user explicitly sends an update into chat when they want to discuss it.
Current proactive review is polling-based. It is not presented as instant or as a promise that every provider supplies the same freshness.
Review consequential action
Robin-owned knowledge and roadmap changes follow their applicable version and review semantics. Meaningful external provider writes remain limited to supported action types and require the applicable human-approved proposal and worker reauthorization.
Inspect the connected boundary
Continue with the current integration families and their provider-specific limits, explore workflows suited to this context-first mechanism, or review the security model that governs identity, tenant scope and consequential action.