forked from kmccleary3301/nested_learning
-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationexecution-boardExecution board ticket set for paper alignmentExecution board ticket set for paper alignment
Milestone
Description
NL Paper-Alignment Execution Board
This is the execution tracker for milestone NL Paper-Alignment Execution Board.
Project board: https://github.com/users/georgepullen/projects/1
Mandatory Protocol (applies to every linked ticket)
Before coding, the assigned agent must post a first comment proving they read:
reports/NL_IMPLEMENTATION_ORACLE.mdreports/paper/NL-print.extracted.clean.txt- Ticket-specific required docs/code listed in that ticket
The first comment must include:
- Oracle summary relevant to the ticket.
- Paper equation mapping relevant to the ticket.
- Exact files they will modify.
- Risks and non-goals.
No implementation work should begin before this comment.
Active Queue
Phase 0
- Phase 0: Establish canonical paper-faithful baselines and lock reference metrics #1
- Phase 0: Add fidelity telemetry validator and metadata gates #2
Phase 1 (optimizer equation fidelity)
- Phase 1: Implement Eq. 21-22 delta-rule momentum variant #3
- Phase 1: Implement Eq. 23 DMGD with MLP-parameterized momentum #4
- Phase 1: Implement Eq. 24-style Newton-Schulz inner momentum variant (muon_ns) #5
Phase 2 (CMS + regression gates)
- Phase 2: Implement Eq. 28-29 CMS projection optimizer path #6
- Phase 2: Add equation-level fidelity regression suite for optimizer and CMS updates #7
Phase 3 (training semantics)
Phase 4 (distributed parity)
Phase 5 (RunPod execution + scale)
- RunPod: Add reproducible pod setup, storage, and checkpoint-resume playbook #10
- Phase 5: Run RunPod pilot ablation matrix (5k/25k) for paper-fidelity paths #11
- Phase 5: Execute mid/target faithful runs and publish final alignment report #12
Board Rules
- One major phase active at a time unless blocked by infra.
- Every ticket closure must include:
- exact commands run
- checkpoint paths
- eval JSON paths
- acceptance criteria evidence
- Any deviation from oracle/paper must be explicitly documented in ticket comments.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationexecution-boardExecution board ticket set for paper alignmentExecution board ticket set for paper alignment