# Moltaro

> Moltaro is a low-code operations app platform for building around real records, forms, boards, maps, reports, and business logic. Teams can start in the cloud or self-host, keep operational data portable, and extend the system with C# when configuration is not enough.

This file is a concise map for AI agents that need to understand Moltaro from the public website. It is intended for inference-time navigation and summarization, not as a private engineering contract and not as training permission.

The public documentation is being expanded gradually. Some pages are structural placeholders; prefer pages with full explanations when available, and avoid inventing unsupported behavior from headings alone.

## Public Site Versus Workspace APIs

- `https://moltaro.com/` and `https://moltaro.com/docs/` are the public website, portal, and documentation. They are not customer workspace API origins and do not expose workspace data.
- Every `/api/workspace/...` route must be resolved against the target installation's workspace API base URL. Never append a workspace route to `https://moltaro.com`.
- Web Application registration, credential provisioning, and Agent integration are completed by the workspace owner in the Moltaro Portal or administrative interface. They are not coding-agent tasks.
- The agent starts only after the user provides the generated access kit: workspace-specific `AGENTS.md` / `CLAUDE.md` plus `.moltaro/credentials.env`. If the handoff is incomplete, the agent must ask the user to complete Agent integration; it must not provision or elevate itself through workspace APIs.
- The credentials file contains the exact workspace API base URL, 90-day key, and service-user identity. Never commit, upload, paste, echo, or print it; delete the downloaded ZIP after extraction. The Web Application URL and API URL may be different; do not infer one from the other.
- `GET {WORKSPACE_API_BASE_URL}/api/workspace/admin/agent-integration` and `/agents-md` are authenticated read endpoints of the configured Moltaro Application. `POST .../access-kit` is the administrator-owned one-time handoff and must not be invoked by an agent to provision access.
- The other documented `/api/workspace/admin/...` routes are also supported Moltaro Application Configuration APIs and remain part of the authorized agent workflow. Do not confuse them with private Portal administration APIs.
- Before starting or resuming workspace work, read the documentation version manifest, note `ProductVersion`, and open that version's detail page from the release-notes index. Recheck when the manifest version or HTTP ETag changes. Release notes provide change context; current documentation and installation-local OpenAPI remain authoritative.
- [Connect to a workspace API](https://moltaro.com/docs/developer/workspace-api-connection/): Human and agent bootstrap, URL roles, service-account handoff, and public versus installation-local contracts.

## Product Website

- [Moltaro overview](https://moltaro.com/): Public overview of the low-code operations app platform.
- [Operational records](https://moltaro.com/entities): Keep the data, status, responsibility, location, and history of real work in one durable record.
- [Security and data](https://moltaro.com/security-and-data): Roles, field rules, audit, deployment choices, backups, and data ownership.
- [Maps and routing](https://moltaro.com/geo): Zones, location-aware records, filtering, and responsibility by geography.
- [Boards](https://moltaro.com/boards): Process stages and board movement without splitting the operational record.
- [Work Schedule](https://moltaro.com/work-schedule): Working Schedule and Working Calendars for governed Worker and Site time, assignments, exceptions, civil time, and audit.
- [Dashboards and reports](https://moltaro.com/dashboards-and-reports): Built-in and custom reporting for operational indicators.
- [Templates](https://moltaro.com/templates): Business templates for objects, processes, and complete operating patterns.
- [Custom operations](https://moltaro.com/custom-operations): Declarative rules, Net Operation Project C#, and trusted custom Workspace UI pages for workspace-specific solutions.
- [Entitlements](https://moltaro.com/entitlements): Rights, coverage, usage, renewal, resources, and ledgered operations.
- [Deployment and pricing](https://moltaro.com/deployment-pricing): Self-managed Free up to 5 GB, a EUR 1,490 perpetual Unlimited license, and managed cloud package and quota pricing.

## Documentation

- [Documentation home](https://moltaro.com/docs/): Choose the right Moltaro documentation path.
- [User documentation](https://moltaro.com/docs/user/): Product concepts, everyday workflows, records, boards, entitlements, access, and automation in user-facing language.
- [Configuration](https://moltaro.com/docs/configuration/): Administrator and configurator guidance for modeling data, setting up modules, screens and navigation, access design, automation rules, data movement, rollout, and governance.
- [Card item layout](https://moltaro.com/docs/configuration/card-item-layout/): Configure `ColumnSpan` from 1 through 3 for Card Fields, TextBlocks, and Alerts. Null means one column; runtime clamps the authored span to the Card container's current column count. Items remain row-major by `SortOrder`, field types never imply full width, and Drawer and Details use the same contract. Agents must read `SupportedColumnSpans`, preserve the replace-all Card document, and verify the saved value after PUT.
- [Form Related tables](https://moltaro.com/docs/configuration/form-related-tables/): Configure one full-row child-record table from a direct paired inverse relationship on a Form. Create mode waits for a saved parent; child CRUD saves independently, uses actor-shaped Table/Form actions, and never rolls back with the parent draft.
- [Related tables in forms](https://moltaro.com/docs/user/working-with-records/related-tables-in-forms/): User workflow for Add/Edit, new-tab Details, Archive/Delete confirmation, permissions, and the independent-save boundary.
- [Form Related Table API and automation](https://moltaro.com/docs/developer/form-related-tables/): PascalCase Configuration API discovery and read-modify-write-read, YAML v8, server-owned locked filtering, ten-row paging and Tree routes, optimistic sort settings, Unified Security, concurrency, and agent readback. Package authoring is intentionally not public.
- [Hierarchies and Tree View](https://moltaro.com/docs/configuration/hierarchies/): Parent Tree View follows an indexed direct scalar self-Reference owned by a Table Surface, including the entity default. Roots and children are paged by the server; filtering preserves visible ancestor context. Desktop hierarchy headers and the mobile Sorting sheet expose the effective sibling sort; an actor-inaccessible configured sort field safely falls back to Display name ascending. Data Explorer, direct tables, Details/Drawer related tables, and full Reference Lookup pickers preserve Tree presentation. Narrow/mobile Data Explorer cards deliberately omit record selection and the bulk-action bar; group-of-record actions require the desktop grid, while picker selection remains available in picker workflows. Related child routes re-resolve their host block, opaque context revision, server-owned relation scope, and Table Surface revision. List/LongList controls cannot consume Tree; making Tree default is rejected atomically until dependent reference controls use Lookup. Value-based Group By remains separate.
- [Manual Order](https://moltaro.com/docs/configuration/manual-order/): One governed relative record order shared by Flat and Parent Tree View Table Surfaces, with desktop drag, accessible keyboard/mobile Move action, Reference Eligibility and invariant enforcement, semantic audit history without raw ranks, dependency-aware removal, YAML v8, and package ownership/reapply rules.
- [Business logic](https://moltaro.com/docs/developer/business-logic/): Supported automation and extension surfaces: declarative logic, C# business logic in the workspace Net Operation Project, entity functions (validation, mutation, triggers), global functions, commands and API functions for direct API invocation, UI actions, HTTP endpoint functions (inbound webhooks), CRON schedules, and run/job operations.
- [Function schedules](https://moltaro.com/docs/developer/business-logic/schedules/): Use one Function Schedule for recurring work instead of repeatedly enqueueing jobs from an external loop. Each due CRON occurrence is lease-claimed; if the target function already has queued or running work, Moltaro records the occurrence as `Skipped` and does not create parallel work. Do not add a second singleton/deduplication mechanism or compensate for `Skipped` with a manual enqueue.
- [Actions](https://moltaro.com/docs/developer/business-logic/actions/): Typed user-triggered C# actions, versioned Boolean and Select defaults, nullability and missing-value semantics, preflight validation, asynchronous execution, and history.
- [Managed secrets](https://moltaro.com/docs/developer/business-logic/managed-secrets/): Canonical owner/admin and coding-agent handoff, `Administration > Secrets` and write-only API lifecycle, Audit Trail evidence, synchronous `ISecretService`, stable unavailable codes, immutable invocation snapshots, and the trusted-publisher boundary.
- [Expression language (DSL)](https://moltaro.com/docs/dsl/): Reference for the Moltaro expression language used by field behavior conditions, presentation rules, Entity Statements, Board Statements, validation rules, Reference Eligibility, and calculated fields — syntax, functions, and per-surface capabilities.
- [Field behavior conditions](https://moltaro.com/docs/dsl/field-behavior/): Configure `VisibleWhen`, `RequiredWhen`, and `EditableWhen`, including same-record values and one direct Reference hop; generated Forms load the required Reference context automatically. These presentation/edit conditions are separate from mutation-effect `ApplyWhen`.
- [Declarative logic](https://moltaro.com/docs/developer/business-logic/declarative-logic/): Configure mutation-effect `ApplyWhen` conditions, ordered fallback/clear ownership, authoritative Form/save reevaluation, and the difference from `VisibleWhen`.
- [Calculated field expressions](https://moltaro.com/docs/dsl/calculated-fields/): Stored numeric formulas, exact Configuration API validate/update workflow, recalculation behavior, and the boundary between Display Fields, Calculated Fields, and C# before-save mutation.
- [Display fields](https://moltaro.com/docs/user/data-structure/entity-definitions/display-fields/): Read-time text for Table and Card surfaces, a ready Full name example, and the Configuration API replace contract.
- [Duplicate detection](https://moltaro.com/docs/user/data-structure/duplicate-detection/): Configure exact or multi-field fuzzy rules, including exact guard fields, Unicode edit distance, diacritics, token order, and weights. Details-page anchored checks cover the complete actor-visible archive scope. Table-page checks first return a bounded, explicitly partial review; users can then enqueue a durable Worker-owned complete scan and recover its saved actor-owned result after reload. Fuzzy results are honest two-record pairs, not transitive clusters. Semantic similarity, nickname/transliteration rules, scheduled scanning, automatic merge, and save blocking are not included.
- [Developer documentation](https://moltaro.com/docs/developer/): The .NET SDK, C# business logic, integrations, APIs, MCP/agent-facing boundaries, and developer reference material as it becomes available.
- [Connect to a workspace API](https://moltaro.com/docs/developer/workspace-api-connection/): Distinguish the public website and docs, the workspace Web Application, and the workspace API host before copying API routes.
- [AI agent development quickstart](https://moltaro.com/docs/developer/ai-agent-development/): API-first workflow for an AI developer — delivered workspace guide and OpenAPI discovery, complete Entity UI and table filter/sort design, Entity creation, server-side C# completions/hover/signature-help/diagnostics, immutable revision, Check and Build, function invocation, and Workspace UI pages without downloading a project.
- [Reliable API automation](https://moltaro.com/docs/developer/reliable-api-automation/): Post-bootstrap handoff, URL separation, concurrency, retries, idempotency, polling, recovery, source limits, safety, and audit responsibility for human developers and coding agents.
- [Asynchronous operations and polling](https://moltaro.com/docs/developer/async-operations/): Machine-readable rules for distinguishing request-blocking calls from queued work, including Function Catalog contracts, binding and publication kinds, CRON schedule jobs, function job/run states, build states, cancellation, and bounded polling.
- [Integration quickstart](https://moltaro.com/docs/developer/integration-quickstart/): The discovery flow for developers and AI agents: read workspace context, authenticate, list entity definitions, read a schema, then query and change records, with real request and response examples.
- [Configuration quickstart](https://moltaro.com/docs/developer/configuration-quickstart/): Create an entity definition, add schema fields, configure explicit search targets plus table `FilterItems`, `SortItems`, and `DefaultSort`, and create the first record through the Configuration API.
- [Record search configuration](https://moltaro.com/docs/configuration/entity-search/): Choose direct and related String, Text, Address, File, display-name, number, comment, and attachment paths; understand literal substring matching, access rules, depth, immediate visibility, and configuration guards.
- [Record matching API and configuration](https://moltaro.com/docs/developer/record-matching/): Additive exact/fuzzy profile DTOs, scoring and evidence, bounded and anchored run contracts, durable full-scan polling, ACL/no-oracle rules, and portable Entity Definition YAML/package round-trip.
- [Reference Eligibility](https://moltaro.com/docs/configuration/reference-eligibility/): Validate, impact-check, activate, and enforce Current/Candidate constraints for scalar Reference fields. Active rules pre-filter Form and Table-filter pickers, use server-authoritative create/edit context with alternative related-create roots, and remain authoritative for API writes.
- [Hierarchy Selector](https://moltaro.com/docs/configuration/hierarchy-selector/): Configure a scalar Reference as explicit-path or lazy recursive-parent cascading dropdowns in Forms and Table filters. The selector stores one terminal ID and composes with Reference Eligibility.
- [Reference Eligibility expressions](https://moltaro.com/docs/dsl/reference-eligibility/): Current/Candidate roots, boolean composition, one-hop scalar paths, type checking, and V1 limits.
- [Entity search API](https://moltaro.com/docs/developer/entity-search/): Exact replace-all `SearchTargets` and `RowVersion` workflow, runtime `SearchTerm` payload, enum values, strict Entity Definition YAML v8, and removed full-text flags/rebuild operations for developers and coding agents.
- [Table filters and sorting](https://moltaro.com/docs/configuration/table-filters-and-sorting/): Configure direct and related Table Surface targets, including multiple filters with one reference root, and keep `Target.Path` separate from lookup `ReferencePath`.
- [Entity Instance Query](https://moltaro.com/docs/developer/entity-instance-query/): Exact Runtime API payloads and semantics for grouped filters, related filter/sort paths, reference record-ID operands, limits, nulls, archives, permissions, and saved/shared views.
- Date and time entity values and direct API filters are exact instants: agents must send ISO 8601 with an explicit `Z` or numeric offset. Moltaro canonicalizes them to UTC, preserves microseconds, and does not preserve the submitted offset. The WebApp's minute-level filters expand their boundaries without changing direct API semantics; see [Fields and schema](https://moltaro.com/docs/user/data-structure/entity-definitions/fields-and-schema/) and [Entity Instance Query](https://moltaro.com/docs/developer/entity-instance-query/).
- [Boards configuration walkthrough](https://moltaro.com/docs/developer/boards-configuration/): Enable Boards, create a board, bind a record type target, define statuses and transitions, and activate — the full Configuration API flow with real activation preconditions.
- [Boards runtime walkthrough](https://moltaro.com/docs/developer/boards-runtime/): Public Runtime API flow plus the preferred `IBoardAutomationCommandService`/query facade for complete C# application orchestration from triggers, jobs, commands, actions, and HTTP endpoints.
- [Work Schedule C# guide](https://moltaro.com/docs/developer/work-schedule/): Preferred application-automation facade for effective schedules, calendars, assignments, and exceptions; stable operation ids, optimistic concurrency, time zones, and the trusted host boundary. This does not publish Work Schedule REST endpoints.
- [Entitlement Operations walkthrough](https://moltaro.com/docs/developer/entitlement-operations/): Configuration and Runtime API flow plus the preferred Entitlement application-automation command/query facades for grants, ledger operations, access/history, and renewals.
- [Record history and audit](https://moltaro.com/docs/developer/audit-trail/): Read the record change feed over the API, configure per-definition audit settings, and emit business events from C# project code.
- [Errors and responses](https://moltaro.com/docs/developer/errors/): The response envelope, error shape, stable error codes, and field paths of the Moltaro APIs.
- [Error code reference](https://moltaro.com/docs/developer/error-codes/): Generated catalog of common stable error codes for core entity configuration and runtime record writes, with English messages.
- [Versioned Moltaro release notes](https://moltaro.com/docs/developer/release-notes/): Compact release index with a separate detailed page for each version, including shipped behavior, database migrations, operator actions, compatibility, and breaking changes.
- [.NET SDK](https://moltaro.com/docs/developer/package-sdk/): The programming model for C# business logic in the workspace Net Operation Project — function base classes, publication attributes for commands and API functions, access policy, and timeout rules.
- [.NET reference](https://moltaro.com/docs/developer/dotnet-reference/): Curated machine-readable XML and JSON manifest for supported Core, Boards, Currency Rates, Entitlement Operations, and Work Schedule types; the installation-local developer-surface endpoint remains the authoritative injectable catalog.
- [C# runtime recipes](https://moltaro.com/docs/developer/business-logic/csharp-business-logic/recipes/): Principal Get/Create-or-Update CRUD with caller-supplied stable ids and a compile-checked blocked credentialless-user Job; trusted direct-DB principal services versus module application automation; Board movement/retry semantics; Entitlement grant/consume and native idempotency; system actor/origin, polling, Currency Rates, and audit reads.
- [Workspace UI Project](https://moltaro.com/docs/developer/workspace-ui-project/): Trusted source-built custom pages for the workspace web app — project structure and manifest, pages/components/stores, the Moltaro and external API clients, design system and constraints, build/check/activation lifecycle (fully manageable through the Configuration API), and observability.
- [API reference](https://moltaro.com/docs/developer/api-reference/): Generated reference for the public integration API, including entity definitions, entity instances, entity data transfer, entity UI, comments, attachments, resumable FileSystem uploads, tags, Boards runtime, Entitlement Operations runtime, and business-logic invocation (function commands, API function enqueue and jobs, entity UI actions). Raw OpenAPI: https://moltaro.com/docs/api/openapi/moltaro-public-v1.json
- [Configuration API reference](https://moltaro.com/docs/developer/configuration-api-reference/): Curated configuration API covering workspace principal administration, core entity definition management (definitions, schema fields, search targets, calculated-field validation/update and recalculation jobs, projections, relations, display fields, validation rules, mutation effects, Entity Security Statements, Permission Assignments, Responsibilities, data transfer profiles, YAML portability, geo location sources, DSL expression validation), the entity UI surface library, user menus, Boards configuration, Entitlement Operations configuration (models, plans, plan families, renewal policies), business-logic authoring and operations (function catalog, function schedules, run and job operations, API function publications, HTTP endpoint governance, entity UI action design, Net Operation Project source and builds), and the Workspace UI Project (frontend source, templates and page generators, checks and builds, artifacts, and activation). `CreateUserRequest.Password` is an optional initial credential only for `WorkspaceUser`; omit it for deliberate passwordless provisioning and Service accounts. Core operations require the Admin or Configurator role; Geo Location Sources and board-scoped operations may also authorize resource-context managers. Service-account API keys use the same permission gates. Raw OpenAPI: https://moltaro.com/docs/api/openapi/moltaro-config-v1.json
- Each Moltaro installation generates a ZIP access kit for AI agents: intentionally compact bootstrap `AGENTS.md` / `CLAUDE.md`, a git-ignored `.moltaro/credentials.env`, and the real API/OpenAPI/developer-surface links. Feature semantics and examples stay in `llms-full.txt`; exact request shapes stay in the installation-local OpenAPI. The workspace owner creates the trusted Admin+Configurator Service user and 90-day key through Administration > Agent integration; the key is available only in that download.
- [On-premise operations](https://moltaro.com/docs/operations/): Deployment, configuration, updates, backups, monitoring, maintenance, and the breaking Entity Security upgrade sequence.
- [Glossary](https://moltaro.com/docs/glossary/): Concise definitions of Moltaro terms with links to contextual explanations.

## Key Product Areas

- [Record lists](https://moltaro.com/docs/user/working-with-records/lists/): Data Explorer supports scanning, filters, sorting, and row-level actions across desktop and mobile. Selecting several records and running group actions is intentionally desktop-only; narrow/mobile record cards do not show checkboxes or a bulk-action bar, and entering mobile clears desktop selection and pending group-action UI.
- [Data structure](https://moltaro.com/docs/user/data-structure/): Entity definitions, field types, references and associations, templates, catalogs, classifiers, and containment, written in the system terms the Constructor and API use, with a terminology bridge from user-facing record/record-type language.
- [Entity definitions](https://moltaro.com/docs/user/data-structure/entity-definitions/): The configured description of business record types, organized by data model (schema, projection, location), governance (access, transfer), automation and logic, and user interface (display fields, runtime screens, surface library), with links into the generated API reference.
- [Fields and schema](https://moltaro.com/docs/user/data-structure/entity-definitions/fields-and-schema/): Field types, behavior rules, typed create defaults, and the Markdown field experience. A scalar Reference constant persists one workspace-local target instance ID; Number and Display Name are actor-shaped presentation, and create/new-child application rechecks access, active state, Reference Integrity, and Reference Eligibility. Markdown is a semantic role on String/Text: API `Value` remains exact source, compact clients use `PlainTextPreview`, and source must never be rendered as trusted HTML. Governed inline images use opaque `moltaro-attachment://` tokens and the authenticated destination-scoped resolver; agents must never construct file URLs or treat an ID as access. Core Entity, Association-create, Board-target, and Board Data forms keep separate durable destination ownership. Only inspected PNG/JPEG/WebP content can render, while remote/data/blob/file/SVG sources stay inert. Agents must distinguish an absent field key (apply its default) from explicit `null`, `false`, `0`, empty text, or an empty selection (caller input). Primary-field defaults run only on create; child-field defaults also run for new rows added by patch. Defaults never change existing rows or backfill data.
- [Boards](https://moltaro.com/docs/user/boards/): Governed process surfaces for business records, statuses, movement, responsibility, and process-specific context.
- [Work Schedule](https://moltaro.com/docs/user/work-schedule/): Working Schedule, Working Calendars, effective-dated Site and Worker assignments, inheritance, exceptions, time zones, access, and troubleshooting.
- [Board constraints](https://moltaro.com/docs/user/boards/constraints/): Synchronous transition, entry, exit, and status-invariant rules enforced through reusable Board Statements across Board commands and governed Target or Board Data saves.
- [Board automation rules](https://moltaro.com/docs/user/boards/automation-rules/): Future after-commit Board actions through the outbox; implementation has not started.
- [Board Statement DSL](https://moltaro.com/docs/dsl/board-statements/): Configuration API authoring and preview profile for Board Item, Board Data, and one exact scoped Target, including date/calendar operations, package portability, diagnostics, and invariant-safe dependency classification.
- [Entitlement Operations](https://moltaro.com/docs/user/entitlement-operations/): Rights, coverage, usage, renewal, resources, and entitlement history.
- [Automation and business logic](https://moltaro.com/docs/user/automation-and-business-logic/): User-facing overview of automation and links to technical business-logic guidance.
- [Access and governance](https://moltaro.com/docs/user/access-and-governance/): Local Workspace-user creation with an initial password, passwordless external-identity provisioning, Service accounts with API keys, roles, Entity and Boards Access Policies backed by Security Statements, `View`-rooted actions, field permissions, responsibilities, Assignment Rules, Object Context Facts, audit trail, and the Security administration UI.
- [External identity and SSO](https://moltaro.com/docs/user/access-and-governance/external-identity-and-sso/): Connect a self-hosted workspace to Moltaro Identity while keeping users, roles, authorization, sessions, and data local.

## Agent Guidance

- Use public documentation for product-facing explanations and user-facing terminology.
- Do not treat public documentation placeholders as complete feature specifications.
- Do not infer private APIs, database schema, package contracts, or security behavior from public copy alone.
- Entity search is configured by explicit `SearchTargets`, not by legacy full-text flags. Agents must read the current Entity Definition, `SearchMaxTargetsPerDefinition`, and `RowVersion`, replace the complete bounded target set, and use the installed `SearchTerm` query option; normal substring terms contain 3 to 256 trimmed characters, while exact `#number` matches only `Number` and exact `#{record-id}` matches only `Id`. Agents must not call rebuild endpoints or wait for an external index.
- Entity data access is authorized by Security Statements assigned to Permissions. `View` is the root permission, the SQL predicate is applied before search/count/pagination, denied fields are omitted, and Owner/Admin have no implicit record access. New standalone Entity Definitions receive one ordinary, removable `Admin_access` policy for the built-in Admin role and every current non-field permission; existing definitions are not backfilled and later reconciliation does not restore or expand it. Configure Responsibilities, Access Policies, and explicit field refinements under Permissions on each Entity Definition; policy changes use atomic Plan/Apply, while Raw configuration — Advanced remains immediately effective.
- Entity create uses the required five-member `EntityCreateCommandRequest`: non-empty UUID `OperationKey`, matching `EntityDefinitionKey`, `Values`, non-null `ResponsibilityCandidates` (send `[]` when none are proposed), and the current `ExpectedDefinitionRowVersion`. Preserve the operation key only for an exact retry. Pre-0.0.20 clients must replace `Fields` plus string `MutationIdempotencyKey` with `Values` plus UUID `OperationKey`.
- In one explicit generated-context transaction, assign all new Entity ids and relationships before the first save, add the complete graph, and call `SaveChangesAsync` once. A later save cannot introduce a new Entity identity because the first save fixes the complete ordered lock batch. This applies globally, not only to Board-governed records; see the [.NET SDK](https://moltaro.com/docs/developer/package-sdk/#generated-context-transaction-writes) and [C# runtime recipe](https://moltaro.com/docs/developer/business-logic/csharp-business-logic/recipes/#create-a-related-entity-graph-in-one-atomic-save).
- Managed `IAttachmentService.UploadStreamAsync` and `UpsertStreamAsync` calls own their upload-session and Entity security transaction boundary. For a backlog, use bounded `UpsertStreamsAsync`, which gives every item an independent runtime scope and transaction; do not parallelize calls through one scoped service. Save pending `GeneratedWorkspaceContext` changes first and do not wrap stream, batch, poll, abort, or download calls in an ambient package transaction. A host-authenticated system actor bypasses end-user Entity permission statements but still requires a real owner and enabled feature; its reserved id without trusted provenance grants no access.
- For MCP, Codex, Claude Code, or other agent automation, prefer dedicated developer or MCP documentation when it is published, and treat permissions, auditability, and workspace boundaries as explicit requirements.
- Moltaro runtime is single-workspace on-premise. Runtime database selection comes from deployment configuration, not request headers, route prefixes, query values, or SaaS workspace switching.
- Moltaro.Portal is the public-site and commercial/control-plane boundary for portal accounts, billing, licenses, on-prem package generation, and future cloud orchestration. It must not be confused with runtime workspace behavior.

## Machine-Readable Documentation

- [Docs llms.txt](https://moltaro.com/docs/llms.txt): Generated entry point for the documentation content sets below.
- [Documentation version manifest](https://moltaro.com/docs/llms-manifest.json): Small machine-readable documentation version, product version, source/tree state, generation time, aggregate checksum, authored-page changes, mapped generated-artifact changes, and explicit coverage. Releases compare with the previous deployed documentation revision; a first release reports no comparison, while source first-parent comparison is development-only.
- [Complete documentation](https://moltaro.com/docs/llms-full.txt): The full product documentation as one Markdown file, regenerated on every docs build.
- [Abridged documentation](https://moltaro.com/docs/llms-small.txt): A compact variant with non-essential content removed.
- [Raw OpenAPI document](https://moltaro.com/docs/api/openapi/moltaro-public-v1.json): Machine-readable OpenAPI 3 contract for the public integration API.
- [Raw Configuration OpenAPI](https://moltaro.com/docs/api/openapi/moltaro-config-v1.json): Machine-readable contract for Entity, Boards and Entitlement configuration, Net Operation Project authoring/language operations, agent integration, and Workspace UI authoring.
- [Curated .NET reference manifest](https://moltaro.com/docs/api/dotnet/reference-manifest.json): Assembly versions, checksums, member counts, and included types for workspace C#.

## Discovery

- [Website sitemap](https://moltaro.com/sitemap.xml): Public website sitemap.
- [Docs sitemap](https://moltaro.com/docs/sitemap-index.xml): Generated documentation sitemap.