BANTAM FACTORY / fight card
Context packet.
Fit complete, attributable context sections into a strict UTF-8 byte budget.
The recorded factory floor
Meet the contenders.
Astra directs. Terra or Sol builds.
Both roles included in the totals.
Choose a pair. Open its work.
Bars show elapsed time against the longest recorded run, not percentage of work completed. Token counters advance only when a saved response supplies them.
Recorded system comparison
Context packet
| System | Outcome | Time | Groups | Project accepted | Clean finish | Input | Output | Cached input | Fresh input | Scope |
|---|---|---|---|---|---|---|---|---|---|---|
| BANTAM FACTORY · AstraGPT-6 Astra · wrapped CLI | PASS | 98.6s | 5/5 | Yes | Yes | 40,728 | 2,772 | 27,776 | 12,952 | Recorded totals |
| Codex · AstraGPT-6 Astra · native CLI | PASS | 102.4s | 5/5 | Yes | Yes | 75,244 | 2,932 | 60,288 | 14,956 | Recorded totals |
| BANTAM FACTORY · Astra → TerraGPT-6 Astra → GPT-5.6 Terra · supervised factory | PASS | 228.3s | 5/5 | Yes | Yes | 523,875 | 7,513 | 434,944 | 88,931 | Recorded totals |
| BANTAM FACTORY · Astra → SolGPT-6 Astra → GPT-5.6 Sol · supervised factory | PASS | 192.6s | 5/5 | Yes | Yes | 99,562 | 4,888 | 46,464 | 53,098 | Recorded totals |
Qualification historyProgress includes the misses.0 local editions +
Selected qualification editions, not every development experiment. Earlier included failures are retained. These are separate attempts, not repeated trials of an unchanged system. An unrecorded task is not a failure.
Method & evidenceThe work order and run conditions.Read the method +
The recorded comparison
1 included work order: BUILD — Context packet (repeat 1). 4 systems and 4/4 recorded attempts. Every arm receives the supplied materials for its work order; independent acceptance checks remain separate from worker tests.
Astra supervises a BANTAM Terra or Sol worker. Mixed-model lanes include both roles in their token totals. Native and wrapped single-model lanes are also shown. All included outcomes remain visible; missing results are not zero-cost runs and do not count as passes. Elapsed times and completion status are reported separately.
These are selected development work orders. The original and follow-up recording windows, model settings, tool policies and time limits are documented with each card.
Reading an outcome
PASS: project accepted and clean harness completion. OUTPUT_ONLY: the artifact passed but the run did not reach accepted completion. FAIL: a required check failed. Timeouts and unrecorded tasks remain visible.
Passing independent groups alone does not override a failed public suite or protected-file check. Accepted project and clean finish are separate facts. The independent groups check the supplied work order.
Clocks & counters
Replay aligns each run's recorded start to zero. Runs did not all start simultaneously. Counters use actual saved response times, not animated estimates. Untimed evidence is not assigned an invented timestamp.
Input includes cached input; fresh input excludes cache hits. These three numbers are not additive. Partial metering displays only the measured subset, with coverage disclosed. Unknown never means zero. Native reports and server windows are overlapping scopes, not extra tokens.
The recorded work
The measurement download contains the task identity, outcomes, timings and token receipts used by this page. Reviewed work records provide the associated actions, checks and delivered files. Qualification history contains selected editions, not every development experiment; earlier included failures are retained.
The page runs without telemetry. Source hashes bind the displayed measurements to their saved records.
Source summary SHA-2563e510539621bfe7ec97faa5d1958dce35e2cfab58c6eaec87f2a2ea1dd9fe827
Put your model to work.
Your model.
A better factory.
Recorded results, ready to explore.