Source document index

Documents generation of the five-project application, local Aspire verification, separately versioned template/runtime baselines and optional Workflow candidate limitations.

Distinguishes Consumer checks from Matrix maintainer gates and describes targeted iteration, fresh Full verification, evidence reuse limits and separate browser/publication/adoption status.

Defines Consumer and module terms, typed C# composition, constrained JSON inputs, precedence, startup snapshots and the separation of presentation from authorization.

Connects individual capabilities to implementation, package and acceptance evidence, distinguishing dated slices, published baselines and current candidates.

Covers named profiles, trusted query predicates, generated navigation, renderer contracts, form and draft lifecycle, and release-dependent embedded presentation options.

Describes context, record and selection launch callbacks with reauthorized prefill, Consumer transactions, subject-bound receipts and refresh after confirmed acceptance.

Alpha.48 local antiforgery POST in every role, initiating return to the configured login route, signed-receiver isolation and the superseded alpha.46/47 confirmation contract.

Provides bootstrap, implementation, contribution, upgrade and continuation workflows grounded in repository instructions, pinned toolkit versions and observable Product requirements.

Describes neutral, API and Web project boundaries, stable catalog targets, protected endpoints, typed clients, stylesheets and startup-only module instances.

Explains page-owned report bindings, shared and independent widget state, bounded manual refresh, authorized drill navigation and optional layout preferences.

Documents typed bounded sessions, step validation, final command acceptance, uncertain-outcome recovery and the absence of durable draft or process-engine semantics.

Explains package-only application setup and the real-journey evidence needed to evaluate independent delivery, including all setup, rework and maintainer costs.

Defines inward dependencies, provider-neutral Core contracts, Shell composition, optional feature ownership, context isolation and the API/Web integration surface.

The entry point for adopting Matrix in a business application. Defines the platform family, package-first development and the first requirement-to-verification journey.

Sets out coherent API/Web rollout, report and cache budgets, readiness checks, durable audit decisions and recovery rules that distinguish diagnostics from receipts.

Records the deferred provider-neutral capability catalog, optional Assistant and MCP adapter, requiring every future invocation to preserve the owning module's authorization and execution boundary.

Provides the required requirement-to-capability, domain ownership, permission, environment and acceptance records for a Consumer without storing credentials or customer data.

Specifies typed worklist handlers and mandatory server scope, filter initialization, authoritative entity actions, bounded totals/export and source-candidate query limitations.

Defines report identity and measure semantics, Consumer query responsibilities, protected export/drill/print execution, freshness and audit delivery behavior.

Own-user identity, versioned HTTP operations, ETag/idempotency rules and application-owned storage migrations.

Installation handoff requirements and consumer checks for launch, logout and preferences integration.

Participant configuration, captured-user preferences credentials, conditional writes and optional filter favorites.

Browser navigation, local authentication routes and the explicit preferences backend contract.

Application directory, credential separation, card projection and the independent preferences module.

Portal-owned confirmation entry and historical alpha.46/47 routing. Current standard-menu behavior is superseded by Core's alpha.48 direct sign-out contract.

Directory claims and reader boundaries, registration flow, token/session limits and deployment acceptance.

Portal responsibilities, adopted capability baselines and separation of implemented features from future requirements.

Optional Matrix Activity dependency, verified package provenance and separation of publication from consumer adoption.

Authenticated publication, recipient state, change cursors, current directory observations and canonical actions.

Immutable publication identity, atomic acceptance and receipt transactions, and separate runtime/migration authority.

Shared inbox presentation, immutable attachments, canonical navigation and scoped display acknowledgement.

Destination enrollment, typed interaction inputs, current owner eligibility and registered-task navigation boundaries.

Monotonic snapshots, terminal tombstones, current task eligibility and the distinction between publication and task completion.

Defines the restricted acyclic BPMN profile, participant obligations, recovery requirements and separate operational acceptance gates.

Historical critical handoff for command identity, transaction boundaries, executor receipts, reconciliation and cancellation semantics, with subsequent local closure noted.

Describes owner-scoped HTTPS execution, release-dependent RabbitMQ response enrollment and owner verification connectivity. It does not establish production rollout.

Records the planned current-engine/Elsa installation choice, preserved participant contracts, excluded migration behavior and required acceptance.

Lists the administration routes, request boundaries, lifecycle permissions, schema vocabulary and migration/restore constraints.

Documents authenticated schema and manifest registration, separate approval, typed bindings, process authoring and local integration observations.

Defines commands, events, receipts, human messages, identity context, registered actions and subscriber custody. Its status preamble records an earlier milestone baseline.

Defines the distinction among principals, groups, authorization policies, business roles and typed human/service bindings. The design itself does not claim runtime completion.

Defines field-copy mapping syntax and bounds, schema validation, authority restrictions and compiler/Worker compatibility requirements.

Describes the product architecture, release adoption, catalog and process boundaries, plus locally verified milestone scopes. Historical paragraphs must be read with their stated baseline.

Application identity and proxy trust, development/production composition, artifact publication and independent application deployment.

Fresh v1 foundation composition, reviewed target checks, service verification and separate renewal/recovery acceptance.

Local application development, trusted release planning, protected identity operations and separate deployment enablement.

Common source versus installation state, consumer ownership and the distinction between source checks and target acceptance.

Portainer-owned v2 composition, generic consumer handoff and staging/production qualification boundaries.

Scoped PostgreSQL, RabbitMQ and Redis allocations with TLS, least privilege, monitoring and isolated restoration.

Application-neutral infrastructure, explicit profile ownership and additive identity onboarding.