Skip to content

Confirmed-bar receipt: versioned metadata from lowering decisions - #173

Merged
luisleo526 merged 8 commits into
mainfrom
lv/fu12-admit-proven
Oct 5, 2026
Merged

luisleo526 merged 8 commits into
mainfrom
lv/fu12-admit-proven

Conversation

@luisleo526

Copy link
Copy Markdown
Contributor

Summary

Adds an independently versioned confirmed-bar receipt to generated strategy libraries. It is metadata only: generated trading code is unchanged.

  • New exports strategy_confirmed_bar_api_version() (version 1) and strategy_confirmed_bar_receipt(...), using the same immutable buffer protocol as the existing capability receipt.
  • The JSON has version, requests (including the requested expression), sorted orders classifications, and intrabar_persistence.
  • Feed classification comes from the emitter's own lowering decisions (its foreign / heikinashi flags), not from symbol text. Symbol "" is a foreign-feed requirement. Constant timeframes and single-call helper clocks resolve from static registration metadata; runtime, input and mutable timeframes stay unresolved.
  • Order metadata is an allowlist of modeled strategy calls and arguments. Risk rules, unmodeled order arguments, and account, sizing or slippage declarations outside the tested profiles are marked unproven.
  • The original capability receipt is unchanged. Old runners ignore the new symbols, and a new runner paired with an old library keeps its original policy.

Availability: unreleased (after 1.2.0). This is paired with the engine PR that adds the runner's admission policy. Merge this one first: its symbols are additive, and older engines ignore them.

Evidence

  • Generated trading outputs for all 325 corpus sources are byte-identical to main.
  • The compiler test suite, corpus compilation and the parity gate pass on this head, with one exception: test_committed_host_members_are_the_derived_set (set_recorded_series) fails identically on unmodified main.

🤖 Generated with Claude Code

@luisleo526
luisleo526 merged commit 0fe4b1f into main Oct 5, 2026
9 checks passed
@luisleo526
luisleo526 deleted the lv/fu12-admit-proven branch October 5, 2026 13:04
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant