Repository navigation
LiteSpec 5.0.0
LiteSpec 5.0.0 lets a project claim only the record layers it uses, writes every file a person edits in YAML, replaces exceptions with departures, and ships the litespec command line as a native executable for Windows, Linux and macOS. It is a major release: a consumer upgrades by following the steps in Part H, then running litespec model check until it is clean.
Part A: Claim the Record Layers the Project Uses
layersin the project file replaces the conformance level. A project names each record layer it claims,intent,behavior,implementationandproof, leaving layers out only from the bottom;implementationandproofeach takelitespec, LiteSpec's practice for the layer, orown, which keeps the team's practice and checks only that code and tests mark their records.- Every provision and every finding code carries the record layer it governs and whether it ties that layer to the records (
trace).model check,rules, the book and the analyzers report only what the claim covers, and the book shows an unclaimed layer as not claimed. - A page's Scope block names its
Concern; a provision's Applies to line may name itslayerandtrace. - The operations alert and runbook checks belong to the
deliveryextension. - The analyzers read the claim: the traceability rules run when Implementation is claimed, the architecture rules when it follows
litespec, and LS4001 when Proof is claimed.
Part B: People Write YAML, Programs Exchange JSON
.litespec/project.yaml,litespec.manifest.yaml, the schemas (schemas/<name>.schema.yaml), the pattern catalog (.litespec/implementation/patterns/catalog.yaml), the UI source lock (ui-source-lock.yaml) and the presets are YAML that states itsschemaVersionand names its schema in a first-line# yaml-language-server: $schema=<url>comment. Check results,--format jsonoutput, the book data and the provision index stay JSON.- The project file holds
frontendsandui.packageat the top level,stackConfig.dotnet.webapiandworkeras lists, and noconformance,$schema,unstructuredDocs,paths.records,surfaces,sites,apiSolutionorrefusals.prefixes. - The schemas publish at
https://litespec.dev/5.0.0/schemas/<name>.schema.yaml, including the newcheck-result.schema.yaml; a harness result that fails it reportsproof-invalid. litespec model renderwrites the UI source lock: each component's digest, the preset and the CLI pin.
Part C: One Departure Record
- The departure record replaces the exception record. It covers provisions, pages or finding codes on its
subjectorpaths, with a reason; a gap the team means to close carriesexpiresOnandexit, and a lasting choice carries neither. It lives in.litespec/governance/departures/. departure-expiredanddeparture-invalidreplace the exception codes. No departure covers the findings the model needs to load.
Part D: One Name per Concept
- A finding's
outcomeisblocking,reportedorcovered;severityleaves the JSON, andmodel checkends withN findings, M blocking, K covered. - Completion stages read
unfulfilled,specified,codedandverified. - The qualified identifier is gone; a record shows its folder path and its module.
- Provision strengths read
required,defaultandadvisory.
Part E: A Smaller, Bound Standard
- Near-duplicate provisions keep one home, and every citation follows it. Departures, testing and formats each have one page; how-to guides live under
docs/guide/. - Each UI pattern offers its Default and at most two other options.
- The
jobsextension is cut to what a small team follows;realtimeandcustomer-rulesare extensions; tenant delegation is part oftenancy; sagas and workflow engines leave the standard. litespec-maintain validatereports a cited finding code, template or example record that does not exist, aChecked byline for the model check that names no code, a page the index does not reach, and a pattern with more than three options. The finding-code, folder and pin tables are generated.quality/testing.mdholds one mock rule for every stack: a test substitutes only what the code under test does not own and what is not deterministic.- An agent never weakens a test that proves a scenario, and
model check --sincereportsproof-hash-driftfor a proving test that changed while its scenario did not.
Part F: A Native Command Line on Every Platform
- The CLI compiles ahead of time with .NET Native AOT for
win-x64,win-arm64,linux-x64,linux-arm64,linux-musl-x64,linux-musl-arm64,osx-x64andosx-arm64, and needs no .NET runtime. LiteSpec.Clion NuGet is a per-platform tool package, sodotnet tool install,dotnet tool restoreanddotnet litespecwork unchanged; every GitHub release carries a standalone archive per platform,SHA256SUMS,install.shandinstall.ps1, each with a build provenance attestation.litespec init --install standalonewrites a project that runs the CLI aslitespec; in a consumer root, the install scripts install the release that.litespec/project.yamlreviews.- The Linux glibc binaries run on glibc 2.28 and later and the musl binaries on Alpine 3.21 and later; the CLI computes SHA-256 itself.
- The CLI and the maintainer tool check every schema with LiteSpec's own JSON Schema evaluator, draft 2020-12 without dynamic references, anchors,
unevaluatedProperties,unevaluatedItemsandcontentSchema. - Every archive and package ships
THIRD-PARTY-NOTICES.md.
Part G: Provision Changes Since v4.0.0
Provision Changes Since v4.0.0
Added (162):
litespec/backend/domain#raise-the-past-tense-of-a-methods-own-verblitespec/backend/dotnet/domain#keep-clock-reads-and-random-values-out-of-domainlitespec/backend/dotnet/domain#keep-double-and-float-out-of-exact-quantitieslitespec/backend/dotnet/domain#mark-each-changing-root-method-with-one-use-caselitespec/backend/dotnet/naming#check-architectural-role-suffixeslitespec/backend/dotnet/naming#check-repository-variable-nameslitespec/backend/dotnet/naming#check-result-part-nameslitespec/backend/dotnet/persistence#keep-pipeline-owned-collaborators-out-of-handlerslitespec/backend/dotnet/stack#identify-an-aggregate-root-by-its-mark-and-state-recordlitespec/backend/dotnet/stack#pin-the-test-packages-in-the-manifestlitespec/backend/dotnet/stack#run-mutation-testing-with-stryker-netlitespec/backend/dotnet/stack#start-the-integration-database-in-a-containerlitespec/backend/dotnet/stack#test-with-xunit-v3-on-microsoft-testing-platformlitespec/backend/persistence#test-persistence-against-the-pinned-databaselitespec/core/agent#protect-proofs-from-implementation-editslitespec/core/departures#depart-from-advice-without-a-recordlitespec/core/departures#record-a-project-wide-lowering-as-a-departurelitespec/core/departures#record-accepted-gaps-as-departureslitespec/core/language#cite-shared-provisions-in-their-published-formlitespec/core/language#exclude-declared-content-paths-from-the-ascii-checklitespec/core/language#exclude-the-compound-that-names-another-conceptlitespec/core/language#follow-the-identifier-form-of-each-record-typelitespec/core/language#keep-wire-codes-stablelitespec/core/language#name-records-with-one-to-six-wordslitespec/core/language#record-the-project-vocabulary-as-datalitespec/core/language#reject-a-recorded-synonym-inside-its-scopelitespec/core/language#resolve-every-identifier-citationlitespec/core/language#review-each-term-for-its-lookalikeslitespec/core/language#state-mannered-terms-literallylitespec/core/language#use-every-identifier-oncelitespec/core/language#use-the-declared-record-identifier-grammarlitespec/core/model#classify-every-specification-filelitespec/core/model#declare-structured-specification-metadatalitespec/core/model#derive-a-computed-fact-instead-of-restating-itlitespec/core/model#keep-code-out-of-intent-and-behavior-fieldslitespec/core/model#rewrite-every-link-on-a-renamelitespec/core/model#scaffold-pages-and-reserve-identifierslitespec/core/model#start-each-explanation-file-with-its-titlelitespec/core/model#state-what-happens-in-every-behavior-statementlitespec/core/model#use-one-metadata-carrierlitespec/core/model#validate-a-single-page-before-committinglitespec/core/release#record-accepted-debt-as-a-departurelitespec/core/scope#claim-the-record-layers-the-project-useslitespec/core/scope#write-every-hand-written-litespec-file-in-yamllitespec/core/scopes#depart-from-a-rule-only-through-a-recorded-departurelitespec/core/scopes#give-every-provision-its-layer-and-tracelitespec/ext/customer-rules#bound-tenant-rule-runs-per-periodlitespec/ext/customer-rules#isolate-hook-failures-from-the-triggerlitespec/ext/customer-rules#record-the-customer-rules-cataloglitespec/ext/customer-rules#refuse-unknown-catalog-entrieslitespec/ext/customer-rules#state-what-a-hook-may-not-assumelitespec/ext/customer-rules#state-what-a-hook-may-rely-onlitespec/ext/customer-rules#treat-tenant-rules-as-datalitespec/ext/customer-rules#version-catalog-entrieslitespec/ext/delivery#ask-only-unanswered-questionslitespec/ext/delivery#close-incident-departures-within-seven-dayslitespec/ext/delivery#cover-every-quality-requirement-with-an-alert-or-a-checklitespec/ext/delivery#hold-back-example-rows-from-the-implementing-workerlitespec/ext/delivery#name-every-runbook-from-an-alert-job-reaction-or-failure-policylitespec/ext/delivery#name-the-requirement-and-runbook-on-every-alertlitespec/ext/delivery#point-each-operations-file-at-its-decisionlitespec/ext/delivery#restrict-a-worker-to-its-pathslitespec/ext/delivery#verify-before-accepting-worker-outputlitespec/ext/delivery#write-a-brief-before-handing-offlitespec/ext/realtime#authenticate-and-authorize-subscriptionslitespec/ext/realtime#bound-realtime-resourceslitespec/ext/realtime#declare-realtime-freshnesslitespec/ext/realtime#place-realtime-code-at-outer-boundarieslitespec/ext/realtime#reconnect-and-refresh-authoritative-statelitespec/ext/realtime#record-realtime-needlitespec/ext/realtime#record-transport-supportlitespec/ext/realtime#reject-cosmetic-realtime-adoptionlitespec/ext/realtime#reject-unbounded-slow-client-bufferinglitespec/ext/realtime#revalidate-long-lived-accesslitespec/ext/realtime#subscribe-through-narrow-functionslitespec/ext/realtime#tolerate-notification-ordering-differenceslitespec/ext/realtime#use-server-sent-events-for-notificationslitespec/ext/realtime#use-signalr-for-interactive-messaginglitespec/frontend/blazor/stack#bind-blazor-routes-to-their-addresslitespec/frontend/blazor/stack#build-blazor-forms-on-the-shared-form-entry-pointlitespec/frontend/blazor/stack#declare-blazor-outside-the-controlled-ui-contractlitespec/frontend/blazor/stack#keep-blazor-test-mocks-to-the-owned-boundarieslitespec/frontend/blazor/stack#keep-class-and-style-bindings-out-of-blazor-page-codelitespec/frontend/blazor/stack#keep-layouts-and-error-components-unmarkedlitespec/frontend/blazor/stack#keep-the-blazor-frame-routes-and-moduleslitespec/frontend/blazor/stack#load-blazor-route-data-before-its-view-renderslitespec/frontend/blazor/stack#localize-blazor-copy-through-a-pinned-dictionary-librarylitespec/frontend/blazor/stack#mark-each-blazor-route-entry-with-its-screenlitespec/frontend/blazor/stack#name-blazor-drawings-with-the-visual-suffixlitespec/frontend/blazor/stack#render-raw-html-only-through-markupstringlitespec/frontend/blazor/stack#run-blazor-logic-tests-on-xunitv3litespec/frontend/blazor/stack#show-route-failure-in-the-frames-route-error-componentlitespec/frontend/blazor/stack#use-a-layout-for-the-blazor-shelllitespec/frontend/blazor/stack#validate-blazor-route-parameters-before-loadinglitespec/frontend/mobile/android/stack#accept-app-links-in-the-host-activitylitespec/frontend/mobile/android/stack#apply-system-insets-to-each-screenlitespec/frontend/mobile/android/stack#declare-android-outside-the-controlled-ui-contractlitespec/frontend/mobile/android/stack#hold-one-navigation-controller-in-the-platform-projectlitespec/frontend/mobile/android/stack#keep-android-core-test-mocks-to-the-owned-boundarieslitespec/frontend/mobile/android/stack#keep-hosts-and-failure-views-unmarkedlitespec/frontend/mobile/android/stack#keep-screen-styles-in-resourceslitespec/frontend/mobile/android/stack#keep-the-android-frame-routes-and-moduleslitespec/frontend/mobile/android/stack#mark-each-android-screen-with-its-screen-recordlitespec/frontend/mobile/android/stack#read-android-copy-through-the-generated-resource-classlitespec/frontend/mobile/android/stack#request-audio-focus-before-playing-soundlitespec/frontend/mobile/android/stack#request-permissions-at-the-point-of-uselitespec/frontend/mobile/android/stack#route-the-back-gesture-through-the-activity-dispatcherlitespec/frontend/mobile/android/stack#run-android-core-tests-on-xunitv3litespec/frontend/mobile/android/stack#store-navigation-state-in-the-activity-bundlelitespec/frontend/mobile/android/stack#store-persisted-state-in-app-private-storagelitespec/frontend/mobile/android/stack#use-the-system-pickers-for-medialitespec/frontend/web/react/stack#add-the-tanstack-query-plugin-to-the-client-generatorlitespec/frontend/web/react/stack#apply-the-page-code-lint-to-route-and-module-codelitespec/frontend/web/react/stack#declare-route-search-parameters-in-validatesearchlitespec/frontend/web/react/stack#hold-a-routes-parts-in-its-route-filelitespec/frontend/web/react/stack#keep-layouts-error-components-and-route-groups-unmarkedlitespec/frontend/web/react/stack#keep-react-test-mocks-to-the-owned-librarieslitespec/frontend/web/react/stack#keep-the-react-frame-routes-and-moduleslitespec/frontend/web/react/stack#keep-the-tone-table-in-one-states-filelitespec/frontend/web/react/stack#load-intent-targets-before-navigationlitespec/frontend/web/react/stack#mark-each-react-route-entry-with-its-screenlitespec/frontend/web/react/stack#meet-the-locale-dictionary-contract-with-the-dictionary-librarylitespec/frontend/web/react/stack#name-drawings-with-the-visual-suffixlitespec/frontend/web/react/stack#prefetch-route-reads-in-the-loaderlitespec/frontend/web/react/stack#read-route-data-with-usesuspensequerylitespec/frontend/web/react/stack#render-raw-html-only-through-dangerouslysetinnerhtmllitespec/frontend/web/react/stack#run-the-registry-build-commandlitespec/frontend/web/react/stack#show-route-failure-in-the-route-error-componentlitespec/frontend/web/react/stack#use-named-props-for-class-and-style-bindingslitespec/frontend/web/react/stack#use-the-shared-package-form-hooklitespec/frontend/web/react/stack#use-the-tsx-extension-on-shared-fileslitespec/frontend/web/svelte/stack#add-the-tanstack-query-plugin-to-the-client-generatorlitespec/frontend/web/svelte/stack#apply-the-page-code-lint-to-route-and-module-codelitespec/frontend/web/svelte/stack#declare-route-parameters-in-a-schemalitespec/frontend/web/svelte/stack#hold-a-routes-parts-in-its-folderlitespec/frontend/web/svelte/stack#keep-layout-files-error-pages-and-route-groups-unmarkedlitespec/frontend/web/svelte/stack#keep-route-group-names-in-router-syntaxlitespec/frontend/web/svelte/stack#keep-svelte-test-mocks-to-the-owned-librarieslitespec/frontend/web/svelte/stack#keep-the-svelte-frame-routes-and-moduleslitespec/frontend/web/svelte/stack#keep-the-tone-table-in-one-states-filelitespec/frontend/web/svelte/stack#load-intent-targets-before-navigationlitespec/frontend/web/svelte/stack#mark-svelte-route-entrieslitespec/frontend/web/svelte/stack#meet-the-locale-dictionary-contract-with-the-dictionary-librarylitespec/frontend/web/svelte/stack#name-drawings-with-the-visual-suffixlitespec/frontend/web/svelte/stack#name-the-module-extension-on-each-importlitespec/frontend/web/svelte/stack#prefetch-route-reads-in-the-loadlitespec/frontend/web/svelte/stack#read-route-data-with-a-query-creatorlitespec/frontend/web/svelte/stack#render-raw-html-only-through-one-template-taglitespec/frontend/web/svelte/stack#resolve-imports-through-the-lib-aliaslitespec/frontend/web/svelte/stack#run-the-registry-build-commandlitespec/frontend/web/svelte/stack#show-route-failure-in-the-route-error-pagelitespec/frontend/web/svelte/stack#use-named-attributes-for-class-and-style-bindingslitespec/frontend/web/svelte/stack#use-the-shared-package-form-creatorlitespec/frontend/web/svelte/stack#use-the-svelte-extension-on-shared-fileslitespec/frontend/web/svelte/stack#write-components-in-runes-modelitespec/quality/testing#derive-expected-values-from-the-scenariolitespec/quality/testing#keep-the-test-projects-the-size-requireslitespec/quality/testing#prove-each-rule-through-its-scenarioslitespec/quality/testing#prove-each-scenario-through-the-public-boundarylitespec/quality/testing#refuse-surviving-mutants-on-changed-lineslitespec/quality/testing#use-evidence-rather-than-one-coverage-targetlitespec/quality/testing#use-one-mock-rule-for-every-stack
Removed (114):
litespec/backend/dotnet/domain#expose-cross-record-keys-from-the-aggregatelitespec/backend/dotnet/domain#raise-the-past-tense-of-a-methods-own-verblitespec/backend/dotnet/stack#identify-an-aggregate-root-by-its-mark-and-state-record-at-tracedlitespec/backend/identifiers#cite-shared-provisions-in-their-published-formlitespec/backend/identifiers#follow-the-identifier-form-of-each-record-typelitespec/backend/identifiers#keep-wire-codes-stablelitespec/backend/identifiers#name-records-with-one-to-six-wordslitespec/backend/identifiers#resolve-every-identifier-citationlitespec/backend/identifiers#use-every-identifier-oncelitespec/backend/persistence#test-persistence-against-postgresqllitespec/backend/testing#derive-expected-values-from-the-scenariolitespec/backend/testing#mark-the-test-that-proves-each-scenariolitespec/backend/testing#prove-each-rule-through-its-scenarioslitespec/backend/testing#refuse-surviving-mutants-on-changed-lineslitespec/backend/testing#test-application-coordinationlitespec/backend/testing#use-evidence-rather-than-one-coverage-targetlitespec/core/access#declare-every-operation-on-every-external-systemlitespec/core/access#name-every-entry-point-with-its-kindlitespec/core/authoring#classify-every-specification-filelitespec/core/authoring#declare-structured-specification-metadatalitespec/core/authoring#derive-a-computed-fact-instead-of-restating-itlitespec/core/authoring#exclude-declared-content-paths-from-the-ascii-checklitespec/core/authoring#exclude-the-compound-that-names-another-conceptlitespec/core/authoring#keep-code-out-of-intent-and-behavior-fieldslitespec/core/authoring#record-the-project-vocabulary-as-datalitespec/core/authoring#reject-a-recorded-synonym-inside-its-scopelitespec/core/authoring#review-each-term-for-its-lookalikeslitespec/core/authoring#rewrite-every-link-on-a-renamelitespec/core/authoring#scaffold-pages-and-reserve-identifierslitespec/core/authoring#start-each-explanation-file-with-its-titlelitespec/core/authoring#state-mannered-terms-literallylitespec/core/authoring#state-what-happens-in-every-behavior-statementlitespec/core/authoring#use-one-metadata-carrierlitespec/core/authoring#use-the-declared-record-identifier-grammarlitespec/core/authoring#validate-a-single-page-before-committinglitespec/core/layers#close-incident-exceptions-within-seven-dayslitespec/core/model#give-every-use-case-its-resultslitespec/core/model#reach-behavior-from-every-intent-recordlitespec/core/model#record-a-project-wide-lowering-as-an-exceptionlitespec/core/model#record-accepted-gaps-as-exceptionslitespec/core/principles#build-only-what-the-specification-stateslitespec/core/principles#declare-every-edgelitespec/core/principles#enter-facts-from-the-world-as-research-or-constraintslitespec/core/principles#map-each-engine-step-to-one-use-caselitespec/core/principles#prove-scenarios-with-testslitespec/core/principles#raise-what-a-lower-layer-needs-to-the-ownerlitespec/core/principles#write-each-layer-from-the-layer-abovelitespec/core/release#record-accepted-debt-as-an-exceptionlitespec/core/scope#declare-the-conformance-levellitespec/core/scope#keep-every-record-about-the-softwarelitespec/core/scopes#depart-from-a-rule-only-through-a-recorded-exceptionlitespec/core/scopes#give-every-provision-a-conformance-levellitespec/core/writing#keep-company-facts-out-of-intent-proselitespec/core/writing#name-each-title-in-its-record-type-formlitespec/ext/automation#bound-tenant-rule-runs-per-periodlitespec/ext/automation#isolate-hook-failures-from-the-triggerlitespec/ext/automation#record-the-automation-cataloglitespec/ext/automation#refuse-unknown-catalog-entrieslitespec/ext/automation#state-what-a-hook-may-not-assumelitespec/ext/automation#state-what-a-hook-may-rely-onlitespec/ext/automation#treat-tenant-rules-as-datalitespec/ext/automation#version-catalog-entrieslitespec/ext/compat#declare-published-facts-as-integration-eventslitespec/ext/delegation#ask-only-unanswered-questionslitespec/ext/delegation#hold-back-example-rows-from-the-implementing-workerlitespec/ext/delegation#restrict-a-worker-to-its-pathslitespec/ext/delegation#verify-before-accepting-worker-outputlitespec/ext/delegation#write-a-brief-before-delegatinglitespec/ext/delivery#apply-schema-work-before-trafficlitespec/ext/delivery#keep-schema-work-out-of-startuplitespec/ext/jobs#bound-the-ingest-bufferlitespec/ext/jobs#declare-ingest-steps-in-orderlitespec/ext/jobs#declare-the-engine-carrierlitespec/ext/jobs#define-the-closed-drop-reason-setlitespec/ext/jobs#discard-poison-records-after-three-attemptslitespec/ext/jobs#expose-drop-counts-per-reasonlitespec/ext/jobs#keep-engine-retry-configuration-in-implementationlitespec/ext/jobs#map-each-engine-step-to-one-use-caselitespec/ext/jobs#name-engine-steps-after-use-caseslitespec/ext/jobs#read-enrichment-data-from-declared-sourceslitespec/ext/jobs#record-one-drop-reason-per-dropped-recordlitespec/ext/jobs#reject-unmapped-engine-stepslitespec/ext/jobs#state-each-step-compensationlitespec/ext/jobs#state-the-freshness-consequencelitespec/ext/outbox#authenticate-and-authorize-subscriptionslitespec/ext/outbox#bound-realtime-resourceslitespec/ext/outbox#declare-realtime-freshnesslitespec/ext/outbox#place-realtime-code-at-outer-boundarieslitespec/ext/outbox#reconnect-and-refresh-authoritative-statelitespec/ext/outbox#record-realtime-needlitespec/ext/outbox#record-transport-supportlitespec/ext/outbox#reject-cosmetic-realtime-adoptionlitespec/ext/outbox#reject-unbounded-slow-client-bufferinglitespec/ext/outbox#revalidate-long-lived-accesslitespec/ext/outbox#subscribe-through-narrow-functionslitespec/ext/outbox#tolerate-notification-ordering-differenceslitespec/ext/outbox#use-server-sent-events-for-notificationslitespec/ext/outbox#use-signalr-for-interactive-messaginglitespec/frontend/patterns/dialogs-and-overlays#bottom-sheet-on-a-phonelitespec/frontend/patterns/forms-and-fields#keep-entered-values-after-a-refused-submitlitespec/frontend/patterns/lists-and-tables#list-on-a-phonelitespec/frontend/patterns/navigation#phone-navigationlitespec/frontend/patterns/page-frames#record-drawerlitespec/frontend/patterns/page-frames#show-one-primary-action-in-a-page-framelitespec/frontend/patterns/record-detail#hold-built-record-headers-to-one-primary-actionlitespec/frontend/patterns/record-detail#record-header-on-a-phonelitespec/frontend/testing#keep-mocks-at-owned-boundarieslitespec/frontend/ui#prove-every-result-a-route-callslitespec/frontend/web/svelte/components#write-components-in-runes-modelitespec/quality/operations#apply-schema-changes-outside-request-startuplitespec/quality/operations#cover-every-quality-requirement-with-an-alert-or-a-checklitespec/quality/operations#name-every-runbook-from-an-alert-job-reaction-or-failure-policylitespec/quality/operations#name-the-requirement-and-runbook-on-every-alertlitespec/quality/operations#point-each-operations-file-at-its-decision
Renamed (13):
litespec/backend/dotnet/application#keep-command-handlers-to-load-call-and-stagetolitespec/backend/dotnet/application#bind-command-handlers-to-load-call-and-stagelitespec/backend/dotnet/application#keep-query-handlers-free-of-writestolitespec/backend/dotnet/application#keep-query-handlers-free-of-repositorieslitespec/core/authoring#state-one-layer-per-pagetolitespec/core/authoring#state-one-tier-per-pagelitespec/core/release#qualify-the-checker-with-known-good-and-known-bad-fixturestolitespec/core/release#qualify-the-reader-with-known-good-and-known-bad-fixtureslitespec/frontend/mobile/screens#restore-the-visitors-placetolitespec/frontend/mobile/screens#restore-the-users-placelitespec/frontend/patterns/admin-screens#bringing-data-from-spreadsheetstolitespec/frontend/patterns/admin-screens#importing-data-from-a-filelitespec/frontend/patterns/admin-screens#budget-codes-and-advancestolitespec/frontend/patterns/admin-screens#budget-limits-and-advanceslitespec/frontend/patterns/admin-screens#supplier-invoicetolitespec/frontend/patterns/admin-screens#subscription-invoiceslitespec/frontend/patterns/create-edit-remove#publishing-and-unpublishing-a-policytolitespec/frontend/patterns/create-edit-remove#publishing-and-unpublishing-a-draftlitespec/frontend/patterns/forms-and-fields#color-field-for-the-mail-accenttolitespec/frontend/patterns/forms-and-fields#color-fieldlitespec/frontend/patterns/forms-and-fields#repeatable-group-for-budget-codestolitespec/frontend/patterns/forms-and-fields#repeatable-grouplitespec/frontend/patterns/lists-and-tables#trips-as-a-gridtolitespec/frontend/patterns/lists-and-tables#the-layout-of-a-short-listlitespec/frontend/patterns/record-detail#expense-recordtolitespec/frontend/patterns/record-detail#whole-record-screen
Extensions added (2):
customer-rulesrealtime
Extensions removed (2):
automationdelegation
Part H: Upgrading a Consumer
- Install
LiteSpec.Cli5.0.0 (dotnet tool update LiteSpec.Cli --version 5.0.0) or rerun the install script. - Rename
.litespec/project.jsonto.litespec/project.yamland write it as YAML: add the schema comment andschemaVersion: 1, setreviewedLiteSpecVersion: 5.0.0, and replaceconformancewithlayers:recordsbecomesintentandbehavior;tracedbecomes all four withimplementation: ownandproof: own;fullbecomes all four withlitespec, plus thedeliveryextension when the project runs alerts and runbooks. - Move
paths.frontendstofrontendsandpaths.uiPackagetoui.package, makewebapiandworkerlists, and delete the removed fields Part B names. - Convert the pattern catalog and the UI source lock to YAML at their 5.0.0 paths, drop
kindandshellfrom theDESIGN.mdmetadata, and runlitespec model renderto rewrite the lock. - Rewrite each exception record as a departure under
.litespec/governance/departures/:kind: gapkeepsexpiresOnandexit;kind: departuredropsexpiresOnwhen the choice is lasting;coversbecomes a list. - Rename the code citations and marks of every provision the Part G list renames, and read
--format jsonoutput foroutcomeinstead ofseverityandknown. - Run
litespec model checkand fix each finding.