OPEN PRACTICE • REVIEWABLE CHANGES • SHARED LEARNING

Improve the platform with evidence, not just opinions.

Community members can contribute code, playbooks, practice rubrics, learning modules, evaluation datasets, connectors and documentation. Start with the user problem, make the change reviewable, and show how we will know it helped without creating avoidable risk.

CHOOSE A CONTRIBUTION PATH

What do you want to improve?

PROPOSESales playbook

A versioned, testable sales practice with evidence, steps, success signals, risks and human-review points.

  • Problem + target user
  • Evidence required
  • Measurable success/harm signals
  • Version + review points
Open proposal form
PROPOSEPractice / learning module

A realistic exercise or evidence task that helps people build capability rather than passively consume content.

  • Learning objective
  • Scenario/task
  • Transparent rubric
  • Evidence of skill
Open proposal form
PROPOSEConnector / integration

A scoped integration proposal for CRM, calendar, email, social or another authorized system.

  • User workflow
  • Permissions/scopes
  • Data minimization
  • Failure + revoke path
Open proposal form
PROPOSEDataset / evaluation set

Synthetic or lawfully sourced data used to test scoring, recommendations, safety or fairness.

  • Provenance
  • Allowed use
  • Sensitive-data review
  • Evaluation purpose
Open proposal form
PROPOSEFeature / product improvement

A user problem, workflow improvement or platform capability proposal with a measurable outcome.

  • User problem
  • Current workaround
  • Success metric
  • Privacy/security impact
Open proposal form
PROPOSEBug / reliability issue

A reproducible defect, regression, accessibility issue or confusing behaviour.

  • Steps to reproduce
  • Expected vs actual
  • Environment
  • No secrets/customer data
Open proposal form
MERGE GATES

What every material contribution should survive

1Explain it

A contributor should be able to state what the change does, who benefits, what inputs it needs and where it can fail.

2Test it

Material behaviour needs a deterministic test, evaluation set, rubric, smoke test or other reproducible check appropriate to the feature.

3Protect people

Do not commit customer confidential data, credentials or unnecessary personal information. Document permissions, retention and human control.

4Document it

Changed behaviour, schemas, evaluation rules and operational requirements must be reflected in the repository documentation.

5Pass CI

Pull requests must pass TypeScript checking and the production Next.js build before merge.

START SMALL

A good first contribution

You do not need to redesign the platform. Useful first contributions include improving one confusing sentence, adding an ambiguous practice scenario, documenting a failure case, expanding a lawful synthetic evaluation set, or proposing a measurable local sales/community workflow.

Do not submit: passwords, API keys, production exports, customer conversations, private personal details, scraped datasets without rights, fabricated performance claims, or AI features with no documented human-control/fallback path.
COMMUNITY GOVERNANCE

Open source should make the reasoning visible.

A contribution can be clever and still be unsafe or unhelpful. The platform favors changes that are understandable, testable, reversible, documented and respectful of user data. Maintainers should explain why material changes are accepted, changed or declined.