CSM One Vision

Last checked: 2026-06-20

CSM is the client schema manager for 12d delivery. Its job is to turn a client standard into a controlled, auditable, survey-friendly package without hardcoding client logic into new 12d macros.

The app owns the knowledge. The fixed macro owns the 12d execution.

Product Direction

CSM must support ADAC, A-SPEC, and client-specific delivery requirements by storing the client schema, the Veris mapping, the project runtime settings, and the evidence trail in one system. It must not become a collection of one-off client macros.

The operator workflow is:

1. Import or maintain a client schema and its code/attribute expectations.
2. Map client codes and attributes to Veris/CM codes with reviewable provenance.
3. Export a runtime package containing a settings sidecar, field input spec, project sub-profile, evidence files, and the single fixed macro.
4. In 12d, load the fixed macro, pick the source model, select the client, review seeded groups, fill project values, and apply attributes.
5. Keep evidence for what was scanned, what values were used, what was skipped, and what changed.

Macro Direction

There is one production macro:

• `exports/CSM_Apply_Profile.4dm`
• compiled to `exports/CSM_Apply_Profile.4do`

The fixed macro must stay generic. CSM generates data files; it does not generate a new production macro per client.

The macro UI must follow the latest prototype shell direction:

• real `GridCtrl_Box` tables, not drawn tables
• `Source_Box` for source model selection
• `Choice_Box` for client selection
• compact horizontal button rows
• seeded group review on the left
• selected group/attribute/element review on the right
• project/runtime values from `csm_field_input_spec.csv`
• run evidence visible in the panel and exported to files
• "Go to element" from grid row keys, using model uid + element uid columns

Reference prototype:

`C:\Users\a.almouhajer\Downloads\CSM_Apply_Profile_UI_Shell_v2_prefilled_extracted`

Runtime Package Direction

The package is two-file at the operator boundary:

• Client settings sidecar: read-only CSM export, normally `*.12d_runtime.txt`
• Project sub-profile: project/runtime values, read/write

The sidecar and sub-profile drive the fixed macro. The field input spec tells the macro which 12d controls to show for project-specific values.

Current Truth

The fixed macro is built and compiled. It has the intended shell structure and is wired to the runtime package path. Static macro audit is clean as of 2026-06-20.

The remaining acceptance boundary is live operator proof in 12d: the generic worker harness cannot prove the visible panel macro because it correctly blocks panel macros. A dedicated panel-runner or manual visible-panel proof is still needed before claiming the 12d UI is fully production accepted.