Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
33 lines (25 loc) · 1.32 KB

CONTRIBUTING.md

File metadata and controls

33 lines (25 loc) · 1.32 KB
Raw

Contributing to the ProScript specification

Every language-visible change must be synchronized as one change set.

Required change set

  1. Add or revise the owning P-, S-, or STD-numbered decision.
  2. Update the consolidated specification.
  3. Update lexical grammar, syntactic grammar, type-system, runtime, package, tooling, standard-library, or native text affected by the decision.
  4. Update the reference program or add a focused example when useful.
  5. Update conformance/FEATURE_MATRIX.md with testable obligations.
  6. Update SPEC_STATUS.md and CHANGELOG.md when the baseline advances.
  7. Run ./scripts/check-spec.sh.

Implementation behavior by itself is not a specification change. If code lands before a language decision, document it as experimental and fail closed for ordinary source until the decision is approved.

Synchronization evidence

A synchronization commit should state:

  • compiler repository and immutable revision;
  • old and new P/S/STD baselines;
  • affected feature families;
  • conformance tests added or changed;
  • unresolved implementation gaps; and
  • the result of the specification integrity check and compiler test gate.

Do not copy milestone reports into normative prose. Extract stable observable behavior, keep implementation mechanisms informative, and preserve rationale in the design record.