Approve Common Lisp as the sole Star-Lang architecture #43

Merged

lost-rob0t merged 41 commits from agent/starlang-comparison-design-implementation-pass into main

2026-07-27 02:56:06 +00:00

lost-rob0t commented

2026-07-27 00:06:19 +00:00

(Migrated from github.com)

Decision

Common Lisp is the sole approved implementation language for Star-Lang.

This PR approves the language ownership and architecture. It does not claim that the implementation is complete.

Net changes

add the final Common Lisp language-selection record
add the approved Common Lisp parser, compiler, runtime, and recovery architecture
add an active implementation tracker with an explicit acceptance ledger
separate the archived research sequence from active implementation status
deny alternate Star-Lang parser, compiler, dispatcher, and runtime implementations
retain versioned JSON and generated Python/TypeScript bindings as boundary artifacts only
expand the Common Lisp workflow so Star-Lang design and implementation documents trigger the implementation test suite
add a CI guard rejecting retained Racket, Scheme, Guile, and alternate-language workflow artifacts

Status split

language selection: APPROVED
architecture: APPROVED
implementation: IMPLEMENTING
remaining hardening: tracked by #47

Architecture boundary

Common Lisp owns:

the closed .star parser
source spans and import origins
semantic validation
normalized IR
canonical manifests
lifecycle and delivery semantics
deterministic dispatch
durable recovery
document construction
direct execution
optional cl-gserver integration
transport adapters
the public Star-Lang API

Versioned JSON may cross process boundaries. It is an interchange format, not another Star-Lang implementation.

Validation

The Star-Lang Common Lisp Research workflow now runs for changes under the Star-Lang research, design, implementation, and index trees. It executes the existing Common Lisp suites and enforces the Common Lisp-only implementation boundary.

The Org-roam Pages workflow validates publication and internal links.

Merge only after the current head is green. Use squash merge because the branch contains exploratory history.

## Decision Common Lisp is the sole approved implementation language for Star-Lang. This PR approves the language ownership and architecture. It does **not** claim that the implementation is complete. ## Net changes - add the final Common Lisp language-selection record - add the approved Common Lisp parser, compiler, runtime, and recovery architecture - add an active implementation tracker with an explicit acceptance ledger - separate the archived research sequence from active implementation status - deny alternate Star-Lang parser, compiler, dispatcher, and runtime implementations - retain versioned JSON and generated Python/TypeScript bindings as boundary artifacts only - expand the Common Lisp workflow so Star-Lang design and implementation documents trigger the implementation test suite - add a CI guard rejecting retained Racket, Scheme, Guile, and alternate-language workflow artifacts ## Status split - language selection: **APPROVED** - architecture: **APPROVED** - implementation: **IMPLEMENTING** - remaining hardening: tracked by #47 ## Architecture boundary Common Lisp owns: - the closed `.star` parser - source spans and import origins - semantic validation - normalized IR - canonical manifests - lifecycle and delivery semantics - deterministic dispatch - durable recovery - document construction - direct execution - optional cl-gserver integration - transport adapters - the public Star-Lang API Versioned JSON may cross process boundaries. It is an interchange format, not another Star-Lang implementation. ## Validation The `Star-Lang Common Lisp Research` workflow now runs for changes under the Star-Lang research, design, implementation, and index trees. It executes the existing Common Lisp suites and enforces the Common Lisp-only implementation boundary. The Org-roam Pages workflow validates publication and internal links. Merge only after the current head is green. Use squash merge because the branch contains exploratory history.