Connect a business workspace to governed AI.
StudioLens is a venture research and portfolio workspace. The founder’s contribution connects its company context and account permissions to Ascape, where governed agents and workflows can run.
- Project
- StudioLens integration
- Contribution
- Founder’s Ascape integration and access-control contributions to the existing StudioLens product.
- Current stage
- Implemented integration
The problem and the work.
People should not have to recreate company context in every tool, or gain access to another company simply by changing a link. The integration needs to carry the right identity, company and permissions between two products.
Founder’s Ascape integration and access-control contributions to the existing StudioLens product.
- Account handoffAn OpenID Connect sign-in flow with proof-key checks and signed identity assertions.
- Company contextCompany and membership mappings that preserve the authorized tenant, studio and company.
- Reliable synchronizationSigned events, delivery retries, reconciliation and a recorded integration contract.
- Agent and workflow accessA partner client for authorized catalogs, run results and scheduled automations.
How it was implemented.
Keep identity and company access together
The sign-in and company-context paths check the person and their membership before exposing the corresponding workspace. Device or connector credentials do not replace user authority.
Make delivery recoverable
An outbox records pending integration events. Retry rules and reconciliation support recovery when a receiving service is temporarily unavailable.
Check the boundary between products
Response validation, signed assertions and explicit contract versions give the two systems a shared shape. Tests exercise identity, company context and partner requests using fixtures.
From the need to the result.
- Sign inEstablish the current person through the account handoff.
- Resolve the companyCheck membership and map the permitted company context.
- Run governed workUse the authorized agent or workflow through the partner client.
- Return resultsValidate results and synchronize changes through recorded events.
What is implemented and checked.
Implemented integration
The integration is implemented in the local code. This review did not qualify a live partner deployment. The contribution described here is the integration and access-control work within StudioLens.
StudioLens integration verification notes
32 focused local checks passed on 15 October 2026: identity and event contracts, partner-client requests, and company-context authorization. Partner requests used mocked transport; company-context checks used an in-process test database.
These are local implementation checks. Production rollout and live services require their own acceptance checks.
Implementation reviewed .
Build around your business.
Useful for companies connecting an existing portal, research workspace or SaaS product to governed AI without losing account and company boundaries.