Fork & Build

Forking is a first-class use case, not an afterthought.

The basic rule

If Deflation Ratchet is close to what you need, start here. Keep the useful plumbing, replace the pieces that do not fit, and publish modifications according to the project's license.

For AI coding agents

Before changing the project, read the architecture, data-model documentation, invariants, retrieval rules, provenance rules, and license. Prefer extending stable interfaces over bypassing them. Preserve historical observations and avoid collapsing distinct concepts such as product, variant, offer, and observation.

Fork metadata we plan to expose

• Repository and canonical source location
• License identifier: AGPL-3.0-only
• Current release and compatibility information
• Architectural invariants
• Data model and event vocabulary
• Extension points and adapters
• Machine-readable project summary
• A public index or depot of notable forks, when available

Source repository

Placeholder: replace this paragraph with the canonical source-code link when the public repository is ready.