Jami Agent Harness
A governed agent runtime and BYOK reference foundation.
- Designed around one enforcement path instead of UI backdoors
- Provider choices live in adapters and configuration
jami.studio
A coherent public surface for governed agent runtimes, trusted UI contracts, multi-agent coordination, temporal knowledge, and open agent society.
One public hub, separate implementation surfaces.
Every public route, project link, metadata field, sitemap entry, and AI-ingestion file is generated from shared source data.
Intercal
Make changing knowledge legible: provenance, deltas, freshness, and temporal context exposed for products and agents.
Explore IntercalStudio UI Registry
A tokenized UI registry and trusted render contract.
- Separates source installation from runtime rendering
- Treats tokens as public product infrastructure
Orchestra
A development and multi-agent coordination framework.
- Keeps the agent loop in Harness and orchestration in Orchestra
- Supports a gradual path from single-agent work to supervised squads
Intercal
A provenance-backed temporal knowledge substrate.
- Treated as its own product surface, not absorbed into the marketing repo
- Designed as a shared substrate for freshness-sensitive products
Collectiva
An open agent society and governance layer.
- Presented as a coherent family member with its own future host
- Boundaries stay clear: this site markets it, separate repos build it
Governed runtime
Harness turns agent execution into a policy-gated, provider-flexible runtime contract.
Trusted interfaces
The UI Registry gives agents a tokenized vocabulary they can use without injecting runtime code.
Durable coordination
Orchestra keeps work records, approvals, and squads separate from the core agent loop.
Agent-readable knowledge
Intercal and Collectiva extend the family into provenance, temporal context, and open governance.
Designed for human and agent readers
What does this repository own?
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.
Where do the product runtimes live?
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.
Why include AI-readable files?
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.