Here we will cover milestones, security work, governance decisions, and any material shifts in strategy, parameters, or economics.

CLUE is being built as long-term infrastructure. That means prioritizing verifiable progress over noise: what changed, why it changed, and what it implies for the protocol’s direction. When decisions affect core mechanics or incentives, we’ll explain the reasoning and the tradeoffs.

Our goal is simple: build with transparency as a default. If something meaningfully changes, it will be documented here — publicly, consistently, and with enough context for builders, contributors, and stakeholders to track the protocol’s trajectory over time.

This release explains how the protocol works in practical terms: assumptions, invariants, and mechanism behavior are documented so they can be reviewed, discussed, and improved.

In v1.0.0, readers will find:

• System architecture: the roles of core components and their interaction boundaries.
• Market lifecycle mechanics: creation, participation, resolution, and dispute/arbitration flow.
• Economic model: incentive alignment, staking assumptions, and value-flow rationale.
• Governance model: decision rights, upgrade path, and accountability constraints.
• Risk model: key failure modes, safeguards, and mitigation priorities.

The document is simple and readable: each section explains what the mechanism does, why it exists, and which tradeoffs it introduces.

This is the first version, not the final one. Next revisions will be versioned and published with clear diffs, so changes in assumptions, parameters, and governance logic are easy to track.