Repository navigation
Conversation
…eam link receipts
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Orgize keeps Org syntax and semantic interpretation in Scheme. Rust consumes source-backed syntax and Element projections, admits typed native responses, and exposes the public document/query interfaces. The cutover remains in progress; this draft does not claim complete parser replacement or merge readiness.
The current engine pins
gerbil-parsertodd0719585d6d5e54f44beaa6877c95152e89c914and the embedded FFI runtime to1e4f1f65c7ff8e95fe764f2e8549fa9d92275db4. A POO strategy owns its derived helper descriptors and prepared event-fold program. Refining strategy slots derives the corresponding program, rather than retaining the original constructor's grammar. Native initialization belongs to exclusive process startup before worker or child creation.Corpus execution batches syntax events and document metadata. Private metadata packets retain the existing Scheme document semantics, source order, per-document errors, strict response framing, and limits of 64 documents and 64 KiB of encoded fields. Oversized single-document configuration fields retain the existing individual call. Public contracts remain Version 1. Worker-local profiling transfers observations after join; overlapping duration sums are not caller wall time.
Producer-owned FFI bundles bind the exact source revision, target, runtime pin, parser identity, headers, ordered archives and file hashes. Downstream consumers validate and link the prebuilt Scheme program; missing or rejected bundles never trigger a Scheme rebuild. Producer CI relocates each bundle and reruns Rust tests with an absent program manifest before publication. The external-program runtime still compiles its small C lifecycle bridge, so this is not a completely compiler-free distribution.
Earlier macOS ARM64 validation at
33e49a7656f5bd83be1646f1152ea1714635133a:HARNESS-OKand finalOK; the failure control preserved its nonzero exit.Exact-head CI and downstream artifact qualification remain open. ASP consumes this existing PR through its built-in Orgize submodule; no external Orgize provider synchronization, new Orgize PR, or merge into main is required.
Current delivery
11b95cd5b03394b9b3ae7d70fb800dd3f9aab93dalso incorporates the concurrent shared-parser compiler update. FFI export carries static OpenSSL, zlib and SQLite archives instead of relying on producer library paths. All six current build-support admission tests pass, including missing and changed dependency archives. A local export attempt rejected missing static OpenSSL at obsolete library paths embedded in the installed SDK; this negative result is preserved, with no host-path discovery fallback.Standalone bundle initialization at the earlier pin succeeds. Same-process composition with MRR exposes overlapping generated Scheme globals and fails module initialization. A combined consumer needs compatible module identities and one admitted lifecycle/program owner; independent producer tests or successful Rust linkage do not prove that boundary. Latest producer CI and current parser performance qualification are pending; earlier functional and 516.552292 ms performance observations are not promoted to current-head results.