Repository navigation
[IGLA-Coder] P6 Scale-up to deployable 0.5B-1.5B (budget-gated) #1039
Description
Part of epic #1032 (IGLA-Coder). Plan: t27_coder_model_plan.md P6. BUDGET-GATED ($10K-50K) -- requires explicit approval.
Goal
Scale the winning recipe to a deployable 0.5B-1.5B model.
Sub-tasks
- P6.1 Scale to 0.5B (then 1.5B if budget allows), ~500B-1T+ tokens, with annealing.
- P6.2 SFT for code: Evol-Instruct / OSS-Instruct-style synthetic instructions, multi-language directed, verified-execution filtered.
Done when
Instruct model beating the pilot on MultiPL-E + the t27-native eval.
Decision point: explicit compute-budget approval required. If $0, stay at P4 pilot scale (still a real, publishable artefact).
Anchor: phi^2 + phi^-2 = 3
Activity
fix(rtl): R-SI-1 compliance — barrel shifters + Wallace tree multiplier
fix(build): resolve P0 build failure — Cyrillic purge + HeaderValue i…
fix(infra): P0 infrastructure hardening — duplicate workflows, Coq al…
fix(ci): Coq workflow rename + infrastructure cleanup
gHashTag commentedon Oct 7, 2026
Reopened 2026-10-07: the bulk close of issues without a
## Boundarysection was reverted by the owner. Nothing to do here; this comment replaces the earlier close notice.tri-claw commentedon Oct 9, 2026
The Queen cannot take this issue yet. A bee starts only on an issue whose body has every section below, and this one lacks:
- specs/x.t27); without it the Queen reserves nothing and no bee can take the issueFR-001: ... MUST ...exit 0, or a backticked commandShe tried to write them 2 times and could not (last: not a task: This issue describes a model training/scaling task (P6 scale-up to 0.5B-1.5B parameters with specific compute budget) that does not correspond to any files in the t27 specification repository. No .t27). Add them and the next round takes it. The rule is
specs/policy/issue_shape.t27.