AI company blueprints · harness-powered workflows

Create any company blueprint with AI. Run every workflow with AI.

Start with templates, skills, agents, and Jentrix Foundry primitives, or let AI assemble the blueprint with you. Import the versioned blueprint to generate its workspaces, policies, roles, and harness-powered workflows, then operate and improve them with people and agents.

AI-assisted blueprint buildertemplates · skills · agentsharness-powered workflowsportable · shareable

Create a blueprint See the blueprint model

01 / Blueprint product

Blueprints turn company design into runnable operations

Use templates, skills, connectors, agents, and operating patterns as composable building blocks. AI helps design and validate the blueprint; Jentrix Foundry imports it, generates the working environment, and runs its workflows on the governed Agentic OS foundation.

Blueprint

Any company, one runnable definition

Structure, workspaces, roles, processes, policies, agents, connector requirements, dashboards, metrics, and setup questions live in one versioned blueprint.

Building blocks

Compose with templates, skills, and agents

Start from proven components or ask AI to assemble and adapt them. Each dependency stays explicit, versioned, testable, and replaceable.

Harness

Blueprint processes become executable

Import a blueprint to generate its workspaces and turn each process into a governed, AI-harness-powered workflow with evidence, gates, retries, and recovery.

Runtime

One operations core

The UI, automations, and a 242-tool MCP server share the same authorization, activity, notifications, realtime, and conflict-recovery contracts.

Portability

Configuration travels, authority does not

Blueprints carry operating structure and requirements, never secrets, credentials, live company data, tenant identity, or legal authority.

Lifecycle

Install, upgrade, learn

Preview generated workspaces, bind local identities and connectors, pin versions, migrate safely, roll back, detect drift, and feed proven improvements into the next version.

02 / Agentic OS

The governed runtime beneath every blueprint

Agentic OS remains the architecture inside Jentrix Foundry. It briefs agents, checks plans, meters credentials, records evidence, and routes genuine exceptions to people. Blueprints describe the company; this layer runs it safely.

03 / Reference company

The software company is the first blueprint, not a demo

Software delivery is already the deepest operating loop in Jentrix Foundry. The next step is to complete the company around it, run every process on real work, and package the proven configuration instead of inventing a generic template in isolation.

deliverypr.openedchecksreviewmerge gatedeploydeploy gaterelease

harnessspecplanstagereviewfixvalidatecommit gate

The factory already works

Specs, work orders, harness stages, pull requests, CI runs, deployments, releases, and incidents form one evidence-backed delivery graph.

Complete the company around it

Product, customer, finance, legal, people, reliability, security, data, and cost loops become governed processes on the same runtime.

Package only what proves useful

Successful operating structure, policies, roles, workflows, skills, connector requirements, dashboards, and metrics become the first Software Company Blueprint.

Software Delivery OS Harness Automation

04 / Blueprint lifecycle

Create, import, operate, improve

A blueprint is not a folder of prompts. AI composes it from Jentrix Foundry primitives, templates, skills, and agents into a signed, versioned company definition: structure, workspaces, roles, processes, policies, connector requirements, dashboards, metrics, and configuration questions.

Installation binds local people, identities, systems, and authority. Secrets, business records, credentials, and legal permissions never travel with the blueprint.

M14
Complete the governed foundation
01
Skills, memory, connectors, dynamic discovery, async work, and human input become verified references that later blueprints can depend on.
M15
Build the runtime and reference company
02
Define the blueprint manifest, general workflow engine, installer, versioning, upgrades, rollback, and workspace generation. Run the complete software company on it.
M16
Turn proof into a blueprint
03
An agent interviews the operator, configures and validates the operating model, previews installation, and produces software company, agency, support, sales, and back-office packs.
M17
Distribute and instantiate safely
04
A private-first registry, marketplace, enterprise tenancy, SSO, SCIM, quotas, billing, audit, compatibility checks, and rollback make reuse governable.

05 / Connect

Use Jentrix Foundry through MCP or the CLI

The current operating foundation is served from /api/mcp over Streamable HTTP with bearer authentication and structured errors. The same surface will power blueprint authoring, installation, operation, and evidence collection.

01Mint a token. Sign in and create a personal access token: pick read / write / admin scopes, pin it to one workspace, give it a name and an emoji.
02Add the server. Point any MCP client at /api/mcp over Streamable HTTP with the token as a bearer. Third-party clients can use OAuth 2.1 instead.
03Watch it work. Every agent action lands in the same activity feed as your team's, badged with the token's identity.

Read the platform reference

or use the clidocs →

# npm install -g @jentrix/cli
# or: brew install jentrix-au/tap/jentrix

jentrix login          # OAuth, or export STACKS_TOKEN=tm_…
jentrix whoami
jentrix task list --board eng --json \
  | jq -r '.tasks[].key'

# any of the 242 tools, by name
jentrix tool get_board_snapshot \
  --args '{"boardId":"board_1"}' --json

Every MCP tool becomes a shell command with the same scopes, idempotency, and attribution.