A shared studio / Your preferred LLM

Continue the work,
with your tools.

Add https://ids.hereandmore.com/mcp as a remote MCP server. The connector uses Streamable HTTP and supports OAuth with PKCE. Each call checks your current identity and repository permissions.

Connect

In Dialog, open Settings → Devices → API keys and create a named key for your own use.
In your LLM client, add the studio connector address. If it supports OAuth, finish the consent page with your Dialog key. If it supports custom headers, use Authorization: Bearer YOUR_DIALOG_KEY.
Ask your model to call studio_whoami and studio_projects. Follow pagination to see all your projects.

Never put a live credential in a repository, shared prompt, screenshot or changelog. Revoke the key in Dialog to end its access. OAuth carries an encrypted copy of the key on the studio server; a direct bearer connection stores no copy there.

Add a frontend version

Use your normal Git workflow to save your version in a repository you contribute to on Everything. Then ask your LLM:

Register my frontend with studio_submit_version.
Project: owner/repository
Revision: the full 40-character Git commit
Entry: the frontend entry file
Title: a short name for this version
Summary: what I changed and why
Parent: the studio version I continued, if any
Tool and model: what I actually used
Request ID: a new unique ID, reused for an identical retry

The studio confirms that revision and entry file under your identity, then records a version and its contribution. Source remains in its repository. Uploaded code is never executed by the studio.

Continue through the studio

studio_history, studio_my_activity, studio_inspect_version — revisit work, personal contributions and results.
studio_map_frontend — connect a UI element to a HERE ontology entity, contract, operation, authority and validation plan.
studio_record_evidence — attach a generated concept, photograph, measurement or test report with a fingerprint and limitations.
studio_review — record design, ontology, security, stability or physical review findings.
studio_request_release — propose an exact target, version, checks and rollback plan for Universe.
studio_release_gate — operators check that an approval still matches the revision, target and current review.
studio_record_deployment — attach an operator’s deployment and postcheck receipt under that approval.

Files and patterns

studio_file_tree walks the files at an exact version, preserving object IDs and pagination. studio_register_pattern records an algorithm or pattern's source, inputs, outputs, constraints and validation plan. studio_patterns retrieves those contracts. Each remains a proposal tied to its source; none runs automatically.

Who decides, and what is proven

Universe approves through a recent HERE session with two-factor assurance. An LLM connector cannot approve a release. Approvals expire after 24 hours, can be revoked, and become invalid when the version’s mapping, review or release request changes.

The connector does not run code, deploy services or manufacture objects. Operators must integrate the release gate into each project’s deploy procedure. A recorded deployment is an attributed operator report; independent checks and photographs remain separate evidence.

Current projects come from Everything repository memberships. Tool history covers work explicitly recorded through IDS. Historical work in external tools is not silently invented or imported.

Physical creation

Keep the source photograph or measurement, its SHA-256, capture time with timezone, location or reference frame, units, uncertainty and limits. A generated image remains a concept. An uploaded photograph remains submitted evidence until its relationship to the built object and measured constraints has been reviewed.

Read the IDS philosophy ↗