nejimakibird_model-weave/docs/V0.8-codeset-state-usage-policy.md

V0.8 Codeset State Usage Policy

Purpose

This note defines how Model Weave V0.8 documents structured conditions and codeset value usage across Screen, Rule, app_process, mapping, and codeset formats.

Structured-field-only analysis

Natural language text is for human explanation. Model Weave analyzers use structured table fields only.

Do not parse arbitrary prose in:

• Summary
• Notes
• prose descriptions
• free-form rule or process text

Codeset value usage is detected only from explicit qualified value references in structured fields.

Qualified value reference syntax

Supported forms:

• [[CODE-ID]].value
• [[path/CODE-ID]].value
• CODE-ID.value, only when CODE-ID resolves to a codeset

Do not detect:

• value code alone, such as available
• value label alone, such as Available
• arbitrary prose
• app_process Flows.from / Flows.to
• screen Actions.target

Format-specific targets

Screen:

• Fields.condition
• Actions.condition
• Messages.condition
• Local Processes Steps.condition
• Local Processes Errors.condition

Rule:

• Conditions.condition
• Conditions.expression, if present
• Conditions.ref + Conditions.value

app_process:

• Inputs.data
• Outputs.data
• Flows.condition
• Transitions.condition when used as a structured condition
• table-based Steps reference fields

mapping:

• Scope.ref
• Mappings.source_ref
• Mappings.target_ref
• Mappings.rule
• Mappings.condition, if present
• Mappings.expression, if present

codeset:

• Values.code is the stable value identifier.
• Values.label is display text.
• Values.notes is descriptive only.
• Value references should use code, not label.

Screen vs app_process boundary

Screen is a UI-bearing process-like format where practical, but its subject remains the UI/screen.

Screen V0.8 does not gain app_process Flows. Complex flows should be represented as app_process and referenced from Screen Actions.invoke.

Screen relationships continue to use Fields, Actions, Transitions, and Local Processes.

Relationship View integration

Codeset object usage appears in normal inbound relationships.

Codeset value usage appears as Value usage only when viewing a codeset model.

V0.8 does not introduce a separate Codeset Usage View.

Out of scope

• Natural-language reference extraction
• Value usage heatmaps
• State transition diagrams
• Screen Flows
• Mermaid or graph rendering
• Runtime or parser changes in this documentation ticket