This tree holds cross-repo proposals produced during AffineScript co-development that target a repo other than affinescript. They are staged here — as real, diff-able files — because the working agreement for this session is writes go to the affinescript repo only; everything destined for idaptik, echo-types, standards, etc. is parked here for human review before it is applied to its home repo.
Each subdirectory is a self-contained proposal with its own README.adoc
explaining what it is, where it belongs, how it was verified, and how to
land it.
| Subtree | Target repo | Status | What |
|---|---|---|---|
|
|
Verified |
|
|
|
Verified |
Two worked, verified coprocessor ports + one honest non-port:
|
|
|
Drafted |
Estate-standards implications with drafted normative text: the
integerization + differential-parity acceptance bar (AS-MIG-1/2), the
String host-boundary ABI spec (AS-ABI-STR-1), the github-only install
recipe (EST-CI-NET-1), the |
|
|
Drafted |
Six compiler/toolchain findings: the variable-string-backend gap (#1
leverage), compiler-emitted |
The frontier-practices guide development is first-class affinescript
content, so it landed directly (not under proposals/):
-
docs/guides/migration-playbook.adoc— the systematic Co-processor Integerization chapter (six named, verified patterns + pattern index). -
docs/guides/frontier-guide.adoc— conceptual Chapter 9: The Co-processor and the Integer. -
docs/guides/frontier-programming-practices/AI.a2ml— the machine-readable companion stanza (the bot-loaded session-start file), so AI agents get the same patterns humans do.
Three reasons, all from the session’s working agreement:
-
Review gate. The owner wants to review anything touching repos other than affinescript before it lands.
-
Honest provenance. A staged proposal records exactly how it was produced and verified, so the receiving repo’s maintainer can re-run the checks rather than trust a claim.
-
No silent cross-repo drift. Estate policy (see the standards repo’s license + no-automated-edits guardrails) is firmly against bulk cross-repo sweeps; per-repo human acceptance is the rule.