Extension Submission Guidelines

HIRMOS is building a curated marketplace for compatible extensions, workflow packages, stack guidance, design resources, and supporting tools for orchestrated AI software engineering.

All submitted extensions are reviewed before publication. Creating a vendor account or submitting a product does not guarantee approval.

What vendors can submit

Vendors may submit products that extend, support, or improve HIRMOS workflows, including:

• Lifecycle workflow extensions
• Extensions that integrate with existing HIRMOS entrypoints, hooks, or extension surfaces
• Stack-specific guidance, standards, templates, or validation packages
• Design packs, presentation resources, prototype ingestion helpers, solution brief formats, or reporting templates
• Documentation, packaging, or workflow resources that make HIRMOS easier to apply in real projects

Submissions should be useful to software teams and grounded in a clear HIRMOS use case.

Required submission materials

Each submission should include:

• Extension name
• Version number
• Short product description
• Full product description
• Downloadable package, if applicable
• README or usage instructions
• Compatibility notes
• Changelog, if applicable
• Product images or screenshots, if relevant
• Vendor support process or support contact method
• Pricing and subscription information, if applicable

Incomplete submissions may be returned for revision.

Compatibility expectations

Vendors should clearly explain where the extension fits inside HIRMOS.

A strong submission should identify:

• Which HIRMOS version or version range it supports
• Whether it depends on another extension
• Whether it provides a runnable workflow, hook integration, stack package, design resource, or support package
• What files, folders, artifacts, or outputs users should expect
• Any known limitations or setup requirements

Compatibility claims must be accurate and should not overstate what the extension does.

Review process

HIRMOS may review submissions for:

• Marketplace fit
• Product clarity
• Compatibility claims
• Package completeness
• Security or trust concerns
• Support expectations
• Pricing/subscription clarity
• Documentation quality
• Whether the listing could confuse customers

HIRMOS may inspect submitted packages for obvious packaging issues, unsafe files, misleading contents, missing documentation, or files that do not match the submitted listing.

HIRMOS may approve, reject, request changes, or defer a submission.

Updates and replacement packages

Vendors are responsible for maintaining their listings and packages.

Updates may require review before publication, especially when they change:

• Package contents
• Compatibility
• Pricing
• Subscription behavior
• Product claims
• Customer-facing documentation
• Support expectations

Do not replace downloadable files with materially different packages without updating the listing and changelog.

Vendor responsibilities

Vendors are responsible for:

• Keeping descriptions, screenshots, and package contents accurate
• Documenting compatibility with HIRMOS versions, stacks, or related extensions
• Providing clear usage instructions or a README
• Supporting customers for product-specific questions
• Submitting meaningful updates when packages change
• Following marketplace review, refund, and listing rules

HIRMOS handles marketplace-level questions and escalation concerns. Product-specific support belongs to the vendor.

Free, paid, and subscription extensions

HIRMOS may support free, paid, and subscription-based listings.

Paid and subscription products may be subject to:

• Marketplace commission
• Payment processing fees
• Refunds
• Chargebacks
• Taxes
• Payout timing rules
• Vendor eligibility requirements

Final payout and commission details should be reviewed before a listing is approved for sale.

Payments, fees, and payouts

Paid marketplace listings may be subject to marketplace commissions, Stripe/payment processing fees, refunds, chargebacks, taxes, and payout timing rules. Vendors are responsible for reviewing payout terms before a paid listing is approved. HIRMOS may require additional review for vendors, countries, or payout configurations that depend on Stripe Express/Connect availability.

Grounds for rejection or removal

HIRMOS may reject or remove listings that are incomplete, misleading, incompatible, unsupported, unsafe, low quality, or outside the marketplace’s purpose.

HIRMOS may also remove or pause listings if vendor support, package quality, payment status, or customer trust issues create marketplace risk.

Before submitting

Before submitting, make sure your extension answers these questions clearly:

• What does it do?
• Who is it for?
• Where does it fit inside HIRMOS?
• What does the customer receive?
• What versions or dependencies does it support?
• How does the customer use it?
• How will support be handled?