Versions and source pins¶
Every claim on this site is relative to a commit. This page lists them all, so a reader never has to hunt through pages to reconstruct what "current" meant.
Repositories are private. The identifiers below are meaningful to anyone with source access and are recorded here so that claims remain checkable and falsifiable rather than merely asserted.
Application sources¶
| Component | Reference | Commit | Tree |
|---|---|---|---|
| Frontend | origin/andrew |
99f49dae6368414896bf2858cb848f5a7c7fcf98 |
19cde0416b5fad4898f1256574b2b3f148fafa56 |
| Backend (handoff) | origin/andrew = origin/main |
efa38e04e2db37a444e9f17100323c2ad4b83647 |
0e7275ae5f0e66a9e6acd04e81837ff1a0565820 |
| Backend (functional source) | — | f80bc316ca01e9ea68a77ad6fd2ca0efe89ee7ba |
97d85d899d0240fc7c73483d68e206631ea78576 |
| macOS client | origin/main |
984bdf6cb7b7fe187931665a4b8d022bae8330d9 |
0d93fcf96ffda208fbafb314a7ee863ac68e6787 |
The backend carries two pins because the handoff commit is the release-facing reference while the functional source commit is where the code being described actually lives. Pages cite whichever one they read from.
iOS: two candidates, no canonical reference¶
The iOS client has no canonical repository reference. This is an open blocker, not an omission.
| Candidate | Commit | Tree |
|---|---|---|
| A (earlier) | 9ce6595cebe8c77660f02a00be5c7a97ddcd72e1 |
bdc3f2c66be72957043d58037474f02a65b2e668 |
| B (later, local) | 85cbdf09499ed3f5c3c37fb6ace34f8926e741f5 |
fa9f9699254873bd4b72d4eab047ce43e0be5c2f |
Neither is promoted as authoritative. iOS pages are badged accordingly and state which candidate any given claim came from. See the iOS client.
Upstream¶
| Item | Value |
|---|---|
| Package | nautilus-trader |
| Version | 2.0.0rc3 |
| Official tag | v2.0.0rc3 |
| Tag commit | 648970ce64a304d93da0a29320cb6e19b905fa39 |
| Tag tree | 7f9b3aaf4f550a3eba854875ff5eaeb05c6b6b99 |
| Documentation | https://nautilustrader.io/docs/ |
ONIX runs at least one private modification of upstream that is not publicly distributed. It is documented only as a support boundary — what area differs and what that means for expectations — and never as an artifact. See the NautilusTrader boundary.
Contract surface¶
| Item | Value |
|---|---|
| Schemas in the accepted set | 58 |
| Schema-set SHA-256 | 28fdebfb5b5a318455dacdff4375deb77237dc5a1d56ab26238cd27f59c2ec42 |
| Vendored contract manifest SHA-256 | 37aa9aff837628208ca8e668261f4c6274b364bc39b66b24fc6a51a57207c843 |
| Vendored payload file count | 63 |
| Frontend pin authority | scripts/engine-pin.mjs, blob c3fc8e051ab9c413d0691961e2871f595774f9ac |
| Frontend contracts tree | 1428be4c299fb20789704222740909af49acb213 |
| Vendored contract tree | 562264ae4767908019e289a3ec3fae88a6ef7e73 |
| Vendored schema tree | ac8ac60a5515520da17c4ebca13fd3701869c70b |
| Accepted backend handoff | efa38e04e2db37a444e9f17100323c2ad4b83647 |
| Accepted backend handoff tree | 0e7275ae5f0e66a9e6acd04e81837ff1a0565820 |
| Accepted backend functional tree | 97d85d899d0240fc7c73483d68e206631ea78576 |
| Accepted backend artifact SHA-256 | 1edc98c82751b8df8564e7a01b5d635735be8629a8fa310977bc7341e3425b4e |
| Backend development lock | python/uv.lock, blob 2ab0bac2e8d674afeb8b5f39e9d298390665eb44 |
A frontend build whose declared contract does not match this set fails at build time rather than at runtime. See gateway and schemas.
Tracked production record¶
Record, not observation
The values below describe what the repository states production is meant to
be running. No live host was observed during this documentation pass, and
no external deployment ledger was read. Pages that depend on this record carry
the Production record badge, which is a weaker claim than Verified.
The authority record itself¶
| Item | Value |
|---|---|
| Path | feature-state/rc3-data-plane-frozen-current-production.yaml |
| At commit | efa38e04e2db37a444e9f17100323c2ad4b83647 |
| Git blob | 46266982a7c162f9358e527db6bc145855736f24 |
| SHA-256 | 60cb49477d2edad465bcb64b486e2f54e11c145c0bfb066383db73a264041fcc |
| Declared state | CURRENT_PRODUCTION |
Backend release chain¶
| Item | Value |
|---|---|
| Release merge commit | 108403e73a14b461957120d378a56f0804688667 |
| Release merge tree | 6c7b6e6c14311b633f001a1db1377beaaeda4804 |
| Functional commit | bdde20b6715e49805889b6d24fe0bca6fa0f0c4d |
| Functional tree | 6c7b6e6c14311b633f001a1db1377beaaeda4804 |
| Artifact SHA-256 | e2bc5627498074e3e26c064adfe70068c3f5a3663773b5f5f3a392f2a79f8c81 |
| Activation manifest | deploy/activation.json, blob 62c4448fc4d050a4709e2c6656f9dc80fc89dbfe, SHA-256 6115917b948e300571ff9c099dbecbd29876a342c88e09f3e87bc0951a0f043a |
| Activation semantics | Bybit only |
| Retained-ingestion manifest | deploy/retained-ingestion.json, blob 518832eba54db29db255d1e154c9aefe414ef7a5, SHA-256 081509754b6db270f8250790404fb2cebe30427003ee98dafe124ee9d7eb309e |
| Retained-ingestion version | manifest version 5, epoch 1 |
| Dependency lock | python/uv.lock, blob 11be1ac32864a9dd6ca9e96329b3f0fd1605e8fd, SHA-256 bb6956be1425d1900996f19a457c6c35b596a2d4464c74a6d259b74688d01690 |
Frontend release chain¶
| Item | Value |
|---|---|
| Release commit | e1d4de0e2d0d3a7cc3e7f294012c8f84818ad3b6 |
| Release tree | 949b01a19cc3a6c084ddedcc050ec28ecf7d8be9 |
| Artifact SHA-256 | a2f74ac82af0c37dd2f64ac812a31289da17244fa9a2ee193c670a8099ea54a7 |
Where the chain stops¶
| Item | Value |
|---|---|
| External receipt id | RC3-DATA-PLANE-FROZEN-GREEN-20260825T052738Z |
| External receipt SHA-256 | 4f0cfb3e6efc12917a2b6f928c34f8725ffc8b99743876af56e17ae1160895f6 |
| Receipt bytes tracked in the repository | no |
| Deployment ledger read | no — the ledger lives at an operational path that is not published |
| Live host observed | no |
The chain above is complete up to the point where it leaves the repository. The last link — an external receipt attesting that a host actually activated this release — is named by id and hash but its bytes were never read, so the chain is recorded as unclosed at the deployment boundary rather than presented as proof of a running system.
Development pins are not production¶
The development pins carry a different activation set and a later ingestion manifest version — Bybit, Hyperliquid and Binance at manifest version 8 — against production's Bybit-only manifest version 5. That is development intent, not deployed reality, and this documentation never presents it as the latter. See runtime and deployment and the venue capability matrix.
This documentation set¶
| Item | Value |
|---|---|
| Site | https://docs.onixlab.ai/ |
| Repository | onixlab-ai/onix-docs (private) |
| Generator | Material for MkDocs, dependencies pinned in requirements.txt |
| Immutable classification input | 61-row disposition matrix, SHA-256 393a8c5818de5ce294c4d3cf796d70b6e092bb3dbab135ebf73b573bbb6eb1d3 |
| Published pages | 58 |
| Legacy pages accounted for | 61 of 61 — 34 published, 9 merged, 3 retired, 1 split, 14 quarantined |
| Fully closed | 45 |
| Closed with an open blocker | 2 — rows 2 and 42 |
| Silently dropped | 0 |
Two rows are published but not fully closed, and the contract says so rather
than rounding up. Row 42 depends on an unambiguous iOS repository reference that
does not exist, and row 2 asked for observed stream evidence before any
present-tense claim, which a documentation pass that started no process cannot
supply. Both are named in manifest/page-route-contract.json under
open_blockers.
A1 also asked, on most rows, for a named repository owner's sign-off. There were
no separate repository owners in this pass. What was produced instead — per-lane
evidence packets bound to Git blob ids, plus an independent verification and
disclosure challenge — is recorded once in the contract under owner_signoff,
with obtained: false. No page on this site claims an owner approved it.
The build is deterministic and is run twice with its outputs compared before any release. See the documentation platform.
How to use this page¶
If a claim elsewhere on the site matters to you, take the pins from that page's status strip, find them here, and read the source at exactly those commits. If the pins on a page are older than the ones listed here, the claim has not been revalidated at the current pin and should be treated as provisional — that is tie-break rule 5.
Evidence and source pins for this page
Verified. Current behaviour, confirmed in source at the pinned commit.
Verified on against the following immutable sources:
frontend@99f49dae:scripts/engine-pin.mjsbackend@efa38e04:docs/handoff/contract-manifest.jsonbackend@efa38e04:feature-state/rc3-data-plane-frozen-current-production.yaml
Status tokens are defined on the documentation and status model page. Every pin on this site is listed under versions and source pins.