Platform module map

Account and entitlement

Registration creates the organization owner. Trial or verified payment creates the entitlement and credit pool. Provisioning advances through durable states rather than browser-side success messages.

Developer API

Organization tokens are scoped and shown once. APIs use stable errors, idempotency keys, audit correlation IDs, and asynchronous run identifiers.

Repositories and agents

One customer source repository maps to one logical agent. Local providers, managed ADK, and GCP BYOK are endpoints of that agent. One organization receives one private Dharma control repository with permanent agent branches and remediation branches.

Trajectories and traces

Endpoints emit provenance, tool, timing, model, failure, and evidence records. Local raw evidence stays encrypted unless organization policy authorizes bounded disclosure. Managed traces remain tenant-scoped.

Evaluation

Deterministic checks run first. Semantic judgment runs only when evidence, configuration, and billing gates permit it. Rubrics and contracts are versioned; hidden truth is never shown to the evaluated agent.

Failure Atlas

Failure families connect repeated findings to evidence lineage, affected endpoints, business consequence, recurrence, and remediation state.

Remediation and skills

Candidates move through GitHub review, held-out evaluation, regressions, signing, installation, matched rerun, and rollback. Every agent target is independently reversible.

Tasks and A2A

The broker can dispatch signed tasks or structured handoffs to authorized same-organization endpoints. Requests include expiry, authority, workspace, acceptance, budget, and task lease. There is no arbitrary cross-agent chat or unrestricted remote shell.

Organization control agent

The portal and CLI assistant provide a conversational interface to the same scoped APIs. Reads may run automatically. Paid or mutating actions require scopes and explicit approval.

Usage

Usage events record organization, agent, run, purpose, provider/model where applicable, tokens, runtime, tools, landed-cost inputs, rate-card version, billable credits, and settlement state. Customer views show consumed credits; internal cost and margin remain restricted.