Content basis 15 October 2026 · manuals issued 16 October · source checks 17 October · localhost UI demo

ACLASA methodology workspaceProduction persistence is not yet deployed

This page demonstrates the employer layer only on HTTP(S) loopback hosts. Production save, editing, JSON export and employer PDF publication remain disabled until a tenant-bound GET/PUT backend, exact grants and an approval audit trail are deployed.

Current pack scope: SK/EN, IT/EN, GR/EN, ES/EN and private LT/EN use exact country-program entitlements. LV/EN remains excluded and has no program, preview or full document.

Public reader

ACLASA rule: modified wording is employer wording on top of ACLASA methodology, not a new ACLASA default.

Workspace flow

Use localhost to test the future controlled workflow

Only the labelled localhost demo can persist employer wording today. The ACLASA default stays locked and production remains fail-closed.

Start

Confirm environment

Browser persistence is permitted only in the labelled localhost demo; a production session does not enable editing.

Check access boundary

Then

Select methodology

Choose the country pack, language view, employer name and effective date.

Choose pack

Edit company wording

Write only the employer layer; changed text remains highlighted beside the ACLASA default.

Open editor

Finish

Test export controls

Demo export requires exact draft/download or draft/publish grants. It is not an effective employer instrument.

Review demo export

Country methodology Language view Company Company ID Effective from Program period Search

Employer layer

Default text remains locked; company wording is highlighted

Fields remain disabled in production. On localhost, use them only to test employer wording; leave a field empty when the ACLASA default should apply unchanged.