Add Refix — growth autopilot for product experiments, SEO, content, and ads

[christiina02]

Summary

Adds Refix to this list under the growth / domain-tools section.

Entry

New project in data/projects.json (id refix, category domain-tools):

• Refix (refixai) · https://github.com/refixai/proactivity-sdk · TypeScript · Apache-2.0 · 12 stars at capture
• Summary (en): Refix is a growth product that runs product experiments, SEO, content, and ads, with a public framework-agnostic proactivity SDK.
• Bounded decision (en): Scores and routes bounded growth actions across product experiments, SEO, content, and ads before the consuming workflow runs them.
• Evidence reviewed: https://github.com/refixai/proactivity-sdk/blob/d0ec87795799e287bb6b29c573e693bf0848b0d8/src/core/governance.ts
• Scenario: added a membership reference to filter-content in data/scenarios.json (en/zh/ja).

Why it fits

Refix uses TypeSafe Jev for typed/bounded growth decisions (Choice / Score) across product experiments, SEO, content, and ads. Jev decides / scores / routes; it does not write campaign copy and is not a claim that Jev alone improves rankings. The catalogue entry points at Refix's public framework-agnostic proactivity-sdk as the nearest inspectable artifact for the governance/gating layer.

Evidence limitation (please read)

Refix's production Jev integration is not publicly inspectable: there is no public commit in a Refix repository that shows the Jev client calls for the hosted growth product. The best available public evidence is the refixai/proactivity-sdk repository (Apache-2.0, TypeScript), whose governance/dispatch code is the closest open-source artifact for the bounded-decision execution step. The live product is at https://refix.ai. I can provide deeper source links on request.

Because of this, the entry is below this repository's 50-star policy floor (the public repo currently has 12 stars), and npm test reports catalogue metadata is explicit failing on the hardcoded catalogue count (184 vs 183). I left the validation test untouched rather than weaken the star-floor guardrail; happy to adjust if you want the entry to remain in the catalogue as an explicit exception or to hold until a public integration commit exists.

Checklist

• Followed the repository's CONTRIBUTING rules where possible (documented deviation above)
• Added the entry in the correct section/position and curated scenario membership
• Regenerated README navigation with npm run catalog:readmes
• Disclosed affiliation

Disclosure

Affiliation: Refix. Built with TypeSafe Jev. This PR was prepared with AI assistance.