Skip to content

SPEC_STATUS.md

Latest commit

 

History

History
69 lines (55 loc) · 3.43 KB

SPEC_STATUS.md

File metadata and controls

69 lines (55 loc) · 3.43 KB
Raw

Specification status and precedence

Current baseline

  • Language mode: 0.1
  • Semantic decisions: P-000 through P-374, excluding unassigned P-171/P-172
  • Syntax decisions: S-000 through S-205
  • Standard-library decisions: STD-000 through STD-150, applied according to their current decided/superseding status
  • Last synchronized: 2026-08-28

ProScript remains pre-1.0. The baseline is complete for the currently admitted 0.1 language surface, but parts of the ecosystem and production implementation remain deliberately incomplete.

Normative precedence

When two repository statements conflict, apply this order:

  1. A later current Decided P-numbered semantic entry that explicitly revises an earlier decision.
  2. A later current Decided S-numbered syntax entry for source notation.
  3. The consolidated language specification and technical companion documents.
  4. A decided STD-numbered standard-library entry, within the standard-library boundary only.

Historical, exploring, provisional, candidate, deferred, reopened, rejected, and superseded entries are non-normative. Implementation code, test behavior, milestone reports, backend design documents, and implementation-status tables are evidence, not sources of language semantics.

If prose remains inconsistent after applying these rules, open a specification issue rather than choosing implementation behavior silently.

Document classes

Location Class Authority
language/ Normative Language syntax and semantics
packages/ Normative where marked decided Package, project, manifest, and lockfile contracts
tooling/ Normative where marked stable CLI, formatter, and diagnostic interoperability
stdlib/STANDARD_LIBRARY_SPEC.md Normative for decided STD entries Standard-library API contract
design/ Authoritative status index plus design history Current decided rows govern; other rows are rationale only
native/PS_FFI_V1_DRAFT.md Draft No stable third-party ABI claim yet
conformance/FEATURE_MATRIX.md Normative index Required feature-family coverage
conformance/IMPLEMENTATION_STATUS.md Informative snapshot Never overrides the specification
reference/ Normative syntax fixture where its owning decision is decided Not a claim that every referenced library API exists

Known open boundaries

  • External dependency sources, registries, acquisition, and serialized package interfaces are not yet specified.
  • Standard-library breadth remains evolvable. The decided package surface through STD-150 is normative; roadmap and implementation entries are not.
  • ps_ffi_v1 source semantics are decided, but final public artifact, packaging, and complete ABI conformance remain unfinished.
  • Production allocator, collector, arena storage, additional target loaders, cross-target packaging, and performance thresholds remain implementation or release gates unless an observable P-/STD-numbered rule says otherwise.
  • P-374 makes authenticated target-native code plus the native runtime the sole conforming v1 production architecture. No bytecode VM, interpreter, or JIT tier is normative.

Compiler synchronization identity

The compiler workspace inspected for this baseline has a committed native-only baseline plus uncommitted follow-on work. Synchronization records both the commit identities and SHA-256 digests for mutable evidence. Neither changes the normative decision precedence above.