Repository navigation
License: the PineForge Source License 1.2; a funded-trader challenge, evaluation or simulated account is not Personal Trading and is investment capital - #177
Merged
Conversation
luisleo526
force-pushed
the
docs/source-license-1-2
branch
from
October 5, 2026 14:49
42f9c12 to
073b674
Compare
luisleo526
changed the title
luisleo526
force-pushed
the
docs/source-license-1-2
branch
2 times, most recently
from
October 5, 2026 14:55
073b674 to
39a61c3
Compare
… evaluation or simulated account is not Personal Trading and is investment capital The licensor decided on 2026-10-05 that an account a proprietary-trading firm or funded-trader program provides or allocates is not Personal Trading, its challenge, evaluation and simulated accounts included, and that trading such an account is Commercial Use. The last bullet of the Personal Trading section spoke only of "capital" that a program "provides or allocates", and "investment capital" meant money or other assets, so a challenge, evaluation or simulated account holding simulated capital was left open on both counts. 1.2 closes that, and changes nothing else: - Personal Trading, last bullet: an account that a proprietary-trading firm or a funded-trader program provides or allocates to the person to trade, including a challenge, evaluation or simulated account, whether the capital in it is real or simulated, is likewise not the person's own account and is not funded by the person's own capital. - Commercial Use, "Investment capital": the capital in such an account is investment capital whether it is real or simulated, so trading it, or researching, developing or backtesting strategies for it, is Investment Management, which is Commercial Use for every individual. - A dated paragraph under the title says what 1.2 changes against 1.1. - Every other section, the Required Notice line included, is unchanged. Surfaces: the LICENSE header, change paragraph, bullet and definition; README (name, the Personal Trading and Investment management bullets); LEGAL.md (name, the Personal Trading and Investment management bullets, and the history lines: the PolyForm sentence made version-neutral, and 1.1 replaced 1.0 while 1.2 replaces 1.1 for the code on main and in future releases); AGENTS.md and CLAUDE.md; and npm/README.md (version 1.1 in release 1.2.0, version 1.2 in later releases). Releases up to and including 1.2.0 keep the license text they shipped with. The pyproject.toml comment still names 1.1; it is left for a change outside the docs-only route. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
luisleo526
force-pushed
the
docs/source-license-1-2
branch
from
October 5, 2026 23:45
39a61c3 to
792f40c
Compare
luisleo526
added a commit
that referenced
this pull request
Oct 6, 2026
* docs: changelog and version scoping for 1.3.0 1.3.0 pairs only with engine v1.3.0. The changelog section takes in the Unreleased note and covers #173, #178, #179, #177, #174 and #175: the confirmed-bar receipt and what engine v1.3.0's live runner does with it, the capability receipt's request entries now read from the lowering, the order-shapes receipt, which no engine reads yet, the checked settings fix for string dropdowns with built-in constants (now supported=false where 1.2.0 wrote an integer code or published the input as supported), the PineForge Source License 1.2, and the pairing and migration steps. The Python and JSON contract is unchanged; the engine's report harness is the same file as in v1.2.0, so no report key changes. The README, AGENTS.md / CLAUDE.md, CONTRIBUTING.md, LEGAL.md, docs/PUBLIC_CONTRACT.md, docs/pine-cap-activation.md and npm/README.md name 1.3.0 where they named 1.2.0 as the current release or pair, the pairing table gets a 1.3.0 row, the "unreleased (after 1.2.0)" markers name 1.3.0, and the license badge reads 1.2. The release scoreboard sentence and the pf markers are left to the release lane. Measured for 1.3.0: the engine's 325 corpus sources and the 277 gate fixtures, each in a fresh process, transpile to 1.2.0's C++ byte for byte once the confirmed-bar and order-shapes functions are removed (13 refusals, same messages), with transpile_full results and transpile_json envelopes without cpp equal to 1.2.0's, each in under 0.1 s on CPython 3.14.6 on an Apple M4 Max. The tutorial run of the quick-start C++ against engine main 7a1f01c0 (Linux x86_64, GCC 13) prints 9 trades and +738.20, and 13 trades with the old sizing declared, as 1.2.0 with engine v1.2.0 does. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> * docs: release 1.3.0's grades in the README and the changelog, from the facts tokens The README's release sentence moves to the releases[1.3.0] tokens and its main-scoreboard lines re-render, and the 1.3.0 changelog says which registry baseline grades the release and why that baseline is the release's code, all rendered from pineforge-release facts/facts.json at ff21de0 (#32). Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> --------- Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
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.
What
The PineForge Source License moves from 1.1 to 1.2. Two terms change, both about an account that a proprietary-trading firm or funded-trader program provides or allocates to a person (a funded account, and its challenge, evaluation and simulated forms):
Until now the bullet spoke only of "capital" that a program "provides or allocates", and "investment capital" meant money or other assets, so a challenge, evaluation or simulated account holding simulated capital was left open on both counts. The licensor decided on 2026-10-05 that such an account is not Personal Trading and that trading it is Commercial Use.
Nothing else in the LICENSE changes. The four LICENSE hunks are the title, a dated paragraph under it that says what 1.2 changes against 1.1, the Investment capital definition, and the bullet.
Files (6, all Markdown or
LICENSE)LICENSE: the title, the dated change paragraph, the Investment capital definition, the bullet.README.md(License section): the version in the link text, and the Personal Trading and Investment management bullets carry the same two points.LEGAL.md: the version; the Personal Trading and Investment management bullets; the history paragraph (1.1 replaced 1.0 and 1.2 replaces 1.1 for the code onmainand in future releases; release 1.2.0 was published under 1.1 and keeps that text); and the PolyForm sentence no longer names a version.AGENTS.md,CLAUDE.md: the version in the one-line description of the repository.npm/README.md: the package'sLICENSEline (version 1.1 in release 1.2.0, version 1.2 in later releases).Not in this PR
pyproject.tomlstill has a comment naming 1.1. It is not a documentation file, so it waits for a later non-docs change. The build readslicense = { file = "LICENSE" }, so a package built frommaincarries the 1.2 text regardless.CHANGELOG.mdkeeps the 1.2.0 history as it is (1.2.0 shipped under 1.1). The next release's notes will say that it is the first release under 1.2.How it is gated
Only Markdown files and
LICENSEchange, so this is a documentation/legal-only PR. The installedgateworkflow classifies the head as docs-only, skips the differential gate and the pytest matrix, and reports the requiredgatestatus itself. Expectgate: success("docs-only preflight+docs; no sweep"), withdifferentialandpytestskipped.Checked
git diff --checkis clean, no file mode changes, and the new LICENSE lines are ASCII and at most 78 columns..github/pineforge/ci/codegen-docs-check.mjs, run locally on this head againstmain:accepted: true, six files,docs_only=true.🤖 Generated with Claude Code