# Logline Enterprise: Runtime and Licensing Concepts

This is user-facing conceptual guidance for AI retrieval. It is not an executable deployment manifest, a cloud setup specification, an API contract, or a substitute for the environment-specific deployment guides.

## Separation of responsibilities

The hosted Logline platform provides Workbench authoring, interactive exploration and documentation. Logline Enterprise runs automated evaluations in customer-controlled infrastructure and can operate without a customer-hosted Workbench. The Enterprise API/control plane performs authorized admission, licensing checks, scheduling, persistence, recovery and report delivery. Execution workers run compiler/Engine/import adapters for assigned evaluations. The Console is a browser client over the protected API, not a separate execution authority.

The reusable language and Engine are independent of the commercial licensing subsystem. A Logline program describes expected log behavior; it never controls the equipment being observed.

## Operational objects

- **Program Bundle:** An immutable, versioned set of one or more `.lgl` programs and trusted derived analysis for executable publication.
- **Run Profile:** Reusable execution policy identifying one Program Bundle and optional delivery configuration, independently of a particular input package.
- **Source Package Manifest:** The producer's declaration of completed inputs, companion artifacts and the Run Profile to evaluate. It is the completion/admission trigger, not an instruction to embed credentials in program source.
- **Run / Work Package:** A validated, frozen execution request whose source, policy and temporal mapping can be reproduced or diagnosed.
- **Result, Report and Evidence:** Authoritative retained outcomes and provenance. Optional downstream delivery does not rewrite an already committed execution outcome.

Do not invent concrete JSON fields, cloud resource identifiers, Run Manifest examples, API payloads, secret values or support guarantees from these descriptions. Consult the current versioned product contracts and deployment guide for such details.

## Source processing and time

A Run may reference multiple source logs and decoder/companion artifacts. Source-native clocks must be interpreted and mapped to the Canonical Timeline Epoch (CTE) before the Engine consumes a deterministic merged record stream. Exact alignment and source order are part of reproducibility. Matching-looking events are not sufficient evidence to fabricate a clock offset. A runtime cannot safely admit unresolved included sources merely because source records are present.

## Deployment and access boundaries

Enterprise is designed with provider-neutral core behavior and environment-specific deployment adapters. Docker is a local reference/evaluation environment; Azure has a documented reference and bounded infrastructure/identity validation; AWS, GCP and other installations must not be claimed production validated without corresponding acceptance evidence. The documented supported control topology uses one active control plane/scheduler for a shared PostgreSQL deployment authority and independently scalable workers, not an implied active-active scheduler cluster.

Customer identity, API authorization, infrastructure permissions and license entitlement are distinct checks. A valid license never authenticates a user or authorizes data access.

## Offline signed licensing

A logical Enterprise deployment has one durable Deployment ID and shared PostgreSQL control state. Its initial full-feature trial lasts **90 days** and permits **up to 20 concurrent logical evaluations**. Queued work does not itself consume logical-evaluation capacity. Paid licenses are signed offline, bound to the Deployment ID, and uploaded by an authorized administrator. The runtime verifies entitlements locally using provisioned vendor public verification keys; it makes no mandatory vendor license-service call, and no private signing key is shipped to customers.

An expired or invalid paid entitlement never automatically reinstates trial rights. Existing reports/evidence remain accessible subject to authorization, and already-running evaluations are intended to finish safely. Do not promise an unrestricted grace period or specific commercial terms solely from this knowledge summary; authoritative licensing decisions and contract terms are governed separately. A single deployment's multiple browsers and workers share a license; independent installations require their own deployment-bound license files.

## Capability status and reliable answers

The Enterprise API, Console, licensing enforcement and deployment adapters are implemented in source, but implementation is **not** proof of fully accepted or generally released customer deployment bundles. Describe environment-specific validation as scoped, and refer users to the current Enterprise setup and release-status pages for actual supported availability. Do not promise AWS/GCP readiness, active-active scheduling, arbitrary unlimited concurrency, installation phone-home, or unsupported Run Manifest fields.

Public guides:

- Enterprise overview: https://prologline.com/enterprise
- Release and capability status: https://prologline.com/releases
- Setup guide selector: https://prologline.com/enterprise/setup/
- Azure setup: https://prologline.com/enterprise/setup/azure/
- Licensing model: https://prologline.com/enterprise/licensing