HONESTY
On the record, even when it hurts
Roadmap steps carry their real status rather than their intended one. Seven code-versus-spec divergences are listed instead of quietly patched. An admission of weakness is treated as information.
About
What Astrolune is, who builds it, and the rules the project holds itself to — stated where they can be checked.
Open source · pre-mainnet
/ 01Mission
A network nobody must trust blindly
The two dominant ways to secure a chain both sell influence — Proof of Work prices it in hardware, Proof of Stake in capital. Astrolune exists to remove that market entirely: weight comes from time spent behaving honestly and from a trust graph built out of recorded facts. Nothing on the input list is purchasable, which is the whole point.
That claim is kept narrow on purpose. What is proven is labelled proven; what is argued is labelled argued; what is open stays open in writing. A consensus that oversells itself is just marketing with a ledger.
OPEN SOURCE
100%
Consensus core, tooling and this site — one public tree.
TEST ASSERTIONS
~29,800
Over the consensus arithmetic alone, all clock-free.
SPEC DOCUMENTS
24
Every layer documented; gaps recorded as gaps.
PURCHASABLE WEIGHT
0
No hashrate, no stake, no delegation market.
/ 02Principles
Four rules, held in public
These are not values on a wall — each one changes what the repository accepts and rejects.
OPENNESS
Everything readable, nothing hidden
The specification is generated from the same tree the core builds against. Decisions land in writing where they can be linked, quoted and disagreed with.
CRAFT
Mechanics over discipline
Rules that depend on memory get broken. Layering is enforced as link edges, boundary rules as compile errors — the build rejects what a tired reviewer would miss.
ACCESS
No capital gate
Every level of participation is reached by running the client and behaving well. There is nothing to buy at any step, and the design treats that as a requirement rather than a discount.
/ 03How we work
Small team, long horizons
Astrolune is built by a small distributed group of engineers who would rather ship less and document it than ship more and explain later. The pace follows from the constraint that every layer must stay reproducible — a speed-up that costs determinism is a regression here.
- Development model
- Public code, public specification, decisions recorded in the open. The roadmap carries real statuses because pretending otherwise helps nobody.
- Review
- Every change is read by someone who did not write it — and the rules most often forgotten are enforced by the compiler, so some reviews cannot be slept through.
- Testing
- Pure functions exercised by ~29,800 assertions over the consensus arithmetic. Where coverage is thin, the documentation says so out loud.
- Documentation
- Generated against the same source the core builds with. Where a header and a document disagree, the header wins and the divergence is listed.
/ 04People
Three habits that define the work
No headcount page with stock photos. The culture is easier to describe as habits the repository enforces:
01
Docs land with code
A merge without its documentation update is not done. The spec travels with the tree, so it cannot rot quietly in a wiki.
02
Review like an adversary
Reviewers are expected to attack a change, not to be polite about it. The trust graph gets the same treatment from research.
03
Reproducible or it did not happen
Numbers come from height-derived protocol days, not wall clocks. If a result cannot be re-derived by a stranger, it does not go in the docs.
GET INVOLVED
Read the source. Then change it.
The fastest way in is the issue tracker and the dev chat. Good first contributions are documentation fixes — they teach the tree faster than any tour.