docs: typed-wasm is a meeting point for two unrelated languages#73
Merged
Merged
Conversation
Adds a top-of-file [NOTE] admonition to README.adoc making it unambiguous that AffineScript and Ephapax — both of which target typed-wasm and both of which interface with crates/typed-wasm-verify/ — are two SEPARATE, UNRELATED languages. Why: AI agents have repeatedly conflated AffineScript with Ephapax (or with Ephapax's internal ephapax-affine sublanguage). The repos at hyperpolymath/affinescript and hyperpolymath/ephapax share zero AST / typing / borrow-checker / codegen — they meet only here, at typed-wasm. Workers on crates/typed-wasm-verify/ in particular need to know that the agreement theorems against each consumer are independent. This is the meeting-point repo's callout. Companion PRs land in: - hyperpolymath/ephapax#152 - hyperpolymath/affinescript#393 - canonical doc at hyperpolymath/nextgen-languages docs/disambiguation/ephapax-vs-affinescript.md (commit 2fcb55a) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Closed
3 tasks
hyperpolymath
added a commit
that referenced
this pull request
May 26, 2026
The `hypatia-scan.yml` wrapper landed in #66 pinned to `97df762107501909f50bb770e9bc200b6c415600` — the SHA of the hypatia-scan-reusable.yml commit on standards#193's feature branch. After standards#193 was squash-merged into standards/main on 2026-05-26, that feature-branch commit was orphaned (`gh api repos/.../compare/main...97df762` reports `status: diverged, ahead_by: 1, behind_by: 24`). GitHub Actions cannot resolve reusable-workflow references to orphaned commits, so every hypatia-scan run since #73 merged has failed at the workflow-parse stage with "This run likely failed because of a workflow file issue" — the run JSON shows `jobs: []` because no job is ever instantiated. The required check `Hypatia Neurosymbolic Analysis` (per branch protection on main) is therefore never produced, blocking every PR including #72 (proof-debt items 1-8) and #74 (items 7+8 deepening). Repin to `915139d73560e65a8240b8fc7768698658502c89`, the actual merge-commit SHA on standards/main. File content at this SHA is byte-identical to the orphan (`diff -q` returns empty), but the commit is reachable from standards/main, so the GitHub Actions runner can resolve it and the workflow's `scan` job actually instantiates. Estate impact: ~250+ repos across hyperpolymath/* pin the same orphaned SHA (verified via `gh search code "@97df762"`). This is a typed-wasm-local fix; standards-side closure of the estate-wide sweep is upstream work tracked separately under the reusables campaign (standards#215 closure doc, hypatia#336-339 detection issues). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
May 26, 2026
The `hypatia-scan.yml` wrapper landed in #66 pinned to `97df762107501909f50bb770e9bc200b6c415600` — the SHA of the hypatia-scan-reusable.yml commit on standards#193's feature branch. After standards#193 was squash-merged into standards/main on 2026-05-26, that feature-branch commit was orphaned (`gh api repos/.../compare/main...97df762` reports `status: diverged, ahead_by: 1, behind_by: 24`). GitHub Actions cannot resolve reusable-workflow references to orphaned commits, so every hypatia-scan run since #73 merged has failed at the workflow-parse stage with "This run likely failed because of a workflow file issue" — the run JSON shows `jobs: []` because no job is ever instantiated. The required check `Hypatia Neurosymbolic Analysis` (per branch protection on main) is therefore never produced, blocking every PR including #72 (proof-debt items 1-8) and #74 (items 7+8 deepening). Repin to `915139d73560e65a8240b8fc7768698658502c89`, the actual merge-commit SHA on standards/main. File content at this SHA is byte-identical to the orphan (`diff -q` returns empty), but the commit is reachable from standards/main, so the GitHub Actions runner can resolve it and the workflow's `scan` job actually instantiates. Estate impact: ~250+ repos across hyperpolymath/* pin the same orphaned SHA (verified via `gh search code "@97df762"`). This is a typed-wasm-local fix; standards-side closure of the estate-wide sweep is upstream work tracked separately under the reusables campaign (standards#215 closure doc, hypatia#336-339 detection issues). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
16 tasks
hyperpolymath
added a commit
that referenced
this pull request
May 28, 2026
…#90) The `hypatia-scan.yml` wrapper landed in #66 pinned to `97df762107501909f50bb770e9bc200b6c415600` — the SHA of the hypatia-scan-reusable.yml commit on standards#193's feature branch. After standards#193 was squash-merged into standards/main on 2026-05-26, that feature-branch commit was orphaned (`gh api repos/.../compare/main...97df762` reports `status: diverged, ahead_by: 1, behind_by: 24`). GitHub Actions cannot resolve reusable-workflow references to orphaned commits, so every hypatia-scan run since #73 merged has failed at the workflow-parse stage with "This run likely failed because of a workflow file issue" — the run JSON shows `jobs: []` because no job is ever instantiated. The required check `Hypatia Neurosymbolic Analysis` (per branch protection on main) is therefore never produced, blocking every PR including #72 (proof-debt items 1-8) and #74 (items 7+8 deepening). Repin to `915139d73560e65a8240b8fc7768698658502c89`, the actual merge-commit SHA on standards/main. File content at this SHA is byte-identical to the orphan (`diff -q` returns empty), but the commit is reachable from standards/main, so the GitHub Actions runner can resolve it and the workflow's `scan` job actually instantiates. Estate impact: ~250+ repos across hyperpolymath/* pin the same orphaned SHA (verified via `gh search code "@97df762"`). This is a typed-wasm-local fix; standards-side closure of the estate-wide sweep is upstream work tracked separately under the reusables campaign (standards#215 closure doc, hypatia#336-339 detection issues). <!-- SPDX-License-Identifier: MPL-2.0 --> ## Summary <!-- Briefly describe what this PR does and why. Link to related issues with "Closes #N". --> ## Changes <!-- List the key changes introduced by this PR. --> - ## RSR Quality Checklist <!-- Check all that apply. PRs that fail required checks will not be merged. --> ### Required - [ ] Tests pass (`just test` or equivalent) - [ ] Code is formatted (`just fmt` or equivalent) - [ ] Linter is clean (no new warnings or errors) - [ ] No banned language patterns (no TypeScript, no npm/bun, no Go/Python) - [ ] No `unsafe` blocks without `// SAFETY:` comments - [ ] No banned functions (`believe_me`, `unsafeCoerce`, `Obj.magic`, `Admitted`, `sorry`) - [ ] SPDX license headers present on all new/modified source files - [ ] No secrets, credentials, or `.env` files included ### As Applicable - [ ] `.machine_readable/STATE.a2ml` updated (if project state changed) - [ ] `.machine_readable/ECOSYSTEM.a2ml` updated (if integrations changed) - [ ] `.machine_readable/META.a2ml` updated (if architectural decisions changed) - [ ] Documentation updated for user-facing changes - [ ] `TOPOLOGY.md` updated (if architecture changed) - [ ] `CHANGELOG` or release notes updated - [ ] New dependencies reviewed for license compatibility (MPL-2.0 / MPL-2.0) - [ ] ABI/FFI changes validated (`src/interface/abi/` and `src/interface/ffi/` consistent) ## Testing <!-- Describe how you tested these changes. --> ## Screenshots <!-- If applicable, add screenshots or terminal output demonstrating the change. --> Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Adds a top-of-file [NOTE] admonition to README.adoc making it unambiguous that AffineScript and Ephapax — both of which target typed-wasm and both of which interface with `crates/typed-wasm-verify/` — are two SEPARATE, UNRELATED languages.
The shared `affine` syllable in both names is substructural-logic family terminology, not a project relationship. Ephapax is internally dyadic and contains an `ephapax-affine` sublanguage — that sublanguage is not AffineScript.
Why
AI agents have repeatedly conflated AffineScript with Ephapax (or with Ephapax's internal `ephapax-affine` sublanguage). The two repos share zero AST / typing / borrow-checker / codegen — they meet only here, at typed-wasm. Workers on `crates/typed-wasm-verify/` in particular need to know that the agreement theorems against each consumer are independent.
Companion PRs
Test plan
🤖 Generated with Claude Code