Only retirement mutates the repository.
Adaptive software building
One goal. A living plan. Small blocks that keep moving.
Solana keeps the real outcome fixed while its strategy adapts. Sol plans, Luna implements, independent evidence decides, and one authority safely integrates the result.
Goal contract
Preserve intent
Execution strategy
Adapt from evidence
Disjoint blocks overlap when resources allow.
Every stage resumes independently.
Capacity metric only—never a quota or reason to discard work.
Architecture explorer
The same system scales from one fix to a huge product.
Pick a goal size. The graph changes, but every runnable leaf keeps the same safety contract.
Small fix
One block, no ceremony
One honest goal
Must-have outcomes remain traceable to proof.
One reusable block
Frontend and backend are facts, not separate runtimes.
One retirement authority
Many agents can work; only one boundary integrates.
Adaptive goals
Change the strategy, not the truth.
Failed evidence rewrites only the affected future. Valid accepted work keeps moving.
- 01Repair precisely
Use the rejected candidate and exact evidence when it remains safe.
- 02Split the block
Reduce one oversized or confused outcome into fitted leaves.
- 03Reroute capabilities
Add diagnosis, contract, visual, security, or performance proof only when needed.
- 04Replace the strategy
Change a library, algorithm, architecture boundary, or implementation approach.
- 05Revise optional scope honestly
Only the product contract can justify a tradeoff. Throughput metrics never can.
No reimplementation and no repeated proof.
Rerun evidence without asking Luna to rebuild.
Repair from the candidate when its lineage is safe.
Independent siblings continue through the pipeline.
Pipeline execution
Five stages, occupied at the same time.
Planning can prepare tomorrow's blocks while Luna builds one, verification judges another, and retirement promotes a third.
1Fetch
Select the highest-value compatible block.
Quick settings fixforeground
2Decode
Pin context, contracts, claims, and proof.
Session recoverycontext ready
3Execute
Luna writes inside an isolated worktree.
Tab lifecycleLuna lane 2
4Verify
Run focused evidence against the candidate.
Navigation shellbrowser proof
5Retire
Integrate once and update requirement truth.
URL loaderqueue position 1
Initial local envelope
Fast where independence is real.
Three is a ceiling. Solana lowers concurrency when work conflicts, evidence backs up, or the computer is under pressure.
Interrupt
Foreground
Background
Maintenance
Implementation
Implementation
Reserved when useful
One exclusive session
One repository authority
Composable capabilities
No mandatory frontend-to-backend conveyor belt.
A block takes only the path its evidence and risk require.
Symbols, nearby contracts, tests, and current behavior.
Used only when the repository cannot resolve an ambiguity.
High-fan-out decisions become accepted artifacts first.
One outcome and one primary write domain.
Focused leaf checks, broader milestone evidence.
Added at architecture, security, visual, and release boundaries.
Deterministic outputs tied to exact accepted source.
Exclusive lease, smoke proof, and rollback evidence.
Multiple Solanas
Many systems can work. Authority stays singular.
Scale execution outward without allowing two controllers to mutate the same repository.
Invariant
Many systems may think and execute; one named authority retires each resource.
Capacity, measured honestly
20–40k is an instrument panel—not the destination.
The benchmark tells us whether planning, execution, testing, and retirement are flowing. Missing it starts a bottleneck investigation. It never changes product scope or the meaning of complete.
3Luna lanes
×
2–3blocks / hour
×
250–400accepted lines
18–43kmodeled range over 12 hours
Generated, copied, vendored, duplicated, and formatting-only lines are excluded.
Build order
Prove the idea before trusting it.
Each phase earns the next one with running evidence.
Planning kernel
FirstGoal contract, ledger, recursive expansion, fit gate.
Path and scheduler simulation
PlannedCapability routes, hazards, priority, machine pressure.
Durable stage engine
PlannedCrash every boundary and prove exact resume.
One live Sol + Luna block
PlannedSmall real canary, one accepted retirement.
Adaptive parallel pipeline
PlannedThree lanes, rejection split, and quick-fix priority.
Cross-capability product
PlannedUI, API, responsive proof, and combined integration.
Endurance benchmark
PlannedTwelve hours, failures, restarts, and honest throughput.
Satellite federation
LaterRemote immutable execution and multi-workspace contracts.
The shortest version