Skip to content

Auto-update meta.yaml files - #141

Open
github-actions[bot] wants to merge 11 commits into
mainfrom
auto/update-meta-yamls
Open

Auto-update meta.yaml files#141
github-actions[bot] wants to merge 11 commits into
mainfrom
auto/update-meta-yamls

Conversation

@github-actions

Copy link
Copy Markdown

This PR was automatically generated by a GitHub Action to update meta.yaml files.

@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 4 times, most recently from b477acc to dc4455f Compare March 19, 2026 14:23
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 6 times, most recently from edbd55b to 45bdc45 Compare March 27, 2026 22:12
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 3 times, most recently from 57164a8 to dc25c70 Compare April 3, 2026 11:50
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 6 times, most recently from 62de42c to d36a953 Compare April 22, 2026 15:56
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 3 times, most recently from e218b1b to 21c25ac Compare April 29, 2026 23:10
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch from 21c25ac to fe258a6 Compare May 2, 2026 01:42
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 5 times, most recently from 29ffeff to effe882 Compare May 22, 2026 00:11
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch from effe882 to 5067075 Compare May 23, 2026 12:52
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 5 times, most recently from aaa5a94 to b095ef5 Compare June 9, 2026 16:51
@lornecodes
lornecodes force-pushed the auto/update-meta-yamls branch from b095ef5 to 6b519c1 Compare June 10, 2026 00:42
@github-actions
github-actions Bot force-pushed the auto/update-meta-yamls branch 12 times, most recently from 3d81deb to 54b6f91 Compare June 14, 2026 01:26
pgroom2 and others added 11 commits July 17, 2026 14:56
…neral-k limit (K1 vs K2)

Registered before any data: ADE-cascade round 1 (diagram selectivity,
affine-vertex reading of the k-1 offset, mode-count bridge) with locked
decision rules and inconclusive branches per the midnight invariant-
registration discipline; M15 exp_05 K1 (odd-harmonic, 46/15 and 352/105)
vs K2 (Fibonacci, 21/8 and 55/21) discriminator with k=2 anchor gate.
No ADE-coupling cascade and no k>2 holonomy has been run as of this commit.
…d scripts; exp_00 gate PASS

energy_cascade gains optional coupling_matrix (default bit-identical to
legacy; verified G1 kernel identity 0.0, G2 per-scale diff 0.0, G3
baseline -1.6126 vs -1.6083 ref) and records psd_shift per scale (threat
T1). coupling.py: graph-distance kernels on Dynkin diagrams reusing
milestone12 DynkinDiagram + milestone15 build_cycle. exp_01/exp_02
implement the locked R1/R3 and R2 rules; code committed before any
registered arm has been run.
… exp_05 both candidates dead, F6/F4 retired

R1: diagram topology sets the exponent at equal rank (E<D<A at ranks 6-8,
separations 20-90x CI half-width). [D] the legacy engine's 3.3% miss of
-5/3 is an A-family artifact: D_8 = -1.6624, 0.26% from Kolmogorov.
R2: affine-vertex reading of k-1 KILLED per registered rule (median
rho=0.91, direction reversed — cycle closure steepens). R3: mode-count
map survives kernel swap. exp_05: anchor 8/3 to 6e-8; L3=5.4913,
L4=11.1863 kill both K1 (odd-harmonic) and K2 (Fibonacci) — general-k
limit OPEN, no post-hoc fit; Z2 even-telescoping universal (det H=+1).
Anchor gate caught+disclosed a sign-convention instrument bug (VOID run
recorded in results).
…(Q1 2e-15, Q2 4e-9, Q3 1.1e-8)

Vorticity-streamfunction, 2/3 dealiased, RK4, backend-agnostic (numpy
now, torch swap = GPU port). Taylor-Green exact to machine precision;
energy budget closes to 4e-9; resolution-consistency on the common
resolved band to 1.1e-8, with the gate-design history (two rejected
wrong-test variants) documented in the script. Instrument qualification
only -- no physics claims at v0; registered measurement runs follow on
the 3090.
…tration (before run)

Derivation (developed after exp_05 data, disclosed): the general-k limit
generator is G[j',j] = 4jj'/(j'^2-j^2) for odd j'-j — the box momentum
matrix element, parity selection rule included. Explains the K1/K2 double
death (L_k leaves Q for k>=3: L3 = 8*sqrt(106)/15). Registered exp_06
predictions L5=17.010952, L6=25.778092 with 0.1% CONFIRM / 1% KILL rule;
committed before any k=5,6 computation.
…tum operator; general-k limit solved

Anchors reproduce k=2,3,4 to ~5e-8; registered predictions L5=17.010952,
L6=25.778092 confirmed at 6.7e-7 / 1.1e-6; entrywise generator match to
~1e-5 at m=2000 (up to diagonal gauge). Curvature of the complement-frame
connection = momentum; parity selection rule = local face of the Z2 whose
global ledger is det H = +1 (SEC-local/PAC-global in miniature).
…v1.2)

Propagates the audit corrections (Xi-in-NS, MED-NS proofs, pac_dag_fluid,
She-Leveque beta renaming, exp_15 800x->1063x, A-family artifact / D_8,
F6/F4 retirement + momentum-operator resolution) into the living registry;
lists the three preprints still carrying uncorrected claims as open,
pending owner review.
The prior-formulation preprints are the earlier layer of the lineage,
not drift to fix; corrections are layered forward per the Imperfection
Engine. Revising them is the author's call, not required for correctness.
…clarative to registered-open conjecture

Adversarial panel review (2026-07-17) caught a declarative leak in the
Consequences section: 'same object under two boundary twists' asserted
what is an open conjecture conflating three distinct Z2 candidates and
p-hat with p-hat-squared. Amended to conditional with the cutoff
arithmetic on record: 1+pi/55 = 3/(2N*) exactly at non-integer
N*=3F10/2pi=26.2606; integer-N spectral ratio tends to 1. The
registrable question is stated. Own-draft fix on the unmerged branch,
disclosed here.
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.

2 participants