Skip to content
Select Language

Apply with your experience. Agree rights before sharing work.

Our Privacy Policy, Website Terms and Applicant & Submission Terms are prepared for counsel review. For now, send a nonconfidential skills and interest summary. Please do not submit original code, designs, invention details or proprietary proposals before a separate contribution agreement is approved and signed.

HartBeat intends to own the rights expressly transferred in a signed contribution assignment, including agreed use if a contributor is not hired. Applying does not itself transfer your résumé, portfolio or work, and no draft changes earlier submissions. Identity is not published without separate permission; necessary providers and lawful disclosures are addressed in the privacy notice.

Crypto · U.S. markets · AI stocks ↗
Top news
Read market news on TradingView ↗
Appearance

Build the principles into the work.

Before proposing a contribution, read the Architect Charter. Explain who your change helps, foreseeable risks, required permissions, how it will be tested and how failures can be corrected. When serious risks remain unresolved, pause the work, seek qualified human guidance, and proceed only when those risks have been responsibly addressed.

Read the Ten Commandments and our Charter →

Build a reusable capability around a business problem.

A useful capability begins with a clear business problem, defined inputs and an outcome someone can verify. Build reusable Skills, connectors and Mission Packs on the common Beat framework.

Your build playbook

  1. Define the customer problem, inputs, expected output and acceptance criteria.
  2. Decide whether the contribution is a Skill, connector, Mission Pack, evaluation or shared-framework improvement.
  3. Agree ownership or licensing, scope, attribution, maintenance and compensation before original work begins.
  4. Use the common Beat contract and approved interfaces; declare tools, dependencies, data access and requested permissions.
  5. Test representative work and failure cases, including misleading input, denied access, cost limits and escalation.
  6. Package versioned evidence, supported model/runtime combinations, limitations and rollback instructions.
  7. Submit for review and address findings before acceptance or publication.
  8. Maintain the capability and repeat affected evaluations after changes.

For a future marketplace listing

Explain who the capability serves, what it does, what it requires and its limitations. Choose free, one-time or subscription pricing under the published marketplace terms. State compute requirements and charges separately from the capability or Mission Pack price.

Use test data and work you have the right to share. Your contribution agreement will define the rights in the designated work; a résumé or application is not an assignment of your intellectual property.

Discuss My Contribution Area