Glossary
Read this once and bookmark it. Every Claresia doc assumes these definitions.
Adaptive Card
Section titled “Adaptive Card”A JSON UI primitive shared by Microsoft Teams, Outlook, Webex, and others. Claresia wraps every skill response in an Adaptive Card so the rendering is consistent across surfaces and the footer (“Claresia · skill name · cost · latency” + “View record” link) stays branded.
Agent Operator
Section titled “Agent Operator”The third level of the Maturity Engine ladder. An Agent Operator orchestrates multiple skills + agents to produce work that previously required a team. Productivity multiplier vs Baseline: 2.55×. Cycle time: 0.31×.
AI-Adopted Operator
Section titled “AI-Adopted Operator”The middle level of the Maturity Engine ladder. An AI-Adopted Operator uses AI daily for ≥5 work artifacts per week. Productivity multiplier vs Baseline: 1.45×. Cycle time: 0.62×.
Archetype
Section titled “Archetype”A canonical role definition. Claresia ships 14 archetypes in the SaaS bundle (cc-051) and 14 archetypes in the manufacturing bundle (cc-051 + cc-057 extension): AE, PM, Marketing Manager, FP&A, Engineering Lead, plus manufacturing-specific roles like Firmware Engineer, 3D Product Manager, Production Planner, Talent Maker, etc. Each archetype has a RoleRuntimeSpec defining cadence, artifacts, KPIs, decisions, and SOPs.
Archetype Bundle
Section titled “Archetype Bundle”The runnable contract library/archetype_bundle.json produced by cc-051 that
holds N archetypes’ RoleRuntimeSpecs. The Synthetic Twin (cc-052) consumes a
bundle to drive the simulator.
Archetype Coverage Engine
Section titled “Archetype Coverage Engine”Phase-0 instrument (cc-052 M5) that scores how well a prospect’s DNA fits
Claresia’s existing archetype library. Output: coverage_report with nearest
archetype, secondary archetype if blend_margin ≤ 0.08, and gaps.
Baseline
Section titled “Baseline”The first level of the Maturity Engine ladder. Productivity multiplier: 1.0×. Cycle time: 1.0×. SaaS spend index: 1.0×.
BYOC — Bring Your Own Cloud
Section titled “BYOC — Bring Your Own Cloud”Mode C deployment topology where the Hub data plane lives in the customer’s AWS / Azure / GCP account and only telemetry envelopes (no payloads) reach Claresia Cloud.
Claresia Cloud
Section titled “Claresia Cloud”The Claresia control plane, deployed across eu-south-1 and eu-central-1
active-active. Hosts Identity, Distribution Plane, Telemetry, Command Center,
Onboarding Portal, billing, and (in Modes A and B) the Hub data plane.
CMEK — Customer-Managed Encryption Key
Section titled “CMEK — Customer-Managed Encryption Key”In Modes B and C, the Hub Postgres uses a per-tenant KMS-managed encryption key that the customer can rotate at any time. Claresia operates the key ring under a Customer Lockbox contract.
Command Center
Section titled “Command Center”The IT-admin pane of glass at app.claresia.com/{tenant_slug}. Manages tenants,
RBAC, skill entitlements, connectors, audit log, billing.
Cowork
Section titled “Cowork”A pre-bundled pack of skills for one archetype. Example: the
coworks/account-executive pack ships ~5 skills (pipeline-hygiene,
deal-summary, competitive-battlecard, discovery-call-prep,
proposal-outline). Claresia ships 83 coworks.
DeepLens
Section titled “DeepLens”External brand name for the Claresia tool that transforms systems — SaaS
rationalization, function consolidation, cost-out via the Synthetic Twin.
Internal codename: SaaS Optimizer (roadmap ID cc-022).
Dependency Graph
Section titled “Dependency Graph”cc-051 M4 output. A directed graph showing which archetype produces an artifact
that another archetype consumes. Cycles are real org behaviour (e.g.,
pm ↔ eng_lead PRD/release-notes loop) and are surfaced in reports.
Distribution Plane
Section titled “Distribution Plane”Layer 3 of the architecture. Per-LLM admin-API publishers that push your tenant’s skill catalog into Claude Enterprise (cc-063), Microsoft Copilot (cc-065), ChatGPT Enterprise (cc-070), and Slack (cc-071).
DNA Archetype
Section titled “DNA Archetype”A 10-dimensional feature vector describing a company. Used by the Synthetic Twin DNA Library to instantiate a stochastic communication + artifact overlay for a prospect.
fn_telemetry_event
Section titled “fn_telemetry_event”The canonical telemetry record schema. Shape: {skill_id, ts, success, latency_ms, tokens_in, tokens_out, cost_usd_estimate, ...envelope}. In Modes
A/B the full payload is also captured; in Mode C only the envelope.
Governance Event
Section titled “Governance Event”One of the six Hub record types. Emitted on every privileged action (admin login, RBAC change, skill entitlement change, tenant config change, deployment mode upgrade).
Hero Scene
Section titled “Hero Scene”A high-salience event cluster surfaced by the Synthetic Twin’s Hero Scene
Director (cc-052 M4). Used to render the most narratively compelling moments in
a prospect dashboard. Top-K selection over score_scene_candidate with
provenance.
The canonical org-memory store. Six record types: output, decision,
governance_event, artifact, employee_profile, telemetry_event. SHA-256
provenance over canonical JSON. See Hub schema.
IR — Intermediate Representation
Section titled “IR — Intermediate Representation”Generic term for a portable JSON contract. The Skill IR is Claresia’s intermediate representation of any skill, transpiled into per-LLM implementations by the Distribution Plane. See Skill IR reference.
Lazy Rendering
Section titled “Lazy Rendering”cc-052 M3 component. Templates are picked most-specific-first from a TemplateRegistry; per-instance cache; LLMCallable hook so an artifact can be fully rendered or stubbed.
Maturity Engine
Section titled “Maturity Engine”cc-053. Three-level ladder (Baseline → AI-Adopted → Agent Operator) with per-role anchors for productivity, cycle time, agent assist, headcount retention, and function adoption. Drives the maturity_report + transformation roadmap.
Mode A / B / C
Section titled “Mode A / B / C”The three Claresia deployment topologies. See Deploy overview.
PowerLens
Section titled “PowerLens”External brand name for the Claresia tool that transforms people — adoption,
certification, AI-fluency progression, manager dashboards. Internal codename:
Shadow Observer (roadmap ID cc-019).
Provenance
Section titled “Provenance”A SHA-256 hash over the canonical-JSON form of a Hub record (whole-valued floats normalized to ints — the cc-050 contract). Provenance is co-signed: data plane writes the hash, control plane co-signs it, neither can repudiate the other.
Role-Based Access Control. Claresia delegates the role assignment to your IdP (via SCIM groups) and resolves the role to one of 14 archetypes via cc-061. Skill entitlements are then granted per archetype.
RoleRuntimeSpec
Section titled “RoleRuntimeSpec”cc-051 schema (versioned, currently 1.0.0). The runnable definition of an
archetype: cadence calendar, artifact templates, KPIs, decisions, SOPs. Bundle
of N RoleRuntimeSpecs = an Archetype Bundle.
SCIM 2.0
Section titled “SCIM 2.0”Industry-standard user-lifecycle protocol. Claresia exposes a SCIM endpoint per tenant; your IdP pushes user create / update / delete events; we deprovision in real time.
The smallest unit of Claresia capability. Defined in Skill IR, versioned, RBAC-gated, telemetry-instrumented. Claresia ships 56 skills across 9 functions.
Skill IR
Section titled “Skill IR”The portable JSON contract that defines any Claresia skill. Same IR is consumed by all four LLM platform Distribution Planes. See Skill IR reference.
SHA-256 Canonical-JSON Provenance
Section titled “SHA-256 Canonical-JSON Provenance”The exact algorithm: serialize the record to canonical JSON (sorted keys, no
whitespace, whole-valued floats normalized to ints), SHA-256 the bytes, base64
the digest. Cross-language fixtures (cross_language_fixtures.json) verify
Python ⇄ TypeScript byte-equality.
Symbolic Event Stream
Section titled “Symbolic Event Stream”cc-052 M1 output. A 17-field SymbolicEvent schema × 32-action vocabulary × 7 event kinds × 5 cc-050 hub targets. Drives the deterministic sampler over an archetype bundle.
Synthetic Twin
Section titled “Synthetic Twin”cc-052. The simulator that generates an instrumented org from a DNA Archetype. Used in Phase-0 prospecting (Coverage Engine) and Phase-3 forecasting (Maturity Engine).
Telemetry Pipeline
Section titled “Telemetry Pipeline”Layer 4
of the architecture. Pull-style connectors that ingest LLM-platform audit logs
into fn_telemetry_event. Surfaces in Command Center within 5 min p95.
Tenant
Section titled “Tenant”A customer’s logical Claresia instance. Each tenant has a tenant_slug (URL
component), a region, a deployment mode, RLS row in shared Postgres (Mode A),
or a dedicated Postgres (Mode B), or a customer-cloud Hub endpoint (Mode C).
Time-to-value (TTV)
Section titled “Time-to-value (TTV)”The wall-clock time from contract signature to first end-user skill invocation. Mode A: <24h. Mode B: 5 business days. Mode C: 2–6 weeks.
Trust Center
Section titled “Trust Center”The public site at trust.claresia.com listing every certification, every
sub-processor, the DPA template, and the customer security questionnaire
pre-fills.
WorkOS
Section titled “WorkOS”The identity provider Claresia uses to abstract over your IdP (Okta / Azure AD / Google Workspace / generic SAML). WorkOS handles the SAML/OIDC handshake; Claresia never sees your password.
Zero-Retention
Section titled “Zero-Retention”A contractual commitment from a model provider that customer prompts and completions are not stored or used for training. Anthropic, OpenAI, Google all offer zero-retention enterprise modes; Claresia only routes through these.