ADR-005: One .model File Equals One Process

Status

Temporary

Context

SOTER distinguishes Action, Process, and Task conceptually, but Logos currently implements Action as the concrete modeled activity type.

Process does not yet have explicit language syntax. A process refers to actions, subjects, and objects; it does not own them as nested definitions.

Decision

Until explicit process syntax exists, SOTER treats one .model file as one implicit process container.

The file groups the actions, subjects, and objects that belong to one business flow.

Rationale

This convention keeps the MVP grammar small while still allowing complete process examples to be modeled and projected.

It avoids introducing unstable Process syntax before the model semantics are settled.

Consequences

Positive

• No new parser syntax is required.
• Process examples remain easy to locate and compile.
• The convention supports quick MVP progress.

Negative

• Shared subjects and objects may be duplicated across files.
• Multi-process models need include or future syntax.
• The convention is not sufficient for mature enterprise modeling.

Neutral or Operational

• This ADR is temporary and should be revisited when process syntax is designed.

Alternatives Considered

Explicit type: Process

Deferred because the language does not yet define process ownership and composition semantics clearly enough.

One Repository Equals One Process

Rejected because it is too coarse and blocks multi-process examples.

Migration or Adoption

When explicit process syntax is introduced, existing one-file process examples should be migrated mechanically or treated as backward-compatible shorthand.

Related Documents

• DocumentationStyleGuide.md
• writing profile and document-type rules.
• AdrTemplate.md - ADR document template.
• AdrIndex.md - architecture decision record index.
• LogosOverview.md - Logos modeling entry point.