- Open-core, agent-native product studio
- 5 projects generated from one shared source
- Readable by humans and agents alike
jami.studio
A coherent public surface for governed agent runtimes, trusted UI contracts, multi-agent coordination, temporal knowledge, and open agent society.
Every public route, project link, metadata field, sitemap entry, and AI-ingestion file is generated from shared source data.
About the studio
We build open foundations for agent-native products.
One studio, five surfaces.
This repository owns the public marketing hub, project pages, metadata, sitemap, robots policy, AI-readable files, and shared presentation foundations for the Studio project family.
Harness, Studio UI Registry, Orchestra, Intercal, and Collectiva are separate implementation surfaces. This site links to their routes, repositories, docs, APIs, and subdomains through centralized project metadata.
The site publishes compact and expanded AI source files so agents can resolve the product family, public routes, project summaries, and source boundaries from stable generated text.
Read the sourceWhat the studio ships
Four foundations, one shared contract
Each layer of the family owns one job; every layer shares the same governed source of truth.
Harness turns agent execution into a policy-gated, provider-flexible runtime contract.
View projectsThe UI Registry gives agents a tokenized vocabulary they can use without injecting runtime code.
View projectsOrchestra keeps work records, approvals, and squads separate from the core agent loop.
View projectsIntercal and Collectiva extend the family into provenance, temporal context, and open governance.
View projectsThe project family
Five projects, one source of truth.
Runtime, interface, coordination, knowledge, and society — the same shared records generate every page, link, and AI surface.
- Jami Agent HarnessA governed agent runtime and BYOK reference foundation.
- Studio UI RegistryA tokenized UI registry and trusted render contract.
- OrchestraA development and multi-agent coordination framework.
- IntercalA provenance-backed temporal knowledge substrate.
- CollectivaAn open agent society and governance layer.
Proof, not promises
Why the boundaries hold
Commitments distilled from the family's own design records — the closest honest thing to a testimonial.
Designed around one enforcement path instead of UI backdoors.
Separates source installation from runtime rendering.
Keeps the agent loop in Harness and orchestration in Orchestra.
Get in touch with the studio
One contract,
five open surfaces
Questions, integrations, or contributions — write to the studio, or start with the project family.
For agents and humans
Read the source, not a feed.
No newsroom here — the studio publishes stable machine-readable text instead. Resolve the whole family from these generated files.