Skip to content
ContractSpec
Start here

Area guide · 10 packages · Compose a form respondent and management surface

Forms, data views and data exchange

Collect structured input, present records, and plan governed import/export flows using shared models and explicit host ports.

What are you trying to do?

  • Which package owns form lifecycle versus form UI?
  • How do immutable form publications relate to responses?
  • Where can I preview a mapping before applying it?

Why start with these packages

Suggested entry point

@lssm-tech/lib.forms-runtime

Use the canonical caller-port form lifecycle, document compiler and validation helpers.

Read package manual →

Suggested entry point

@lssm-tech/module.forms

Choose reusable builder, respondent, results and administration composition for the host.

Read package manual →

Suggested entry point

@lssm-tech/lib.data-exchange-core

Start with codecs, mapping, plans and preview contracts before binding a transport or store.

Read package manual →

Practical steps

Step 01

Select one data path

For a form, trace document creation through publication and response storage. For import/export, trace decode, schema mapping, validation and preview. Record where trusted actor scope and the selected schema enter that path.

Step 02

Supply the required ports

Inspect the exact publication or exchange requirements before wiring storage, verification, delivery or AI adapters. Use a deterministic local adapter for a source walkthrough, then qualify the intended durable adapter separately.

Step 03

Review replay and recovery

Use an existing fixture to examine duplicate submission, stale revision, denied scope and a bounded retry. Confirm that a preview, queued delivery, accepted response and completed external effect remain visibly different states.

Choose lifecycle and UI separately

FormsRuntime owns management, immutable publication, submission, consent, deterministic navigation, idempotency and document validation. ModuleForms keeps reusable builder, respondent, results and administration behavior. A product host supplies authenticated creator authority, storage, delivery providers, public routing, branding and feature flags. This split helps when embedding a form in an existing product: reuse the lifecycle and selected UI without assuming the package owns your tenant identity or deployment.

Read the published form’s requirements

Forms capabilities are organized into independently gated milestones. A document requiring a disabled milestone is rejected at publication. Verification, AI follow-up, distributed request defense, secrets and outbox delivery are optional host ports until the selected publication policy requires them. Responses remain bound to immutable revisions. When adapting an example, inspect the enabled milestone, required ports, locale fallback and response-session scope together; a working authoring screen alone does not show that a particular published document can accept valid responses.

Preview interchange before applying changes

DataExchangeCore provides CSV, JSON and XML codecs, normalized record batches, SchemaModel mapping/coercion and import/export plans. Its preview and reconciliation surfaces allow a caller to inspect differences before choosing an effectful delivery path. Governed projection contracts carry sharing, consent, residency, retention and revocation responsibilities. Recovery dispatches deliberately contain narrower, receiver-specific references than central queue records. Keep source values and scheduler internals out of an unrelated product’s recovery message.

Follow a practical path.

Select one data path

For a form, trace document creation through publication and response storage. For import/export, trace decode, schema mapping, validation and preview. Record where trusted actor scope and the selected schema enter that path.

Supply the required ports

Inspect the exact publication or exchange requirements before wiring storage, verification, delivery or AI adapters. Use a deterministic local adapter for a source walkthrough, then qualify the intended durable adapter separately.

Review replay and recovery

Use an existing fixture to examine duplicate submission, stale revision, denied scope and a bounded retry. Confirm that a preview, queued delivery, accepted response and completed external effect remain visibly different states.

Packages in this area (10)

10 of 10 shown