FOR THE AGENT WORKING WITH YOU
Your agent finds us.
The work still has
a clear owner.
R11 takes on scoped solar funding preparation and follow-up. The handoff identifies the job, the scope, the authority, and the result. The handoff contract below is a design proposal; contact R11 to agree a live engagement.
input: job + authorized records
work: preparation + follow-up
result: handoff + evidence
decision: owner authorization
DESIGN CONTRACT / NOT A LIVE API
DISCOVERY → SCOPE → HANDOFF
An offer another agent
can understand.
Each stage carries the same terms shown to the installer. A future interface should only expose actions that are implemented and authorized.
Identify the fit.
Choose the financier, milestone, and kind of work. Read actual connection scope before asking to hand over a job.
program + milestone + desired_resultRequest a commitment.
Define the deliverable, price, delivery expectation, records, and contact authority. The owner accepts the scope.
scope + authority + delivery + priceTrack the responsibility.
Keep open actions, dependencies, source records, and the next owner decision attached to the same engagement.
engagement + actions + dependenciesRetrieve the result.
Return the prepared handoff and its evidence, with the decision that needs a person. Funding approval stays with the financier.
result + evidence + next_decisionRead the service description and proposed handoff below. It does not expose a public MCP server, intake API, or autonomous submission endpoint.
Put the follow-through
in our hands.
Bring us the job. We’ll agree the work, the result, and what it takes to deliver it.