# LDS 0.9.7 — team activation

Use the [full handbook](https://montri-th.github.io/Landometer/v0.9.7/), [Story Color Atlas](https://montri-th.github.io/Landometer/v0.9.7/color-atlas.html) and [Location Intelligence profile](https://montri-th.github.io/Landometer/v0.9.7/location/). Download the pinned [v0.9.7 release](https://github.com/montri-th/Landometer/releases/tag/v0.9.7).

## What changes

LDS 0.9.7 / `color-srgb-10` adds the approved Story vocabulary (17 generic colours), refreshes the colours of all 20 retained analytical families (14 sequential + 6 diverging), and adds a separate Location Intelligence profile (16 named roles, 12 measured metrics, four qualitative SWOT lenses). Analytical scales and Story/Location role colours use exactly the same original HEX, anchors, LUT and value direction on light and dark backgrounds. No dark lightness/chroma adaptation or reversed data direction applies. Preserve readable boundaries, backing surfaces, labels, symbols, units and exceptional-value states. Exact HEX uniqueness is not universal colour discrimination or an accessibility certificate.

Brand Energy, brand voice, typography, original identity assets, wordmark permission, motifs/animation, categorical colours and atmosphere recipes retain their existing contracts. Keep historical releases explicitly pinned when a task requires them.

## Choose the few files needed

| Work | Current Project Sources |
|---|---|
| General Landometer / CityMETER | Complete LDS base Markdown |
| Location Intelligence | Complete LDS base + separate Location Intelligence Profile |
| ijji, CityChat or CityWiki | Complete LDS base + matching separate Product Add-on |
| A product with Location Intelligence work | Complete LDS base + matching Add-on + Location Profile |

The [Project Source download page](./project-source-0.9.7.md) lists exact files and hashes. Every Markdown contains readable guidance and embedded exact machine data. JSON is an alternative projection; uploading both formats is normally unnecessary. No 0.9.4 or 0.9.6 normative master is required alongside the current full base.

## ChatGPT Projects and Claude Projects

1. Download the exact current documents above and upload them to the relevant Project Sources / Files / Knowledge.
2. Update Project Instructions to identify `LDS 0.9.7`, `v0.9.7-owner.1`, `color-srgb-10` and the separate product/profile scope. Attach documents to a standalone chat when it has no Project Sources.
3. After verifying the new files, remove or deactivate the superseded LDS normative/overlay/Add-on copies from the active rule set. Preserve research, briefs, business evidence and unrelated data. Keep historical source versions only when clearly marked and explicitly selected.
4. Start a new session. Ask the tool to read the document ID and return the exact `water` seven-class values for both themes. They must be identical. For Location work, also retrieve `li.service_gap` and explain its zero and denominator; SWOT must not automatically acquire a numerical gradient.

A link in a message does not prove that every future chat can retrieve its contents. Uploaded Project Sources are versioned copies and do not update when GitHub changes. Do not infer team-wide activation from one account.

## ChatGPT Chat plugin resources

For ChatGPT Chat, use the additional [self-contained resource adapter](https://montri-th.github.io/Landometer/v0.9.7/chatgpt-resource-adapter.md). It retains LDS/plugin version `0.9.7` and the exact released normative, colour and asset bytes; `chatgpt-skill-resources-r1` identifies the packaging distribution. Update the existing `landometer-design-system` entry rather than creating a duplicate. Keep its intended workspace access and installation policy.

A new Chat test read the required release, scale and normative resources; filesystem verifier execution was unavailable. A new Work test after upload still mounted the original full 0.9.7 layout and passed its 9,769 checks. This is evidence for that full runtime, not native Work acceptance of the adapter layout. The adapter separately passed 9,768 local checks. The guide records the remaining boundary and warnings. Keep the original full package available for other supported runtimes.

Test new Chat and Work sessions separately using actual release/scale resources, and distinguish resource retrieval from verifier execution. Seeing SKILL.md alone is not a full package test. Existing matching 0.9.7 Project Sources do not need replacement for this packaging adjustment; they remain the authoring fallback when a runtime cannot read plugin resources. Other tool installations are separate.

## Claude Chat / Cowork and Claude Code

Use the full `landometer-design-system-0.9.7.zip` plugin where the interface accepts a plugin ZIP. Where it accepts a single skill, use `apply-landometer-design-system-0.9.7.zip`. Enable the current installed item; verify actual new-session retrieval of the normative and the exact colour runtime. A child skill viewer showing few files is not by itself evidence that plugin assets are absent; test actual file access.

For local Claude Code / Codex, clone or update the repository and review the installer plan before applying it:

```sh
python3 tools/install-lds097.py
python3 tools/install-lds097.py --apply
```

The installer verifies the package, preserves backups and updates only its declared local routing block. It does not install into ChatGPT Projects, Claude web accounts, Design libraries or colleagues' machines. Existing sessions can retain old loaded context; start a new session after switching.

## Claude Design and other design libraries

Update the existing intended library with the full base, matching Add-on/profile and exact `color-srgb-10.production.css` / `color-srgb-10.scales.json`. Location uses its separate profile machine JSON/CSS. Ensure CSS is an actual imported stylesheet and inspect the rendered values, not just a file-list badge. Save/publish the current revision within the existing library scope and verify the library assigned to the next design session. Preserve unrelated product visual values.

## Human design, code and exports

Use the exact downloadable LUTs and 3/5/7/9-class selections. Do not interpolate only from endpoints, invent a midpoint or derive a dark rendition. The full package contains fonts, logos, CSS and runtime assets. Review Thai/English output at the intended size, including print/export and dark backgrounds. Colour alone is not enough for zero, missingness, suppression, sign, units or business evidence.

## Verify what actually changed

Record the document/version/hash, platform or Project, activated library/skill and successful retrieval/render checks. Repository publication, local installation, account installation and team adoption are different events. No new digital signature, universal accessibility compliance or entire-team activation is implied by package integrity.